WAS6.2 Test Suite Logon Problem

[Former Member]

I have installed the MINIWAS Ok on XP Home.

Service starts and stops.

MSLOOPBACK pings ok.

However SAPGUI login gives following error.

Partner not reached (host MJWHOME.,service sapdp00)

Component NI(Network Interface)

Release 6.2

Version 36

MOdule ninti.c

Line 979

Method NIPConnect2

Return Code -10

System Call SO_ERROR

Error No. 10061

Error Text WSAECONNREFUSED

Counter 1

Hosts Snippet

-

---

127.0.0.1 LOCALHOST

10.10.0.10 MJWHOME.

Any help would be appreciated

Martin Ward

[axel_angeli3]

JUst an addition, as this problem occurs regularily and this eems to be the only Google hit on the topic:

If no HW ID received the cause is mostly due to being unable to connect to the message server.

This can be tested by going to the directory where Miniwas is installed, e.g. D:\MINIWAS and executing from a CMD prompt:

saplicence -test pf=DEFAULT.PFL

if it is so, an error message will say: "connect to message server failed"

Solution:

Editing the

%windir%driversetchosts.

file and making sure that an entry exists normally helps:

127.0.0.1 p72367

p72367 is the SAP host name specified in the prfile DEFAULT.PFL

Good luck

Axel

[Former Member]

Craig,

I have un-installed and re-installed the MiniWAS and have installed on d: instead of C:. I don't know why it made a difference but after 4 goes at re-starting process, I now have a miniWAS that I can log into.

Many thanks for your help. Points are in the post.

[Former Member]

strange but I'm glad it's working now!

[Former Member]

Craig,

I do not think that I am getting any message server dying messages when starting the ABAP engine and no matter what settings I have in the hosts file I still gett the warning message on log on. I have re-installed the MS Lopback and have tried logging on without it as well. Please find below a digest of my settings. Maybe you can see something obvious that I am missing

IPCONFIG

C:\Documents and Settings\Martin>ipconfig

Windows IP Configuration

Ethernet adapter msloopback:

Connection-specific DNS Suffix . :

IP Address. . . . . . . . . . . . : 10.10.0.10

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

Ethernet adapter Bluetooth Network:

Media State . . . . . . . . . . . : Media disconnected

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :

IP Address. . . . . . . . . . . . : 192.168.2.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

HOSTS (Partial)

#127.0.0.1 MJWHOME

10.10.0.10 MJWHOME

SERVICES (Partial)

sapmsBSP 3600/tcp

FIREWALL

McCaffee

Port 3600 enabled

Pinging MJWHOME gets 10.10.0.10

Standard network via Wireless

Current ABAP Engine script

C:\MiniWAS>REM =====================================================

C:\MiniWAS>REM Set the Environment for the DB Connect

C:\MiniWAS>REM =====================================================

C:\MiniWAS>set DBMS_TYPE=ada

C:\MiniWAS>set PATH=D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\WINDOWS\syste

m32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\RedStrike\UltraWipe;C:\

MiniWAS;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;D:\sapdb\programs\sap;D:\sap

db\programs\bin;D:\sapdb\programs\sap;D:\sapdb\programs\pgm

C:\MiniWAS>REM =====================================================

C:\MiniWAS>REM Start the Database (SAP-DB)

C:\MiniWAS>REM =====================================================

C:\MiniWAS>cmd /c strdbsBSP.cmd

C:\MiniWAS>set DBNAME=BSP

C:\MiniWAS>x_server

18641 ERROR: XSERVER is already running!

C:\MiniWAS>dbmcli -U c db_warm

OK

Database BSP successfully started !

C:\MiniWAS>REM =====================================================

C:\MiniWAS>REM Start SAP System

C:\MiniWAS>REM =====================================================

C:\MiniWAS>rem del pxastat

C:\MiniWAS>start /B msg_server.exe pf=BSP_D00.pfl

C:\MiniWAS>disp+work.exe break pf=BSP_D00.pfl

dp Ctrl-C enabled

rslgwr1(21): Searching for overlap point in pre-existing SysLog file...

maximum pfclock time: 4294sec (1)

gw Ctrl-C enabled

dp Ctrl-C enabled

dp Ctrl-C enabled

dp Ctrl-C enabled

maximum pfclock time: 4294sec (1)

maximum pfclock time: 4294sec (1)

maximum pfclock time: 4294sec (1)

maximum pfclock time: 4294sec (1)

adjust_clock: delta 2412

IcmHandleArgs: Illegal option break

adjust_clock: delta 2192

adjust_clock: delta 747

• ICM up and operational (pid: 2200) ***

Apologies for 'War and Peace' but I don't know where to go from here.

Many thanks,

Martin

[Former Member]

Do you also have the sapgw00 3300/tcp defined in the services?

sapdp00 3200/tcp

sapmsBSP 3600/tcp

sapgw00 3300/tcp

Have you tried without the firewall active?

[Former Member]

Craig,

Port sections that you have identified exist in the services file.

I still get the problem even if the McAfee and Router Firewalls are disabled

[Former Member]

Craig,

Firstly, a thousand apologies for not replying before now (very bad form). Unfortunately I have been out of the country doing the 'day job'.

On my return I started up the Start ABAP Engine stuff with the intention of sending you a full log with details of network, loopback etc. This time however, the SAP Login worked and I was presented with a normal SAP Login page!

However now if I try to login as any of the default users BCUSER,DDIC I get the following error in the status bar

No Logon Possible (No hw ID received by mssg server)

So close but I've still got a long way to go.

Any guidance would be appreciated.

Regards,

Martin

[Former Member]

If you look in the window "Start ABAP Engine" you'll notice a message about the message server dying. Your loopback is not set correctly I had the same problem recently moving my MiniWas from one system to another.

Double check your MS Loopback and you should be able to get it then.

[Former Member]

Are there any log or Trace files which would help me determine the problem?.

The only log that I 'see' is when I start the ABAP Engine.

Thanks,

Martin

[Former Member]

You will see .trc files and so forth but the problem is not the system the problem is your network settings the SAPLOGON can't find your server.

Did you try starting using "localhost" or your IP address?

[Former Member]

Craig,

I used my FQN and my IP. Will try localhost.

[Former Member]

I tried localhost and its IP equivalent, still no success.

[Former Member]

Perhaps your loopback is not correctly set or your network confirugration is incorrect.

[Former Member]

when you ping mjwhome do you get a response?

[Former Member]

Craig,

Thanks for the prompt response. I can ping the computer name MJWHOME ok.

REgards,

Martin

[Former Member]

Just a strange thing Inoticed in your hosts snippet there is a . after MJWHOME is that so?

[Former Member]

Yes, however even if I remove the period, it makes no difference to the logon 'failure'.

Just an aside, What is the recommended way of starting miniwas

I have tried the Sapdbstart and Sapdbstop in my MiniWAS directory also using the Start SAP ABAP Engine on the Desktop. I have also checked that the SAP BSP Service is running via COntrol Panel Admin. None of these methods has any affect on my problem, but I should be consistent in my approach.

[Former Member]

Basically the SAP ABAP engine icon will start the ABAP instance as well as the DB if it is not already started.

you should then be able to connect to the mini was using the SAP GUI that came on the CD's

then in the sapgui you set the system with the hostname for the system and system number 00

try using the IP address or "localhost" for the connection.

[Former Member]

Also ensure you have your MiniWAS directory shared. Let us know what happens. Tiest

[Former Member]

The share is important but not at this poiunt the share comes into play for the transport system.