Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 49 Source: CPQTeamMP

Source
Level
Description
PROBLEM: This Teaming Miniports configuration Parameters section of the Registry is either missing the <value> Parameter or the Parameter is unreadable. Setting value to <number>. ACTION: No action is required if the Default behavior is acceptable. Otherwise reconfigure the <value> value.
Comments
 
From an HP Support Forum:
Corrupt XML file messages when you click on the VLAN tab of the network configuration utility plus missing VLAN parameter errors in the Windows event log. This might only occur if you have teamed two or more network interface cards. (HP calls each card a Miniport.):
- 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.
- Event ID: 49 from Source: CPQTeamMP. "This Teaming Miniport-Edge Configuration Parameters section of the Registry is either missing the VlanId parameter, or the Parameter is unreadable."
Plus similar errors for VlanDefaultID Parameter, TaskOffloadChecksumIPv4TxTxpOptions Parameter, and the TaskOffloadChecksumIPv4RxTcpOptions Parameter.

These errors are caused by upgrading the network configuration utility. The upgrade keeps the old XML configuration file, which is missing parameters needed by the new version of the utility.

The solution is to rename the directory that the network configuration utility was originally installed in (normally C:\Program Files\HP\NCU), and then reinstall the network configuration utility. That forces it to install the new version of the XML file. Your existing network configuration will be lost."
In my case, I also added the DWORD values VlanID and VlanDefaultID with a zero value and it solved my problem, except that the registry path was HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0009. In addition, when you opened the HP Network Configuration Utility and viewed the properties of the teaming configuration, you got an error whenever you pressed the VLAN property. The registry entry also solved that problem.
Write down the TCP/IP settings of the Team adapter. Launch HP Network Configuration Utility, dissolve the adapters and team them back up. Reconfigure the TCP/IP properties of the Team adapter and check to see if the problem is solved.
In my case, the missed values were VlanID and VlanDefaultID. I added both values under HKLM\SYSTEM\CurrentControlSet\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0008 as a REG_DWORD value with data value 0. This solved my problem.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...