Sage 100

Have a client where I'm currently assisting with a disaster recovery (no backup/system crash). When we go to install v4.3 from the CD the install is hanging. I'm about out of ideas as to what may be screwing this up though I'm guessing there may be some installshield files left somewhere? Where in the Windows folder do I need to look. Have never had this many issues getting a regular old MAS install running before -- issues occurring if we install to local C: or to network. Odd

I think this is part of the resolution though I'm not entirely sure why only some client sites seem to ever have install errors (I suspect it has to do with a combination of their network, rights, anti-virus). Possible Resolution: 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. Complete one or more of the steps listed below to resolve this issue. Start at the top of the list, and reinitiate the installation or upgrade process after completing each step. Continue with the list if the error recurs. Run Pvxcom.exe. Sage MAS 90 or 200 version 4.20 and later: Pvxcom.exe is located in the Common Components folder: C:\Program Files\Common Files\Sage\Common Components\ Sage MAS 90 or 200 version 4.10 and earlier: Pvxcom.exe is located in the ..\Mas90\Home\ folder Reinstall the program. Select the Install a new instance of this application option. Reinstall using the Windows Add or Remove Programs option. 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\ Note: Registration keys must be reentered. Remove multiple installations of the same version of Sage MAS 90 or 200 if they exist. Only the primary installation should remain on the computer. Note: Use extreme caution when editing the registry. If the registry is edited incorrectly, Windows may not function properly or may not run at all. Sage Software Customer Support is not responsible for assisting with editing the registry. Always back up the registry before accessing it. If necessary, seek the assistance of a qualified computer technician. In some instances, it is necessary to remove entries in the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstal\ Before proceeding with this final step, e-mail the setup.ilg file to Customer Support. The file is located in the ..\Mas90\Uninstall Information\ folder. Customer Support will assist in determining that all other methods are exhausted.

On the folder look to see if there are any Best of Sagesoftware folders left behind from before. The Uninstall files would there there.

I had this happen to me twice. Renaming the Uninstall Information file and rebooting did the trick on the first occurance. The second was tricky. There was a slight smudge, barely visable on the disk. I did my best to clean it to no avail. Fortunately I had my dealer disk with me, install from it and the problem was solved.

Talk about a problem -- I've tried re-running the install probably 8 to 10 times. It hangs every time before it starts to install. Unsure on whether the client has antivirus issues or what may be the cause. My best guess now because I've ripped most files out is some type of registry hack. I've seen this type of problem where install simply won't run for some reason on a server or workstation -- though it's extremely rare. What we're trying to do is give a clean install to another workstation and if that's a go we can drag/drop MAS back to the server...

I had one situation on ver 4.2 where I could not install directly on the server but was able to install from a workstation using a mapped drive, just like in the old days.

Still not sure what caused the issue but from what I can see because I was trying to install over an existing MAS90 install. I had also removed the MAS_SYSTEM which could have been the cause of the failure to install. Irrespective it seems that the client's data is corrupt so we're still in the process of investigating.

Was this a virutual machine install?

Not virtual - - just a MAS server. We pulled it to a local machine and had some issues installing over the top of data. Finally had to keep moving and we installed to a local copy. I can't rule out that their system files are hosed as well as data. I've never seen this extensive type of damage before -- where the files are still there but many of them are damaged. The closest I've seen is when someone runs an anti-virus scan and answers ""yes"" to an inquiry about whether they want to clean an bogus infection from a MAS file.