Sage 100

Customer upgraded from Sage 100 Advanced v4.5 to 2013. Significant issues with errors appearing on the console. Running as an application due to prior issues with hung users (40 user system). On 4.5 this was running smooth as silk. Now on Microsoft Windows 2008 R2 - about half the users are coming in via TS. Is there a best practices regarding these Sage PDF printers. I see a redirected Sage PDF printer and a local Sage PDF Printer. Which is the one that the TS users should be dealing with? Do I turn off the redirected? We continually are getting sporadic BEX type errors which pop up on the console. We've changed DEP settings to exclude Launch32 on the server and TS stations. Situations is soon going to become a big problem. Anyone have thoughts of steps that have worked to reduce or solve this? I called Sage and they were clueless.

I've always had issues with redirected printers, even with 100 Standard.

Here's a note I made - just additional info - explains a different way to set port for TS users - culled from SC prior message https://www.evernote.com/shard/s1/sh/fe6590c4-ae44-4a45-8aef-5a4b79e9fb52/9a4aa22bfe7e0c510a2204116803a910

The users on Sage 100 Advanced aren't getting errors on their end. What is happening is the error pops up on the console where the App is running. I seem to remember discussion(s) that this can happen if there is not a printer available which the workstation is calling for (or something similar). There is also some prior discussion around this whole BEX error issue which is what I'm really trying to cure. Unfortunately it's a 40 user site with users in different time zones and there's no luxury to bring the server down mid-day to spend an hour or two poking around. You have to tweak it at night. Hope and pray it's fixed for the next day. Then invariably you get the ""problem is back"". Very frustrating because 4.5 was running smooth as silk and we incorrectly assumed this was going to be a low impact upgrade.

In our experience, we have had issues with Sage 100 anytime the terminal server sees more than one copy of a given printer. For this reason, we use redirected printers for persons or offices that only make a single connection to Sage 100 on the TS. For offices that have multiple TS users, we inhibit all TS clients from sharing printers and put a queue for each of the office's printers directly on the Terminal Server. This has worked well for us. This does allow cross printing between those offices which so far, no one has seen as a problem and a couple saw as a benefit.

You need to remove all the redirected printers and then not allow redirected printers on the terminal server. If a printer is needed then as John said above you need to make it a network printer.

I presume that this works for the Sage PDF printer?

This is the recurring problem that is happening - Sage 100 Advanced ERP 2013 (Running as Application) - Microsoft 2008 R2

Customer says it's a mix of both TS and non-TS users where the error is being seen.

We have not had issues with redirected printers as long as they come from a single remote user. This is necessary for people who are connecting from hotels or customers offices. Mas has issues when it sees more than one copy of a printer which occurs when people in the same office share the same printer, or when one shares and the queue also exists on the Server. The PDF printer for TS users should be on the server and their shouldn't be a problem with redirected PDF printers as a TS client normally does not have a MAS client.

Continue to have significant issues. Sage's suggestion was to run as service. General consensus has been ""yeah Microsoft server 2008 is better you shouldn't have any problems"". We run as service and it throws the infamous "" Connection timed out..."". Sage KB advice? Run as an application. I'm rapidly loosing confidence that Sage 100 Advanced can be reliably recommended to sites with 20+ concurrent users (this site has 40). The problem with this instability problem is that once you're up over 20 concurrent users and they're doing more than GLAP it's a major hassle to (a) trial and error these fixes and (b) get every user out of the software so that the server can reboot. It only takes a few days/weeks of this before the owner is asking what's going on .

We're pursuing the ""run as service"" and making the mods https://www.evernote.com/shard/s1/sh/4ba87667-d062-4c48-8046-c95a6cb27acb/b2f94b05fdc1253db9f036719422422f

Hard to tell exactly what's happening but when I look in the event viewer I can see there is some type of issue with .NET. This seems to precede any type of hung process.

Update: We swapped from running Sage 100 ERP Advanced 2013 as an APPLICATION to running it as a SERVICE. We were on a MS Server 2008 R2. We had to bump the memory parameter to 3072 (there are 40 concurrent users). Details on the memory parameter change: https://www.evernote.com/shard/s1/sh/4ba87667-d062-4c48-8046-c95a6cb27acb/b2f94b05fdc1253db9f036719422422f After that the issue appeared to resolve (or at least it's not locking users periodically as it was when we ran this as an application). Still unsure exactly what is/was going on here as we toyed with DEP regarding BEX issues. And as described above - this was a customer on 4.5 who did just a single level upgrade. Makes me very skittish about large # of users under Sage 100 Advanced or Premium. The biggest concern is there is NO way to tell if you will have problems without putting Sage 100 ""under load' which means if you do have a problem you have a real problem. If you roll back to 4.5 you have to go do wksetup on 40 stations, if you toy with 2013 you potentially have 40 people in a wholesale distribution setting not taking orders, shipping, etc. This is a pretty serious concern imho. Based on prior feedback that I've read here and elsewhere (Sage online) -- the problem seems to be the same whether you are on Advanced or Premium. IOW an upgrade to Premium does not automatically resolve this issue.

I posted some addt'l info/questions here: https://90minds-com.socialcast.com/messages/15095386