Error message when you back up a Windows Server 2003-based virtual machine on a Windows Server 2008 Hyper-V-based computer: “GetWriterStatus FAILED for Selected writer [Microsoft Hyper-V VSS Writ …

Consider the following scenario:You run a Windows Server 2003-based virtual machine on a Windows Server 2008 Hyper-V-based computer.The virtual machine has files that reside on the array disk volume.You try to back up the virtual machine by using Windows Server Backup.
Note Windows Server Backup uses the Microsoft Hyper-V VSS writer to create a hardware snapshot. In this scenario, the Hyper-V VSS writer crashes. Therefore, the snapshot is not created. Additionally, you may receive following error message:

GetWriterStatus FAILED for Selected writer [Microsoft Hyper-V VSS Writer], writer is in state [9] [VSS_WS_FAILED_AT_FREEZE]. hrWriterFailure [80042319] When this issue occurs, the following VSS error is logged in the Application log:
An unhandled exception was encountered while processing a VSS writer event callback. The VSS writer infrastructure is in an unstable state. The writer hosting process must be restarted in order to resume VSS functionality.
Writer name: Microsoft Hyper-V VSS Writer
Writer id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer instance: {d18f2732-5a1d-4f18-b82c-433507243560}
Process command line: C:\Windows\system32\vmms.exe
Process ID: 2264
Writer operation: 1013
Writer state: 4
Exception code: 0xe06d7363
Exception location: 02If you run the vssadmin list writers command in Windows Server 2008, “Microsoft Hyper-V VSS Writer” is not listed in the output. Therefore, you have to restart the Hyper-V Management service so that the Hyper-V VSS writer works correctly.
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or tocreate a separate service request, visit the following Microsoft Web site:
( The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.PrerequisitesTo apply this hotfix, you must have Windows Server 2008 installed on the computer.Restart requirementYou have to restart the computer after you apply this hotfix.Hotfix replacement information This hotfix does not replace any other previously released hotfixes. Registry information To use this hotfix, you do not have to make any changes to the registry.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2008 file information note The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment arelisted separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformVssvc.exe6.0.6001.223081,055,74413-Nov-200804:50x86For all supported x64-based versions of WindowsServer 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformVssvc.exe6.0.6001.223081,433,60013-Nov-200806:05x64For all supported Itanium-based versions of WindowsServer 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformVssvc.exe6.0.6001.223082,438,14413-Nov-200805:51IA-64

Information about lingering objects in a Windows Server Active Directory forest

This article contains information about lingering objects in ain a Microsoft Windows 2000-based forest or in a Windows Server 2003-based forest. Specifically, the article describes the events that indicate the presence of lingering objects, the causes of lingering objects, and the methods that you can use to remove lingering objects.
Lingering objects can occur if a domain controller does not replicate for an interval of time that is longer than the tombstone lifetime (TSL). The domain controller then reconnects to the replication topology. Objects that are deleted from the Active Directory directory service when the domain controller is offline can remain on the domain controller as lingering objects. This article contains detailed information about the events that indicate the presence of lingering objects, the causes of lingering objects, and the methods that you can use to remove lingering objects.

Error message on a computer that is running Windows Vista Service Pack 1 or Windows Server 2008: “Stop 0×00000024″

On a computer that is running Windows Vista Service Pack 1 or Windows Server 2008, you may receive a Stop error message that resembles the following:

Stop 0×00000024 (parameter1, parameter2, parameter3, parameter4)NotesThe results of a Stop error message may vary, depending on the system failure settings of the computer.The parameter values may vary, depending on the computer configuration.Not all “STOP 0×00000024″ error messages are caused by the problem that is described in this article.
When the NTFS.sys driver is updating a shared security descriptor, an exception may occur because of a disk error or because a log file is full. In this situation, the NTFS.sys driver may release a shared security descriptor structure prematurely. This behavior causes the NTFS.sys driver to access a freed shared security descriptor structure. Therefore, a Stop error is triggered.

LDAP queries are executed more slowly than expected in the AD or LDS/ADAM directory service and Event ID 1644 may be logged

On a Windows Server 2003-based or Windows Server 2008-based computer that uses an Active Directory Lightweight Directory Services (AD LDS) or Active Directory Application Mode (AD/AM) directory service, certain applications do not perform at the performance levels that are expected.
When you enable field engineering (debug) logging to trace an LDAP query, the following event log shows that the LDAP query is an inefficient query:
Event ID : 1644
Category : Field Engineering
Source : NTDS General
Type : Information
Machine : ComputerName
Message : Internal event: A client issued a search operation with the following options.
Starting node: DC=contoso,DC=com
Filter: (&(objectcategory=user)(gidnumber=29831))
Search scope: subtree Attribute selection: …
Server controls:
Visited entries: 31950
Returned entries: 1 Note The attributes that are used in this event are only examples.
Additionally, you experience a slow response time.
When you inspect the attributes in the search filter, you find that they all have indexes that are defined. Additionally, if attributes do not have indexes that are defined, and you add the indexes through a schema change, the problem persists.
When you create a network trace of the LDAP query, you notice that it is a paged query.
However, the LDAP server can only use one index to process a paged query. This is because LDAP does not have a transaction to end a query, and the implementation for paged searches does not create an expensive context for the query.

SQL Server Questions and Answers, SQL QA