Can't STC - loss of network connection

[tonyisenhoff]

We have a handfull of users that are losing their network connection and are unable to STC... It is random in occurance, but it does seem to happen to some users more than others. We've never had this issue prior to Revit 2010. Many times, there is only one user working on the project and they're in their local file.

Our IT dept. has checked the network when this is happening and the network is fine. Other users in the office don't have any issues when this is occuring, so we're narrowing it down to the workstation.
The issue typically shows its ugly face when a user tries to STC. They will get one of two errors:

1. Central File doesn't exist at the path you provided...

OR

2. Central file is being accessed by someone else and is not available...

Here are some examples and what we've seen and our workaround:

User 1: "Central File doesn't exist at the path you provided" today.
Workaround: He got it to work by closing Newforma.

User 2 - "Central file is being accessed by someone else and is not available"
Workaround: Restart PC. Opened local and was then able to STC.

Usesr 3: Loss connection to the network. Couldn't STC or save his Word doc to the S: drive (unavailable).
Workaround: Waited ~5 minutes, then it worked.

User 4: Lost connection to the network. Could not STC
Workaround: Restarted his PC

I've attached a few of the errors we get when this occurs...

Any thoughts???

[cliff collins]

A couple of best practice items to check/confirm:

1. Have each user create a new local each day, by opening the Central and clicking "create new local". Overwrite the existing.

2. Make sure all users are on the most current and exactly the same build of Revit.

3. If you have linked files, make sure paths are set to point exactly to the same folder
on each user's machine to the server location.

4. Try rebooting the server at lunch or at a scheduled downtime.

5. As an extreme measure, Detach from Central, Save-as as a new Central, make new locals and Synchronize.

cheers......

[tonyisenhoff]

See reply below


A couple of best practice items to check/confirm:

1. Have each user create a new local each day, by opening the Central and clicking "create new local". Overwrite the existing.

We do this already...

2. Make sure all users are on the most current and exactly the same build of Revit.

They are...

3. If you have linked files, make sure paths are set to point exactly to the same folder
on each user's machine to the server location.

They are...

4. Try rebooting the server at lunch or at a scheduled downtime.

I'll have to check w/IT on this one...
cheers......

[tonyisenhoff]

Forgot this question...


A couple of best practice items to check/confirm:

5. As an extreme measure, Detach from Central, Save-as as a new Central, make new locals and Synchronize.

Some users HAVE to do this to fix the problem... but it appears to be a temporary solution

cheers......

[lhanyok]

We've been having similar errors, and haven't been able to pinpoint a solution that works each time. We also haven't been able to recreate the errors - at this point it seems kind of random. Associated with this, users have also been losing their license while they're in the middle of working. We've found that by going to the licensing dialog box and just clicking ok, they get their license back.

[anthony.67953]

I make sure I reboot my computer every morning. That works for me.