Revit Error: Cannot make Editable on the fly in At Risk environment

Revit Error: Cannot make Editable on the fly in At Risk environment

Anonymous
Not applicable
1,875 Views
6 Replies
Message 1 of 7

Revit Error: Cannot make Editable on the fly in At Risk environment

Anonymous
Not applicable

Does anyone know what this message is about. I assume that it could be related to the none Editable Workset warning that you can only cancel, but I do not know what this is really about?

0 Likes
Accepted solutions (1)
1,876 Views
6 Replies
Replies (6)
Message 2 of 7

RobDraw
Mentor
Mentor

Please provide a detailed description of what were you doing at the time.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 3 of 7

Anonymous
Not applicable

Someone sent me this issue while he was managing sheets. It may have something to do with Worksets Editable and other people in the central model at the time, but once he click the Close button on the dialog window, Revit allowed him to proceed.  

0 Likes
Message 4 of 7

ToanDN
Consultant
Consultant

What is "managing sheets" exactly?

0 Likes
Message 5 of 7

loboarch
Alumni
Alumni
Accepted solution

Well "Editing at Risk" means you do NOT have a connection back to the central model.  Without that, if something was not checked out to you before you went "at risk" then it can't be made editable.  You can only alter the things that were editable when you went "at risk".  If this person is not working remotely or working on something off the network, then you need to investigate their network communications, something is broken there.  if there are intending to work "at risk" (off the network) then there are limitations they have to accept.



Jeff Hanson
Principal Content Experience Designer
Revit Help |
Message 6 of 7

Anonymous
Not applicable

The project is in a cloud network environment; and we have had some network latency between data centers. Thank you for the explanation.

0 Likes
Message 7 of 7

Basam.Yousif
Advisor
Advisor
How about a user in the office, wired into the network, and working on a traditional workshared model? where do I look for signs of trouble? what could it be?
0 Likes