Skip to main content
M
MF_106050604-Participant
4-Participant
March 14, 2024
Solved

EXCEPTION_NONCONTINUABLE_EXCEPTION when using OTK .dll compiled in different machine

  • March 14, 2024
  • 2 replies
  • 1831 views

In my company, we developed a plugin for Creo Parametric 9.0 using the C++ object toolkit. The plugin consists in a .dll that is compiled with Visual Studio 2022, with dependencies linked statically. The .dll works synchronously.

 

Between developers, we tried to distribute internally the .dll after compilation. But if the .dll is used in a different machine from the one it was compiled in, Creo crashes with EXCEPTION_NONCONTINUABLE_EXCEPTION. I'm attaching the traceback. log with the name of our plugin replaced with "<OUR_PLUGIN_NAME>".

 

My question is:

is it possible to distribute a .dll between machines, if all of them have the OTK installed, within the same license server? Is it possible between different licenses?

Best answer by FV_01

it is highly unlikely you are experiencing a license issue - if it would be a license problem your app would fail to initialize with some kind of error message.

 

start with the basic checks:

- was the dll built using PTC specified visual studio version, windows SDK version and platform toolset version.

- was the dll compiled with the correct runtime library and PTC specified preprocessor macros.

 

traceback file - just curious - how is it possible to have the trace creation timestamp to be a month earlier that the executable build timestamp? 

 

traceback file - having your exception trace to be between  libui_sh and VCRUNTIME140 - this could possibly point to a problem of filesystem or graphic system access and/or memory stack corruption by your app.

 

Try to make a do-nothing app similar to otk_install test app. Make sure it loads everywhere and go to the next step(s).

HIH

2 replies

M
MartinHanak24-Ruby III
24-Ruby III
March 14, 2024

Hi,

I hope that you unlocked application before distribution. Also the application must be digitally signed.

F
FV_0117-PeridotAnswer
March 14, 2024

it is highly unlikely you are experiencing a license issue - if it would be a license problem your app would fail to initialize with some kind of error message.

 

start with the basic checks:

- was the dll built using PTC specified visual studio version, windows SDK version and platform toolset version.

- was the dll compiled with the correct runtime library and PTC specified preprocessor macros.

 

traceback file - just curious - how is it possible to have the trace creation timestamp to be a month earlier that the executable build timestamp? 

 

traceback file - having your exception trace to be between  libui_sh and VCRUNTIME140 - this could possibly point to a problem of filesystem or graphic system access and/or memory stack corruption by your app.

 

Try to make a do-nothing app similar to otk_install test app. Make sure it loads everywhere and go to the next step(s).

HIH

    M
    MF_106050604-ParticipantAuthor
    4-Participant
    April 2, 2024

    Thanks for the replies, in the end the cause was an unhandled exception in our code. It could not be a licensing issue as FV said.

    Terms & ConditionsCookie settingsAccessibility statement