Local file not compatible with central

[chris.macko]

We've been having some problems lately with one users local file randomly giving her the error that her file has become incompatible due to the same object being edited in both files. There are 3 of us working on the project right now, all with our own local files saved on our workstations. This happened yesterday too, but since there weren't any major changes made since it last saved successfully, we just created a new central file and made new locals from there. This time there were more changes by both users so we would be losing some work by throwing away the local.
Has anyone had this kind of thing happen? I thought revit wouldn't even allow 2 users to edit the same element, so i'm confused as to why this is happening at all. We are using 2008 and nobody has been working in the central file other than to create locals.

[Scott Womack]

Chris, What type of network, are there athentication servers being mirrored? How fast is your network, and are you using the Worksharing monitor? How may Revit or AutoCAD files are linked in, and have you imported any AutoCAD files? How big is the central file?

[xiqx]

Could it be that someone has been accidentally working in the central file?

[bcgatti]

I've seen this happen when a user accidently opens the Central file for editing.

[twiceroadsfool]

Ive also seen this happen when two users have the same "name" under Settings > Options.

Basically, one person is invalidating the other persons work. Check all the users names and make sure no two are the same...

[chris.macko]

Ive also seen this happen when two users have the same "name" under Settings > Options.

Basically, one person is invalidating the other persons work. Check all the users names and make sure no two are the same...

Looks like that was the problem. Two us recently had to reinstall revit due to some graphics driver issues and they had to be installed by the administrator. So sure enough, revit picked up that login name as its username.
Such a simple fix too. Thanks for the catch!

[twiceroadsfool]

ive done that myself a bunch of times, thats why i figured it was that.

Glad you got it sorted out...