topic Impossible to add models to Creo Workspace in Windchill

Impossible to add models to Creo Workspace

CG_14509797 — Thu, 05 Mar 2026 13:51:27 GMT

Version: Windchill 12.0

Use Case: New users with Windchill access can add models to their workspace from the browser and edit them, but when they try to do so from CREO, it's not possible. Error message

Description:

New users with Windchill access can add models to their workspace from the browser and edit them, but when they try to do so from CREO, it's not possible. Error message:

"Server error: wt.util.WTRuntimeException: ATTENTION: Secured Action. You do not have the necessary authorization for this operation. Contact your administrator if you believe you have received this message in error. Nested exception is: (wt.access.accessResource/19) wt.access.NotAuthorizedException: ATTENTION: Secured Action. You do not have the necessary authorization for this operation. Contact your administrator if you believe you have received this message in error."

In the browser, you can see all the models in the workspace. But the Creo workspace is empty.

I'll appreciate your help.

Thanks,
Carlos

Re: Impossible to add models to Creo Workspace

TDT — Thu, 05 Mar 2026 16:30:58 GMT

Hi @CG_14509797,

Did you get a chance to check the Method Server log?

It should contain more details related to the error.

Re: Impossible to add models to Creo Workspace

CG_14509797 — Thu, 05 Mar 2026 18:16:25 GMT

This issue was resolved by the IT team and PTC consultants. If anyone encounters a similar problem, here's what happened:

The company I work for used to have a longer name, but changed it to a shorter one a couple of years ago. Currently, all models are associated with the new, shorter name. However, when user IDs were created, IT used the old name. As a result, some users still had access tied to the old name despite everything now being under the new name.

In a nutshell, imagine we had folders labeled "old" and "new." New users were mistakenly given access to the "old" folder instead of the "new" folder. To rectify this, the old folder was removed, and access was transferred to the new folder to prevent this mistake from happening again. Problem solved.