[V8i] OneDrive file errors ?

While working with a dgn file in a synced OneDrive folder I suddenly received this message in MicroStation: "Error opening file" [file path] = (0x13013)

The file is in a folder only I can access so this should have nothing to do with simultaneous updates by multiple users.

Now the file can no longer be opened in MicroStation. Additionally, if I attempt to copy or rename the file in Windows File Explorer I receive this error message: An unexpected error is keeping you from copying the file... Error 0x80071129: The tag present in the reparse point buffer is invalid.

The file is essentially locked and becomes unusable in any way. This happens randomly and some of my colleagues have reported the issue resolves on its own overnight but it's usually not practical to wait that long. The only solution I have found is using Command Prompt to run ChkDsk as described in this YouTube video (https://youtu.be/SMd2s1Em42Q). While this works and no dgn data is lost, it is frustrating because it requires admin rights and a restart that takes 10-30 minutes for full ChkDsk to be completed.

According to Reginald Wallace's reply in this post (https://communities.bentley.com/products/microstation/f/microstation-forum/232487/microstation-accessing-files-stored-in-google-drive) "ProjectWise Drive is the preferred (and certified) file exchange service for Bentley desktop products". My company has chosen to use SharePoint/OneDrive for project folders so I don't think PW Drive is an option for me.

Is there a known cause for this OneDrive error? Is there anything I can do to avoid it?

Is this an issue unique to V8i or does this also happen with CE? We are in the process of transitioning to CE.

Any assistance would be greatly appreciated. Thanks.

MicroStation V8i (SELECTseries 10) Version 08.11.09.931

Parents
  • One drive attempts to sync files to Microsoft's cloud service in the background. My suspicion, without proof, is that OneDrive and MicroStation are both working with the file at the same time and that while OneDrive is writing to the cloud service, MicroStation is changing the file under it and file corruption occurs. This is most likely a sign that OneDrive is ignoring the lock that MicroStation places on the file while it is in use. I have no idea why it would do this.

    One possible solution is to slow down the rate that MicroStation auto-saves the file this can be done with the MS_DGNAUTOSAVE variable. This variable sets how long MicroStation must be inactive before it auto-saves the file. It defaults to 2 seconds. This doesn't mean it auto-saves every 2 seconds, it means every time there is no activity in the file for 2 seconds.

    While we don't save dgn files to our OneDrive (as far as I know, I'm sure some user is doing it), but we have MS_DGNAUTOSAVE set to 10 seconds and I've yet to see a ticket on OneDrive corruption (I'm not the only support person so it's possible that others are handling it and I'm unaware of it).

    Some other things I would try:

    Make sure the OneDrive Files On Demand feature is off. This feature keeps stub files on the local machine until a program attempts to access them, then downloads the actual file. This maybe causing problems as well. It's in OneDrive's Advanced Settings. If you need to limit how much space OneDrive is using, you can use selective sync to only sync specific folders. You set this under your Account, there should be a "Choose Folders" listed to set which folders are sync'd to the computer.

     

  • Also, while you aren't sharing with others, is it possible you have multiple computers sync'ing your OneDrive for yourself? If you leave MicroStation open with a file on one computer while you work on that same file on another computer, even though you aren't sharing the file with other users you are sharing it with yourself and this can also cause problems.

    Also if you use print organizer with another computer while you work on files that's it printing I could see some potential problems arising from that as well.

     

  • Seems Onedrive is using some locking mechanism meant for backups so it creates file snapshot and then sync it. Regarding Microstation save mechanism it seems the incremental save fools it as doesn't save all file at once.

Reply Children
No Data