PDA

View Full Version : Moved Central File and there are problems



mmiles
2008-12-29, 05:06 PM
We moved our files to a new server over the holidays. Now, I have opened a workshared file, performed a save-as with option to make new central file. Then, I performed another save-as to make the local copy on my machine (i am the administrator, too). there were no problems. But, my colleague opened the central and did a save-as to make a local copy....but she cannot do anything in that file. Every edit results in an error: "permission to edit the element cannot be obtained".

Of course the deadline is looming large....and we are bleeding money and time....can anyone help? What is the possible problem?

Also: not sure if this means anything, but the last saved view in the central file contains a jpeg in the background. when this colleague opens the central the screen which is normally white, is black (like in ACAD) until I turn off the raster image visibility.

thanks!

twiceroadsfool
2008-12-29, 05:10 PM
You didnt STC after you made the central file, so im betting if she goes in the workset dialogue, you have everything checked out.

Although that would be a different warning (have xxx user STC and reload latest...) The "permission to edit the element cannot be obtained" sounds like a file permissions issue on the new server. Are you sure you all have editing rights on the new files?

mmiles
2008-12-29, 05:16 PM
opened central>save -as (create central file). Save as>to local directory>stc
then she opened central>save as>to local directory. errors began.

twiceroadsfool
2008-12-29, 05:21 PM
First...

You need to Open > save as (create central file) > Save to Central (relinquish every element).

EDIT: I see that youre doing that STC after creating your local. Not sure if that would cause the issue, but i STILL think thats not the correct error message for that issue. It sounds like something else.

FWIW, she shouldnt open the central to make a local anyway. Use windows explorer, copy the central to the local machine, rename, then open. We (as a practice) dont let anyone in central files...

mmiles
2008-12-29, 05:54 PM
....so I reversed the process and created a new central file (save-as central) then STC. Then, copy/paste/open and rename to create local. we did this from workstation producing errors. and, this time she made local copy first. Now, I am the one getting the errors about permissions.

also we have received this error too: "a generic error has occurred".

twiceroadsfool
2008-12-29, 06:27 PM
Yeah, like i said in my first post... i dont think its the process, or anything in Revit. I think its a permissions issue on the server, personally...

mmiles
2008-12-29, 07:03 PM
okay, let's say it is... I do not understand why one person (whomever makes local file 1st) would be able to connect to the central file while no one else can. If you told me I could because I have administrative priveledges I would say, sure okay. But the fact that a power user can make and edit a local file and an administrator cannot after the fact doesn't jive with my understanding of rights. I

I am having our IT mover and shaker take a look at the general security settings. And, I hope it gets resolved soon, as I have already lost 2/3rds of a days work x 2. thanks for your input, i appreciate the quick reply.

twiceroadsfool
2008-12-29, 07:10 PM
Ive seen permissions set up where the person who creates the file on the network has edit and write access to it, but no one else.

For instance, YOU make the central, then go to HER computer and make a local, and it cant "talk (edit/write)" to the central file. Only your computer can.

Then, you reversed the process and did it from her machine, and now YOU cnat talk to the central file.

Its just a shot in the dark...

mmiles
2008-12-29, 07:29 PM
sounds feasible....I understand that.
believe it or not, I am now using ACAD files (different project) from 1996 before layouts were created. It's just one headache after another today!
thanks again.

mmiles
2008-12-29, 08:50 PM
problem solved. Permissions on server was culprit. thanks.

twiceroadsfool
2008-12-29, 08:59 PM
Glad you got it sorted... :)