isaacgrover
IS-IT--Management
- Jun 13, 2006
- 54
Greetings,
At a client site is a Windows Server 2003 R2 box, no Active Directory, mostly as a file server to the workstations with the exception of multi-user Peachtree 2011, which is accessed by three remote users who RDP in to the server, and not always at the same time.
The client asked us to update Peachtree 2011 with Sage 50 Premium 2013, but at the 'removing applications' step, the program seemed to stop progressing. We ended the setup process after thirty minutes, restarted the server, and called Sage tech support. They suspected a bad CD, so sent us to the download. Same thing. This time we tried uninstalling Peachtree 2011 before installing Sage 50, only to receive an 'error 1628'. Researching that error led us to clear out the registry entries that indicated an installation still in progress. Again the server got restarted. We called Sage tech support back - they suspected that the Installshield engine was corrupt, but was beyond their ability to support.
Sage 50 installation was still hanging at the same step, Peachtree 2011 wouldn't uninstall, so I tried cleaning it out with Revo Uninstaller, removing both program entries using MSI Cleanup, and rebuilding the Installshield engine for version 10.5 - the one Sage 50 uses during installation. Even the Installshield repair utility hung during installation.
Does anyone have any suggestions on repairing a botched Windows Installer database and/or Installshield engine, botched so much that even the tools to fix them don't work?
Thank you in advance,
Isaac Grover
--
Isaac Grover, Owner
Quality Computer Services of River Falls, Wisconsin
Web:
At a client site is a Windows Server 2003 R2 box, no Active Directory, mostly as a file server to the workstations with the exception of multi-user Peachtree 2011, which is accessed by three remote users who RDP in to the server, and not always at the same time.
The client asked us to update Peachtree 2011 with Sage 50 Premium 2013, but at the 'removing applications' step, the program seemed to stop progressing. We ended the setup process after thirty minutes, restarted the server, and called Sage tech support. They suspected a bad CD, so sent us to the download. Same thing. This time we tried uninstalling Peachtree 2011 before installing Sage 50, only to receive an 'error 1628'. Researching that error led us to clear out the registry entries that indicated an installation still in progress. Again the server got restarted. We called Sage tech support back - they suspected that the Installshield engine was corrupt, but was beyond their ability to support.
Sage 50 installation was still hanging at the same step, Peachtree 2011 wouldn't uninstall, so I tried cleaning it out with Revo Uninstaller, removing both program entries using MSI Cleanup, and rebuilding the Installshield engine for version 10.5 - the one Sage 50 uses during installation. Even the Installshield repair utility hung during installation.
Does anyone have any suggestions on repairing a botched Windows Installer database and/or Installshield engine, botched so much that even the tools to fix them don't work?
Thank you in advance,
Isaac Grover
--
Isaac Grover, Owner
Quality Computer Services of River Falls, Wisconsin
Web: