Skip to main content
13-Aquamarine
November 27, 2020
Solved

ToolKit function ProEngineerStart returns ProError code -48, what does that mean??

  • November 27, 2020
  • 2 replies
  • 2518 views

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

 

 

Best answer by MartinHanak

@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.

 

2 replies

24-Ruby III
November 27, 2020

@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.

 

RPN
18-Opal
November 27, 2020

God bless, the answer was not 42 🍀