Files opening as Read Only

Files opening as Read Only

When files on a file server (not a local drive) are opening in Solid Edge as "Read Only" (often being listed as Available, with the current user listed in the Read-Only message) please try one of the following:
  1. Have an Administrator connect to the file server and open up Computer Management, then under System Tools, Shared Folders, go to Open Files and look for the offending file
    1. This will tell you if the offending file is open by anyone else, and if there are any file locks on it.
    2. If the file has a file lock on it AND the user reports the file is now closed you can clear the file lock by right clicking and choosing "Close Open File"
      You should not do this unless the user no longer has the file open, otherwise they will loose any edits made.

  2. A reboot of the server will normally fix this issue, but you should ensure that it is done when no users have files open, otherwise they will loose any edits made.
    1. Rebooting the file server periodically during off hours can help mitigate or minimize this issue as well, so is a good file management practice.

    • Related Articles

    • Solid Edge 2022 managed (SEDM) files not fully indexed - Workaround

      There is a known issue found in Solid Edge 2022 Built in Data Management, introduced by a change to Windows Indexing, that causes files in the Solid Edge Vault to not be fully indexed. Microsoft are working on a fix, but until that is completed, ...
    • Tip - using the Solid Edge 2023 Open-Save Macro

      Tip - Run the Open-Save Macro It is often helpful after upgrading Solid Edge to a new version to also update all of your files to the new version too (this avoids some issues we have seen with working with very old files). The Open-Save macro is ...
    • NOTICE: Problem with SE2024 Update 02, Build 003

      It has come to our attention that on the first day that Solid Edge 2024 Update 002 was released, the incorrect build (003) was posted to the Siemens Download Center instead of the correct build of Update 002 which is build 004. The incorrect build ...