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.

Thread Deadlock When Windows NT Backup Is Stopped


View products that this article applies to.

This article was previously published under Q185694

↑ Back to the top


Symptoms

When you are running a backup using the Windows NT Backup program against a Microsoft Exchange Server computer, if the backup is stopped before the backup completes, Windows NT Backup stops responding (hangs).

↑ Back to the top


Cause

When a backup is stopped, the closing procedure blocks infinitely, waiting on a thread's handle to close. The thread handle is never closed, so Windows NT Backup stops responding.

↑ Back to the top


Resolution

Exchange Server 5.5

To resolve this problem, obtain the latest service pack for Microsoft Exchange Server version 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack

Exchange Server 5.0

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server 5.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Component: Exchange Database Engine

File nameVersion
Edbbcli.dll5.0.1461.31

Exchange Server 4.0

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Component: Exchange Database Engine

File nameVersion
Edbbcli.dll4.0.997.1

↑ Back to the top


Status

Exchange Server 5.5

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Microsoft Exchange Server Service Pack 1.

Exchange Server 5.0

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.0.

Exchange Server 4.0

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 4.0.

↑ Back to the top


Keywords: KB185694, kbfix, kbexchange500presp3fix, kbbug, kbhotfixserver, kbqfe

↑ Back to the top

Article Info
Article ID : 185694
Revision : 5
Created on : 10/30/2006
Published on : 10/30/2006
Exists online : False
Views : 360