PI ProcessBook Installation Guide
Uploaded by
Pawan VaskarPI ProcessBook Installation Guide
Uploaded by
Pawan VaskarCommon questions
Powered by AIWhen upgrading PI ProcessBook, the installation process removes the previous version but retains the .ini file settings, ensuring that displays and ProcessBooks created with older versions remain functional. However, if the version being upgraded is significantly outdated, intermediate version installations may be needed to ensure successful migration .
PI ProcessBook shares the installation root path with other client products like PI DataLink. To avoid DLL incompatibility issues, they should share the same directory paths, typically C:\Program Files\PIPC. Moreover, when PI BatchView is installed, a compatible Batch group symbol is added automatically .
SetupProcessBook.log contains information about the installation process, including directory structure, node information, DLL files, usernames, and the installation status of various PI ProcessBook files. It is crucial for troubleshooting and verifying that the installation has proceeded correctly .
When migrating from significantly older versions of PI ProcessBook, it might be necessary to pass the files through intermediate versions to ensure a successful migration. This step is crucial to maintain the integrity of displays and ProcessBooks .
PI ProcessBook is a 32-bit application that can run on both 32- and 64-bit Windows systems. It is important to ensure compatibility with other PI System client products, as the installation path typically used is C:\Program Files (x86) for 32-bit applications on 64-bit systems .
Documentation for installed files is included in the SetupProcessBook.log file within the PIPC/Dat directory. Additionally, online help files and release notes outlining a complete list of files are available at C:\Program Files\PIPC\procbook\en\ProcessBook.pdf .
Silent installation allows system administrators to deploy PI ProcessBook across multiple desktops without interaction, saving time and reducing the possibility of installation errors. It's beneficial in large organizations where software needs to be installed uniformly and efficiently .
If the SetupProcessBook.log is not found in the PIPC\DAT directory after installing PI ProcessBook, the next step is to check the root directory of the system drive, such as C:\, as it might have been placed there instead .
The silent.ini file is used to conduct a silent installation, allowing PI ProcessBook to be deployed without user interaction. This file contains site-specific configurations and arguments for the setup process. Administrators can customize it as needed, facilitating unattended installation across multiple desktops .
Compatibility is critical to ensure that the correct Batch Trend symbol loads and functions with the current version of PI ProcessBook. Installing PI BatchView after PI ProcessBook ensures aligned and compatible features, preventing potential compatibility issues with shared DLL files .