Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
Solved! Go to Solution.
While coding with Creo VB API your code throws exception XToolkitAppVersionMismatch when connecting to Creo instance.
Apologies for delay in coming back to you.
The name of the exception tells that your code version and the Creo instance's mismatch. Theoretically datecodes datecode differences do not usually have an impact.
Release difference is more critical due to retro compatibility.
All in all, with VB calling vb_api_unregister and vb_api_register back to back resolve many of the issues.
If the issue still persists or if you need to pursue this conversation, i recommend that you file a new Tech Support case.
Please confirm that the issue is resolved.
Hi again,
seems like I found the problem. We installed a second Version of Creo, so we have M140+M150 installed. With M150 the connection works, with M140 it fails with above error.
After researching I've found out, that when 2 versions are installed, the vb_api_register.bat of the older version has to be executed. This didn't happen here.
While coding with Creo VB API your code throws exception XToolkitAppVersionMismatch when connecting to Creo instance.
Apologies for delay in coming back to you.
The name of the exception tells that your code version and the Creo instance's mismatch. Theoretically datecodes datecode differences do not usually have an impact.
Release difference is more critical due to retro compatibility.
All in all, with VB calling vb_api_unregister and vb_api_register back to back resolve many of the issues.
If the issue still persists or if you need to pursue this conversation, i recommend that you file a new Tech Support case.
Please confirm that the issue is resolved.