Corrupt revit files over the network

[Wagurto]

Hi guys, I'm having problems when I open a file over my LAN. The files get corrupted and useless. I used to have my library on mapped network location and every time I open a file it gets corrupted. Does anyone knows if this is a bug?
Thanks

[dhurtubise]

Never happen to me but here's a few suggestion :
- Use UNC path instead of Map drive, Revit reverts everything to that anyways
- Use fix IP adress for your Revit machine at least instead of DHCP
- Make sure you have the least latency possible. That means use GB networks with good hardware

[studio3p]

What does UNC path describe? I don't think I've heard of that before.

We were having very regular file corruption issues a few weeks ago. Autodesk Tech Support told us that we should be using Worksets for all of our network files, even those on which only 1 person is working. We've been following their suggestion since then and have had no subsequent file corruption problems. Revit still crashes way more regularly than seems reasonable, but the files are no longer being destroyed.

[Wagurto]

Thanks for the info, and thanks for the work around but if this is a known issue the factory should be issuing a patch or something to correct this problem. I remember having the same issue with release 9 and there was a patch at that time is it one available now?

[dhurtubise]

UNC path stands for Universal Naming Convention. It means that instead of K:\Revit you get \\Servername\Share\Revit.

As far as being a bug, i doubt it since it never happened to me at all. There must be something else related to your network setup.

[mlgatzke]

Autodesk knows about this issue. It's actually existed for a few years now. Autodesk Support told me that there is a known "issue" with Revit saving over a network. Apparently there is a problem with Revit's error correction algorithms over a network. Their solution is to copy the file to a local folder, work on it from there, then copy it back to the network location when finished. I toasted a couple of files by saving over a network, but have had absolutely NO problems working with a local file.

I know this sounds ridiculous, but it's what Autodesk Support told me and it's worked for me so far (about 2 years now).

[Mr Spot]

That's interesting as I can honestly say I've never had issues saving over a network and I do it every day...

We only have a CAT5e network on a 100MB network running Windows Server SBE 2006 so its nothing special...

Files are saved sometimes with UNC and sometimes with mapped drives. Server is running 3 drives in RAID 1.

Guess we must be lucky. TOUCH WOOD!

[truevis]

Just this morning I was making a new Central for a new Project. I used copy/paste into a new folder and Revit said it was corrupt with the dreaded "manual"-something message. I copied the RVT again using Total Commander and all was fine. I assume there was some hiccough on the network during the first attempt.

Remember Xcopy has a /V switch for verify. There must be some reason for that. Perhaps different copy methods are more reliable than others.

[Wagurto]

I've been told by Revit technical support that I should work only in local machines, or use workset even is only one person working in the project.
All these sounds as workaround and shouldn't be happening I just wondering why some peoplo has this problem and others don't. Any clues?

[Elmo]

Could simply be your network speed. I had a client have problems with his Autocad LT 2007 with saving over the network. We got their IT to change his network speed to always work at maximum speed which fixed the problem right away.

[Wagurto]

Well I have a GB router and each computer has GB ethernet card I think that's the best you can get on the market right now. I don't think that's the problem. Any other ideas?
thanks!