1. Setup Troubleshooting

  2. Check the Log Files

If problems are encountered during the setup process the first place to look is in the log files.

The progress of the overall setup is logged in SetupPISDKMaster.log in the root of the system drive (for example C:\) and then copied to the user TEMP directory (%TEMP%) or %PIHOME%\dat directory (for example C:\Program Files\PIPC\dat, if it exists, when the setup proccess is complete. Failures to install prerequisites, such as MDAC will abort the setup process. This master log will show the various stages of the setup that have completed. The file is written in append mode so the most recent activity is recorded at the bottom of the file. Each setup attempt in the log begins with the date and time that the log was opened.

Problems specific to the PI-SDK setup are logged in the file setuppisdk.log found in the %PIHOME%\dat directory (for example C:\Program Files\PIPC\dat). This file, produced by Windows Installer, is relatively complex and contains details of each step of the setup process. Often searching for the word "rollback" in the file will locate the phase of the setup where an error occurred. Windows Installer performs a rollback to the beginning state of a setup when fatal errors are encountered.

If the cause of a setup problem is not readily apparent from the log files, they may still provide good input for the support engineers. These files should be provided when submitting a setup problem to OSI technical support.

  1. Self-extracting Zip Files and Setup.exe

You may have obtained the PI-SDK setup in the form of a self-extracting zip file, from a Web or ftp download. Typically you only need to double click on the self-extracting zip file in Windows Explorer to begin the installation.

Under rare circumstances you could see a different setup program start at this point. The self-extracting zip software extracts all files, including setup.exe, into a sub-directory of the %TEMP% directory. If there is already a file named setup.exe in that directory that is read only, that executable may not be replaced and is run rather than the one from the self-extracting zip file. This can be remedied by simply renaming the spurious setup.exe to something else, then re-launching the self-extracting zip.

Enabling Operational Intelligence