Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
My (simplified) ToolKit program calls ProEngineerStart() looks like :
void main()
{
ProError status;
status = ProEngineerStart("parametric.bat","");
printf("ProEngineerStart(): %d\n", status);
}
Run it in our office using company network (so as to get license) and sometimes the returned error code were -48 (failed) and 0 (OK) other times.
When it returned -48 colleagues' computers (two actually) were also had the same problem.
When it returned 0 , the two colleagues were all OK.
The strange thing is, run on my computer were OK always, no -48 at all.
I am suspecting the license server . . . however, what does the -48 exactly means?
suspecting license server's behavior
Solved! Go to Solution.
@Kittychen wrote:
My (simplified) ToolKit program calls ProEngineerStart() looks like :
void main() { ProError status; status = ProEngineerStart("parametric.bat",""); printf("ProEngineerStart(): %d\n", status); }
Run it in our office using company network (so as to get license) and sometimes the returned error code were -48 (failed) and 0 (OK) other times.
When it returned -48 colleagues' computers (two actually) were also had the same problem.
When it returned 0 , the two colleagues were all OK.
The strange thing is, run on my computer were OK always, no -48 at all.
I am suspecting the license server . . . however, what does the -48 exactly means?
suspecting license server's behavior
Hi,
according to http://www.vmould.cn/CREO_HELP/api/protoolkiterrors_h.html page,
-48 ... PRO_TK_CANT_MODIFY
According to https://lost-contact.mit.edu/afs/enea.it/software/ptc/proeWildfire/sgi/protoolkit/includes/ProCore.h page,
ProEngineerStart command has 2 arguments:
proe_path - The path and file name of the Pro/ENGINEER executable, or a script that runs it.
prodev_text_path - The path under which the Pro/TOOLKIT message and menu files are held. This is used in full asynchronous mode only. Otherwise, pass a null string.
According to https://www.ptc.com/en/support/article/CS110564 page,
Windows environment variable PRO_COMM_MSG_EXE with the value pointing to the location of pro_comm_msg.exe must be set.
@Kittychen wrote:
My (simplified) ToolKit program calls ProEngineerStart() looks like :
void main() { ProError status; status = ProEngineerStart("parametric.bat",""); printf("ProEngineerStart(): %d\n", status); }
Run it in our office using company network (so as to get license) and sometimes the returned error code were -48 (failed) and 0 (OK) other times.
When it returned -48 colleagues' computers (two actually) were also had the same problem.
When it returned 0 , the two colleagues were all OK.
The strange thing is, run on my computer were OK always, no -48 at all.
I am suspecting the license server . . . however, what does the -48 exactly means?
suspecting license server's behavior
Hi,
according to http://www.vmould.cn/CREO_HELP/api/protoolkiterrors_h.html page,
-48 ... PRO_TK_CANT_MODIFY
According to https://lost-contact.mit.edu/afs/enea.it/software/ptc/proeWildfire/sgi/protoolkit/includes/ProCore.h page,
ProEngineerStart command has 2 arguments:
proe_path - The path and file name of the Pro/ENGINEER executable, or a script that runs it.
prodev_text_path - The path under which the Pro/TOOLKIT message and menu files are held. This is used in full asynchronous mode only. Otherwise, pass a null string.
According to https://www.ptc.com/en/support/article/CS110564 page,
Windows environment variable PRO_COMM_MSG_EXE with the value pointing to the location of pro_comm_msg.exe must be set.
God bless, the answer was not 42 🍀