REP-50600 : Broadcasting is disabled. Please enable cosnaming for Reports discovery.

 

 

REP-50600 : Broadcasting is disabled. Please enable cosnaming for Reports discovery. 

 

Few days ago, we faced one issue with our customer where customer couldn’t start oracle standalone report server after they had restarted their physical server .

 

While tried to start the report server using command failed with following error

[oracle@dev-wls bin]$ ./opmnctl startproc ias-component=RptSvr_dev-wls_asinst_1 opmnctl startproc: starting opmn managed processes...================================================================================ opmn id=dev-wls.rcf.gov.in:6701 Response: 2 of 3 processes started.   ias-instance id=asinst_1 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ias-component/process-type/process-set:   RptSvr_dev-wls_asinst_1/ReportsServerComponent/RptSvr_dev-wls_asinst_1/   Error --> Process (index=1,uid=1518988558,pid=30017)   failed to start a managed process after the maximum retry limit   Log:   /u01/app/oracle/Middleware/asinst_1/diagnostics/logs/ReportsServerComponent/RptSvr_dev-wls_asinst_1/console~RptSvr_dev-wls_asinst_1~1.log

 

Upon checking console~RptSvr_dev-wls_asinst_1~1.log we didn’t find much information.

However we checked rwserver_diagnostic.log in same location and we found following error message

[2025-04-08T20:36:47.506+05:30] [reports] [INCIDENT_ERROR] [REP-50600] [oracle.reports.server] [tid: 10] [ecid: 0000POLw7MfFo2c5xjg8yW1bxJi2000001,0] REP-50600 : Broadcasting is disabled. Please enable cosnaming for Reports discovery.  [[ oracle.reports.RWException: IDL:oracle/reports/RWException:1.0         at oracle.reports.utility.Utility.newRWException(Utility.java:1053)         at oracle.reports.server.RWServer.startServer(RWServer.java:1123)         at oracle.reports.server.RWServer.jniMain(RWServer.java:307)

 

Solution:-

The issue is generally observed if the system has firewall enabled.

In our case firewall was disabled however it was not disabled on startup and when server came on it started the firewall service.

#systemctl stop firewalld #systemctl disable firewalld

 

Upon executing above, we finally fixed the issue and  report server started successfully.