Problem

When run from a OneDrive-synced folder, SACS cannot overwrite the locked Postvue file - manually deleting it first (or running the analysis from a local C: drive) restores successful Postvue generation. 

Solution 

Although OneDrive itself shouldn’t block analysis, Windows can fail on paths longer than 260 characters. To eliminate this possibility: 

• Move your project to a folder whose full path is under 260 characters.
• Rerun the analysis. If you still see errors, ask your IT team whether your system enforces additional OneDrive folder restrictions. 
  
  

Issue with OneDrive -  “Cannot Merge Changes” error

There's an article that describes the resolution for this issue, see: https://www.technipages.com/onedrive-we-couldnt-merge-the-changes-in-office-file/

OneDrive Troubleshooting:

1. Reset the OneDrive Sync App.
2. Disable Autosave on the problematic files.
3. Repair Microsoft Office. via Control panel > Programs > Office > Change > Repair (please seek IT/Administrator assistance).
4. Avoid simultaneous edits - ensure only one user or process opens the same file at once.
   
   

Bentley recommends running SACS analyses on a local drive (e.g. D:\) rather than directly in a network-shared or OneDrive-synced folder to avoid file-locking and execution errors. Working locally ensures reliable result generation. 

1. Copy the entire project folder (including .sacinp) to a local drive (e.g., D:\Projects\MyJob).
2. Run the SACS analysis locally so that no sync user locks the result files. 
3. Verify that the new .psvdb opens successfully. 
4. Move the completed folder back into OneDrive for sharing.
   
   

Implementing these steps should eliminate manual deletions and restore smooth Postvue generation.