Error opening file

Hello, my co-worker received this error message when trying to get into his file.

He happened to be in the file when his network cable was switched from one outlet to another. Now he can't get into the file or even reference it into another drawing. I tried the -VRG option with the program shortcut, but it just causes Microstation to crash. I think the file is toast, but I wanted to see if anyone else has had this happen and what they did to resolve it. We have a backup macro that makes a backup copy of a file when you get into it, but unfortunately it made a backup of the corrupt file when he tried to get back into the file, overwriting the last good copy he had from today.

thanks,

Kevin

ms 08.11.09.929

Windows 10

Parents Reply Children
  • Assuming the version of MicroStation V8i is 08.11.09.829. The 0x13013 error code usually indicates you have quite a corrupt file on your hands. Generally, it would be better to retrieve this from your regular backups but it can be submitted to Bentley specialists for possible repair. We would need to be supplied with further information to try and recover this.

    Please provide the following files:
    - The file that is resulting in the errors above (already supplied)
    - A backup of the file in question.
    - The workstation's Exception history:
    -The machine's system and application event logs.

    To get the exception history:
    1.Open a good file.
    2. Key-in: $ % "$(ms_tmp)"
    3.Gather entire "ExceptionHistory" folder. (Typically there will be 5 folders, but there could be more; please send all of them).

    To get the system and application logs:
    1. Go to Start > Control Panel > Administrative Tools > Event Viewer
    2. Expand "Windows Logs" (in XP: "Event Viewer (Local)”) folder.
    3. Right-click on "Application" and select "Save All Events As…" (in XP: "Save Log File As...").
    4.Give it a name and save.
    5. Repeat steps #3 and #4 for "System".

    Notes:
    - DO NOT rename the DGN file. **This will make it hard to locate patterns related to this file in the exception history.
    - DO NOT try to open the file.
    - ZIP all the contents. *This is important to maintain file integrity during the e-mail trip.

    Regards
    Andrew Bell
    Technical Support
    Bentley Systems

  • Andrew, thanks for your reply. We were able to find a backup of the file from the previous day, so he only lost one day's worth of work. We don't need to delve further into the repair of this file, but it's just weird that the loss of network connection would cause something of this severity.
    Thanks again,
    Kevin