Could not log on to nwa or sld or visual administrator

[Former Member]

Hello Guys,

I have been struggling to log on to SLD or NWA or Visual Administrator.

Here is the scenario..

I have installed SAP WEB AS 6.40 sp16 on Windows XP professional SP2.

The isntallation was successful. I could start the J2E system. All of the processes started successfully, I mean msg_server, enserver, jcontrol, igswd, and other J2EE processes like SDM, dispatcher, server0.

Then when I started the nwa url as http://computers:50100/nwa, then a logon page prompted. Then I used the Administrator as user id and and password that I set for the Administrator account.

It says authentication failed.

It is the same story with sld and Visual Administrator. The bottom line is I could not log onto the system in any ways. I have been trying for the last one week. But could not succeed. Finally posting to this group. Please help me overcome this.

And for the info, these are the ports that are related are running and listening on my system.

TCP computers:50100 computers:0 LISTENING

TCP computers:50101 computers:0 LISTENING

TCP computers:50102 computers:0 LISTENING

TCP computers:50103 computers:0 LISTENING

TCP computers:50104 computers:0 LISTENING

TCP computers:50105 computers:0 LISTENING

TCP computers:50106 computers:0 LISTENING

TCP computers:50107 computers:0 LISTENING

TCP computers:50108 computers:0 LISTENING

TCP computers:50109 computers:0 LISTENING

TCP computers:50110 computers:0 LISTENING

TCP computers:50113 computers:0 LISTENING

TCP computers:50115 computers:0 LISTENING

TCP computers:50117 computers:0 LISTENING

TCP computers:50118 computers:0 LISTENING

TCP computers:50120 computers:0 LISTENING

TCP computers:50121 computers:0 LISTENING

Any help is really appreciated.

Thanks

[former_member185954]

Hi,

check the jcontrol trace when you are trying to login via visual admin.

Regards,

Siddhesh

[Former Member]

Hi,

Check on any relevant error messages in the defaulttrace file (/usr/sap/<SID>/DV*/j2ee/cluster/server0/log). May be related to authorization issue or issue with ticketing (OSS note 791649).

Regards,

Mike