Understanding Error Handling in PI Archive Subsystem

sid: basics-of-handling-pi-archsss-errors

Understanding Error Handling in PI Archive Subsystem with NT SERVICE Account

In recent user forums, a notable error message has been frequently reported by PI System administrators: "Unable to manage the file system cache. [1300] Not all privileges or groups referenced are assigned to the caller." This error, logged in the PI Message Logs, affects the PI Archive Subsystem (piarchss) running under the NT SERVICE\piarchss account. Let’s delve into what this means and how to address it effectively.

Context: The Role of PI Archive Subsystem

The PI Archive Subsystem is a critical component responsible for the storage and retrieval of time-series data within OSIsoft's PI System. When piarchss encounters errors, it can lead to complications in data management and performance. This is particularly pivotal for administrators managing PI Data Archive Collectives—environments where multiple PI Data Servers work in unison to provide redundancy and share the data load.

The Error Explained

The error message “Unable to manage the file system cache. [1300]” pertains to permission issues concerning system resource management. It indicates that the NT SERVICE\piarchss account does not possess sufficient privileges to interact with the file system cache effectively. This lack of privilege often results in difficulties in memory management, which is crucial for optimal functioning of the PI Archive Subsystem.

Why It’s Happening

• Non-Privileged Account: The NT SERVICE\piarchss account runs with limited privileges by design. This ensures security by minimizing risk exposure. However, it can also lead to scenarios where essential permissions for system operations are lacking.
• Version-Specific Issues: Those using PI Data Archive version 2018 SP3 or later may encounter this issue due to changes in how permissions are applied in newer Windows Server environments.

Solutions and Best Practices

1. Assessing Account Privileges:

   • Verify whether the NT SERVICE\piarchss account is assigned the necessary privileges for cache management. This typically involves adding the account to user groups that have administrative permissions, albeit temporarily, to diagnose and rectify the problem.

2. Knowledge Base Reference:

   • OSIsoft provides updated knowledge base articles that address such permission issues, often suggesting specific server configuration adjustments or security settings that mitigate these errors. For version-specific discrepancies, reference known issue articles related to error code 2251.

3. System and Security Audit:

   • A comprehensive audit of your system’s security settings can often reveal permission gaps. This involves checking group policies and local security policies that might restrict service accounts like piarchss from executing necessary operations.

4. Consider External Expertise:

   • If internal troubleshooting exhausts without resolving the error, engaging with OSIsoft support or experienced PI System professionals can be beneficial. They offer insights tailored to your specific environment.

Conclusion

Regularly encountering permission-related errors on services like PI Archive Subsystem can be a bottleneck if not promptly addressed. Ensuring that system accounts like NT SERVICE\piarchss have appropriate security privileges while maintaining a secure environment requires a balanced approach. Leveraging community insights, vendor resources, and a thorough understanding of system permissions will equip PI System administrators to tackle such challenges effectively.