Sage 100

Has anyone put the new PEP fix into place and had luck? We have a client running Sage2014 on 3 different term servers that get the WinDx error when there are more than 15 or so people logged into Sage. We have tried everything under the sun to get the error to go away, but had no luck. We installed the patch last night hoping it would resolve the issues, but they are still getting the errors on all three servers. Maybe something else needs to happen if it is running on TS?

I tend to use the old PEP fix...turn it off.

Is this Standard or Advance? Most likely not a PEP issue. There are registry entries that need to be made when on Advanced and over 10 users. You should be able to find the info on what to change, in the Knowledge Base.

@RobertWood PEP is turned off and so is the Sage Advisor Service (disabled). @MadelineStefanou It's advanced, I will look for it and verify the settings are correct. We have been battling this since the upgrade to 2014 several weeks ago, so that might do it. They moved to the cloud at the same time, so the settings would not have carried over from 2013

Then your problem isn't PEP.

I've run into this on past ""upgrades"". End user was perfectly happy - 20+ users on Sage 100 Advanced. Upgraded to 2013 and suddenly connection problems left and right. I believe the only thing that solved it for us was following all the typical fixes and using the registry change (even though some said it should not be required).

@WayneSchulz and @MadelineStefanou I am having trouble finding anything for Sage Advanced registry changes in the KB. Suggestions for keywords I should be looking for?

I believe this is it https://www.evernote.com/shard/s270/sh/397b1123-cb16-459c-88ac-f51390b662c7/386ab700a9af6738b3786c36c426e620

Thank you @WayneSchulz ! I have never seen this before, I will add it to my checklist from here on out!