Connection issues in asynchronous app(makefile project)

Question

Hello,Ihad done necessary changes in sample makefiles available with proe installation & written a simple code which will start a new proe session(.c source code file).Thr was no issue in build I got my executable as well.When I am trying to execute it on windows command prompt I am continuously getting errors.1st I got PRO_TK_APP_UNLOCK error then I unlocked the executable using protk_unlock.bat it passed thr this error but I dont its good practise to unlock executable each I debug my app.Next when Idebug this unlocked executable it thrown an PRO_TK_GENERAL_ERROR.All the possible causes of this error like name service,pro_comm_msg_exe variable are removed.Still I am getting this error.Strange thing I can see xtop.exe in task manager for some seconds.Finally it returns with this error code.Kindly help.RahulThis thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

JamesKerkstra · Answer

Hello,

I am somewhatnew to toolkit programming buta couple suggestions since I have recently encounteredsimilar issues. First inyour proe1.psf file that is in your <prodir>/bin directory make sure the followingline is present

ENV=PROE_FEATURE_NAME=PROE_FlexEng (14)

This will checkout a toolkit license when you start proeand should eliminate the need to keep unlocking the toolkit applications.When you distribute the application you do need to unlock it so users can use the dll.

If you candebug into the user initialize function thenyour issue is more than likely with code. If you cannot you are more than likely have the wrong lib files linked or bad compiler settings. The most recent issue I had with my debugversion wasI had used the Multi-threaded Debug runtime library ( /MTd ) but was not linking protk_dllmd.lib and was instead linking in protk_dll.libwhich is only for if you use the Multi-Threaded flag ( /MT ).

Another trick is to put a message box on the top of the user initialize then if you see it come up you know that you are at least getting into the code. This will also allow you to connect to xtop and if you put a break point on the line immediately after you can debug this function.

extern "C" int user_initialize(int argc, char *argv[], char *szVersion, char *szBuild, wchar_t *wzErrBuf) {

MessageBox(NULL,"HELLO WORLD","HELLO WORLD",MB_OK);

}

Hope that helps, If someone has better tricks up their sleeves please correct me so I can learn too.

Jim,

In Reply to Rahul M.:

Hello,
Ihad done necessary changes in sample makefiles available with proe installation & written a simple code which will start a new proe session(.c source code file).Thr was no issue in build I got my executable as well.When I am trying to execute it on windows command prompt I am continuously getting errors.
1st I gotPRO_TK_APP_UNLOCK error then I unlocked the executable using protk_unlock.bat it passed thr this error but I dont its good practise to unlock executable each I debug my app.
Next when Idebug this unlocked executable it thrown an PRO_TK_GENERAL_ERROR.All the possible causes of this error like name service,pro_comm_msg_exe variable are removed.Still I am getting this error.Strange thing I can see xtop.exe in task manager for some seconds.Finally it returns with this error code.
Kindly help.
Rahul

Sign up

Please use your PTC eSupport account.

Welcome to the PTC Community

Please use your PTC eSupport account.

Scanning file for viruses.

This file cannot be downloaded