The PTC Community is on temporary read only status in preparation for moving our community to a new platform. Learn more here
Solved! Go to Solution.
Thank you for your confirmation.
After searching the knowledge base, I have found this article : https://www.ptc.com/en/support/article/CS287881
It says that The IP of the network driver is part of the session signature when the asynchronous application is started.
The article is about the Java Object Toolkit flavor but the cause remains.
Hi
VB API and Toolkit at large leverage existing functionality.
Can you confirm that switching network keeps the session stable wimply with Creo Parametric ?
what's the behavior when you have, let's say a model in session, then change network ?
When I change networks, everything works fine in Creo. I can check in and out. The license is OK. Downloading .prt and .asm works. It's just the VB API that has crashed.
Thank you for your confirmation.
After searching the knowledge base, I have found this article : https://www.ptc.com/en/support/article/CS287881
It says that The IP of the network driver is part of the session signature when the asynchronous application is started.
The article is about the Java Object Toolkit flavor but the cause remains.
Ok,
So it is only possible to:
Reconnect using the same network driver.
Restart Creo to get a new session signature.
(Copy from https://www.ptc.com/en/support/article/CS287881)
These are the two ways I've also gotten it to work. No other way has worked.
I had hoped that there was a solution to the problem, but it seems there is not.
I have the same issues with asyn toolkit apps, for me this is not the root cause. And I don’t understand why the IP changes, because you are connected to the local machine, and why here the IP should change. I guess the RPC socket will close, and this will fire an event and will finally disconnect the session.
And sometimes reconnect without Creo restart is not possible, and this is a bug in my opinion. Because this may have an impact on your session data.
Your findings are fair and i understand that in our day and age of mobility this only makes sense.
To keep things in context, Creo is 40 years old and was initially designed for workstations.
Initially CAD users weren't supposed to move around with their hardware, let alone have a wireless connection.
So more than a bug it is an evolution and by ways of consequence your filing a enhancement request is more than welcome.
