Error reading OSDD. OSDD file not found” when starting SafeDesigner (AS 4.6 with mapSafety 5.10.1)

Ask Questions
,
1

Hello everyone,
I’m encountering a problem when opening SafeDesigner for a project developed with Automation Studio 4.6 (mapSafety 5.10.1). Here are the details:

  1. Context

    • The project was originally developed on a PC running AS 4.6, which has not been updated in several months.
    • The “non-safety” part of the project shows no version inconsistencies and compiles without errors.

  2. Encountered Problem

    • Upon launching SafeDesigner, I receive the warning:
      > “Error reading OSDD. OSDD file not found”
    • No additional details or help links are provided by this message.

  3. Checks Performed

    • We are certain that the installed mapSafety version (5.10.1) matches the one used during development.
    • We have a complete project backup, which appears to have been correctly saved.
    • The rest of the project (compilation and execution in AS 4.6) works properly.

Request:
Has anyone encountered this error or have suggestions on how to resolve the “Error reading OSDD. OSDD file not found” issue? Could it be a missing file in the project’s directory, or a specific SafeDesigner configuration that was not correctly restored? Any insights or experiences would be greatly appreciated.

Thank you in advance to anyone who can offer assistance.

2

OSDD files are part of the AS Upgrades of the related hardware products. But AS usually complains about missing hardware upgrades (prompts for download when opening the project; generates warnings during compile).

5.10.1 is quite outdated, so you might do a test with latest versions to check if it behaves differently.

3

We would like to provide some additional details regarding the OSDD file error:

  • We used the same backup file that was producing the error and opened it on a fresh virtual machine with only AS 4.6 installed, and the same error still occurred.
  • When we opened the exact same backup in AS 4.12 (after performing all the necessary alignment/updates), the project opened successfully without any issues.
  • We tested this backup on three different installations (two physical machines and one virtual machine) with different operating systems. Despite using the same Automation Studio components on version 4.6, the error persists there, whereas on version 4.12 (only on the virtual machine, since the physical machines are affected by the previously mentioned AS corruption), everything functions correctly.

Best regards

4

Unfortunately, the original issue remains unresolved. Due to production needs, we proceeded with Automation Studio 4.12, updating various components as recommended (including mapSafety 5.24) and are now conducting some final safety tests before delivering the system to our client. While the production stoppage has been resolved by moving to version 4.12, the underlying problem itself has not been identified.
Best regards

5

I think I remember that with very old versions there where issues related to special characters in the path name or too long path names.
Does it also happen when the project is in a short and simple path (like c:\temp\)?

But actually I’m not sure if it was related to the project path or AS installation path (or maybe both)…