Skip to main content
Apr 22, 2025 3:37 AM UTC
Solved

Trouble retrieving .gph file.

I am having issues trying to open a UDF from a folder in our Windchill library.

I get this error:

'wtpub://PDM-PD/Libraries/COMMON CAD/CAD Documents/user defined features/90-4118-795-000' does not exist in the database.

Caught exception: com.ptc.wfc.Implementation.pfcExceptions$XToolkitGeneralError

 

When I dig into the log, it looks like it is failing here:

Exception of type com.ptc.wfc.Implementation.pfcExceptions$XToolkitNotFound

XPFC Message: pfcExceptions::XToolkitNotFound

...at com.ptc.wfc.Implementation.WFCRemoteCommImpl.makeObject line: 5453

 

If I put the UDF "90-4118-795-000" into my working directory, it executes fine and places the UDF as expected. I have tried to retrieve the UDF in a sandbox code and get the same error, so it seems it is related to .gph files?

I can retrieve .prt files fine, so I am looking for any ideas on how to resolve this issue.

jbryant74Answer
Apr 28, 2025 7:59 PM UTC

I just noticed there is a typo in the error. The api seems to be placing an \ incorrectly

wtpub://PDM-PD/Libraries/COMMON CAD/CAD Documents/user defined features/SUSPENSION/SCHRADER/CORE INTERFACE ID CAP/\90-4020-795-000' does not exist in the database.

5 replies

AndrewK
Community Manager
Apr 24, 2025 2:10 PM UTC

Hi jbryant74,

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant.

Apr 25, 2025 1:44 PM UTC

Are you sure to have read and download rights for every cad user?

jbryant74AuthorAnswer
Apr 28, 2025 7:59 PM UTC

I just noticed there is a typo in the error. The api seems to be placing an \ incorrectly

wtpub://PDM-PD/Libraries/COMMON CAD/CAD Documents/user defined features/SUSPENSION/SCHRADER/CORE INTERFACE ID CAP/\90-4020-795-000' does not exist in the database.

Apr 28, 2025 8:21 PM UTC

Your URL contains a. couple of blanks, are you encode this with %20?

jbryant74Author
Apr 28, 2025 8:40 PM UTC

It turned out to be an input error issue.
Should have been 90-4118-795-000 I was looking for, not 90-4020-795-000.
Works now