Hi!
We updated our MicroStation from 11 to 16 and we lost our "File in use"-notfication. Now MicroStation just opens file straight with read only mode, without specifying who is the user that have the file opened.
Has anyone else noticed this behaviour or is this just somekind of bug on our end ?
In big office this is really frustrating when you dont know the exact person who you could ask the releasing the file.
-Joonas
Just noticed same behaviour trying to fix this corrupt file. It also opens after repair as read-only without notice and most tools do not work. Interestingly that implanting model header from seed file it can be opened normally. Seems it is another indication of file corruption.
Hmm.. Interesting. In our case that is not file-spesific and all the files works normally whenever some other user is not using the file. Only the notification has disappeared.
Do a restoredefaults action. Upgrading corrupts user preferences, had also strange defect after upgrade.
This method didn't work for us.
Hi Joonas Salmi,
How are you opening the files? From File\Open or by dragging the file and dropping it on MicroStation desktop icon?
Could you please check if the results are the same?
Are your files saved locally or on the network?
Do you know if there were any changes in the environment? Maybe Windows updates?
Do you know how MS_READONLY configuration variable is set?
Maria Garcia
We are working from the network drive. So basically what we do is open documents from the windows file explorer with new MicroStation instances by double clicking files to open.
There has been no other updates but our MicroStation update as I'm aware of when this started happening.
I noticed that MS is sending the right message but only the pop-up is missing.
I know the MS_READONLY is currently [undefined]. I tried to toggle it to 1 and back to 0 and deleted it but no effect.
I did check if the way of opening the file affects anything but it didn't.
Just for information we ended up making a own VBA popup for this as it was just a small addition to existing code. I think this is a bug but we cannot do full uninstall/install to test if that works for this (too much configurations). Hopefully future updates will have an effect to this.
Joonas Salmi said:We are working from the network drive.
Is that network drive on a server, or is it a self-contained network drive connected to your network without a server?
Sometimes the latter will give you this kind of problem.
Rod WingSenior Systems Analyst
Hi Joonas Saimi ,
To reproduce issue faced at our end
1) Is it possible to share configuration settings from machines where alert box is missed? ( keyin - Show Configuration)
2) Is batch processing used on machine? If yes, which workflows are process?
Thanks,
Swapnil Kanade