Pro/Toolkit Project (exe) built in SPAWN mode doesn't register in the Creo Parametric environment

[AbySelvaraj]

I am using Creo Parametric Release 11.0 and Datecode11.0.2.0

I've built a PRO/Toolkit project in exe (SPAWN) mode. While registering it, I'm getting the following error.

Here are the errors that I faced
"Foreign program did not initialize properly; a communication problem may have occurred."

[MichaelW · Accepted solution]

An Auxiliary Application has failed to register (and run) in Creo Parametric.

This error is supposed to be thrown due to at least one of the following problems:

Improper license (check whether sth. in your code requires an additional license), Coding (check for required code structure and content), Library linking (check the guide whether a certain library is supported in certain mode), Library conflict (do not mix synchronous and asynchronous mode libraries) or expired certificates (a developer/vendor to update Third Party applications certificates).

Please check this Case Solution article for details:

CS220487 Error: Foreign program "XXX" failed to initialize: code 1 when launching Creo Parametric

For further assistance, please reach out to PTC Technical Support by opening a new case for Creo Parametric Toolkit. Remember to include your example code and setup details.

[AbySelvaraj]

Thanks for your suggestion!
I tried with "Advanced" license configuration, the program registers as expected. Earlier I was only using the "Essentials" license configuration.

Is there any particular reason for the "EXE SPAWN" mode to work not on "Essentials" license configuration?

[MichaelW]

1.

You mean the modules in Creo Design Packages: Design Essentials, Design Advanced, Design Advanced Professional, Design Premium and Design Premium Professional don't you?

Those are license packages, each containing a bundle of licenses:

• Design Essentials
• Design Advanced

2.

No, there is no impact from toolkit mode on the license or vice versa.

However, there is obviously at least one license included in the Advanced package that is missing in the Essentials package. This license is required to run at least one specific API in your code.

3.

Regarding Toolkit and licenses:

• A Toolkit-related license is necessary for the developer to build and unlock an auxiliary application using Toolkit.
• Once a DLL or EXE is built and unlocked by the Toolkit developer, it won't require any Toolkit-related license to run.
• However, to run a Toolkit application that relies on at least one API related to specific UI functionality (which is not standard), that additional license is needed for it to operate on the user's end.

Please refer to the Toolkit API Wizard tool shipped with Creo Toolkit, in order to get aware of any additional license required.