Many correct hints have been given already.
- Start with PTC provided ootb examples - they do work with supported software versions (compiler etc.). Enhance the examples step by step - incl. changing your build setup/IDE/dependencies to be able to track down errors.
- No protk.dat needed for asynchronous TK applications (but for synchronous/spawn applications!).
Not mentioned yet, but helps to rule out environment problems: start the asynchronous TOOLKIT application from within Creo (inherits environment variables and other process contexts from Creo that help the IPC pro_comm_msg.exe to find/connect to Creo).
Therefore in Creo use the button/command "Open System Window". A cmd.exe terminal appears, blocking Creo (since synchronous to Creo).
In this terminal, type and execute
start "Creo context" cmd
a 2nd terminal window opens (inheriting Creo context, too) with title "Creo context", but this is non-blocking to Creo.
Now close the 1st terminal to unblock Creo.
The 2nd terminal "Creo context" should be still open and can be used to start asynchronous applications as usual, but more likely to connect.
If this still does not work, something seriously blocks IPC (TCP/IP) or simple errors where made using TOOLKIT API/setting up Creo.
