Log Viewer in NWA displays the error "Connection Refused"

[Former Member]

Dear Experts,

Have updated the latest patches for SAP Net viewer Enterprise portal 7.4 SP12  successfully in Quality server.

But when I'm clicking on the Log and Traces --> Log viewer  getting the error "Connection Refused" and "Log files are not loaded yet.Press Refresh after short time".

The same patches were updated in Dev server where we didn't face any above issue in logs and traces.

Tried following SAP note-1593532 but didn't find any 'FAIL: End of file or no input: 'Operation interrupted or timed out' in  LF.txt

Kindly suggest any solution to resolve the above issue.

Regards,

Ganesh

[former_member224879]

Hi Ganesh,

Can you paste the out put for

      sapcontrol -nr <inst_no> -function ListLogFiles > LF.tx

when you change  this parameter service/protectedwebmethods = DEFAULT

you need to restart services also, i always restart the OS after changing that parameter

since mine are not production systems, also there are security concerns in changing that parameter

and i am not sure changing that parameter will help you here

Thanks and Regards,

Anto

[Former Member]

Hi Ganesh,

Try setting the parameter service/protectedwebmethods = SDEFAULT in default profile with restart and check.

You can also check the defaultTrace log files for more information.

Regards,

Prithviraj

[Former Member]

Hi Prithviraj,

The default profile already contains the mentioned parameter service/protectedwebmethods = SDEFAULT

And also in default trace log also nothing is updating.

Please suggest any alternate solution.

Regards,

Ganesh

[former_member198633]

Hello Ganesh,

NWA uses SAPControl commands to read the logfiles. Setting the protectedwebmethods SDEFAULT (Secure DEFAULT) just makes these SAPControl calls more restricted.

I suspect the log files in the ..\usr\sap\ folders (example ..\usr\sap\<SID>\<Instance>\j2ee\cluster\server<x>\log\) are too large and/or too many. Please backup these files and move them out of ..\usr\sap folder structure and retry the Log Viewer in NWA.

Best Regards,

Peter

[Former Member]

Dear Prithviraj,

As mentioned parameter service/protectedwebmethods = SDEFAULT was already present but I changed it from "SDEFAULT" to "NONE" and restarted the server. The error got resolved and  we are able to see inlogs and traces NWA page.

Is this recommended to change the parameter value from "SDEFAULT" to "NONE".

Please suggest ???

Regards,

Ganesh

[former_member185239]

Dear Ganesh,

You need to set the parameter service/protectedwebmethods = NONE+OSExecute , other wise sapcontrol will not able to run most of the executables at operating system level

for example , if you run SUM tool next time , it will give error while entering <sid>adm user password.

So it is better to keep the value as below

service/protectedwebmethods = NONE+OSExecute

or

service/protectedwebmethods = DEFAULT

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi Ganesh,

The value for the parameter should be either DEFAULT or SDEFAULT. Recommended SDEFAULT

The reason is..

There is a new security feature introduced. The value of property "service/protectedwebmethods" in the default profile "DEFAULT.PFL" could be changed from "DEFAULT" to "SDEFAULT" as shown:
service/protectedwebmethods = SDEFAULT

Since release 7.20 of AS Java kernel, the default security constraints for SAP Instance Agent could be done more restrictive. In this way, the access to Web methods GetVersionInfo, ListLogFiles and ReadLogFile is not allowed without authentication anymore.

Java standalone Web service proxy, which is used by the Log Viewer tool to read log records via SAP Instance Agent Web service, is now supplied with the correct credentials in order to log in correctly and get needed data even in case the used Web methods are now protected.

For more details, check SAP Note 1439348 and SAP Note 927637.

Regards,

Prithviraj.

[Former Member]

Dear Prithiviraj,

Again tried changing the default profile parameter "service/protectedwebmethods" to SDEFAULT and restarted the server but faced the same issue "log viewer in NWA:- Connection Refused"

Afterwards changed "service/protectedwebmethods" to Default and restarted where I the error is not seen.

Is it ok to keep the parameter Default ???

Regards,

Ganesh

[Former Member]

Hi Ganesh,

Not a problem, you can keep the parameter to DEFAULT.

Regards,

Prithviraj.

[former_member198633]

Hi Ganesh,

Please make a test with the following profile settings. Modify it to look like this: 'service/protectedwebmethods = SDEFAULT -GetVersionInfo -ListLogFiles -ReadLogFile'.

Then restart the service:

• from command line by executing ..\usr\sap\<SID>\<Instance>\exe\sapcontrol -nr <instance number> -function RestartService [-user <OS user> <password>]

OR

• from SAP Management Console -> right click on the SID -> All Tasks -> Restart Service

This way you keep the SDEFAULT settings, and only the parameters related to log operations will be removed from the protected list.

Best Regards,

Peter

[Former Member]

Peter Tari has the correct fix.

I had the issue. Added this to my default.pfl. Stopped SAP (sapmmc). Restarted windows SAP services. Startsap. problem solved.

per oss note 2246609 in order to read the logs with logviewer

service/protectedwebmethods = SDEFAULT -GetVersionInfo -ListLogFiles -ReadLogFile -ParameterValue -J2EEGetProcessList