> From: "Madhava Rao" <madhava@idolafori.com>
>
> Below is the code which I have followed to connect to pro-e
> wildfire2 through asynchronous mode.
>
> I have set all the seeting in vc++ complier.
>
> I am able to generate the obj and exe file successfully.
> But while run the exe file the following error is occurring.
> Warning:4068 couldnot start message module 1073823185.
>
> Can any one tell me where I am going wrong in connecting to
> pro-e from externally.
In previous releases, the environment variable PRO_COMM_MSG_EXE
must be set to the pro_comm_msg executable (add .exe for win32)
before ProEngineerStart() and/or ProEngineerConnect(). Check
a working Pro/Engineer startup script (created by ptcsetup) for
an example.
Setting the environment variable can be done in a wrapper script,
batch file, or in the async app itself using putenv() or something
similar. I'm not aware of this being different for Wildfire 1 or
2.
If you are trying to ProEngineerConnect() to a session on another
machine, it seems to work only if you have the PTC portmapper
running, especially if you're connecting to a windows system.
Marc
This 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.
