Sage 100

Remind me why I call Sage support. I have a client that I install 2014 SU 7 over 2014 SU 3. I could see users through the Share (Server Manager) trying to get in while I was doing the install. The install finished. When I tried to start the client it hung at 50% CPU. I have uninstalled and reinstalled the workstation and workstation update. I have renamed SY_ActivityLog, SY_Console, and SY_Workstation. The only advise I am getting from Sage at the moment is to restore last night SOA, Launcher, and SY_System and start over. GRRRR.... Any suggestions on this 1 hour simple IRD update and PU install that is now starting hour 4.

Did you try reinstalling the PU?

I did. I can get the install to open when I replace the SY_System (but the copy I have at the moment is from the conversion a year ago).

If this is Adv, will it run in Std mode?

I had to turn on procmon once when this happened to me after migrating. It turned out PEP was acting up, even though I had opted out. I had to rename the SY_SagePEP.m4t file.

This is Standard. It will not work from the server or the workstation. without replacing the SY_System directory.

Did you have to replace SY_SagePEP or does it create?

I don't believe it generates, but I was disabling it anyway. It can always be disabled back door style if need be. 1.Expand Library Master, Main, Data File Display and Maintenance (DFDM) 2.Select the MAS90/MAS_SYSTEM/SY_System.M4T file 3.Click Edit the EnablePEPForSystem$ field (Should be Field 50) 4.Change the Y value to N 5.Exit DFDM and re-launch Sage 100

And with that... I am back up and running. I replaced all 4 files referencing PEP with the one from my old backup and we are up and running. @RhondaMcNamara , please check the back of your neck. Do you have a cape sprouting from back there because YOU ARE MY SUPER HERO!!! Thank you!

Just some sort of outlet back there, @LarryBradford . Same as everyone else. :-D

I knew it. That explains all of the people that know each other and the doppelgangers. This is the Matrix.