REP-51002 when Accessing Reports Server, but it is up and Ready per Trace Files (Doc ID 415407.1)

Last updated on OCTOBER 18, 2023

Applies to:

Symptoms

Trying to access the Reports Server gives following error:
     REP-51002: Bind to Reports Server <rep_server_name> failed

This error is given when you try to access Reports Server using getserverinfo or showjobs.  For example:
     http://hostname:port/reports/rwservlet/getserverinfo?server=rep_server_name
     or
     http://hostname:port/reports/rwservlet/showjobs?server=rep_server_name

Also, running the command "rwdiag.sh -findAll" gives error:
     REP-50503 No server found in the network

However, in the Reports Server trace files, it shows that the Reports Server is actually up and running.  There are no errors in the trace files.

For example, the rwserver.trc shows:
[2007/2/14 0:20:51:38] Info 56026 (EngineManager:registerEngine): Reports Server started up engine rwEng-0
[2007/2/14 0:20:51:46] Debug 50103 (EngineManager:updateEngineState): Engine rwEng-0 status is 1
[2007/2/14 0:20:51:46] State 56004 (EngineInfo:setState): Engine rwEng-0 state is: Ready
[2007/2/14 0:20:51:57] State 56012 (IdleThread:run): Reports Server is ready

The rwserver.log shows:
*** 2007/2/14 0:20:45:287 -- Reports Server is starting up
*** 2007/2/14 0:20:50:648 -- Reports Server started up engine rwURLEng-0
*** 2007/2/14 0:20:51:38 -- Reports Server started up engine rwEng-0
*** 2007/2/14 0:50:51:509 -- Shutting down engine rwEng-0
*** 2007/2/14 0:50:51:510 -- Reports Server shut down engine rwEng-0
*** 2007/2/14 0:50:51:510 -- Shutting down engine rwURLEng-0
*** 2007/2/14 0:50:51:511 -- Reports Server shut down engine rwURLEng-0

Changes

This is a new installation.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.