Handling Corrupted PIW Files: Steps to Resolution

Corrupting a PIW file, whether due to a system error like CTOCEntries::Load() or a user action like prematurely closing PI ProcessBook, can be a frustrating experience. Corruption can prevent you from accessing valuable data and insights contained within these files. However, understanding the appropriate steps to address this issue can save time and possible data loss.

Initial Diagnosis

The first step towards resolving a corrupted PIW file is understanding the nature of the corruption. PIW files can become corrupted due to various reasons such as:

• System crashes or power failures during the file saving process.
• Software bugs that may manifest during data loading (CTOCEntries::Load() errors).
• User interruptions during the save process.

Reaching Out to Technical Support

While some level of diagnosis and minor fixes might be implemented by a user, dealing with file corruption often requires professional intervention. Here, OSIsoft’s technical support can be invaluable:

1. Accessing Support:

   • Use the OSIsoft support portal by going to https://my.osisoft.com/.
   • You can also contact them via phone. Phone numbers are listed on the support portal.

2. Creating a Support Case:

   • Create a case detailing your issue—describe what actions led to the corruption and any error messages received, such as CTOCEntries::Load().
   • Provide any relevant logs or contexts that could help the support team diagnose the issue better.

Troubleshooting Access Issues

If you face access restrictions on the support portal or if you see messages like "You do not have access to this page," you may need to coordinate with your organization’s designated PI admin:

• Login Coordination:
  • Ensure you have the right credentials. The designated admin typically handles access permissions.
  • Follow the guidance on the access webpage to obtain proper login credentials.

Expectations

While OSIsoft technical support is skilled in offering solutions, keep in mind:

• No Guaranteed Restoration:

  • Success in file restoration isn’t guaranteed; it heavily depends on the extent of file corruption.

• Backup Practices:

  • Develop a robust backup strategy to prevent future data loss. Regular backups can mitigate the risk of losing data during such unexpected events.

By following these steps, you can systematically approach a corrupted PIW file issue. Rely on OSIsoft’s technical expertise to explore possible recovery paths and ensure that necessary precautions are implemented to avoid similar issues moving forward.