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.
