Sage 100

Connection errors out the wazoo!!! Is anyone else encountering the connection issues with Windows 2012? We've had eight (8) clients contact us in the last two days with this issue. Sage says it's a known issue and they're working on it, but we can't be the only ones.

We were just notified that it appears to be centered around clients that have PEP enabled.

Yes, we had several issues too. Disable PEP and you should be okay

Disabling PEP our this problem for us, too.

DISABLE PEP. Lots of issues in the last week................. Sage Tech also commented on it yesterday during our three hour session of WS install futility. Now waiting on Ronnie Aspe to come the rescue........

Disabling PEP worked for our 25+ user client that was impacted late yesterday. Now they think Sage is like the NSA.

And if you don't have the Sage Administrator logon, you can manually change field 50 (EnablePEPForSystem$) in sy_system.m4t (located in mas_system) from Y to N which ""appears"" to do the same thing.

Why suddenly this issues. Is there something that is time/date specific with PEP and now SAGE activated a ""feature""?

Is anyone at Sage support taking the lead on this?

One of my associates received this email from Jeff Konstanzer a short while ago: You should see a post related to the issues that impacted our server/s that run PEP. We are unclear if this was related to the MS Updates or not and we are researching that and our communication protocols to ensure it doesn't happen again in the future. You may want to review the Sage City posting<http://sagecity.na.sage.com/support_communities/sage100_erp/f/98/t/78527.aspx?pi4790=3> to see the details and to obtain the final information that should be posted in the very near future.

Hi Wayne, This is the message that is being sent out as a Partner Communications and posted out to the various communities regarding this issue right now: As some of you are aware, in the last 24 - 36 hours we experienced some communication issues between the Sage 100 ERP application and our PEP data servers that negatively impacted some of our customers. This included application time-outs for some users, and temporary slowness for some others. We were able to restore service early this morning and are taking steps to prevent this issue from occurring in the future. If you have any customers experiencing residual problems, please have them contact Sage technical support. We will provide additional information in the next couple of days on the cause of the issue and what changes we are making going forward. Our goal is to ensure that our customers and partners have confidence in this important tool, which provides valuable information to help Sage prioritize future product improvements for our customers. Sage ERP 100 product team We are exploring the root cause and will follow-up with additional information on it as soon as we are able. We hope that people realize this is a server connection issue, not a PEP issue. We will be modifying how Sage 100 ERP connects to the PEP server as a result of what we suspect is a recent Microsoft security patch. Deborah Nelson Product Manager, Sage 100 ERP Sage North America

So an on-premises implementation is affected by a server off at the publisher and it takes 24-36 hours to fix. Does that give you confidence in them as a technology company, let alone a cloud company.

Between this and all the SPS outages, nobody could say with a straight face that these guys can manage cloud services. I think this is what happens when you combine a company that NObody respects technically with one that has been hollowing out its middle management for 6 years.

Sage announcement. At best I think it took them 24 hours to notify the channel. Anyone who thinks some type of CHANNEL communication tool such as 90 Minds is not mandatory is just fooling themselves. Sage will notify you when and if they feel like it. In this case you would have to stay stuck on support lines until someone picked up the phone and then hope that they leveled with you about what the REAL problem was.

This is really sad, and unnecessary. A couple years ago Sage started looking at using Twitter and/or other social media to disseminate this kind of information. I guess that idea died on the vine? @WayneSchulz, I got that email and since it didn't say not to respond I replied with the following (still haven't heard back - and I'm sure I never will): Dear Sage ERP 100 product team; I had heard about that but for me it's not really a problem as the first thing I do for any new installation is go into Administrative Tools and disable PEP. It has caused various issues right from its inception and this has always been a good way to just sidestep them. As a matter of fact I'm glad you brought this up. I think it would be a nice modification if when you are installing Sage 100 ERP instead of the screen telling you that you have to participate in PEP you were offered a way to opt out. Sincerely, yada yada

Not to be paranoid but considering the fact that we saw crypto viruses pop up all of a sudden when we had these PEP problems I fear that the issues could be related. Somehow I have less faith in sage than before. And to think that when we were experiencing these problems initially sages answer was to uninstall and reinstall the service seems to be ridiculous!!!

@CullenLowe - Although we may agree with your sentiment, Sage wants the information and really doesn't care about our opinion or the customer inconvenience.