prim21525:During installation of Primavera software, the following error appears: 1607: Unable to install InstallShield scripting runtime

http://consumer.installshield.com/kb.asp?id=Q108340

*NOTE – May need to change id to Q108322 for ISScript 10.5

Error -1607: Unable to Install InstallShield Scripting Run Time

Document ID: Q108340
Last Revised On: 12/15/2003

Problem

When running an installation created with an InstallShield product, the following error occurs at the beginning of the installation:

Error -1607: Unable to Install InstallShield Scripting Runtime

More Information

This error message is a system-specific error and can be caused by a system-specific setting. This article attempts to list all the possible steps that have known to resolve this error. Depending on your system, you may need to try some or all of the listed solutions.

Fix

1.Update the ISScript engine on your computer by downloading the latest one. For more information, see Setup Is Unable To Find or Update ISScript.msi.

2.Make sure that the Installer folder in the Windows directory has full access privileges. The Installer folder may be hidden on your computer, so you will have to set your computer to see hidden files and folders and then set the proper permissions to the <WINDOWSFOLDER>\Installer folder:

A.Show Hidden Files and Folder

1.Launch Windows Explorer by pressing the Windows key + E or select Start > Run and type explorer.

2.Select Tools > Folder in the Windows Explorer window.

3.Select the View tab.

4.In the Advanced Settings pane, select Show hidden files and folder.

B.Set the Installer folder attributes

1.Locate the folder <WINDOWSFOLDER>\Installer:

?/SPAN>Windows NT and 2000: C:\WINNT\Installer

?/SPAN>Windows 95/98/Me/ XP: C:\Windows\Installer

Note: In some instances this directory doesn’t appear on Windows XP machines. Follow these steps to view the folder:

a.In Windows Explorer select View > Toolbars and select Address Bar if there isn’t a check box next to it.

b.In the Address Bar type in the full path: C:\WINDOWS\Installer.

                        2.Right-click on the Installer folder and choose Properties.

3.Select the Security tab.

4.Make sure the System, Administrators and the specific user have Full Control of this folder.

C.Repeat the instructions in Step B for the Temp directory. To locate the Temp directory on your machine, refer to the article Clean the Temp Directory.

3.Make sure that the InstallShield registry key in the Windows registry has full access privileges.

1.Select Start > Run and type regedt32.

2.Browse to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield

3.Check the permissions of this key:

?/SPAN>Windows XP users can right click and select Permissions.

?/SPAN>Windows 2000 and NT users navigate to the Security menu and select Permissions.

4.Assign both the Administrators and System group Full Control if they don’t already have it. For an idea of what the permissions property dialog will look like, see step 2B-4.

4.If the installation is located on a network drive, copy all of the files to the local hard drive (i.e., Desktop or Temp directory) and attempt to run the installation again.

5.Install the Windows Installer engine on your computer to make sure that it is not corrupt and that it is properly registered on your computer. For more information, see How Do I Install the Windows Installer Engine on My Computer?

6.Make sure you have full administrative privileges on your computer. This only applies to Windows NT 4.0, 2000, and XP computers; Windows 95, 98, and ME do not require this. For more information, see How Do I Acquire Administrative Privileges on My Computer?

7.Make sure no other applications, installations, or processes are running in the background. For more information, see How Do I Detect and End Previously Running Installation Processes? and How Do I Close Applications Running in the Background?.

8.Make sure to check the location from where the installation is being run. If the downloaded installation files are stored in a directory path that contains special characters, such as “&”, “-”, “.”, etc, change the path to something that does not contain these characters.

Bad path: C:\downloads\Palm\palm desktop & hotsync\x\setup.exe

Good path: C:\downloads\Palm\palm desktop hotsync\x\setup.exe

9.The DCOM settings on Windows NT, 2000, and XP may need to be configured. For more information, see How Do I Configure the DCOM Settings on My Computer?

Additional Information

Another reason your installation may not run is changes to your computer caused by recent updates. For example, updates to your operating system may cause installations created prior to the update to fail. You may want to uninstall any recent updates, install your application, and reinstall the update.

WARNING: You should check with the software vendor who created the update to ensure no adverse affects will result from uninstalling the update.