cancel
Showing results for 
Search instead for 
Did you mean: 

No logon possible (no hw ID received by mssg server)

Former Member
0 Kudos

We have restored a copy of our production R/3 system onto another LPAR. I've done the homogenous copy of that system and have done all the post upgrade steps. I was working on it all day yesterday with no problems.

Today, when I stopped/started the system, when I try and login I get the error "No logon possible (no hw ID received by mssg server)"

When looking in the dev_ms log, there really isn't anything out of the oridinary. Looking in the dev_disp log, there are a bunch of logs that say: *** ERROR => MsISnd2: not_attached [msxxi.c 1334]

***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 4297]

Anyone seen this error before? Any help would be greatly appreciated. I do have a OSS message open as well.

Thanks,

Dale Dingmann

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Dale,

this is a quite normal thing after homo copies that are carried out slightly wrong.

The host names in the profiles, cfgtcp option 10 & 12 and the service sapmsSID need fully to match. If one of these is wrong, the dispatcher is not able to find the message server ... (upper & lowercase is of interest as well)

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

Answers (1)

Answers (1)

Former Member
0 Kudos

Recently, we did move some of the 4.6 systems onto new AIX lpars, and everytime we had to add sapms service entry for the particular SAP instance on the new lpar's services file

In /etc/services, we have to add the following

sapmsSID<tab>36xx/tcp

where SID is sap instance ID

<tab> we have to give tab space here

xx is the instance number

For eg.

sapmsADA 3602/tcp

If you are adding this entry in the last line of the file, then be sure to press Enter so as to leave a blank line at the end of the file.

Former Member
0 Kudos

Thanks for the responses. The fix was making sure that CFGTCP option 10 and 12 were the same. We had a uppercase hostname in option 12 and lowercase in option 10. Once we changed that, we were good.

Thanks again!