Skip to main content

REP-52262 Diagnostic output is disabled

You may have noticed that when you have a new installation of  reports 11.1.2.0 when you try to run a PDF report or even if you simply try to do a  showjobs request you get the error REP-52262 Diagnostic output is disabled. It seems that in a new installation for security reasons diagnostic output from the URL is disabled by default.


If get this pesky error it is actually quite easy to resolve using these easy steps:
1) Backup the rwservlet.properties file located  in %DOMAIN_HOME%\config\fmwconfig\servers\WLS_REPORTS\applications\reports_11.1.2\configuration
For example: 
C:\Oracle\Middleware\user_projects\domains\FRMDomain\config\fmwconfig\servers\WLS_REPORTS\
applications\reports_11.1.2\configuration
2) Then edit the rwservlet.properties the file in notepad++
3) Search for the the lines
 <!–webcommandaccess>L1
4) Remove them from comment so they will look like this
 L1
5) Then change the value from L1 to L2
So it will look like this
 L2
6) Save the file
7) Now all that’s left to do is to restart the WLS_REPORTS domain
 This can be done either via:
1) The weblogic EM console
2) The stop and startup scripts in program files of the server machine
 
After the WLS_REPORTS is restarted you will see it working!
A shout out to PITSS for helping resolve the issue.
 

Comments

Popular posts from this blog

ORA-01033 Oracle initialization or shutdown in progress

ORA-01033 Oracle initialization or shutdown in progress When you connect oracle 12c plug gable database, Thus time you have get oracle initialization or shutdown in progress error. This error occurred because pluggable database are not initialized. To fix this error connect as sysdba and run  ALTER PLUGGABLE DATABASE ALL OPEN    command. ALTER PLUGGABLE DATABASE ALL OPEN Thanks.

Checking operating system version: must be 5.0, 5.1 or 5.2 Actual 6.1 Failed

This error occurred when we are installing old oracle software in latest OS (Operating System).   Basically Its’s occurring on windows platform.

AFTER LOGON Trigger not perfectly working

AFTER LOGON not perfectly working.  I have tried it on single instance oracle 12c database it's perfectly work but it's not perfectly working on multi instance Oracle 12c database. I have submitted this matter in oracle forum but not found any perfect answer. Do you know why  it's not working ???