Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. SCVMM Admin Console crashes with error 1612 and Event ID 19999 and 1 are logged to the VM Manager event log

SCVMM Admin Console crashes with error 1612 and Event ID 19999 and 1 are logged to the VM Manager event log

Source: Microsoft Support

↑ Back to the top

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top

Symptom



The admin console crashes multiple times per day or perhaps the customer is unable to open the admin console. Sometimes the error displayed is 1612 (lost connectivity) or 1700 (during a refresh). These are only symptoms and not the underlying problem.

In the VM Manager event log, the following events are logged:


Log Name: VM Manager
Source: Virtual Machine Manager
Event ID: 19999
Level: Error
Description:
Virtual Machine Manager (vmmservice:6296) has encountered an error and needed to exit the process. Windows generated an error report with the following parameters:
Event:VMM20
P1(appName):vmmservice
P2(appVersion):2.0.3444.0
P3(assemblyName):E.Adhc.Operations
P4(assemblyVer):2.0.3444.0
P5(methodName):M.V.E.A.VirHostDatabaseUpdater.PostVirtualNetworkUpdate
P6(exceptionType):System.NullReferenceException
P7(callstackHash):d1e7

Log Name: VM Manager
Source: Virtual Machine Manager
Event ID: 1
Level: Error
Description:
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.VirtualManager.Engine.Adhc.VirHostDatabaseUpdater.PostVirtualNetworkUpdate(Dictionary`2 nics, List`1 dbNics, SqlContext ctx)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDatabase()
at Microsoft.VirtualManager.Engine.Adhc.HostRefresher.UpdateAllInformation(Host host, HostUpdateInformation hostUpdateInfo, Guid taskID)
at Microsoft.VirtualManager.Engine.Adhc.HostRefresher.RefreshData(HostReference hostRef)
at Microsoft.VirtualManager.Engine.RefreshDriver`1.RefreshThreadFunction(Object obj)-2147467261

↑ Back to the top

Cause

This issue occurs if the Virtual Machine Manager Server or Hyper-V host that's being managed by Virtual Machine Manager is reporting 2 NICs with the same name. This issue is a known bug that will be corrected in the next version of VMM.

↑ Back to the top

Workaround



The workaround options at this point can be:
  1. Update the network card drivers in the hope that it resets the names.
  2. Avoid binding virtual networks to either of the duplicate NICs.
  3. Disable all but one of the duplicate NICs on the host.
  4. Disable host refresh and only do on-demand refresh (for all hosts but the affected one).
  5. Don’t manage the host with VMM.


Note Another potential cause has been reported that if the Host has NIC teaming enabled this issue can occur.

Resolution


Determine which Host is experiencing the problem and remove the ghosted NIC. Either of the following methods will work.

Method 1



Use the devcon utility which can be downloaded from KB311272. After installing devcon, open a command prompt and navigate to the directory where it’s located. Then run the following commands.

devcon listclass net
devcon findall =net

The output should be identical. If not, then any additional devices will have to be manually deleted from the Host.

Method 2



An alternative can be to use the following command:

systeminfo (if local)
systeminfo /s <machine_name> (if remote)

The output will display all NICs for a given machine.

Now the final step is to actually remove the ghosted NIC from the Host. Again, we’ll want to use the DEVCON utility.
  1. From the output from the previous devcon commands, locate the ghosted NIC. The line will look similar to the following:

    PCI\VEN_14E4&DEV_1677&SUBSYS_01A81028&REV_01\4&22443A69&0&00E5: Broadcom NetXtreme 57xx Gigabit Controller
  2. Remove the ghosted NIC by typing the following command:

    devcon remove @"PCI\VEN_14E4&DEV_1677&SUBSYS_01A81028&REV_01\4&22443A69&0&00E5"
  3. An alternative solution to remove the ghosted device is as follows:

    a. Click Start, click Run, type cmd.exe, and then press ENTER.
    b. Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
    c. Type Start DEVMGMT.MSC, and then press ENTER.
    d. Click View, and then click Show Hidden Devices.
    e. Expand the Network Adapters tree.
    f. Right-click the dimmed network adapter, and then click Uninstall.


For additional information on this process, please refer to KB269155.

↑ Back to the top

Status

This issue is resolved in Microsoft System Center Virtual Machine Manager 2008 R2.

↑ Back to the top

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.


TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top

Keywords: kbnoloc, kbrapidpub, kbnomt, kb

↑ Back to the top

Article Info
Article ID : 969269
Revision : 3
Created on : 4/17/2018
Published on : 4/18/2018
Exists online : False
Views : 104