Hi Kiran -
I have an asynchronous application (which, admittedly, uses
ProEngineerStart() with a
NULL pointer for the text directory) that successfully starts Wildfire 2
build m090
or M120. When I do have problems with ProEngineerStart(), I usually test
the pathname
of the .exe and then check the license file. The license file is most
often the problem.
I don't know how licensing is implemented at your site, but on Wildfire 2
I correct the
problem by editing C:\ptc\proe\bin\proe.psf . Near the bottom I find this
line
ENV=PROE_FEATURE_NAME=PROE_Flex3C
and change it to this:
ENV=PROE_FEATURE_NAME=PROE_Flex3C(14)
Again, there may be different licensing scheme at your site, and 14 may
therefore not
be the magic number for your Pro/Toolkit license. It may help for you to
consult whoever
administrates your Pro/E licenses.
|+| M a r k |+|
"Kiran Koka" <kiran.koka@haworth.com>
Sent by: -
07/28/2005 02:50 PM
Please respond to
"Kiran Koka" <kiran.koka@haworth.com>
To
"PTC/USER Programming Tools Discussion" <->
cc
Subject
[toolkits] ProEngineerStart Wildfire 2.0 m100
Hi-
Anyone run into issues with getting ProEngineerStart () function to work
with Wildfire 2.0 m100. It always returns protoolkit general error.
Pro_comm_msg_exe is set correctly.
I am passing the start command and location of the text directory to the
function..any help is appreciated
TIA.
Kiran Koka
Systems Analyst