Wednesday, November 28, 2012

2013 Revit Server : Warping Constant

FROM:
http://www.appliedtg.com/techblog/index.php/2012/08/09/2013-revit-warping-error/


2013 Revit: Warping Constant: Troubleshooting Information Required

source : Autodesk Technical Support

Issue:

Revit 2013 message Warping Constant keeps popping up preventing the opening of a central file

excerpt from Autodesk Technical Support:

The error

Actually means “file not found”. The reason it displays improperly is a conflict between Revit and Windows. The most common cause for that error is that during the time period that the first Revit session creates the model on the server, but does not finish upload data yet, a second session of Revit tries to access it. Even though the user can see the file, it is not complete and should trigger a “File not found” error.

I have some questions that will help me troubleshoot this issue:

Does their server have DFS?

Are all machines accessing the central file the same way (same mapped driver letter vs. UNC)?

Does this happen in all files?

What operating system is their server running?

Please also reply with the journal file from a session where a user got that error.

Where are the workstations and servers physically located?

Are they on the same domain? If not, how are they connected?

What is the ping times to and from the workstations and server?

If you copy a file of similar size to and from the server using Windows Explorer, what is the actual throughput?



Other helpful files:
Provide the log files from the accelerators
Provide the project files

Observations and Analysis:

As I mentioned, there is a mismapping that can sometimes occur where Revit shouldsay “File Not Found” but instead says “Warping constant.” In both of the journals supplied by the user, there is a save to central that fails, followed by an attempt to sync with central. Since the central model on the server was not correctly saved, the SWC does not succeed. In both cases, the user should expect to receive a file not found message, but instead they get the warping constant one.
As for why the initial save failed; it looks like that in one case, it is because they are attempting to overwrite an existing central, which is not supported. In the other case, it looks like a network glitch in the middle of an operation.

If there is a network switch between the workstation and server, I would try resetting it. otherwise, when users get errors about not being able to save or sync, they should wait a minute or two then try the exact same operation again, not different operation.

Closing Remarks:

One thing we are starting to see with 2013 is that it has much more problems with WAN accelerators (Riverbed) than 2012 had. If you havea WAN accelerator, I would try exempting the Revit traffic from it to see if the behavior changes.