Configuration Notes:
The table below describes a number of causes and remedies for when installation of STEP 7 is aborted with a message regarding the InstallShield (InstallShield Scripting).
 

No.	Causes and remedies:
1	Check DCOM settings and reset to default settings Like many other current applications the Setup of STEP 7 uses the new Windows Installer technology (also known as Microsoft Installer or MSI). The Windows Installer uses the DCOM technology (Distributed Component Object Model) and requires specific DCOM security settings. The default settings meet these minimum requirements. If, for example for security reasons, the DCOM settings are restrictive, it might happen that the installation procedure aborts with one of the following error messages: "InstallShield: 1601: internal error in Windows installer". "1607: "Cannot install InstallShield Scripting Runtime". Open the "DCOM Configuration" dialog in Windows by selecting "Start > Run..." and then entering "dcomcnfg". The MSI Setup doesn't work if the default properties have been set as follows: Default Authentication Level: None Default Impersonation Level: Anonymous In this case reset the default settings as shown in Fig. 01. Fig. 01
2	Set Full Control access for SYSTEM account When installing STEP 7 on an NTFS drive the administrator must assign all standard users working on that computer with STEP 7 Full Control access to the STEP 7 installation directory. Mark the system drive in the Windows Explorer and select the "Properties" dialog from the pop-up menu (right-click). Switch to the "Security" tab and make sure that Full Control is set for the SYSTEM account. Fig. 02 Make sure that the SYSTEM account with Full Control has the following folders or paths if these are not on the system drive: TEMP folder Target path for installation Path <Windows>\Installer Source drive if installing from the hard disk.
3	Check permissions for Registry access by the SYSTEM account The InstallScript supplied cannot be installed or the InstallScript is already installed and it is not possible to install STEP 7, because the system might not have Read permission for the source. The following operating systems are affected: Microsoft Windows NT Microsoft Windows 2000 Microsoft Windows XP Unlike earlier versions of STEP 7 in STEP 7 V5.3 and higher you only need to log on as user. You need administrator rights to install the STEP 7 software and install modules via the application "Set PG/PC Interface". When installing STEP 7 on an NTFS drive the administrator must assign all standard users working on that computer with STEP 7 Full Control access to the STEP 7 installation directory. Open the Registration editor in Windows by going to "Start > Run...", entering "Regedit32" and marking the path (example: HKEY_LOCAL_MACHINE) whose permissions you want to check. Right-click and then in the pop-up menu that opens you select "Permissions...". When you select "SYSTEM" in the dialog that opens (Fig. 03), Full Control (Under "Permissions") should be enabled. Fig. 03
4	Restore Security Key for the MSI service Open the Registry editor via "Start > Run..." and then entering "regedit". Then localize the following code: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer\Security  Rename this code to "Old_Security", for example and reboot your PC (absolutely necessary). Start the "InstMsiW.exe" application to repair the Windows Installer. This file is usually located in the same directory as the "Setup.exe" file of the application to be installed (in some cases in a subfolder marked "MSI"). Fig. 04 Note: If the Windows Installer cannot be started and you get the error message "Specified service is already available", rename the Msisip.dll file in the System32 folder to Msisip.old. After installing the Windows Installer you must restart the computer.
5	Installation of the InstallScript with STEP 7 V5.2 / V5.3 in Windows 2000 If you get the message "Error 1: The InstallScript Engine is missing from this machine" in Windows 2000, then the InstallScript provided by the installation has probably not been installed correctly. Find the "Idriver.exe" file on your hard disk and open the "Properties" dialog for this file (right-click and pop-up menu). In the "Properties" dialog you mark and copy the file's storage path (C:\...) into the storage. Then open the input window in Windows 2000 via "Start > Run..." and enter the instruction "Idriver.exe/RegServer" with full file path specification (copy from storage) in the input window. Example: C:\Programs\Shared Files\InstallShield\Driver\7\Intel 32\IDriver.exe /RegServer Fig. 05 Acknowledge with OK and restart the Setup of STEP 7 V5.2 / V5.3.
6	If the remedy in Point 5 does not work, then start the file ISScript.Msi or ISScript8.Msi (with STEP 7 V5.3) from the path: [CD-ROM DRIVE]:\STEP7\DISK1 of the STEP 7 CD. Fig. 06 When the "InstallShield Scripting" program is running you get a message like: "Error 1327 Invalid Drive: X:\". This drive might be a non-connected network drive or the system path is invalid, for example: Personal Folder is on "H:\" and drive "H:\" is not connected in the Explorer or there are no access rights (read and write). All operating systems are affected. Remedy: Check and if necessary correct the system paths with Regedit (HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders) and connect the relevant network drive. Assign the appropriate access rights to the drives (as described in Point 3).
7	Not enough memory on the hard disk Check the space that is still free on the hard disk and in the virtual main memory. The exact amount also depends on the operating system and the file system used on the PC. Also refer to the relevant notes in the readme file of the version of STEP 7 you have installed (section 3.2 Memory Requirements). More information on setting the virtual main memory in the Windows operating systems is available in our Entry: "How do you make the settings for the virtual memory in MS Windows XP/2000/ME/NT/9x?" Entry ID: 20440472 Another cause might be that there are too many files in the Temp folder. In this case you should delete all the files in the Temp folder.
8	Firewall The InstallScript supplied cannot be installed when you have installed a firewall such as "Zone Alarm". This firewall blocks the InstallScript - even when the firewall is not activated. Remedy: Uninstall the firewall.
9	The error messages described above have also appeared during installation of the Automation License Manager V2.1 in CAT Client Windows XP SP2. When starting installation of the file "ISScript8.msi" the following message appears: "Windows Installer: the Windows Installer service cannot be accessed". Running Windows in Safe mode or incorrect installation of the Windows Installer is the cause of this behavior. Remedy: Check the "Windows Install" service.