Skip to main content
avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
March 3, 2025
Question

Cannot clear user from Personal Cabinet Administrator

  • March 3, 2025
  • 2 replies
  • 922 views

I have a user who has been deleted. Well, they have been deleted twice since I see two entries in WTUser table for them. The two accounts have different IDA2A2 in the WTPart table. One of those accounts shows up in the Personal Cabinet Admin to remove but fails with the following message:

DeleteUserCabinetList:wt.folder.Cabinet:969083953<username>
2025-03-03 16:19:51,314 INFO [ajp-nio-127.0.0.1-8010-exec-22] wt.system.err - (wt.epm.util.EPMResource/32) wt.epm.util.EPMCannotDeleteWorkspaceFolderException: Folder <workspace name> belongs to Workspace <workspace name> , and may not be deleted.

Ok, so I go to view other user's workspace as admin on my homepage. The two deleted user account appear but I am able to distinguish one from another. When I got to pull them up to clear the workspaces I see this error:

2025-03-03 16:47:42,863 ERROR [ajp-nio-127.0.0.1-8010-exec-4] com.ptc.windchill.uwgm.cadx.workspaces.WorkspacesPageContext - WorkspacesPageContext.getOtherUser :: (wt.fc.fcResource/18) wt.util.WTException: Malformed URL: "uid={wt.org.WTUser:969083949}<username>,<ldap path>". Format must be: "classname:idValue" 
Nested exception is: java.lang.NumberFormatException: For input string: "969083949}<username>,<ldap path>" (wt.fc.fcResource/18) wt.util.WTException: Malformed URL: "uid={wt.org.WTUser:969083949}<username>,<ldap path>". Format must be: "classname:idValue" 
Nested exception is: java.lang.NumberFormatException: For input string: "969083949}<username>,<ldap path>"

I can see the workspaces are tied to this user account id. I can see the second account was created from an upgrade event. I also get same message when I try to look up workspaces by that user's second account. 

2 replies

R
RandyJones20-Turquoise
20-Turquoise
March 3, 2025

Maybe try adding an x to the end of the name for one of the accounts in wtuser table - on test server.

And then see what happens on it.

avillanueva
23-Emerald I
avillanueva23-Emerald IAuthor
23-Emerald I
March 4, 2025

Do you mean the name field where it shows {wt.org.WTUser:<ID>}<username>? I did that on one of them but not sure it made a difference. Curious why it is showing the full LDAP path as this is a deleted user. I looked in remoteobects table and its not listed there. Curious where its getting this data from.

R
RandyJones20-Turquoise
20-Turquoise
March 4, 2025
@avillanueva wrote:

Do you mean the name field where it shows {wt.org.WTUser:<ID>}<username>? I did that on one of them but not sure it made a difference. Curious why it is showing the full LDAP path as this is a deleted user. I looked in remoteobects table and its not listed there. Curious where its getting this data from.

That is what I meant. I thought maybe adding to the wtuser.name eg:  {wt.org.WTUser:<ID>}<username>x would help you distinguish between the 2. Article https://www.ptc.com/en/support/article/CS94037 gives good information on the relationships between the 5 tables dealing with wtusers.

I did some quick poking around and found that for my system deleted users only exist in wtuser table eg: {wt.org.WTUser:<ID>}<username>.

I did not find any trace of them in the other 4 tables.

The remoteobjectid.remoteobjectid field is where the ldap path is kept - at least for non deleted users.

R
rhart16-Pearl
16-Pearl
March 11, 2025

Some objects such as BoM Notes go into into a TransWS workspace rather than the normal CAD/WTParts workspaces. I found this out when a users account was deleted from AD before they had a chance to check-in their work and it kind of went down hill from there.

Terms & ConditionsCookie settingsAccessibility statement