Skip to main content
M
MH_1036695710-Marble
10-Marble
December 5, 2022
Solved

Toolkit Scripts Receiving failed to start error.

  • December 5, 2022
  • 2 replies
  • 8850 views

Creo Toolkit registry file xxx/creotk.dat : application 'xxx' failed to start; see trailfile for details.

 

I am receiving this error when I am trying to launch some OTK dll script in Creo 9.

 

I am using Object Toolkit C++ on Creo 9.0.1.0. I am updating OTK scripts that all worked successfully on Creo 5. However, now, after updating everything, I can get the DLL's to all compile successfully, but after unlocking the scripts and registering them in the Registry file, only some work while the others receive the above error. Is there another location where the error details appear so I can do some more trouble shooting?

 

Any and all help would be greatly appreciated.

 

Thanks,

Mark Hardebeck

Best answer by YaroslavSin

The lib is a dll file? Try to add full path to dll folder into environment variable PATH.

2 replies

M
MartinHanak24-Ruby III
24-Ruby III
December 6, 2022

Hi,

I suggest you to contact PTC Support.

Y
YaroslavSin17-Peridot
17-Peridot
December 6, 2022

Do you have this files?

'Legacy toolkit Application Runtime' option is checked within the Creo installation.
-> The following files exist in the Creo xxxx/Common Files/x86e_win64/lib folder of the
installation:
• udata46.dll
• udata64.dll
• ucore46.dll
• ucore64.dll

M
MH_1036695710-MarbleAuthor
10-Marble
December 6, 2022

Yes, those files are there.

F
FV_0117-Peridot
17-Peridot
December 6, 2022

There could be a number of reasons.

  • Creo 9 had 'obsoleted' quite a number of old functions, but 'obsoleted' functions do not fail compilation...
  • could be as simple as the app cannot access its message file...
  • could be a config.pro setting and/or installation option related to 'legacy toolkit' application...

 

you could start a debugger session, connect to xtop.exe process (with no apps running yet), set breakpoints in the user_initialize function, start the app via UI command, step through debugger.  At least it will tell you where your app is failing.

 

HIH.

    Terms & ConditionsCookie settingsAccessibility statement