Microsoft KB Archive/897666

= An event ID 1080 message is logged in the System log every three seconds in a clustered environment in Exchange Server 2003 SP1 =

Article ID: 897666

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange Server 2003 Service Pack 1

-





SYMPTOMS
Consider the following scenario. You are using Microsoft Exchange Server 2003 Service Pack 1 (SP1) in a clustered environment. In Exchange System Manager, you manually add a domain controller for the Configuration domain controller on the Directory Access tab of the server properties. After you close the server properties, you open the server properties again, and then you click to select the Automatically discover servers check box on the Directory Access tab. In this scenario, the following event is logged in the System log every three seconds. This event is logged even though the Exchange services are operating as expected: Event Type: Error

Event Source: ClusSvc

Event Category: Database Mgr

Event ID: 1080

Date:

Time:

User: N/A

Computer:

Description: Cluster service could not write to a file (C:\DOCUME~1\ADMINI~1.DIE\LOCALS~1\Temp\CLS77.tmp). The disk may be low on disk space, or some other serious condition exists.

Data: 0000: fa 03 00 00 ú…

Additionally, the following entries are logged in the Cluster.log file every three seconds:

000006a8.00000fa0::2005/04/27-09:54:13.085 INFO [CP] CppRegNotifyThread checkpointing key System\CurrentControlSet\Services\MSExchangeDSAccess\Instance0 to id 3 due to timer

000006a8.00000fa0::2005/04/27-09:54:13.085 INFO [Qfs] QfsGetTempFileName C:\DOCUME~1\ADMINI~1.DIE\LOCALS~1\Temp\, CLS, 119 => C:\DOCUME~1\ADMINI~1.DIE\LOCALS~1\Temp\CLS77.tmp, status 0

000006a8.00000fa0::2005/04/27-09:54:13.085 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\ADMINI~1.DIE\LOCALS~1\Temp\CLS77.tmp, status 0 000006a8.00000fa0::2005/04/27-09:54:13.085 INFO [Qfs] QfsRegSaveKey C:\DOCUME~1\ADMINI~1.DIE\LOCALS~1\Temp\CLS77.tmp, status 1018

000006a8.00000fa0::2005/04/27-09:54:13.085 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\ADMINI~1.DIE\LOCALS~1\Temp\CLS77.tmp, status 0

000006a8.00000fa0::2005/04/27-09:54:13.085 WARN [CP] CppCheckpoint failed to get registry database System\CurrentControlSet\Services\MSExchangeDSAccess\Instance0 to file C:\DOCUME~1\ADMINI~1.DIE\LOCALS~1\Temp\CLS77.tmp error 1018

000006a8.00000fa0::2005/04/27-09:54:13.085 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\ADMINI~1.DIE\LOCALS~1\Temp\CLS77.tmp, status 2

000006a8.00000fa0::2005/04/27-09:54:13.085 WARN [CP] CppRegNotifyThread CppNotifyCheckpoint due to timer failed, reset the timer.



CAUSE
This problem occurs because the  subkey is removed from the following subkey in the scenario that is described in the &quot;Symptoms&quot; section:

The  subkey is removed only if no registry subkeys are under the   subkey. By default, no subkeys are under the  subkey.

The  subkey is included in registry synchronization in Exchange Server 2003 SP1 clustering. Therefore, the events that are described in the &quot;Symptoms&quot; section are logged when this subkey is missing.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

Restart requirement
You do not have to restart the computer after you install this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfix.

File information
The 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 tool in Control Panel. Date        Time   Version            Size    File name --  07-Jul-2005  19:27  6.5.7233.35     3,210,752  Exmgmt.exe



WORKAROUND
To work around this problem, use the Cluster Server Recovery utility to restore the Exchange system attendant cluster resource checkpoint.

Note To use this workaround, the Exchange virtual server must be online. And, the Exchange virtual server must be logging the events that are described in the &quot;Symptoms&quot; section.

To restore the checkpoint, follow these steps:  Obtain the Cluster Server Recovery utility.

The Cluster Server Recovery utility is included in the Windows Server 2003 Resource Kit Tools. Alternatively, you can download the Cluster Server Recovery utility.

The following file is available for download from the Microsoft Download Center:

Download the Clusterrecovery.msi package now. For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file. At a command prompt, type clusterrecovery.exe, and then press ENTER. Click Browse, click Your_Cluster_Name, click OK, and then click Done. Click Restore cluster resource checkpoints, and then click Next. Click Specify Resource, and then click the   instance.</li> Click Restore, and then click OK.</li> Click Exit.</li></ol>

This workaround will not work if the following conditions are true:
 * The Exchange system attendant is taken offline after the events are logged. Then, the Exchange system attendant is brought back online.
 * Failover occurs after the events are logged.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
If the Exchange virtual server is taken offline and then brought back online, you notice the following behavior:
 * The events that are mentioned in the &quot;Symptoms&quot; section no longer occur.
 * When you view the server properties, you notice that the domain controller that you manually configured for the Configuration domain controller is again listed on the Directory Access tab.

You also notice this behavior if the Exchange virtual server is failed over to another node. If the domain controller that you manually configured for the Configuration domain controller is offline, Exchange services may not operate as expected.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

817903 New naming schema for Exchange Server software update packages

Additional query words: XADM

Keywords: kbqfe kbhotfixserver kbfix kbbug kbpubtypekc KB897666

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.