Cluster service could not write... RG Ver 7.2.1.82
joserami
Posts: 3
Hello Everyone,
We are running Red Gate Version 7.2.1.82 in a clustered environment. A while back we fixed this error by upgrading to a higher version of the Redgate Software, but seems it came back.
Here's the error:
Event Type: Error
Event Source: ClusSvc
Event Category: Database Mgr
Event ID: 1080
Date: 11/11/2013
Time: 9:23:35 AM
User: N/A
Computer: <<SERVER NAME>>
Description:
Cluster service could not write to a file (C:\DOCUME~1\!CLUST~1\LOCALS~1\Temp\CLSC67F.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
Has anyone else countered this problem, and if so, how was it fixed?
Thanks!
We are running Red Gate Version 7.2.1.82 in a clustered environment. A while back we fixed this error by upgrading to a higher version of the Redgate Software, but seems it came back.
Here's the error:
Event Type: Error
Event Source: ClusSvc
Event Category: Database Mgr
Event ID: 1080
Date: 11/11/2013
Time: 9:23:35 AM
User: N/A
Computer: <<SERVER NAME>>
Description:
Cluster service could not write to a file (C:\DOCUME~1\!CLUST~1\LOCALS~1\Temp\CLSC67F.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
Has anyone else countered this problem, and if so, how was it fixed?
Thanks!
Comments
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
thanks for your post.
The disk isn't even close to being full and the path points to the C:\ drive not the Quorum. We've verified permissions, etc. and it all checks out clean.
This issue first appeared a couple of years back on version 6.x and had something to do with Red Gate's registry key replication.
I know what the work around was back then, but there were side effects that we didn't care for, and it was fixed on a later upgrade... so I am intrigued as to why did it come back, and of course need a solution that wont disable the replication.
thanks again
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8