Can't start reports server on win2000

I'm having a trouble with starting reports server service on win2000 advanced server. I'm getting this message from Event viewer:
The Oracle Reports Server [Rep60_HAL-OraHome6i] service terminated with service-specific error 186.
And I can't find any information about configuring server and errors. Can anyone help me

check ur sqlnet.ora file also. If there is any error in that file u will get a same error.
shailesh
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Kevin Harless ([email protected]):
I am having the same exact error...Anyone have the fix for this.....<HR></BLOCKQUOTE>
null

Similar Messages

Can't start report server on windows 2000

I can't start report server with error code 186, my tnsname.ora is
REP60_DUQ = Rep60_DUQ
is it error?
who can tell me how to resolve it!!!

but I have add tnsnames.ora following
Rep60_REPORT_SERVER =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = REPORT_SERVER)(PORT = 1951))
then I start report server with:
/PATH_TO_REPORTSERVER/report60_server start
it still says:
REP-0186: Daemon failed to listen to port
what is problem?
any thing must be done to activate changes in
tnsnames.ora?
null

Can't start Report Server

Dear all,
I have an envirnment that have Both of the Database (11g) and the Application Server (10gR2) are installed in the same machine. i installed only forms and reports components from the application server and the forms are working well through the web. my problem is that i can't make the in process report server up and runing as it's alwlyes dowen and when i chose it from the web and choose start, the job finished but it still down.
in addition to that i failled to use the comand RWSERVER to create new report server and aloyes the message "Consult the installtion guide for how set up an run this program, so, how can i make the report server up and running as my reports not working.
Thanks,

The EM Console is not the best way to find out if your reports server is up and running, I sugest you use the command rwdiag -findall it will show you the reports servers up in your server, as well if you want to create a new reports server, you have to use *$ORACLE_HOME/bin/addnewservertarget.sh new_servername* as well this command will create an entry in opmn.xml in a way that you can check the status of this using opmnctl status command.
Hope this helps.
Greetings.
Edited by: Roberto Barrera on Dec 9, 2009 12:42 PM
As Paul Mentioned!

Can't start reports server on Windows Server 2003 SP1 Error code 13

Hi,
This morning I figured how to start the rwserver using the command, rwserver server = repsrv. This works using XP pro physical machine but now I am trying to perform the same task on a Windows 2003 virtual machine.
I have used the line:
rwserver -install repsrv.
To add repserv to the list of available services in computer management. This has appeared as an avaiable service and so I click to start it, unfortunately every time I do I get the error message:
"Windows could not start the OracleOraAppServer10g_home1Reports [repsrv] on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 133."
I am assuming this is a security issue with Windows 2003 but I can't find a cure anywhere.
Thanks in advance for any help that anybody is able to provide
Cheers
Daniel

Hello,
Step 1) Check that you can start the reports server from a "DOS Window" :
rwserver server=repserver
Step 2) Check the PATH set for rwserver.exe when it is running as a service
Some sysinternals utilities like Process Explorer / filemon may help :
http://www.sysinternals.com/
Regards

How can I start report server?

Hi all,
Iâm facing a problem in calling reports from forms 10g.
I donât know whether my report server is started or not but then checked by this line of code in a web browser. It give me an error:
http://<server name>:8889/reports/rwservlet/showjobs?server=rep_domain
ERROR:
REP-52266: The in-process Reports Server rep_domain failed to start.exception oracle.reports.RWException {
oracle.reports.RWError[] errorChain={struct oracle.reports.RWError {
int errorCode=52266,
java.lang.String errorString="The in-process Reports Server rep_domain failed to start.",
java.lang.String moduleName="REP"
Can anybody help...
And one more how to start the report server?
Thanks n Regards.

Thanks All,
Good to see response so quick.
In fact two session were open at the time one is Forum Forms n other Forum reports, by mistake I posted this on forms forum.
Anyway, I solved the problem. The actual problem was I made some changes in <server name>.conf file. I uncommented the engine tags properties. I was having backup of it I copied again. Now itâs working fine.
Thanks once again.

Start reports server

hi
i've made some experience with forms and now have to configure reports (9i web).
i read a lot of documents from otn with no success.
i'd like to start reports server as servlet under win2000.
as 2.1.2 in the docu said:
i tried http://test_oas:7778/reports/rwservlet and got the 'Servlet Command Help - page'.
2.2 verifying the reports servlet and server are running
i typed: http://test_oas:7778/reports/rwservlet/help which displayed the same page as above.
then i typed:
http://test_oas:7778/reports/rwservlet/showjobs?server=rep_test_oas which redirects me to 'http://test_dbs:7777/pls/orasso/orasso.wwsso_app_admin.ls_login' where i get a 'page not found'.
then the rep_test_oas.trc sais this:
[2003/7/27 5:42:37] Debug 50103 (RWSecurity:isPortalConnected): s_connection:oracle.jdbc.driver.OracleConnection@682406
[2003/7/27 5:42:37] Debug 50103 (RWSecurity:isPortalConnected): s_connection:oracle.jdbc.driver.OracleConnection@682406
on the EM-Website, ther is a system-component called reports:rep_test_oas whichs state is down. what does this component mean? when i start it, i get the message 'started' but the state is still down.
can someone help me?

used your example-code.
still get a frm-41214 and a 41213.
the errormessage when 41213 occurs is: "could not connect to reports-server rep."
the strange thing is that my server is called rep_test_oas. i've never defined a rep.
here is a rwEng-0 part:
[2003/7/28 0:23:39] Info 55003 (RWEngine:init): Register this engine to Oracle Reports Server rep_test_oas
[2003/7/28 0:28:29] Debug 50103 (EngineImpl:setCommandLine): Running
[2003/7/28 0:28:29] Info 50132 (EngineImpl:setCommandLine): Get command line: REPORT=L:\join3000\reports\test\MODULE2.rdf USERID=JOIN3000@j3000tes BATCH=YES DESTYPE=cache DESFORMAT=PDF AUTHID=ANONYMOUS
[2003/7/28 0:28:29] Debug 50103 (EngineImpl:setCommandLine): Quit
[2003/7/28 0:28:29] Debug 50103 (EngineImpl:run): Running
[2003/7/28 0:28:29] (C Engine) LOG :
[2003/7/28 0:28:29] (C Engine) Angemeldet bei Server: j3000tes
[2003/7/28 0:28:29] (C Engine) Benutzername: JOIN3000
[2003/7/28 0:28:29] (C Engine)
[2003/7/28 0:28:31] Error 50103 (C Engine): 11:28:31 ERR REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
[2003/7/28 0:28:31] Error 50103 (C Engine): 11:28:31 ERR REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
[2003/7/28 0:28:31] Debug 50103 (EngineImpl:run): CRunReport returns: 110
[2003/7/28 0:28:31] Debug 50103 (EngineImpl:run): Quit
[2003/7/28 0:28:31] Exception 110 (): Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
exception oracle.reports.RWException {
oracle.reports.RWError[] errorChain={struct oracle.reports.RWError {
int errorCode=110,
java.lang.String errorString="Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
java.lang.String moduleName="REP"
     at oracle.reports.engine.EngineImpl.run(EngineImpl.java:295)
     at oracle.reports.engine.EngineClassPOATie.run(EngineClassPOATie.java:84)
     at oracle.reports.engine.EngineClassPOA._invoke(EngineClassPOA.java:117)
     at oracle.reports.engine.EngineClassPOA._invoke(EngineClassPOA.java:62)
     at com.inprise.vbroker.poa.POAImpl.invoke(POAImpl.java:2355)
     at com.inprise.vbroker.poa.ActivationRecord.invoke(ActivationRecord.java:104)
     at com.inprise.vbroker.GIOP.GiopProtocolAdapter.doRequest(GiopProtocolAdapter.java:492)
     at com.inprise.vbroker.IIOP.ServerProtocolAdapter.doRequest(ServerProtocolAdapter.java:64)
     at com.inprise.vbroker.GIOP.GiopProtocolAdapter.dispatchMessage(GiopProtocolAdapter.java:653)
     at com.inprise.vbroker.orb.TPDispatcherImpl$TPDispatcher.run(TPDispatcherImpl.java:99)
     at com.inprise.vbroker.orb.ThreadPool$PoolWorker.run(ThreadPool.java:76)
and the rep_test_oas.trc:
[2003/7/28 0:28:29] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Reserved
[2003/7/28 0:28:29] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Running
[2003/7/28 0:28:29] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Idle
[2003/7/28 0:28:29] Debug 50103 (JobManager:runJobInEngine): Send job 20 to engine rwEng-0
[2003/7/28 0:28:29] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Running
[2003/7/28 0:28:31] State 56016 (JobManager:updateJobStatus): Job 20 status is: Mit Fehler beendet:
REP-110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
[2003/7/28 0:28:31] Debug 50103 (JobManager:updateJobStatus): Notify master job 20
[2003/7/28 0:28:31] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Ready
[2003/7/28 0:28:31] Exception 110 (): Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
exception oracle.reports.RWException {
oracle.reports.RWError[] errorChain={struct oracle.reports.RWError {
int errorCode=110,
java.lang.String errorString="Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
java.lang.String moduleName="REP"
     at oracle.reports.RWExceptionHelper.read(RWExceptionHelper.java:28)
     at oracle.reports.engine._EngineClassStub.run(_EngineClassStub.java:159)
     at oracle.reports.server.JobManager.runJobInEngine(JobManager.java:623)
     at oracle.reports.server.JobManager.runJobLocal(JobManager.java:1209)
     at oracle.reports.server.JobManager.dispatch(JobManager.java:701)
     at oracle.reports.server.ConnectionImpl.runJob(ConnectionImpl.java:755)
     at oracle.reports.server.ConnectionPOATie.runJob(ConnectionPOATie.java:282)
     at oracle.reports.server.ConnectionPOA._invoke(ConnectionPOA.java:399)
     at oracle.reports.server.ConnectionPOA._invoke(ConnectionPOA.java:84)
     at com.inprise.vbroker.poa.POAImpl.invoke(POAImpl.java:2355)
     at com.inprise.vbroker.poa.ActivationRecord.invoke(ActivationRecord.java:104)
     at com.inprise.vbroker.GIOP.GiopProtocolAdapter.doRequest(GiopProtocolAdapter.java:492)
     at com.inprise.vbroker.IIOP.ServerProtocolAdapter.doRequest(ServerProtocolAdapter.java:64)
     at com.inprise.vbroker.GIOP.GiopProtocolAdapter.dispatchMessage(GiopProtocolAdapter.java:653)
     at com.inprise.vbroker.orb.TPDispatcherImpl$TPDispatcher.run(TPDispatcherImpl.java:99)
     at com.inprise.vbroker.orb.ThreadPool$PoolWorker.run(ThreadPool.java:76)
[2003/7/28 0:28:31] State 56016 (JobManager:updateJobStatus): Job 20 status is: Mit Fehler beendet:
REP-110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
[2003/7/28 0:28:31] Debug 50103 (JobManager:updateJobStatus): Notify master job 20
[2003/7/28 0:28:31] Exception 110 (): Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
exception oracle.reports.RWException {
oracle.reports.RWError[] errorChain={struct oracle.reports.RWError {
int errorCode=110,
java.lang.String errorString="Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
java.lang.String moduleName="REP"
     at oracle.reports.server.JobManager.runJobInEngine(JobManager.java:669)
     at oracle.reports.server.JobManager.runJobLocal(JobManager.java:1209)
     at oracle.reports.server.JobManager.dispatch(JobManager.java:701)
     at oracle.reports.server.ConnectionImpl.runJob(ConnectionImpl.java:755)
     at oracle.reports.server.ConnectionPOATie.runJob(ConnectionPOATie.java:282)
     at oracle.reports.server.ConnectionPOA._invoke(ConnectionPOA.java:399)
     at oracle.reports.server.ConnectionPOA._invoke(ConnectionPOA.java:84)
     at com.inprise.vbroker.poa.POAImpl.invoke(POAImpl.java:2355)
     at com.inprise.vbroker.poa.ActivationRecord.invoke(ActivationRecord.java:104)
     at com.inprise.vbroker.GIOP.GiopProtocolAdapter.doRequest(GiopProtocolAdapter.java:492)
     at com.inprise.vbroker.IIOP.ServerProtocolAdapter.doRequest(ServerProtocolAdapter.java:64)
     at com.inprise.vbroker.GIOP.GiopProtocolAdapter.dispatchMessage(GiopProtocolAdapter.java:653)
     at com.inprise.vbroker.orb.TPDispatcherImpl$TPDispatcher.run(TPDispatcherImpl.java:99)
     at com.inprise.vbroker.orb.ThreadPool$PoolWorker.run(ThreadPool.java:76)
[2003/7/28 0:28:31] Debug 50103 (JobManager:runJobInEngine): Encounted exception in job 20
[2003/7/28 0:28:31] Exception 110 (): Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
exception oracle.reports.RWException {
oracle.reports.RWError[] errorChain={struct oracle.reports.RWError {
int errorCode=110,
java.lang.String errorString="Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
REP-1070: Fehler beim Öffnen oder Speichern eines Dokuments.
REP-0110: Datei 'L:\join3000\reports\test\MODULE2.rdf' kann nicht geöffnet werden.
java.lang.String moduleName="REP"
     at oracle.reports.server.JobManager.runJobInEngine(JobManager.java:669)
     at oracle.reports.server.JobManager.runJobLocal(JobManager.java:1209)
     at oracle.reports.server.JobManager.dispatch(JobManager.java:701)
     at oracle.reports.server.ConnectionImpl.runJob(ConnectionImpl.java:755)
     at oracle.reports.server.ConnectionPOATie.runJob(ConnectionPOATie.java:282)
     at oracle.reports.server.ConnectionPOA._invoke(ConnectionPOA.java:399)
     at oracle.reports.server.ConnectionPOA._invoke(ConnectionPOA.java:84)
     at com.inprise.vbroker.poa.POAImpl.invoke(POAImpl.java:2355)
     at com.inprise.vbroker.poa.ActivationRecord.invoke(ActivationRecord.java:104)
     at com.inprise.vbroker.GIOP.GiopProtocolAdapter.doRequest(GiopProtocolAdapter.java:492)
     at com.inprise.vbroker.IIOP.ServerProtocolAdapter.doRequest(ServerProtocolAdapter.java:64)
     at com.inprise.vbroker.GIOP.GiopProtocolAdapter.dispatchMessage(GiopProtocolAdapter.java:653)
     at com.inprise.vbroker.orb.TPDispatcherImpl$TPDispatcher.run(TPDispatcherImpl.java:99)
     at com.inprise.vbroker.orb.ThreadPool$PoolWorker.run(ThreadPool.java:76)
[2003/7/28 0:28:31] Warning 50103 (ResourceManager:getString): java.util.MissingResourceException: Can't find resource for bundle oracle.reports.utility.resource.RWGenericBundle, key 5
[2003/7/28 0:28:31] Info 56013 (ConnectionManager:release): Connection 2 is released
i'm sorry. but i cant find the problem with these error-messages.
can U?

How to start report server

Installed oracle 9ias infrasturce and 9ias portal on the same machine. I can access the portal main page.
I cannot start report server. My attempts to start the report server from command line failed. I tried using the trace file also. It is not writing anyting to the trace file.
Any help is appreciated.

I tried to start the report server from command line with the trace ON. I get "report server is starting up" window.( nothing else happens)
The trace file has the following information
[2003/6/29 9:46:55] Info 56025 (RWServer:startServer): Reports Server is starting up
[2003/6/29 9:46:57] Info 50128 (RWServer:startServer): orb init succeeded
[2003/6/29 9:46:58] Info 50129 (RWServer:startServer): boa init succeeded
[2003/6/29 9:47:0] Info 56023 (ServerImpl:ServerImpl): Idle thread has been started
[2003/6/29 9:47:1] Info 56018 (RWServer:startServer): Reports Server rep_p607951 object is ready
[2003/6/29 9:47:1] Info 56020 (EngineManager:spawnEngine): Launching engine rwEng-0
[2003/6/29 9:47:1] Debug 50103 (EngineManager:spawnEngine): Start engine command line = c:\ora9ids\jdk\jre\bin\javaw -cp "c:\ora9ids\j2ee\home\lib\ojsp.jar;c:\ora9ids\reports\jlib\rwrun.jar;c:\ora9ids\jlib\zrclient.jar" -Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB -Dorg.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB oracle.reports.engine.RWEngine name=rwEng-0 server=rep_p607951 ORACLE_HOME=c:\ora9ids engineimplclass=oracle.reports.engine.EngineImpl traceopts=trace_all tracefile=c:\ora9ids\reports\logs\rep_p607951-rwEng-0.trc tracemode=trace_replace cacheDir=c:\ora9ids\reports\cache
[2003/6/29 9:47:1] Info 56021 (EngineManager:spawnEngine): Engine rwEng-0 has been launched
[2003/6/29 9:47:1] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Initial
[2003/6/29 9:47:1] Info 56020 (EngineManager:spawnEngine): Launching engine rwURLEng-0
[2003/6/29 9:47:1] Debug 50103 (EngineManager:spawnEngine): Start engine command line = c:\ora9ids\jdk\jre\bin\javaw -cp "c:\ora9ids\j2ee\home\lib\ojsp.jar;c:\ora9ids\reports\jlib\rwrun.jar;c:\ora9ids\jlib\zrclient.jar" -Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB -Dorg.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB oracle.reports.engine.RWEngine name=rwURLEng-0 server=rep_p607951 ORACLE_HOME=c:\ora9ids engineimplclass=oracle.reports.urlengine.URLEngineImpl traceopts=trace_all tracefile=c:\ora9ids\reports\logs\rep_p607951-rwURLEng-0.trc tracemode=trace_replace cacheDir=c:\ora9ids\reports\cache
[2003/6/29 9:47:1] Info 56021 (EngineManager:spawnEngine): Engine rwURLEng-0 has been launched
[2003/6/29 9:47:1] State 56004 (EngineInfo:setState): Engine rwURLEng-0 state is: Initial
[2003/6/29 9:47:1] Debug 50103 (JobStore:writePersistFile): Purge persistent file
[2003/6/29 9:47:1] Debug 50103 (JobStore:writePersistFile): Purge persistent file done
[2003/6/29 9:47:7] Warning 50103 (EngineManager:registerEngine): REP-55103: API URLEngine:getEngineEnvs not applicable to URL engine
[2003/6/29 9:47:7] Info 56026 (EngineManager:registerEngine): Reports Server started up engine rwURLEng-0
[2003/6/29 9:47:7] State 56004 (EngineInfo:setState): Engine rwURLEng-0 state is: Ready

Can not start Messaging server in Sun Java System Messaging Server 6 2005Q1

Hi all,
I installed Sun Java System Messaging Server 6 2005Q1 from Solaris 10 DVD on Solaris 10.
After the installation, I got directory server, admin server running but messaging server not running. I can not start Messaging server (start smtp, http, pop, imap). I found in directory which I installed messaging server but I could not see script "start-msg" and "stop-msg".
# pwd
/opt/SUNWmsgsr/sbin
# ls
MoveUser ha_ip_config imquotacheck imsdirmig mkbackupdir
UpgradeMsg5toMsg6.pl hashdir imsbackup imsexport readership
configure imexpire imsconnutil imsimport reconstruct
control-params.txt iminitquota imscripter imsrestore relinker
deliver immonitor-access imsdaaci mboxutil useconfig
Any idea what might have gone wrong?
Thanks.

Thanks.
I have a problem when I configure the Messaging Server (by running the /opt/SUNWmsgsr/sbin/configure script):
Hostname mailtest for this machine is not a fully qualified domain name. Please
correct this before attempting to configure Messaging Server. Please make sure
that your DNS is working properly.
<Press ENTER to continue> {"<" goes back, "!" exits}
Can you help me fix this problem?
Thanks.

Can't start http server ASControl service

Hi, I installed http server from companion cd for oracle 10.2.0.3 but when configuration assistants was setting http server give the message failed.
Now i can´t start http server service.
INFO: El asistente de configuración "OC4J Configuration Assistant" se ha ejecutado correctamente
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Created a new file C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.1
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.2
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.3
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.4
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.5
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.6
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: --------------------------------------
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolAllCommands" contiene todos los comandos que van a ejecutar los asistentes de configuración. Este archivo se puede utilizar para ejecutar los asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.7
GRAVE: OUI-25029: Uno o más asistentes de configuración "recomendados" no han terminado correctamente. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
INFO: Usuario seleccionado: Sí/Aceptar
INFO:
*** Fin de Instalación Página***
La instalación de Oracle Database 10g Companion Products ha sido correcta, pero han fallado, se han cancelado o se han saltado algunos asistentes de configuración opcionales.
ADVERTENCIA: ¿Seguro que desea salir?
INFO: Usuario seleccionado: Sí/Aceptar

user13078324 wrote:
How ?in cmd run this
netstat -an
and search for a line like
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
The important is TCP, 80 and keyword LISTENING
Other may differ

New install of SJS Ent 8 on Solaris, can't start Application Server 8.1

Hello,
Appreciate in advance your help.
Just downloaded and installed SJS 8.1 on a new Sun Solaris 10 box. I'm able to run the IDE and have started the Tomcat server, but when attempting to start the SJS 8.1 application server, I get:
The Sun Java System Application Server 8.1 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used)
- Incorrect server configuration
- Corrupted Deployed Applications
The problems are:
- There is no server.log file in the expected directory at /opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs
- I ran netstat -a, but could glean no useful information
- I have not modified the server configuration since the new install
- I have not deployed my application (since I can't start the server).
Forgive my ignorance since I'm not a Solaris expert. I would greatly appreciate your assistance.

No difference in server.log after setting level="FINEST".
Don't know if it would help, but the contents of my server.log file follow:
[#|2006-09-25T15:39:46.485-0400|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
/opt/sun/jstudio_ent8/jdk1.5.0_04/bin/java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs/server.log
-Djava.endorsed.dirs=/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/endorsed
-Djava.security.policy=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/server.policy
-Djava.security.auth.login.config=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/keystore.jks
-Djavax.net.ssl.trustStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/cacerts.jks
-Djava.ext.dirs=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/ext:/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=myDomain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=myDomain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=/opt/sun/jstudio_ent8/AppServ8.1UR2/config
-Djava.library.path=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386/client:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/../lib/i386:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib:/usr/lib/lwp::/usr/lib
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
/opt/sun/jstudio_ent8/jdk1.5.0_04/lib/tools.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/activation.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/mail.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/admin-cli.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-admin.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-jstl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-logging.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee-svc.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jax-qname.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/dom.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/relaxngDatatype.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xsdlib.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote_optional.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/rmissl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xalan.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xercesImpl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-upgrade.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-ext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/install/applications/jmsra/imqjmsra.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/jaxm-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/fscontext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/ant/lib/ant.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbclient.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start|#]
I do notice that the class path references jdk1.5.0_04. When installing SJS I selected the separately installed jdk1.5.0_07. Could that be causing the problem?
You have great patience.

Can I use Reports Server Queue PL/SQL Table API to retrieve past jobs ?

Hi all,
Can I use Reports Server Queue PL/SQL Table API to retrieve past jobs using WEB.SHOW_DOCUMENT from Forms ?
I have reviewed note 72531.1 about using this feature and wonder if i can use this metadata to retrieve past jobs submitted by a user.
The idea would be to have a form module that can filter data from the rw_server_queue table, say, base on user running the form, and be able to retrieve past jobs from Report Server Queue. For this, one would query this table and use WEB.SHOW_DOCUMENT.
Is this possible ...?
Regards, Luis ...!

Based on that metalink note and the code in the script rw_server.sql, I am pretty sure that by querying the table you would be able accomplish what you want... I have not tested it myself... but it looks that it will work... you have the jobid available from the queue, so you can use web.show_document to retrieve the output previously generated...
ref:
-- Constants for p_status_code and status_code in rw_server_queue table (same as zrcct_jstype)
UNKNOWN CONSTANT NUMBER(2) := 0; -- no such job
ENQUEUED CONSTANT NUMBER(2) := 1; -- job is waiting in queue
OPENING CONSTANT NUMBER(2) := 2; -- opening report
RUNNING CONSTANT NUMBER(2) := 3; -- running report
FINISHED CONSTANT NUMBER(2) := 4; -- job has finished
TERMINATED_W_ERR CONSTANT NUMBER(2) := 5; -- job has terminated with

Urgent: Can not start admin server

I installed Sun One directory server 5.1 on Solaris 8 01/01 version patched with Solaris 8 patch cluster.
In installation, there is error message
Can't start Admin server [home/iplanet/servers/start-admin > /var/tmp/aaax0aOBb 2>&1] (error: No such file or directory)
idskture only shows one ERROR message:
ERROR : Patch 111085-02 (SunOS 5.8: /usr/bin/login patch) is required but not installed.
But it seems fine since I reinstalled Solaris 8 01/01 release and install 5.1sp2 and with the same error message running idsktune, the installation of 5.1 but works fine.
Do you have any idea why the installation fail before I reinstlall Solaris 8?
Thanks,
Iris

Have you checked the EAS logs, <MIDDLEWARE_HOME>user_projects\epmsystem1\diagnostics\logs\services
Cheers
John
http://john-goodwin.blogspot.com/

SSRS 2005 why some users can't access report server.

There is one user who can't access report server by clicking a link to a report. A window will pop up asking for login. Even he enters login, the window will keep coming back. I have set the user for that report and assigned the 'Browser' role to the user.
Other users don't have this problem. E.g. for another user I also set him up for the report and assigned 'Browser' role but he can access the same report no problem.

Hi thotwielder,
As per my understanding, I think this issue can be caused by the following two reasons:
The report server can be blocked by Firewall. If Windows Firewall is turned on, the port that the report server is configured to use is most likely closed. Indications that a port might be closed are the appearance of a blank Web page after requesting a
report, or a blank page when you attempt to open Report Manager from a remote client computer. In this scenario, we can try to open port 80 in Windows Firewall on both report server and client computers.
The report server can be blocked by browser. We should ass the report server URL to trusted site in the browser.
We can also grant the user access to site-wide operations with system-level row in report manager to check the issue again.
Please double-check we have been grand the user the browser role on the report. We can navigate to Security property of the report to check the issue.
Reference:
Configure a Firewall for Report Server Access
Configure a Native Mode Report Server for Local Administration (SSRS)
Grant User Access to a Report Server (Report Manager)
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Having issues with starting Reports Server on RHEL5 after installation

Hi, I installed Oracle Application Server 10.1.2 on RHEL, ran the patches to move it up to 10.1.2.3. I've also put a couple patches in addition.
When I go to my application server console, I noticed everything is started up but my Reports Server. I've tried to manually start it via the browser, and it tells me it starts up. But when I go back to the main page of the application server console, it shows still as down. I've tried to log onto the server and issue a statement to start the reports server. However, it still will not start.
I followed the steps made in Metalink Document 564174.1 and did everything that was asked.
Anybody got any ideas on what might be causing this?
The only error (warning message) I received during any part of the installation process was the OPMN Process Manager didn't start. I went ahead and continued (not sure if that's my problem). But that was the only issue. And like I say, the forms server seems to work fine. No issues. I've set up my application and I can call all the forms in my application. It works.
Regards,
Chris

One thing is that the status in EM console is showed ad Stoped and indeed it's stoped and other is that the EM is not able to see if the process is up. Lots of times I had problems like this where the Reports Server is showed as down but the proc exist and the service is attending request.
Have you try to test report server running a sample report?
Have you check is exist a proces for the report server?
Have you use the rwdiag.sh -findall to see if the process exists?
Hope this helps
Greetings.

SSRS Report queries begin running slowly, have to stop and start report server to restore performance

We have had a production issue crop up twice now where reports begin running slowly seemingly at random.
When this happens we can see from running SQL Profiler that the report queries are taking an extremely long time to execute. The same queries when run directly in management studio run quickly.
Initially I suspected parameter sniffing, and tried using OPTION (RECOMPILE) in the reports, as well as clearing out the particular query from the plan cache and running the SQL in SSMS to try and get a better plan etc but no amount of jiggery pokery by
me could get the queries to run any faster.
The really weird thing - is that stopping and starting the report server via the reporting services configuration manager instantly cures the problem.
I'd really love to know - why this might be? Is it something to do with the report server closing and re-opening its connections to the database? That's the only sort of thing I can think of...any ideas? Anyone? Any suggestions would be much appreciated.
LucasF

Hi LucasF,
In your scenario, usually we can monitor the execution log in Report Database. If you run below query, you can get the results how long the report takes to render (TimeRendering), how long to process the report(TimeProcessing) and how long to retrieve data
from Database(TimeData). You can check the starttime and endtime to know the total time for executing a report.
SELECT TOP1000 *FROM[ReportServer].[dbo].[ExecutionLog2]
More details information, please reference to similar thread below:
Steps for troubleshooting a slow SSRS 2014 server
Troubleshooting Reports: Report Performance
In SQL Server Reporting Services, a job will be created by SQL Server Agent if any of the following processes is underway:
query execution on a remote or local database server
report processing
report rendering
To cancel a job that is running on the report server, we can cancel the job directly or reduce the report execution time-out value in the SQL Server Management Studio and then will stop query execution. Please refer to the steps below:
Open SQL Server Management Studio, and connect to "Reporting Services".
Under the Report Server node, right-click on the "Jobs" folder and select "Refresh". Then, right-click on "Jobs" again and click "Cancel All Jobs".
Right-click on the Report Server node and open the "Server Properties" dialog.
Click the "Execution" option, and set the "Limit report execution to the following number of seconds:" to a much smaller number. After this issue is resolved, this configuration should revert to the previous state.
Reference:
Managing a Running Process
Setting Time-out Values for Report and Shared Dataset Processing
In addition, we can also use the KILL Transact-SQL statement to terminate a normal connection by terminating the transactions that are associated with the specified session ID. For the details information, you can refer to:
KILL (Transact-SQL)
If you still have any problem, please feel free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

Can't start reports server on win2000

Similar Messages

Maybe you are looking for