Accessing model in central file

[fjtdogeno]

Hi Guys,

What is the cause of this and how can be avoided? Any suggestions?

Many thanks,

[david_peterson]

There's many causes for it.
If someone is saving, they're accessing the central model.
If someone is opening, they're accessing the central model.
If someone is loading that file as a link, they're accessing the central model.
If someone is opening a file detached, they're accessing the central model.
If someone is opening a file detached and that file is linked into it, they're accessing the central file.
If someone is looking at the file history, they're accessing the central file.
If someone is trying to save back a shared coordinate from another model, they're accessing the central file.
If someone is Looking at the worksets dialog box, adding, renaming or editing, they're accessing the central file.
I think that's about all the normal ones, and they're nothing you can do about it. Other than not having them do that action.
If you're working on a file, and this is happening and everyone swears they're out of the model or not doing anything, Check your server log.
If someone is trying to open a file across a WAN there's a good chance it hung the central file and you'll need to kill that connection.
If someone was working off site and VPN'd into your office from home and saves, that can cause the file to hang for about 15 mins but usually resolves itself.
If someone was opening or saving the file and walked away from their desk, and an error popped up or the it looking for a user input (to clear the error or select the worksets to open), that'll hang the file.

The long and short of it is you can't "Do" anything about it other than wait if it's a normal process.
And fixing the other issues comes down to education.

I think I got all of them, but if I missed any feel free to add to the list.

[fjtdogeno]

There's many causes for it.
If someone is saving, they're accessing the central model.
If someone is opening, they're accessing the central model.
If someone is loading that file as a link, they're accessing the central model.
If someone is opening a file detached, they're accessing the central model.
If someone is opening a file detached and that file is linked into it, they're accessing the central file.
If someone is looking at the file history, they're accessing the central file.
If someone is trying to save back a shared coordinate from another model, they're accessing the central file.
If someone is Looking at the worksets dialog box, adding, renaming or editing, they're accessing the central file.
I think that's about all the normal ones, and they're nothing you can do about it. Other than not having them do that action.
If you're working on a file, and this is happening and everyone swears they're out of the model or not doing anything, Check your server log.
If someone is trying to open a file across a WAN there's a good chance it hung the central file and you'll need to kill that connection.
If someone was working off site and VPN'd into your office from home and saves, that can cause the file to hang for about 15 mins but usually resolves itself.
If someone was opening or saving the file and walked away from their desk, and an error popped up or the it looking for a user input (to clear the error or select the worksets to open), that'll hang the file.

The long and short of it is you can't "Do" anything about it other than wait if it's a normal process.
And fixing the other issues comes down to education.

I think I got all of them, but if I missed any feel free to add to the list.

Thanks for this Dave.

Cheers