Anyone had a problem where Oracle Reports crash and then cause the webserver to crash?
We are running an application which uses webservers loaded with Oracle Developer 6i (6.0.8.16.1/patchset 7)
Oracle 9iAS 1.0.2.2.1 on Windows 2000
JDK version 1.2.2
The error messages we get are
Terminated with Error :
REP-1847: Failed while trying to set up for printing.
Terminated with Error :
REP-0713: Invalid printer name '\\PRINTSERVERNAME\PRINTER_NO1' specified by
parameter DESNAME
Crashed
And job 'stuck on 'opening'.
Oracle Report Writer seems to fail on one report, and then fails on reports requested after this. And then, this Oracle Report Writer failure can carry on to trigger a Web Server crash.
Do you know what lies behind the Oracle Report Writer error messages (ie. What is triggering them? What is broken? How can it be fixed? Are the messages misleading (red herrings) and is the true nature of the problem something else?)
Rebooting the Webserver (causing an interruption to the Users) fixes the problem.
Could the problem be something to do with local caching and refreshing of the Node Name/IP Address resolution?
We are running an application which uses webservers loaded with Oracle Developer 6i (6.0.8.16.1/patchset 7)
Oracle 9iAS 1.0.2.2.1 on Windows 2000
JDK version 1.2.2
The error messages we get are
Terminated with Error :
REP-1847: Failed while trying to set up for printing.
Terminated with Error :
REP-0713: Invalid printer name '\\PRINTSERVERNAME\PRINTER_NO1' specified by
parameter DESNAME
Crashed
And job 'stuck on 'opening'.
Oracle Report Writer seems to fail on one report, and then fails on reports requested after this. And then, this Oracle Report Writer failure can carry on to trigger a Web Server crash.
Do you know what lies behind the Oracle Report Writer error messages (ie. What is triggering them? What is broken? How can it be fixed? Are the messages misleading (red herrings) and is the true nature of the problem something else?)
Rebooting the Webserver (causing an interruption to the Users) fixes the problem.
Could the problem be something to do with local caching and refreshing of the Node Name/IP Address resolution?