Error when trying to configure HP Network Teaming

[Marek Konecny]

Dear all,

I have a few w2k servers using network teaming on 2x NC7781 adapters (integrated on ProLiant DL380). Teaming was configured after the system installation and is working. However, when I start 'HP Network Configuration Utility 7' now I get a message: "An error occurred due to invalid data in the XML file used by this application. The XML file has been corrupted and should be reinstalled from the installation media". After closing this message second message is displayed - "RaisePropertyUi Failed: 0x8000ffff".

I have upgraded to latest NIC driver and HP Network Configuration Utility versions, but problem persists.

Systems are:
ProLiant DL380 (2x NC7781 integrated)
Windows 2000 Server SP4
StoneSoft StoneBeat Security Cluster
Trend Micro IMSS / IWSS

Thanks in advance for your help.

[Martin Giles_1]

Did you ever get a resolution to this problem, as I now have exactly the same error on identical hardware and software.

If you do have any further info please email me at Mgiles@csc.com

Thanks

Martin.

[Kevin Laws]

I just had similar, and the reason was one nic was set for DHCP and the other was not. I set both for DHCP and all was fine.

Hope this helps.

Rgds,

Kevin.

[Brian Vlootman_1]

We've had the same problems as you describe.

The solution was to uninstall the NICs from the Device Manager and have W2K install them again after a scan for new hardware.

[Vijay_44]

The problem occurs with newer NIC driver running with older Network configuration utility. Upgrading to the latest Network configuration utility fixes the issue.

[Paul Richardson_3]

I also have this problem and cannot solve it. Does anyone have any more ideas?

[Nathan Gervais]

As Vijay mentioned above,

Version 7.70 of the Network Utility released on 18 Aug 2004, fixes this specific issue.

http://h18007.www1.hp.com/support/files/server/us/download/19948.html

[Stephen Ostendorf]

Actually version 7.70 does not resolve this issue because I didn't get this error before I installed 7.70. Are there any other solutions?

[Martin Lebeau]

I have the same problem on one DL380 with 2 X NC7781 NIC and the same problems on one ML370 with one NC7781 and NC7770.

To this date, I have the latest network drivers and the latest HP network config utility.

Problem persist

help !

[Paul Richardson_3]

I have only had the problem since upgrading to 7.70.

Any other ideas anyone?

[Harry Oldenkamp_1]

If exist, remove the HP Network Team #1 and/or HP Network Team #2in the "Network and Dial-up Connections" and in the registry.
Reboot the server and try to configure the Team

[zschokkebros]

Last night we were updating our 100 ProLiant servers trough Insight Manager 7. We also discovered the problem with the HP Network Configuration Utility 7.70. After a few tests we found two workarounds that's working for us.

1. If you have allready installed HP Network Configuration Utility 7.70 and you have problems. Check if you are using the latest NIC drivers. Install (downgrade) to HP Network Configuration Utility 7.60 (cp004126.exe) and after that reinstall HP Network Configuration Utility 7.70.

2. If you have currently a version of HP Network Configuration Utility below 7.60 then install the latest NIC drivers, then install HP Network Configuration Utility 7.60 and after that you have to install HP Network Configuration Utility 7.70.

Or

create a deployment task with a custom baseline within the Insight Manager that contains:(in this order!)

1. latest NIC driver
2. HP Network Configuration Utility 7.60
3. HP Network Configuration Utility 7.70


Good Luck
Daniel and Markus

[Paul Richardson_3]

I have now sorted this problem.

1 - upgrade all nic drivers to latest version

2 - uninstall 7.70

3 - remove all refs to teamed nics (search for name of team) from registry

4 - reboot

5 - verify all nics installed correctly (device manager)

6 - reinstall 7.70

7 - Presto!

[Kenneth Zimmerman]

I've got the same issue w/ the "RaisePropertyUI Failed 0x8000ffff" issue. I'm running an old proliant 1600, with an onboardNetelligent Fast Ethernet controller, and an identical PCI version of the card.

I'm unable to even get to the point to where i could create a team, so i have no way to remove them from the registry at all. This is off a completely fresh install of win2k3 server. Both NIC's get recognized, and are functioning properly according to the device manager.

I've tried installing the teaming utility from as far back as smarstart 5.5, and i still recieve this error. When attempting to install the win2k3 specific edition of network teaming that i downloaded from HP's site, it returns the error of "the software willnot be installed because the hardware is not present, or the software/firmware does not support it"

Any suggestions would be a HUGE help on how to get this working, as i'm about to defenistrate (your new word for the day folks) the server.

[Dan_318]

Marek, I presume you still looked for a teamed entry in the registry. This problem may be that the software creates a bogus team entry in the registry upon software installation. I have the identical problem and I will try the software removal and registry search/delete method and I will repost on my results. Regards.

[Jack_128]

Can any one confirm the above steps from Paul work. As i have a customer with a similar problem.
An error occurred due to invalid data in the XML file used by this application. The XML file has been corrupted and should be reinstalled from the installation media
sys info
Product Name ProLiant DL380 G3
BIOS Version P29
BIOS Release Date 05/01/2004
OS Operating System Commercial Name Microsoft Windows 2003 Server Enterprise Edition.
latest support pack.
The unit is part of a cluster and the customer concerns are:
if removing the team and reinstalling the card does not sort the
problem, I will not be able to re-establish the team and therefore will
have a cluster node with no LAN redundancy.

[Dan_318]

Here is what I did:
1. BACKED UP MY REGISTRY. Removed reference to team from registry by exporting the reference before deleting it. This paid off because I must have removed the wrong entry and my nics would not start with any drivers. So I had to reinstall registry entrys and then I HAD TO roll back the NIC drivers to get them to work again. After that nightmare I did this:
2.Installed latest NIC drivers.
3. Reboot
4. Intalled HP Network Configuration Utility 7 for Windows Server 2003 7.71.0.0 for Win2003 Server
5. Reboot
6. Set up my NIC team!

Couple of things I wonder about.
1. I imported all of the removed registry entrys and then rolled back the NIC drivers then updated to latest NIC drivers. Then I installed HP Network Config-7 and it worked. This makes me wonder if I should have just rolled back the drivers first then upgraded the NIC drivers then installed the HP Net/Config-7 and would that have worked? Thank goodness I exported the registry keys i tried to delete. That export helped me avoid a whole registry restore.
I have had similar problems with other versions of HP Net/config.
It works like a champ now.
Thank you all for posting the problem and the solutions. Without out this I may have been up all night!

[Eric_237]

I had this same exact issue (xml corrupt message when trying to open the teaming utility).

To fix this (a Windows 2000 server), I did the following:

1. updated the proliant support pack on the server from 6.4 to 7.10.

2. Updated the teaming utility to the latest version (currently 7.71).

3. Updated the NIC drivers to the latest version (7.80). NOTE that this was required as the teaming utility gave me a message that the 7.40 drivers on the NICs would not work with the latest teaming utility. So I had to put on 7.80.

Worked fine after this.

Note that I did not do ANYTHING in the registry.

[Leonardo Curcuruto]

HP gave us the following answer:

Yes, they have some problems with updating the 'Network Configuration Utility 7'.

Solution:

1. Go to the properties of 'My Network Places' on the desktop.

2. Choose a network connection and open the properties.

3. Click on 'HP Configuration Utility' and click then on the 'Uninstall' button below.

We will test it and place the result in a few houres hier.

[Leonardo Curcuruto]

Ok, I have now the definitively solution for this problem:

This describes the right way:

1. Update everything you can (Server BIOS, NIC Firmware, NIC driver)

2. Uninstall the 'Network Configuration Utility' (look at the previously posting)

3. Install the newest version of the 'Network Configuration Utility'

Now it should work.

Good Luck!

[Guillem]

Hi,

I have just solved this same problem.
Just have to download the latest driver, V7.80, and the latest Network configuration utility. Then install the driver, and then the configuration utility. You don't have to unistall anything and all goes OK.

Good luck!!

Guillem

[Networker_2]

Dear all,

I had identical issue with HP proliant G4 servers (NC7782 Integrated NICS). I tried everything, even i removed the HP configuration management utility and reinstalled it from SMARTSTART but it never resolved.
Then i removed the installed NIC's from the Device Manager. It did the trick!
The error that i encontered was , The Xml file is corrupted and needs reinstallation from source.
I had two other servers which had some funny problems like, one of them showing 100 mbps while it was a gigabit NIC and the other showing 1 Gig. I tried the same on these and they worked.

Note: Even after removing them from the device manager if it never works, then follow the procedure mentioned below:

Remove Both the NIC's from the Device Manager (dont do it physically only software)
Without re-installing them, restart the server.
After you login, go to Device manager and click the "Scan for Hardware Changes" button.
The server will automatically install them again. After that when you get the confirmation of device working properly, team these newly installed NICs. Ignore the change in the number of Local area connections.

Best of Luck.

[Sys Admin]

I know this thread is old, but I am providing this information in case anyone else comes across the problem.

For myself I had to completely uninstall both adapters from Device manager, reboot, before I could get the NICs to work again.

Hope this helps.