No, that means there is no user security configured in the project and (I'm pretty sure) there never has been. Meaning the locks shouldn't be there.
Access-wise, there's no limitation on what you can view through the GUI or select from the database, so checking this stuff does not require admin privileges. And in any case, there is no admin for this project because security is not enabled.
What you might try, after ensuring you've got backups and stuff et cetera, is
enable security, use the admin account to clear all locks, and then disable security again.
There is also another obscure type of lock, although it shouldn't show up with exclamation marks.
You can test for it with a project browser script (go into the Scripting window, create a 'Project Browser' script group, and create a VBScript in that group) like this:
option explicit
!INC Local Scripts.EAConstants-VBScript
sub OnProjectBrowserScript()
dim treeSelectedType
treeSelectedType = Repository.GetTreeSelectedItemType()
Repository.EnsureOutputVisible("Script")
select case treeSelectedType
case otPackage
dim package as EA.Package
set package = Repository.GetTreeSelectedObject()
Session.Output "Package '" & package.Element.Name & "' locked: " & package.Element.Locked
case otElement
dim element as EA.Element
set element = Repository.GetTreeSelectedObject()
Session.Output "Element '" & element.Name & "' locked: " & element.Locked
case else
Session.Prompt "This script does not support items of this type.", promptOK
end select
end sub
OnProjectBrowserScript
Just replace everything EA puts in the script for you with the above, then right-click one of the offending elements / packages and select Script - (whatever you called your script). If it says False, it's not locked in that way either.
/Uffe
