Sage 100

Client running 200 V4.3, SU about # 10 or so. Everytime I log into their server via TS, I get numerous errors per the attached. Does anyone know what is causing this and what the tweak is. 200 is running as a service.

Does this happen right away? If not right away (upon login) - what are you doing when it errors. Also, by the title of the icon does it imply you have third party software installed? Can that be ruled out (mis-matched version, etc) as the cause?

I've experienced this, too. Check the Spawn Tasks from Application Server in User Maintenance. I think these errors are bad sessions. They are intended to interact with the desktop and are waiting for someone to log in to show the error message. That's perhaps why your seeing them when you log in.But that's just my guess.

@Wayne - As soon as I make a TS connection at the server, the messages start popping. @Bill, I'll take a look later today.

Bill - is the spawn task field supposed to be off or on? And should I check the MAS 200 setting to be sure this is set correctly for future users?

I was told to turn it on if you experience problems with orphaned sessions because of dropped conections. Help says ""Select this check box to launch tasks through the Application Server, which provides a stable connection between the Sage ERP MAS 200 server and workstation. Clear this check box to bypass the Application Server when launching tasks, which allows faster processing.

I have the same issue with a MAS500 client. several of those will pop up when logging into terminal server. with admin rights. the regular users don't receiver those.

I been running into this with MAS 90 clients running using terminal services/remote desktop. I've found no cause or solution.

@JeffSchwenk You say ""as soon as I make a TS connection .... the messages start popping"" -- do you mean as soon as you make the connection AND click to start MAS200? Or are you setting up MAS 200 somehow to log in automatically to the TS ? I'm assuming you are following a two step process (which is how I've done it) -- and not embedding an icon on your desktop that somehow when clicked launches MAS200 in a TS session.

TS is at the MAS server. As soon as I get the desktop, the messages start popping. As soon as I clear them, I click on the desktop icon to start my MAS 200 session.

I have seen these messages when a user has a crash in MAS 200; it reflects on the server.

The messages are not popping because of your TS connection - they were already there but ""unacknowledged"" until you clicked on them. They are caused by some type of MAS user crash. Common reason in TS/Citrix is a remote user went to print S/O form but hung because last person who used same form code well their printer (the properties of which) is inaccessible by remote user. So hanging or similar occurs on client side (TS session) and ""Mas has encountered"" error occurs on the server in Application log of Event Viewer. It also appears on server's screen but not until the 1st user who logs on directly to the server's desktop (Jeff S). It's the situation that requires either having separate form codes for each user or clicking checkbox to ""Use Workstation Default Printer for Standard Form Code"".

Great info Alnoor - and poor Sage has never quite gotten printer management down. This type printer issue is especially annoying in 10+ user sites with heavy sales order use ( aka Sage's supposed sweet spot ). They can't error trap ?