Comments
32 comments
-
Hi
i'm still using SQLBackup v6.3 and have had the error on one cluster. I re read this thread and did the following
took sql backup agent resource offline then delete the keys, apply and OK
bring sql backup agent online
take sql backup agent offline
add the keys back in then apply and OK
bring sql backup agent online
I no longer get the errors in the event log -
RBA wrote:By removing 'keys for replication' I specifically mean in Cluster Administrator, not in the registry.
Can you confirm that there are no entries here? This bug can also occur when using Microsoft Exchange on your cluster.
Alternative Resolution
We came across this problem on our SQL Server 2008 database servers, whilst the above recommendation may help resolve the issue we found that you do not need to remove the registry entries from the "SQLBackupAgent" resource in Cluster Administrator. To follow best practices and to resolve this error you should create dependencies for the "SQLBackupAgent". The "SQLBackupAgent" should be configured within the Cluster Administrator to be dependant on the "SQL Server Agent".
Regards
Craig
Add comment
Please sign in to leave a comment.
Event Type: Error
Event Source: ClusSvc
Event Category: Database Mgr
Event ID: 1080
Date: 9/1/2009
Time: 10:12:36 PM
User: N/A
Computer: xxxxxxxxxxxxx
Description:
Cluster service could not write to a file (C:\DOCUME~1\MCS64\LOCALS~1\Temp\CLS623.tmp). The disk may be low on disk space, or some other serious condition exists.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00 00 00 ....
I have upgraded to 6.2 from 6.0 and still have the same error. i have also clean installed and still have the same problem. The disk is not low on space, and the account the cluster service runs under (MCS64) does have access to write to that directory. Any ideas?
-js