Sage 100

Connectivity issues? I'm tearing my hair out and the client is about to start doing it for me! We have been battling an issue for several weeks now. New install - Sage100 Advanced version 2013 sp3. We just installed SP4 last night but I'm not sure it will make a difference. no modifications except custom office Users were experiencing a pop up message ""WindX Client Connection - Re-Connect Your connection to the server ""ServerName"" was severed while running the application ""MAS 200"". Your session has been Re-Connected. Click the OK Button to Proceed."" Contacted Sage, they told us to change the setting in the application configuration on the 'Clients' tab - change the Re-connect drop down box to ""none"". After we changed the Re-connect drop down box to none, now users just have windows randomly close without warning, error message, or anything. I've looked at the Sage log, server logs, term server logs and nothing shows there. We have worked extensively with the IT company that hosts their server and terminal server. There is NO Antivirus software on the server or term server (hard to believe but our IT staff verified this). Their IT staff put a monitor on the server and term server for 3 days and there were no dropped packets even though users were getting this message. Now we are getting an additional issue of crystal reports that seems to be connectivity issue also: I can run the same report 5 times and it might work all five times; or sometimes I might get the attached message Database ""Failed to retrieve data from the database. Details: [Database Vendor Code: 143] Failed to retrieve data from the database. This happens with a custom written crystal and a modified PO form - both take several seconds to generate the data before printing.

With respect to the Sage 100 issue: Is it being run as an application or service -- and how many users (above 20 can be instability city and may require tweaks).

Do you see any errors in the Activity log?

forgot to mention that! We started as a service - they only have a about 10 users but they do tend to open a lot of tasks (we have seen them open the same task several times even) - we switched to running it as an application 2 weeks ago and that did not help

nothing in the sage activity log - we expected error 86 but we are not seeing anything of the sort.

in the server event log we see a lot of group policy errors but the IT staff says those are not an issue, plus they do not correspond to the times when people are getting disconnected. I should also note that they are not booted out of Sage100, the screen just closes (for instance sales order entry - sometimes the data is saved, sometimes not, sometimes we end up with a corrupted record.

WAG - any chance that you have a default printer on the server which is disconnected? I had a similar issue with a customer a day or two ago. Slightly different error. On the server console they were seeing small boxes where the title bar was ""WINDX .."" then the message was (on console) ""Connection failure for port xxxxxx"".

Good idea, I had not checked that - we did make all users turn off their redirected printers several days ago. I checked the server it has 2 SAGE PDF converters listed (exact same name) one is offline one is active the active one is the default, at least I have something to go back to the IT staff with. I'll ask them about why we have two printers with the same name. (neither is listed as ""redirected"" ) I"" not sure if it is the root cause but at this point I'm scratching my head anyway.

If you are running as a service you need to use the RegEdit to bump up memory and it will be resolved. I will try to find the document. This goes back to like 2009.

Here it is.

May be obvious but are the users set to auto logoff (users/preferences)? Also, had a similar issue, here's the thread https://90minds-com.socialcast.com/messages/13870769

no auto log off - but I'm willing to listen to even the obvious - sometimes we get too close to the forest to see the trees. They are no longer running as a service. I wonder if changing the registry might help anyway?

the registry setting for running as a service can be found on Sage KB - search 'Cannot Create A New Session with a Large Number of users' - follow the instructions - reboot server after. Also the account used to start the Sage 100 service must be a domain account with full control to the MAS90 folder - never use the default 'local service'. However if getting the same error running as an application, registry setting would not help - it would be a connectivity issue - something is breaking network connectivity between server and terminal server. Try disabling Data Execution Prevention (DEP) on the main server and the terminal server - IT staff should be able do this.

I tried turning off DEP for the PVXWIN32.exe program and I get a message that This program must run with data execution protection (DEP) enabled. do we need to turn it off for all programs? or am I pointing to the wrong executable?

what is the server operating system?

Windows 2012 Standard

if DEP is set to 'turn on for all except those I select' then add pvxwin32.exe and launch32.exe; If it is set to 'turn on for essential windows programs' only - then it is 'disabled' - always reboot server after changing these settings, even if it doesn't prompt you to. Also configure the servers windows firewall - don't disable it or turn it off - just configure Firewall state On, Inbound connections Allow for Domain Profile and Private Profile.

Is this a wireless computer. If so wire it in and try

@DavidOverholt did you get your problems resolved? Just curious...

We have not yet resolved this the disconnection issue between the TS and Server are still happening and users were randomly dropping tasks until I turned the application server setting for re-connection back to Automatic. Then they again started getting the message that there was a disconnect and it has been re-connected. I recently changed that to ""Hidden"" so the users are not seeing anything, and essentially that has made them happy but it scares the heck out of me until we get this resolved. The crystal error is totally random and appears to be related to the disconnect. I can run the same report over and over and sometimes it works and sometimes it errors out. Still in all of this, there are no errors in Sage activity log, or in the server logs about dropped packets or anything. We did talk to a Sage rep yesterday that thinks she may have some ideas (related to the ping addresses and IP perhaps being dynamic on the server or TS). so I still have my fingers crossed that she will come up with something.