Page 1 of 1

Invalid Drive O:\ when trying to install

Posted: Fri Sep 09, 2011 7:04 am
by vgerretz
I have been trying to install PrimalScript2011 Build 150 on to a Windows 7 x64 workstation. When I run the install, I get the following error:
Image
The workstation is connected to the company's network and Drive O: was here when the initial install occurred.

Invalid Drive O:\ when trying to install

Posted: Fri Sep 09, 2011 7:31 am
by Alexander Riedel
So I take it that the O: drive no longer exists?

In order to install a new service build PrimalScript does a quick uninstall of the previous build while preserving all your data and settings. Then it installs the new build.

If the MSI of the currently installed build is no longer accessible you should try a manual uninstall or remove the previous version's Windows Installer references from the registry.
If a manual uninstall is not working and you need assistance with the latter please let us know.
Then install the new build by running the setup executable.

Invalid Drive O:\ when trying to install

Posted: Fri Sep 09, 2011 7:58 am
by vgerretz
I am installing on a new machine, PrimalScript2011 Build 150 was never installed on it and Drive O: is mapped. PS2011 is not listed in Programs that are installed. The install process does not get that far.

The "My Documents" was moved from the local drive to the network drive. Would this impact the install on a new machine?

Invalid Drive O:\ when trying to install

Posted: Fri Sep 09, 2011 8:10 am
by vgerretz
Got the following entry in Application Event Viewer.

Product: PrimalScript 2011 -- Error 1327. Invalid Drive: O:

Invalid Drive O:\ when trying to install

Posted: Fri Sep 09, 2011 8:25 am
by Alexander Riedel
There can be a couple of places where redirection can be a problem:

The installer tries to create a folder
[My Documents]SAPIEN Scripts.

If the installer has no access permissions this is one of the potential error messages.

The installer also requires elevation. I can't tell if you running under a non-admin user and enter the credentials of an admin account when prompted for elevation. If that is the case, can it be that the account you provide does not have the O: drive mapped?