cancel
Showing results for 
Search instead for 
Did you mean: 

PowerDesigner Error: You cannot get exclusive access to a model document

Former Member
0 Kudos

I just updated a physical model from the database and was able to save it in the workspace. But when I tried to check it into the repository, I kept getting the error message: You cannot get exclusive access to the document 'my PDM name'. And the warning message says my model file was openned in read-only mode. Does any one have ideas what is causing this and how to fix it? Any help will be appreciated.

Accepted Solutions (1)

Accepted Solutions (1)

former_member185199
Contributor
0 Kudos

Hello,

depending on the rights you have on the repository you could check the following:

- Does someone else has a lock on this Model?

- are you self blocking the model because of an earlier breakdown of PD?

To solve the problem i would try to check it in as a new baseversion or complete new file

or checking out the previous Model and MERGE it with your local one, then check it in again

HTH

Former Member
0 Kudos

Dirk, Stefan,

Thank you both for the quick and helpful reply. The issue has been resolved. Below are my findings and what I did.

1. I checked the List of Locks in the repository - nothing was locked.

2. I checked out the previous version of the model from the repository and merged it with my local one, and then tried to check it in again. I got exactly the same error message - I cannot get exclusive access to the model document.

3. I asked our Admin. who has the full privilege to try to check in the same model from his local to the repository. His check in didn't go through either.

4. Then the Admin. deleted the model from the repository and let me check it in as a complete new file. That worked.

We think the model was indeed locked in the repository but for some reason the lock was not showing up in the List of Locks. Not sure why.

Dirk mentioned if I could be self blocking the model. I'm wondering how to check if I'm self blocking something on my local.

This is a very good learning. Now we learned how to deal with it next time. Thank you both again!

Ling Guo

former_member185199
Contributor
0 Kudos

Guo!

You should further investigate, deleting and creating new lets you loose all previous versions.

Normally when you block yourself (or someone else is locking) then you get a message if you want to bypass this lock. I don´t know why this did not happen in your case

But anyway, happy working and a nice weekend.

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Here's a solution that does not included dropping the historical versions of your repository model.

It looks like the problem occurs when a model check-in is not completed by a user.

I'm not entirely sure all below steps are necessary, but this is what worked:

1. From the local model that is failing check-in, copy the changed objects to another model for back-up purposes and save that model.

2. Remove the failing local model from the workspace AND the filesystem

3. Reboot the machine that is causing the exception.

4. As an admin; Go to the Repository > Administration > Locks... window

    You'll not see the locks that you expect to see.

5. As an admin; Add a lock for the model that you want to unlock.

    You'll get the message, saying that you cannot get exclusive access.

6. Bypass the protection

7. As an admin; Remove the lock that you've just added.

    Your model is now unlocked.

8. As an admin; Check out the model and check it back in to make sure a new version number is created.

9. Let your user check out the model from the repository and copy back the changed objects.

10. Check in the changed model et voila.

This worked for us; hopefully it'll help you too!

Cheers,

Rudy

former_member186838
Active Participant
0 Kudos

Hi,

it seems that the document is locked for some reason by another user or a second instance on your PC. Did you check the LOCK in the repository?

Repository admin can use PD menu -> Repository -> Administration -> Locks

to view the list of locks and remove the document from list.

BTW i remember an old issue with locks in an older PD 16.5 version. Use the latest and greatest PD version

HTH

Stefan

Former Member
0 Kudos

Dirk, Stefan,

Thank you both for the quick and helpful reply. The issue has been resolved. Below are my findings and what I did.

1. I checked the List of Locks in the repository - nothing was locked.

2. I checked out the previous version of the model from the repository and merged it with my local one, and then tried to check it in again. I got exactly the same error message - I cannot get exclusive access to the model document.

3. I asked our Admin. who has the full privilege to try to check in the same model from his local to the repository. His check in didn't go through either.

4. Then the Admin. deleted the model from the repository and let me check it in as a complete new file. That worked.

We think the model was indeed locked in the repository but for some reason the lock was not showing up in the List of Locks. Not sure why.

Dirk mentioned if I could be self blocking the model. I'm wondering how to check if I'm self blocking something on my local.

This is a very good learning. Now we learned how to deal with it next time. Thank you both again!

Ling Guo