Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Chronic Central Connectivity Issues

1 ANTWORT 1
Antworten
Nachricht 1 von 2
BethEvanoo
480 Aufrufe, 1 Antwort

Chronic Central Connectivity Issues

I present to you, the mystery of the chronically ill central file. Involved are offices in different states (Hancock, MI and Columbus, OH), a cloud server system (Panzura), and likely user error (a new Revit user with very little experience). While it seems like it is a server issue, the fact that it is just this one project file, and no others, in a large firm, is odd. I've documented the facts below.

   

If anyone has insights into this mystery, I would love to hear your hypotheses. Thank you.

 

2018/09/12

Error: An unknown error occurred while accessing S-CASD_Aux_Gym_2018_CEN

 

Hancock office users unable to sync to central. Error above displayed.

 

I am able to open a new local and sync. I create a new central from my local, but users in Hancock cannot open new locals from the new central. I remotely access user's computer in Hancock, and create a new central from his local. Other users are able to open new locals and sync to central.

I suspect it is a server issue. We have Panzura to connect our 14 offices. There are two server paths for project files. One is \\[company]\dfs\Corporate\Projects, which is the "Central Model Location" in the sync dialog. The other is P:\, which is what our local computer explorers are mapped to. I don't know if this could have any implications for access issues.

 

2018/09/13

IT resets all permissions on the project folder. No issues reported for three business days.

 

2018/09/18
Error: File not saved.

 

All users, including myself, cannot access the central model to create new locals (Image: 20180918_Error_File not save). I cannot save a new central to the folder.

IT resets all permissions on the Revit folder. I can now save a new central and open a new local.

 

2018/09/19
User cannot access elements in the model. Other user did not open a new local from new central on 2018/09/18, and still owns elements.

 

2018/09/21
Error: An unexpected error is keeping you from renaming the file. If you continue to receive this error, you can use the error code to search for help with this problem.

 

Error 0x8007003B: An unexpected network error occurred.

 

12pm: A power surge/outage occurred in Hancock during lunch time.

 

4pm: Users cannot access central at all. Above error received when I tried to change the existing central name for archiving (Image: 20180921_Error_Renaming). I am unable to open the file. The "unable to access central" dialog hangs for an indefinite amount of time.

IT requested to reset permissions. I create a new central on a temporary drive, so users can continue to work while waiting on IT, as it is after 5pm on a Friday and response is uncertain.

 

10pm: IT resets permissions. Users continue to use the temporary central location over the weekend.

 

2018/09/25
New central created back in the project folder. Users go back to working on locals from this central.

 

1 ANTWORT 1
Nachricht 2 von 2
SteveKStafford
als Antwort auf: BethEvanoo

What does "resets permissions" mean? If file/folder access is changing while files are being accessed that can't be good. This is what makes me most nervous about what you wrote.

 

The path that all users PCs use must be the same as the PC that was used to create the central file. The P: drive is a local mapping to a shared resource that uses UNC syntax which is what Revit really sees. The discrepancy of mapping a drive via IP address versus UNC or Named Location is where the issue shows up.

 

If the Create New Local option is disabled (on a project that it normal isn't) that user should not continue to open the project. They won't be able to sync at all. The path needs to reconciled first.

 

If possible, set it up to work in one office (eliminate Panzura from the equation briefly) for a few days and see if any issues occur. If your EyeTee folks are happy to just blame Revit rather than dig into their own infrastructure it will be hard to pin down. It is much too easy to say well all the other software we use is working fine, it's just Revit. No other software in we use works exactly like Revit does though, no other challenges any system's weakness like it does.

 

For example, in one office IT tracked issues down to a single switch for part of the office. Once they replaced it the team got down to work with no more hiccups. It only affected one team for awhile because they were divided across different switches, network wiring path. When a second team that shared that path started complaining they looked at their own system more closely. That's how it was loosely told to me, they tracked it down after my training time with them had ended. I got asked about issues on a break and they sorted it out later.


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.

In Foren veröffentlichen  

Autodesk Design & Make Report