We export reports to different file formats. Our program uses OIPI interface and writes an RTF file on the server.

When I execute the program through the system monitor (on a workstation), the RTF file is written to the server and the program finishes normally.

However, when I execute the same program through a browser call, the program starts and then hangs.

The problem occurs at the following line:

STAT=SET_PRINTER("INIT", Init_Parm1, Init_Parm2, …, Init_Parm7)

The curious thing about this is, that the parameters that go into the function are exactly the same during both executions.

Any suggestions?

Best regards

Wilhelm

Wilhelm,

On the browser call, is OIPI32 started? What is the syntax of your browser call?

Sean

Sean,

On the browser call, is OIPI32 started?

YES

What is the syntax of your browser call?

http://localhost/oi/oecgi.exe/inet_rprt?rlist=list sysprocs

The system monitor call is:

run inet_rprt "rlist=list sysprocs"

inet_rprt is a program that calls rlist with a callback function to capture each print line.

The OIPI is started correctly.

In both cases (via system monitor and via browser) we use exactly the same program.

Regards

Wilhelm

Wilhelm

OIPI uses some presentation server calls.

When you are testing, you have presentation server running, so it works.

From the web, OENGINE runs, but not the presentation server, so the program fails.

As suggested in

This post one soulution is to run an oinsight connected to the same engine that OECGI uses. That is, if OECGI uses an engine on port 777 then on the same machine use an OINSIGHT /sn=777. The good news is your OIPI should start working. The bad news is that you are now using a single engine for reports, although of course you could run multiple copies and round robin them.

Hope this helps

Bob

Thanks, Bob.

View this thread on the Works forum...