Sage 100

I know about issues with running MAS 200 as a service. Anybody have suggestions for why the Providex IO Service would hang up about once a week? MAS 200 4.30.0.21.

Have you applied the SS-3003 patch Jim

When they report it to you, is there a larger number of people concurrently printing Crystal forms / reports than on other days when it doesn't hang? I know of 2 reasons: 1. Runaway reports / queries running at same time: Have a client who I setup FRx to run with a DSN configured for CS ODBC. No problems there but when they do their 10 different variations of financials along with Sales running several heavy duty reports at same time, this happens once in a while. We're talking about only 5 users here but 10 - 20 reports / queries running at same time. 2. Encroaching 15 user CS ODBC limit: Roughly how many people have you turned it on for in User Maint / Prefs? Better question is of that number what's the max number of people that could be printing concurrently? As you know CS ODBC Driver is only 15 users (4.40 and less) and have heard this with those encroaching 15. I wish there was a command I could run to know how many available license slots there are at any time (for all I know it could be counting licenses by number of concurrent connections to the ProvideX IO service not actual number of unique users)

It has to be the number of licenses that's the issue. It locks the service up. I try to restart it and it hangs starting back up. We reboot the server to resolve the issue.

Are they using any boi scripts. Those take up users too.

Yup! Today specifically, I think there were several people doing their end of day reports at the same time.

I never knew about the CS ODBC restriction - does that count people printing canned reports + registers as well as custom created Crystal?

What is the limit on 4.5 and higher?

It would be on any ODBC interaction including canned reports. Allegedly the limit in 4.50 is 50 users, I believe.

Nice ""how to"" - probably created by Alnoor but good step by step for setting this up - http://infosource.sagesoftwareonline.com/sw_attach/sw_long_desc/sage/mmd/sage%20mas%2090%20and%20200/assets/Remote%20Printing%20CS%20ODBC%20for%20MAS%20200[Easy].pdf

Updated Evernote - nice instructions and overall info

@WayneSchulz Your link to the infosource post doesn't work.

I think this is the same. Does this one work? http://infosource.sagesoftwareonline.com/sw_attach/sw_long_desc/sage/mmd/sage%20mas%2090%20and%20200/assets/Remote%20Printing%20CS%20ODBC%20for%20MAS%20200Easy.pdf

Nope. It does from here: http://www.s-consult.com/2012/07/17/how-to-setup-odbc-cs-client-server-for-sage-100-erp-advanced-formerly-mas-200/

@WayneSchulz the link doesn't recognize the [Easy].pdf at the end.

Sorry - yes that looks like Socialcast may have broken the link

Something about the [ ] seems to be confusing Try this: https://www.dropbox.com/s/ot7b97sifjsyps0/Remote%20Printing%20CS%20ODBC%20for%20Sage%20100%20Advanced.pdf

That one works. Thanks @WayneSchulz!

Thanks Wayne.

We have a client who had regular problems on 4.30 with CS ODBC. One of the solutions they came up with was a script file to stop / restart the service every 30 minutes. The interesting thing is that when they moved to 4.5, the CS ODBC was slower than local for all LAN connected users. They have greatly reduced the number of people using the CS ODBC now.

Erik Kaas on the Linkedin Sage 100 group has stated the capacity for the C/S ODBC goes up to 50 in Sage 100 2013. I'm not sure if that implies it is still 15 in 4.5? #fwiw

It's still 15 in 4.3. I'm testing something. I'll post it when I find out if it resolved the issue. That's interesting @ClarkWallister. The CS ODBC driver makes a huge difference. If they had to roll back to the non CS driver, I may get lynched.

Isn't there a way to prioritize the service processing. If so, maybe moving it higher on the processing totem pole would make a difference.

@RobertWood I'm running into the same problems that you mention at the start of this old post. My client is Sage 100 Advanced and they are on version 2014. They can have 10-15 users at a time printing something in Crystal, but not every user has the C/S ODBC Driver checked on in their User setup. In fact only about 5 people do. ls there any resolution to this problem or is the only resolution to create a "".bat"" file that contains ""net stop PVXIOSVR"" and then ""net start PVXIOSVR"" and assign this "".bat"" file to a task scheduler trigger set to run often - I saw this in Sage City and they said to run this batch file every 30 minutes. I just don't understand why this alleged great feature is such a PITA. Is there any more news on this since 2012? I've googled and found only what I just mentioned in Sage City. Also, why would my client have both Sage running as a Service and the Application Server running - shouldn't only the Service be running if that's how we want them to run? I don't know who or how the App Server gets started to run.

We switched them to just running the application server. They stop and restart it twice a week.

I had the same problem in the same environment due to a script opening up too many ADO.Connection objects. Caused the pvxiosvr.exe service to hog up all the memory. Odd thing was, script closing the object did not release all the memory... eventually the server started having the same problems you report. I wrote a utility to figure out how much memory the service was using and stop and start when a threshold was reached. Fired it up out of the task scheduler ... this worked well, but was a band aid until I figured out about the connection objects.... @RobertWood you got any connection objects going on?

@RandyMarion Just SQL linked servers that they use for some reporting.

You could be exhausting the heap which is causing the service to fail. Try increasing the heap size. https://support.microsoft.com/en-us/kb/184802