PDA

View Full Version : Locked Sheet Set



rmk
2006-04-05, 06:29 PM
I am using Autocad 2007. After I create a sheet set and dbl click a sheet, it shows it is locked. I'm running a stand alone single user license. The dwg files are on a server, but the sheet set file is on my local machine. Please help.

Opie
2006-04-05, 06:32 PM
Which one is locked? the Sheet Set or the Sheet? If it is the Sheet, that would be correct. If someone else opened the Sheet Set, they would see that sheet is locked and therefore would be in use.

rmk
2006-04-05, 06:41 PM
The sheets are shown with a lock symbol. I am trying to follow along the sheet view example. I am brand new to sheet sets. Trying to put a sheet view on a sheet. I have a named view, but it doesn't show up. I don't get the resource tab.

Mike.Perry
2006-04-05, 09:07 PM
Hi "rmk" ( Sorry, I do not know your real name )

Please note I have *moved* this thread from the AutoCAD 2007 General (http://forums.augi.com/forumdisplay.php?f=342) forum to this one, as I feel this particular forum is a more appropriate place for such a topic.

Thanks, Mike

Forum Moderator

Mike.Perry
2006-04-05, 09:14 PM
Hi

Plus, have you seen this thread ( What does the pad lock symbol mean next the DST name )...

Have a good one, Mike

alovinescu
2006-06-03, 12:28 AM
I have the same problem with the sheet set lock. I came to this site to find some answers, but no one seems to have any clear direction for what to do to unlock the sheet set. Could anyone possibly list the actions that are required to remove the lock symbol that is located on the left of the sheet set name?
Thanks in advance for your help,
Adriana

CADKitty
2009-01-19, 02:41 PM
Well, I know this thread is...wow, 3 years old now, but we're having the same problem and have found out a few things. We still don't know why this happens (it's only a few of our offices that seem to cause it) but we do now know how to fix it.

Should your Sheet Set be "locked" and you can't seem to unlock it, you have to search through Windows Explorer wherever your Sheet Set is located and find the ".dbl" file. Go through the properties to see who the "owner" is of the file, then contact them. Have them close the SSM and AutoCAD and then they have to delete the .dbl file on their end. Once that has happened the SSM will no longer be locked.

bgambrell
2009-06-09, 06:16 PM
We are having this problem too (repeatedly). I checked the dbl file and there is no one listed as the owner and I can't delete the dbl file. I am totally at a loss. If anyone finds a solution to this, let us know!!

Thanks,

RobertB
2009-06-09, 07:14 PM
What network operating system are you using?

There were known issues with Novell. There may still be issues with Novell.

amg
2009-06-09, 07:20 PM
Your system adminstrator will have to delete the .dbl file. We were having the same issue. Users in remote offices were locking the sheet set just by previewing a sheet. Turned out to be an issue with the Steelhead and how it configured the .dwg for faster performance.

bgambrell
2009-06-09, 07:27 PM
Thanks for the response, but as far as I know we don't run any Novell software in the office. Our server is running Windows Server 2003 SP2 (Standard Edition). Our workstations are XP Pro SP3.

I'm not sure, but it seems that the files might get unlocked after we restart the server, but we of course we can't restart our server at will (and interrupt everyone's access).

-Brad

jnoon
2011-03-21, 09:25 PM
I think I may have discovered the solution however it does require changing the server connection/ permissions for the user.

When you try and open a sheet set and see for example "company" shared (\\dmslocal) (S: ) you wil have locked sheet sets even if you created them. (dms is part of server name)

What you should see is "company" shared (S: )

Last time I ran into something like this it required the tech make a visit and change the permissions or something so I had full access to the server.

Probably not explained very well but I am sure if you point them in the general direction they should be able to figure it out.

john

jnoon
2011-03-24, 07:14 PM
Tech just remapped the server path and it fixed the problem even though it shouldn't have

john