Sage 100

 View Only
  • 1.  Sage 100 Advanced 2013 PU3. One user gets knocked

    Posted 06-11-2014 09:12
    Sage 100 Advanced 2013 PU3. One user gets knocked out of Sage when switching companies. Happens multiple times a day, but not every time & not every day. Once in awhile happens when opening another task. I saw an older post talking about something similar, but no resolution.


  • 2.  RE: Sage 100 Advanced 2013 PU3. One user gets knocked

    Posted 06-11-2014 10:27
    I know I've seen that years ago but I don't recall the resolution. Maybe something to do with assigning a new Terminal ID (TID) to the workstation - but obviously that applies to much older versions. Might be worth a shot to have Sage 100 re-create a new sy_workstation.m4t and sy_console.m4t - by renaming them and then logging in.


  • 3.  RE: Sage 100 Advanced 2013 PU3. One user gets knocked

    Posted 06-11-2014 13:27
    There was an issue present in 410 relating to MAS truncating the TID/Workstation Name. the resolution was to use a more unique name or TID. This issue however was not related to switching companies or tasks. The issue then was upon user logging out for the day causing another users MAS session to shut down. This wouldn't be the issue you are having since users can have multiple tasks open and in various companies at the same time. I can't see switching tasks or companies being treated as or causing a shut down I would start with a review of the system activity log to see if any errors are being captured when the issue occurs. If nothing there would review the share point for renamed or copied files that are being stored within the share point to MAS, especially system files or folders. Copies of and renamed files/folders should be stored outside of the share Avoid using renaming structures like .soa.old or .m4t.old . Instead remove the extension value and/or replace it. Same goes for a OldMAS90 or MAS90.old. From there go to running the Embedded IO Replacement script for module code L/M. Advance system so the Spawn Tasjk feature has potential to cause issue. See KB 110-534911 (https://partners.sagenorthamerica.com/irj/go/km/docs/sageKM/Sage%20MAS%2090%20and%20200/Gated%20Customers/Warr_Svc_Support%20Plan/534911.html) If still unresolved - Open Case with Sage Support.


  • 4.  RE: Sage 100 Advanced 2013 PU3. One user gets knocked

    Posted 06-11-2014 14:12
    Any error message - and if so what's the message?


  • 5.  RE: Sage 100 Advanced 2013 PU3. One user gets knocked

    Posted 06-12-2014 06:56
    No error messages & nothing in the Activity Log. I can see where her user successfully logs in 4 times in a day, but nothing in between each one.


  • 6.  RE: Sage 100 Advanced 2013 PU3. One user gets knocked

    Posted 06-12-2014 07:48
    Have you tried renaming the sy_workststion.m4t?