If you are using Sage Payments Service (aka SPS) and you’ve received a message similar to:

ALERT!

Automatic Settlement Failure: Tuesday, April 23, 2013-Action Recommended

On Tuesday, April 23, 2013 at approximately 11:00 pm EDT, Sage Payments identified a potential issue with automatic settlement. You may notice that your automatic settlement did not run on Tuesday, April 23, 2013 and you may still have transactions from April 22 and April 23 in your open batch. To prevent any delay in your funding, we recommend that you settle your batch manually.

This apparently is the result of a problem with the automatic batch settlement process at Sage Payments / SPS and it is affecting customers that are using the Virtual Terminal for processing.

The work around is for them to manually settle the batches.

 Auto-Batch Issue Alert!

Note: This message was reportedly received by at least one customer on April 24, 2013. By the time you read this the situation may be resolved but we’ve posted this here just

Many states are now requiring electronic filing of payroll taxes. Did you know that Sage offeres electronic eFiling as part of the Sage 100 ERP system?

Streamline your tax reporting process with Sage 100 ERP Federal and State eFiling and Reporting. Eliminate manual for creation and save time by choosing from over 250 federal and state forms for Unemployment, Withholdings, New Hire Reports, W-2, W3 and 1099.

Live Webinar: Learn How To Save Time & eFile Employee Forms with Aatrix

Wednesday December 12, 2012 – 1 pm ET – register

Wednesday December 19, 2012 – 4 pm ET – register

Sage 100 ERP users may report they sporadically receive  an error message – SY_Workstation.M4T cannot be found. In some cases the user can enter through the error and proceed normally.

Resolution:

There are several possible resolutions for this Sage 100 ERP error  - all related to the network.

Antivirus may be scanning the SY_Workstation.M4T at the same time as the user is trying to access it (Recommended: Exclude the Sage files from scanning)

Opportunistic locking may be locking files on the server and workstation (see http://support.microsoft.com/kb/296264 for information on how to turn off opportunistic locking)

In at least one instance this problem has occurred because users were not logging out/into their Windows machines each day. When they left for the night they simply powered down their monitor and did not log out and subsequently when they came into the office they were not logging back in. You are most likely to see this in conjunction with some type of server upgrade and/or workstation upgrade to Windows 7. The solution was to have the user log out from their computer at night (Important: This means the PC logout not the Sage logout). The technical reason behind this appears to be related to Kerberos and there is a lengthy discussion on the Sage Community of others who had this issue:

http://community.sagemas.com/t5/Technical-and-Installation/SY-Workstation-M4T-not-found/td-p/26166

Why Does This Happen To Sage And Not Microsoft Office (or Other Apps?)

We frequently have customers ask why this issue only occurs with Sage and not other applications such as Microsoft Office. In most cases the reason that Sage is displaying an error and not Microsoft Office is because your Sage ERP system reads and writes constantly to the network whereas other applications may only do so when they are opening a new document or saving it.

Version(s):

3.x+

Problem / Description:

Unable to print this report while G/L transactions are being updated

Resolution:

1. File
2. Run
3. GLWSJA

Other Information (Links/Sage KB/Additional Tips):

Another user may be printing a General Ledger report or updating to General Ledger from another module. Wait until the other user is finished before proceeding. If the error persists perform the following:
4.0 or later:
Rerun Workstation Setup. For more information, see How to install Workstation Setup for Sage MAS 90 and 200.

If the error persists, have all users exit Sage MAS 90 or 200, and reboot the workstation and server (if necessary).

3.71 of and before:

Have all users exit Sage MAS 90 or 200 and run the GLWSJA program to clear any flags.

Note: Do not perform this procedure if any user is printing G/L reports or updating to G/L.

Verify that all users have closed Sage MAS 90 or 200.
1. From the Launcher, select File / Run.
2. Enter “GLWSJA” (without quotes) in the ‘Program Name’ field, and click ‘OK’.
3. Click ‘Yes’ to purge the update from SY0CTL.
4. If the error persists, manually delete the record from the SY0CTL file using Data File Display and Maintenance.
5. Note: The actual SY0CTL record being written has the key [ABCRPTTxx,] or [ABCUPDTxx] where ABC represents the company code, RPT indicates a G/L report is being printed or UPD indicates a journal/register is being updated to General Ledger and Txx indicates the workstation/terminal ID in its compressed form.
6. Open Library Master / Repair / Data File Display and Maintenance.
7. In the ‘File Name’ field, enter “SY0CTL.SOA” (without quotes).
8. Click the ‘Key Scan’ button, and select the record.
9. Click the ‘Delete’ button.