Sage 100

 View Only
Expand all | Collapse all

Getting the infamous sy_workstation.m4t error on a

Jeff Schwenk

Jeff Schwenk05-11-2012 12:55

  • 1.  Getting the infamous sy_workstation.m4t error on a

    Posted 05-09-2012 11:23
    Getting the infamous sy_workstation.m4t error on a v4.4.8 installation of MAS 90. Renamed the file last night. Error just raised its ugly head again. Have not tried renaming the other files that @BrettZimmerman suggested a while back. Any other hot fixes that one is aware of?


  • 2.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-09-2012 11:29
    What's the infamous error? Could this be related to the customer not logging off the network?


  • 3.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-09-2012 11:39
    I've had a spate of those lately, as well as the ModuleDate file (which I think Harold had recently). Two different versions, though, so can't point to anything specific. Just renamed the file and moved on and so far it hasn't come back,


  • 4.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-09-2012 11:40
    I guess we're now guessing at the error message? you guys are worse that my customers.


  • 5.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-09-2012 12:05
    sy_workstation.m4t not found. Still trying to get client to give me an error number.........


  • 6.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-09-2012 12:46
    Look in the MAS 90 / 200 community forum and search for SY_Workstation.M4t. There is a lot of discussion about this error.


  • 7.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-11-2012 07:15
    Client can't even get the info button to display. Have connected with them twice and every time we click on the info button, nothing happens. Very difficult to trouble shoot. Client has old and slow server with a 10 gb C drive that has about 5% available space. Looking at ways to free up additional space.


  • 8.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-11-2012 10:20
    It's not worth the headache to deal with those older servers. Time for a hardware upgrade if you ask me.


  • 9.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-11-2012 10:50
    Word from the client is that they are in the discussion stages (finally) of getting a new server. Not sure when though. It is frustrating to have the IT ""guru"" that it is a MAS issue...........


  • 10.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-11-2012 11:31
    even if it is a ""MAS Issue"" you can't fix it without adequate disk space. Hopefully any IT ""guru"" ought to agree with that.


  • 11.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-11-2012 12:23
    He'd better since he will be the one getting the sale..............


  • 12.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-11-2012 12:35
    I apppied the hot fix at one client and they still get the error about every other week. Other clients have never had this issue. It seems that larger systems are more susceptible to this issue.


  • 13.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-11-2012 12:55
    Which Hot Fix are you referring to?


  • 14.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-15-2012 06:00
    Moved their MAS folder from the system drive to a secondary drive with plenty of free space. Network drive now has 25% free space which should be adequate to manage system functions. After moving the folder, I migrated them to v4.5.3. All was quiet yesterday. Today, the errors (various file not found messages) came back. When clicking on the information button, the panel just disappears. Several users have commented that just prior to the MAS error, they get a Windows notification that the network connection was lost. To me, this would lead one to think that their switch is the issue. They are also running Symantec End Point AV. It appears that they have excluded the MAS extensions, but they are running the heuristic monitoring. Since Symantec has been running for a while, don't think that is the immediate issue. Thoughts?


  • 15.  RE: Getting the infamous sy_workstation.m4t error on a

    Posted 05-15-2012 06:10
    For AV configuration I have the whole MAS90 folder and all subfolders excluded. I believe the risk of not monitoring the folder is less that the risk of problems due to AV scanning.