SAP Netweaver is not working after changing the motherboard

[Former Member]

We are running SAP on a HP DL380 G7 using Windows 2008.  After replacing the motherboard last night we are having trouble with Netweaver.  SAPGui works fine, but we cannot using the transaction launcher or quick links in Netweaver.  When we use the menu to launch a transaction in Netweaver, it works.  The message that comes up is "connection to partner 'sapprd01.wheels.local:80 broken" the detailed message shows this information: Component, NI (network interface); Release 710, Version 39, Module nicxi.cpp, Line 4694, Method NIRead: P=192.168.11.254:80; L=192.168.11.254:56890; Return Code -6; System Call recv; Counter 1.

We do have connection to the server because we are able to launch transactions from the menu and SAPGui.  Please don't suggest we use SAPGui or the menu options.  The problem is that we cannot use the transaction launcher or the quick links and we have grown accustomed to having access to those.

Interestingly this same exact thing happened a while back when we failed over to another server because of a comm line failure.  Everything worked except the transaction launcher and the quick links.  When we failed back to the primary server - it started working again.  I'm wondering if there is some kind of license issue that checks something on the hardware. 

[Nibu]

Hi

http port you given is  80 ?

Is your http/https port in SMCIM active ? Is there any port block in firewall happens?

[Former Member]

HTTP port 8000, SMTP port 25 and HTTPS port 44300 are all active.  These are the same ports that are active on my QA system and it is working okay.  The firewall is not turned on for either system - we are managing security at the environment level.  Again - everything was working just fine until we changed the mother board.  Then we started getting those errors. Is it possible that we have some kind of licensing issue?  There are a few dialogs that say changing the NIC will impact the System Key.  The NIC on this system is on the motherboard and that is different.

[bxiv]

Before the mobo replacement did you take the system down on a regular basis or did it stay online for months and changes were made for an upcoming planned downtime?

Where do you think this is a license issue?  At the <SID> level inside of SAP or a license issue with transaction launcher/quick links?

[bxiv]

What happens if you run:  SIAC_PUBLISH_ALL_INT

It should refresh ITS services.

[Former Member]

I cannot run that as a transaction or as a program from SE38.  Is that an OS call?

[bxiv]

You should be able to call that as a transaction.