Can't export a partition since it is grayed out

hrricane34 - Wed Nov 09 20:24:46 EST 2011
Yes, I did create a partition definition and not a partition. While the exported partitions tab shows an exported partition, it is an old one that is not associated with the new partition definition.

Upon further inspection, I did find 2 link modules that show me as having read only access despite what the access rights indicate. The module properties do show inherit from parent checked and that I'm in a group that should have RMCDA access yet the bottom of the access screen shows that I only have read access. Both of these link modules need to be in the partition definition with RMCD access.

I think these 2 link modules are creating the problem. Is there any way to remove the read only lock?

SystemAdmin - Wed Nov 09 21:48:42 EST 2011
I'm assuming here that there are no conflicting access rights here - that you only get your access rights from being a member of a group and that you don't also have individual user rights assigned to you - individual user rights have precedence over group rights.

If the above is true then I hazard a guess that the read lock is because those two link modules are possibly members of the already exported partition that you observed in your last post.

Have a look at the definition for that exported partition and see if the two link modules are included in that definition and have been defined to be modifiable. If this is the case, then the access rights assigned to these two link modules will be overridden by a read lock imposed by the exported partition.

The exported partition needs to be either returned using the Rejoin button, or the exported partition is junked and not returned by asserting a forcible return using the Recover button - both buttons are in the Exported Partitions tab.

hrricane34 - Wed Nov 09 21:59:55 EST 2011
The partition has already been returned into the home database and I do have the correct access rights to all of the other modules that were in the partition definition. Regardless, even if I logon as the DOORS Administrator I still don't have access to the 2 link modules.

Those 2 link modules are not a part of the old exported partition. In the past, I have been able to send these 2 link modules in the partition with RMCD access and was also able to import them into the home database without any issues. I don't understand what made a change this time.

I can't recover the partition since there is no partition to recover, other than the old one but this partition contains other modules that I'm not interested in.

What I don't know yet is the version of the client that the away database is using. In the past they were using 8.x and the home client was 9.x and there were issues but the away database was supposed to upgrade their client to 9.3 5 months ago. Unfortunately they are gone for the day and I didn't get a response to their client version. I'll advise once I get it.

SystemAdmin - Wed Nov 09 22:22:52 EST 2011
Just going back to your earlier post you wrote "...While the exported partitions tab shows an exported partition, it is an old one that is not associated with the new partition definition..."

I just want to be clear because the Partition feature of DOORS can be a little nefarious at times - are you saying that the definition for the exported partition that currently appears in the "Exported Partitions" tab does not include those two link modules?

hrricane34 - Wed Nov 09 21:59:55 EST 2011
The partition has already been returned into the home database and I do have the correct access rights to all of the other modules that were in the partition definition. Regardless, even if I logon as the DOORS Administrator I still don't have access to the 2 link modules.

Those 2 link modules are not a part of the old exported partition. In the past, I have been able to send these 2 link modules in the partition with RMCD access and was also able to import them into the home database without any issues. I don't understand what made a change this time.

I can't recover the partition since there is no partition to recover, other than the old one but this partition contains other modules that I'm not interested in.

What I don't know yet is the version of the client that the away database is using. In the past they were using 8.x and the home client was 9.x and there were issues but the away database was supposed to upgrade their client to 9.3 5 months ago. Unfortunately they are gone for the day and I didn't get a response to their client version. I'll advise once I get it.