Can't config network teaming & team driver update errors re setup dll

[banjo67xxx]

Hi,

I'm running WIN 2008 R2 64bit on an HP DL360 G7 and I'm trying to configure network teaming for LACP to a pair of Cisco Catalyst WS-C3750G-24-T-S switches.

Every time I try to open up the control panel window for the HP Network Configuration Utility (NCU) version 10.10.0.11 it errors with

Code: [Select]

CPQTEAM.EXE has stopped working
And the problem details are ...

Code: [Select]

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: cpqteam.exe
  Application Version: 10.10.0.11
  Application Timestamp: 4c506d31
  Fault Module Name: cqnicif.dll
  Fault Module Version: 10.10.0.11
  Fault Module Timestamp: 4c506ad1
  Exception Code: c0000005
  Exception Offset: 00000000000374b0
  OS Version: 6.1.7601.2.1.0.272.7
  Locale ID: 1033
  Additional Information 1: f1bb
  Additional Information 2: f1bb43381f4d83f1f438ba15a377e653
  Additional Information 3: 7ca6
  Additional Information 4: 7ca62033363c7d4d0cc56c828c01a395

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
So I tried to upgrade the team driver to version 10.80.0.0 (HP NCU driver for Win2008 R2 from the HP website)  and that failed a few times with ...

Code: [Select]

Setup is unable to install a setup dll

but today when I wanted to get the exact error message it successfully upgraded, but the config utility is still failing with

Code: [Select]

CPQTEAM.EXE has stopped working
Problem details ...

Code: [Select]

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: cpqteam.exe
  Application Version: 10.80.0.25
  Application Timestamp: 51cb2d26
  Fault Module Name: cqnicif.dll
  Fault Module Version: 10.80.0.25
  Fault Module Timestamp: 51cb2c4e
  Exception Code: c0000005
  Exception Offset: 000000000003dc80
  OS Version: 6.1.7601.2.1.0.272.7
  Locale ID: 1033
  Additional Information 1: fa45
  Additional Information 2: fa450a6374dffeebab8d5614663e4ee3
  Additional Information 3: 87b6
  Additional Information 4: 87b6dc95492fca08266e460ba3740c04

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


Anyone got any ideas?

PS: I have looked at
http://h30499.www3.hp.com/t5/Windows-Server-2008/Problem-when-running-hpteam-cpl-and-klick-quot-HP-Network-Team/td-p/4719081#.UuUUrDdFCRs
and can't find any subfolder in that part of the Registry which mentions the Team driver. Folder 009 is WAN Miniport. There some folders that represent each NIC, but I'm not going to edit the registry unless I'm sure I'm editing the correct section.

Also looked at
http://h30499.www3.hp.com/t5/HP-BladeSystem/CPQTEAM-crashing-on-latest-bl460g7/td-p/5265994#.UuUUIDdFCRs
but the solution that it references is not there

BTW the drivers that I have updated to were released on the same day ...

From http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome/?sp4ts.oid=4091409&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3DswEnvOID%253D4064%257CswLang%253D%257Caction%253DlistDriver&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken#Driver - Network

HP Broadcom 1Gb Multifunction Drivers for Windows Server x64 Editions (American, International)   
7.8.6.0
10 Sep 2013
3   
7.4.14.0 (B)
19 Feb 2013
 
HP Network Configuration Utility for Windows Server 2008 R2 (American, International)   
10.80.0.0
10 Sep 2013
16.6   
10.70.0.0
19 Feb 2013

 

[banjo67xxx]

SOLVED

Eventually after deleting the drivers for all NICs and connecting via ILO then reinstalling NIC drivers, Team drivers, and BIOS firmware, and rebooting it finally worked.

[Geek-9pm]

Glad we were able to help you! 

Often the solution to a problem is  ---
the ability to state clearly what it sis.

[banjo67xxx]

LOL!

Actually, you have a point.

An import part of Analytical TroubleShooting (TM) is to methodically document the Object/Defect and specify the What/When/Where/Extent of the problem, and so by posting the question on this forum forced me to use this process to demonstrate that I'm not a typical noob. By doing the required research I was able to resolve the issue for myself.

* ATS - Copyright Kepner Trego Inc.