Sage 100

CS ODBC application optimization question Our customer has about 25 users, some remote, and they use the CS ODBC for most users. About once per week the CS ODBC application gets flaky and has to be restarted. Sometimes the server needs to be restarted to clear everything out. The IT manager would like to have 100% up time on it. And it does impact operations because people start running reports,then everything cascades and Sage locks up. Is there any information how to optimize the CS ODBC application?

Sorry sb 4.3

Same situation on 4.4

I've had this problem too. There's 2 ways I've dealt with it: 1) Windows Task Scheduler job to stop and restart ProvideX IO service every night. IOW I had just given up on troubleshooting. This client had to reboot their server a bunch too because pvxiosvr.exe had excessive memory usage when too many people running heavy duty reports. Personally I think CS ODBC driver has a memory leak (at least from v4.50 downward) when user cancels their report or force closes down the report window. 2) On their Server 2008 R2 they had DEP setting to ""Turn on DEP for all programs and services"". They didn't let me change it to ""Turn on DEP for essential Windows programs and services only"". Ergo I added and exceptions for pvxiosvr.exe and while I was at it also exclusions for: pvxwin32.exe launch32.exe masapsvr.exe (in \home\lib\_appserv) And since there was a single TS with 25 users going into it to run MAS (holy carp!!) added DEP exceptions there as well to point to client-side pvxwin32.exe and launch32.exe