Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Windows Server 2008 Standard running a Hyper-V - Event ID 18160

Answered Windows Server 2008 Standard running a Hyper-V - Event ID 18160

  • Tuesday, December 11, 2012 6:10 PM
     
     
    Sign In to Vote
    0

    Hello everyone,        

    I found this error in our Windows Server 2008 Standard running a Hyper-V Role.

                                                                                                                                                                                                          

    The description for Event ID 18160 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    FD677261-6096-44BC-822C-02246C3C1FB9
    FD677261-6096-44BC-822C-02246C3C1FB9
    %%3222072877
    0xC00CEE2D

    The locale specific resource for the desired message is not present.

    Can you help me us out. Thanks

    Anthony

     

All Replies

  • Wednesday, December 12, 2012 3:18 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Event ID 18160 — Virtual Machine Miscellaneous Operations

    Error Message: Failed to get summary information for virtual machine '%1' (Virtual machine ID %2). Error: %3 (%4)

    To resolve the issue: Try getting the summary information by traversing each of the associations individually or try getting the Msvm_SummaryInformation object again later.

    Well, according to your posting, there is another question, the event is logged incorrect. This issue is recorded in KB 961270:

    A custom event is logged incorrectly when you run a 32-bit application in a 64-bit version of Windows Server 2008 or of Windows Vista
    http://support.microsoft.com/kb/961270

    This problem occurs when you register the DLLs that contain the custom event information in the registry by using a path that contains the following string:%SystemRoot%\System32

    In 64-bit versions of Windows Server 2008 and of Windows Vista, DLLs that are installed by 32-bit applications are put in the following folder: %SystemRoot%\SysWOW64

    Even if you specify the System32 folder when you install a DLL, Windows redirects the System32 folder to the SysWOW64 folder. However, this is not the case for the registry. If you register a DLL in the registry by using a path that contains the %SystemRoot%\System32 string, Windows does not redirect the registration to the SysWOW64 folder. When the 64-bit Event Log service tries to locate the DLLs to retrieve the event information, the Event Log service still uses the System32 folder instead of the SysWOW64 folder. Because the System32 folder does not contain the DLLs, the Event Log service cannot retrieve the event information.

    A supported hotfix is now available from Microsoft to fix this issue. Try the hotfix and give us feedback for further troubleshooting.

    For more information please refer to following MS articles:

    Event ID 18160 — Virtual Machine Miscellaneous Operations
    http://technet.microsoft.com/en-us/library/dd582917(v=WS.10).aspx
    Virtual Machine Fails to start
    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/c67724e6-4420-4b3f-8049-1029902176f9/
    VM not appearing in Hyper-V Manager
    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/135d1385-4b75-4737-80de-f8c517c25f8d/

    Hope this helps!

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Lawrence

    TechNet Community Support

     
  • Monday, December 17, 2012 3:25 PM
     
     
    Sign In to Vote
    0

    thanks Lawrence,

    i did a manual run after applying Fix it 50531 and the backup run successfully. then the next day it faile again. i run command promt to check type > vssadmin list writers. and show me No Error except for this one.

    Writer Banme: ' Microsoft Hyper-V VSS Writer'

       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

       Writer Instance Id: {6bae3693-63f8-429d-98e8-e7e603005e7c}

       State: [5] Waiting for completion

       Last Error: Unexpected error

    Any idea ? thanks

     
  • Monday, December 17, 2012 3:48 PM
     
     
    Sign In to Vote
    0

    I faced something like this in the past.. can you check if this is helpfull ?

    http://social.technet.microsoft.com/Forums/en/winserverfiles/thread/a511f2fa-620d-4b65-b830-4207c5c03e05

    regards

     
  • Monday, December 17, 2012 4:47 PM
     
     
    Sign In to Vote
    0

    thanks ales75.

    i didn't found the > Microsoft Hyper-V VSS writer on the link you've given. any idea what causing this to happen?

    thanks

     
  • Monday, December 17, 2012 5:04 PM
     
     
    Sign In to Vote
    0

    Sorry i mistaked the article..

    here it is :

    http://blog.zensoftware.co.uk/2012/02/10/hyper-v-support-host-vs-guests/

    regards

     
  • Monday, December 17, 2012 7:12 PM
     
     
    Sign In to Vote
    0

    thanks Ales75.

    one more thing, i noticed that the article was for  > Writer name: 'SPSearch4 VSS Writer'. Is it the same as ' Microsoft Hyper-V VSS Writer'.

    your help is greatly appreciated.thanks

     
  • Monday, December 17, 2012 7:30 PM
     
     
    Sign In to Vote
    0

    No, i mean could be a different issue but the following icould lead you hot to proceed for your problem..

    Try to isolate the problem, how many vm are you backin up ? start various backup and see on what virtual machine eventually pops up, the into the virtual machine check log for similar errors related to vss writers.

    Or

    just check all your vm logs.. each vm.. and find for related vss errors 

    in that case you should understand better what vss is causing the error

    Or

    if the error its just the hyper vss write take a look at this article..

    http://support.microsoft.com/kb/958662/en-us

    you already have the hyper vss writer reigstered but, may be re-registering it could solve your problem.

     
  • Tuesday, December 18, 2012 5:42 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    What’s the detailed OS version of your Windows server 2008?

    I found some MS KB which describes similar issue, these articles claim to resolve these problems, install the latest service pack for Windows Server 2008.

    Also you may try below update to fix this issue:

    Update for Windows Server 2008 x64 Edition (KB956697)
    http://www.microsoft.com/en-us/download/details.aspx?id=2711

    For more information please refer to following MS articles:

    Error message when you perform a Volume Shadow Copy Service restore operation: "0x80042409"
    http://support.microsoft.com/kb/978773
    Windows Server 2008 Hyper-V VSS writer is not used during a backup job because of corrupted or invalid virtual machine configuration files
    http://support.microsoft.com/kb/956697
    An update is available for Windows Server 2008-based computers to address issues with backing up and restoring Hyper-V virtual machines
    http://support.microsoft.com/kb/959962

    Hope this helps!

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Lawrence

    TechNet Community Support

     
  • Tuesday, December 18, 2012 3:41 PM
     
     
    Sign In to Vote
    0

    Thanks Lawrence,

    Yes.Server 2008 R2 Enterprise SP1. I am planning to do install the KB956697 tonight if the Backup still fails.

    What I am wondered about was, if the backup run on specified schedule time the backup fails. But, when i do a Manual Backup Once the backup (same configuration as scheduled backup time) runs smoothly and successful (I just did a Restart to one of the guest vm appears to be failing - Event ID 10102) Any idea?

    thanks.

    Anthony

     
  • Tuesday, December 18, 2012 3:48 PM
     
     
    Sign In to Vote
    0

    Anthony that update could work..

    I am ok to run updates in such a blind way, honestly and however i am used to locate the error and where does it happen before. it is useful for the fix and useful for the future.

    anyway i suggest you to check all your virtual machine logs and try to individuate wich is failing , by just looking at vss errors.. 

    second can you check all your virtual machine setting, under integration services if you have vss enabled.

    regards

     
  • Tuesday, December 18, 2012 8:28 PM
     
     
    Sign In to Vote
    0

    thanks Ales.

    Can you clarify what you mean "check all your virtual machine setting, under integration services if you have vss enabled." Can walkthrough for the steps? i just want to make sure i am doing it right.

    thanks

     
  • Tuesday, December 18, 2012 8:40 PM
     
     
    Sign In to Vote
    0

    Well ..

    in Virtual machine manager right click on each vm, setting and the vm settings panel opens, scroll down till integration service right under the vm name setting, on the right there are all the integration services avaible for the vm, the last one is backup (vss). 

    check to have it and if it is marked. like the others.. your error could depends on something so easy like this...

    Regards

     
  • Wednesday, December 19, 2012 7:04 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    > What I am wondered about was, if the backup run on specified schedule time the backup fails. But, when
    > i do a Manual Backup Once the backup (same configuration as scheduled backup time) runs smoothly and successful

    You may retry a scheduled backup and check the result.

    > I just did a Restart to one of the guest vm appears to be failing - Event ID 10102

    Event ID 10102 doesn’t have more information, check event log in the guest to analyze why the VSS snapshot failed and then retry backup operation.

    For more information please refer to following MS articles:

    Event ID 10102 — Virtual Machine Integration Services
    http://technet.microsoft.com/en-us/library/dd582389(v=WS.10).aspx

    Hope this helps!

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Lawrence

    TechNet Community Support

     
  • Thursday, December 20, 2012 5:12 PM
     
     Answered
    Sign In to Vote
    0

    thanks Lawrence,

    i wasn't able to install KB956697 because it doesn't apply to our server (Server 2008 R2 Enterprise).

    anyhow, i was able to run the backup after Restarting the guest VM which appears to be the cause of failed snapshot.

    Thanks,

    Anthony