Sage 100

EAccess violation pvxio.dll"" Has anyone ever had to troubleshoot pvxio.dll errors? I have a customer that is getting these in P/O entry and S/O entry randomly. Sage has an article on pvxio.dll and indicates it's a memory issue on the server. Everything I've looked at online indicates that EAccess violation means a memory error. But, they don't get this error with ANY program except for MAS 200. They are running MAS 200 as an application, not service, and are on PU5 4.40. We have tried turning off DEP for pvxwin32.exe and that didn't work. We are next going to try turning off DEP except for essential Windows services. I did check the printer list and everything appears to say ""ready"" so no invalid printers. The error can occur when other users are in the system, if there's only one user in, and also occurs in the test company besides the live company.

Seen it but don't remember any specifics. I'd be looking at the usual suspects for these types of things - anti-virus, malware, user rights, invalid printers. Someone on another forum reported seeing it a Citrix/TS environment - http://goo.gl/lz6xk

pvxio.dll"" errors are usually the end-result of a previous error in a chain of errors. I get them when debugging and exiting task ""improperly"". Is there a pattern related to it occurring when leaving data entry screens idle for awhile (e.g. went to lunch or meeting)? If so, look for common culprits that cause temporary designed network disconnects (short DHCP lease duration, Power settings set to ""turn off"" HD after x minutes, etc) and check for Auto Logoff enabled as well. I hear it doesn't work properly 100% of the time (again) but that applying fix from Res ID 534330 seems to be helping with that.

No anti-virus on the server.

Auto-logoff is not turned on. ""Spawn tasks"" is turned on. On the app config, ""keep alives"" is off, ""reconnect"" is set to none. There isn't anything noted in the activity log when the error occurs. We checked the logs under the _appserv directory and they did not seem to be helpful. We did apply the patch from the RES ID you mentioned and it did not help.

We did find something on the server showing bad device drivers -- some device in the device manager. I'm having the company's IT get that fixed and let me know. We had also tried the DEP setting for essential Windows services and rebooted the server and that didn't work either.

Did you rule out the common network disconnect causes - short DHCP lease duration and Power settings. I still run into short DHCP issue. E.g. At wkstn type ipconfig /all and let's say at bottom you see difference between Lease Obtained and Lease Expires is 12 hrs. This means in 6 hrs a designed disconnect (renewal packet) will occur and anybody in MAS would be impacted.

We did change the power setting and that had no effect. We checked that on both the workstation and the server and made sure both were OFF. However, this can happen right after it works just fine. For example we were in S/O entry today. We made a change to the S/O, Accepted it, then went back into the S/O and clicked on the lines tab. We were not able to get into the lines tab and on the server ""MAS has encountered an error"" was up. When we closed out of that, then the pvxio.dll error came up. As soon as we closed out of the error on the server, the workstation freeze up went away and the S/O screen closed out.

I see. Maybe have 1 user start up MAS 200 in MAS 90 style and run that way for a few hours. Hopefully you will get a non-cryptic error.