I was testing my plugin on other system then creo shown this error. How to run Creo Parametric TOOLKIT applications with a Creo Parametric Session without unlocking during application development stage
Solved! Go to Solution.
You can unlock your plug-in by issuing the command
protk_unlock.bat
which can be found in the bin folder of the PTC Creo installation, e.g. c:\ptc\Creo 6.0.5.0\Parametric\bin
If your plug-in is called
test.dll
you issue the command
protk_unlock.bat test.dll
You can unlock your plug-in by issuing the command
protk_unlock.bat
which can be found in the bin folder of the PTC Creo installation, e.g. c:\ptc\Creo 6.0.5.0\Parametric\bin
If your plug-in is called
test.dll
you issue the command
protk_unlock.bat test.dll
Thanks @JB_87049
did I need to run this command (protk_unlock.bat test.exe) on all pc in which I want to use my plugin(exe).
Is it asking for My Lic or asking every user to get proToolkit Lic to Use this plugin
You need to run this command on your PC only.
After you've done this you can distribute the dll (of your plug-in) to other users.
They only need to install it to be able to run it, nothing else.
Thanks @JB_87049
do you know how I can set name in this its showing ("UNNAMED") and I am using "exe" version of plugin is this command also work with this?
That is something I don't know. I have only developed dll-based apps so far.
I just looked it up in the file tkuse.pdf which can be found in the PTC installation folder.
\Common Files\protoolkit
It says it can be used for dll and exe.
I just looked it up in the file tkuse.pdf which can be found in the PTC installation folder.
\Common Files\protoolkit
It says it can be used for dll and exe.
Hello,
is it also possible to unlock via network?
I have a plugin with c++ project in which I include Creo directories.
I would like to install Creo in our VMware platform and then change the reference of the project to network location. In this way we can avoid to install Creo locally in our pc and creates different VMs for different Creo version and for each VMs-Creo version rebuild our application via network.
Thanks.
Sure, you can unlock. After this you lock a license for a couple of minutes. Toolkit license is only required to run not unlocked dll‘s or executables.
And of course- to set the unlock byte😅
In our c++ project, in the post-build event command line we run:
"C:\Program Files\PTC\Creo 8.0.0.0\Parametric\bin\protk_unlock.bat" "$(TARGETPATH)"
"C:\Program Files\PTC\Creo 8.0.0.0\Parametric\bin\ptcflush.bat" "14 HostName 7788 101"
We want to run this command through our VM with share folder.
In this way we want to create an automatic build mechanism.
Is this correct? It's a good approach?
Thanks.
For sure this is not the right place to answer this, but as far I know the host where you run unlock will hold and lock the License. And I don’t think that you can flush the license in that way, only if you wait 15 min. You should unlock always on the same host. Think about a file Event trigger 😉