Sage 100

New MAS 90 4.4 PU2 on Windows 7 Workstation - sporadically reciving an error ""File s:\Sage\Version440\MAS90\MAS_SYSTEM\SY_Workstation.M4T"" not found. This seems to occur mostly when exiting MAS. Occurs across a range of computers (new network and PCS). My gut says Malware protection or AV issue however I'm trying to rule out MAS as the culprit. Unfortunately the client only uses MAS90 on the workstation and very little else.

And Sage suggests that it is AV settings -- which I told the client and their IT staff from the first time I saw the issue: http://infosource.sagesoftwareonline.com/infasp/kdb.asp?isresolutionconceptid=502653#

Look at this link. I have the same problem with my set up. http://community.sagemas.com/t5/Technical-and-Installation/SY-Workstation-M4T-not-found/td-p/26166 Just haven't had time to troubleshoot. I just rdp to the server and run MAS from there. MAS 200 install runs fine in WIN 7.

disable Shadow copy on your MAS Drive. I think you refered to it as restore point. If MAS is open while this is running and shadow copy hits the SY_Workstation.M4T, it will temporarily lock the file then when mas tries to update the file from the workstation it will not have access. Second Opurtunistic file locking needs to be disabled on the server.

Some chit chat about: ""10 hours is the default time that a kerberos ticket is issued for in a windows Active Directory network. That glitch is not the network dropping, but is the server replying with an explicit access denied to the client because the ticket is expired. The client automatically requests a renewal of the ticket, which is granted, so for most network activities, you never ""see"" that renegotiation. A network application *should* be able to anticipate and accommodate this as this is standard practice in any network. If, however, this is a non-network app that has been forced into a networked situation, you'll want to consider setting up a terminal server instead."" However I'm not sold that this is the problem. The person in the forum seemed to be chasing more of a network issue. I have NON-MAS users on the same network and they don't report lockups