Sage 100

v2014 upgrade (from v4.3), SBS 2008 64 OS. Initial install seemed to be ok. Installed the PU 1 along with the little patches. Then I got brave and tried the new PU3. Threw an error message (missing sy_options????), then I had to remove the install lock and the errors started to cascade. So I decided to start over by deleting the MAS 90 folder and the fun really began. The few minutes that was promised for installing the prerequisites ran all night without ending. Then I thought, what the heck, the prerequisites should already exist because of the previous install so I bypassed the autorun.exe and ran the .msi program. Received the second error after keying in the administrator password. Now I am guessing I have clutter in the registry, thought I would post here before calling Sage....

Isn't PU7 for 2013 and 3 is for 2014?

You would think it wouldn't let you install it.

My bad, it was 3. And I am not a huge fan of skipping PU numbers either.

You wouldn't have ,if you were in the special VIP group lol.

I saw the PVX error in the Sage KB -- Description Error: ""PVX Object init failed to run"" when installing or upgrading Sage 100 ERP Cause InstallShield cannot complete its process because the registry or the InstallShield files are incorrect, damaged, or in use. This may result from multiple installations of the same version, multiple installation attempts, or network file locking issues. Resolution Activate.pvx is corrupt or missing Verify that Home/Lib/Keys/Activate.pvx is present and the client can be launched from pvxwin32.exe (Double click pvxwin32.exe and type Run ""Startup.m4p"" <Click Enter>) If necessary replace Activate.pvx with a valid copy Run Pvxcom.exe 32-bit - C:\Program Files\Common Files\Sage\Common Components\ 64-bit - C:\Program Files (x86)\Common Files\Sage\Common Components\ Rename the Runtime folder located at: C:\Program Files\Common Files\InstallShield\Professional\Runtime\ Rename the Uninstall Information folder located at: x:\..\MAS90\Uninstall Information\ Reinstall Sage 100 ERP Note: Registration keys must be reentered