Windows 2003 Cluster problem

all_experts used Ask the Experts™
I have a Windows 2003 cluster with two (active/active) nodes. Occasionally, one of the nodes hangs. I have to manually power off and on. At the same time, the fail-over doesnt occur, until I reboot.
I've reviewed windows event logs and found the following:
Cluster File Share resource 'Share Name' has failed a status check. The error code is 64.

What can cause this?

Also, I've found in Application Event Log that MSDTC is not starting. After some searching, I found that MSDTC service needs to be clustered. Does it have to be clustered?

The node that fails has two File share resources, IP Address, Network name, Generic Service( nothing fancy, just a service), Physical Disk, Two generic application (ABE resources).

Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Review the cluster log look around the time error 64 was generated, be advised to adjust the log time +/- to Greenwich mean time.

Does the server and or applications need MSDTC?  Can it be disabled?
Otherwise if it's on cluster it's going to be setup as a cluster resource.


The only thing that is around error 64 in the log is that this share resource failed to failover.

I dont know if I need MSDTC. That's what I am trying to find out.
Do I need it for File Share Resource?

MSDTC reg'ed for file share, not that I'm aware of.

From the log no loss of IP address or network name?

Have the dependancies been reviewed for the file share resources?
Amazon Web Services

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.


I dont see any errors about loss of IP. I mean, if it did loose an IP or a Network Name, it should have failed over. for the file share, the only dependency is the physical drive.

Also, after I restarted server i got these errors:
"Cluster service is requesting a bus reset for device \Device\ClusDisk0."
"The driver for device \Device\RaidPort0 performed a bus reset upon request."

Also, after restart, Cluster Service didnt start. I had to manually start it.

Is this a new cluster?
Are the quorum and data drives physical and seperate?


This cluster is not new. It has been configured for 5 months or so. I would say once a month it does this crash.
Quorum and data drives are located on SAN.
Ensure the cluster service account has full access ntfs permissions to the cluster disks and the shared folders.


Cluster Service has full access ntfs permissions. It is also a member of local admins

But are the quorum and data disks separate physical disks?


It is on SAN which has one HUGE RAID of drives for Storage.
It's two different Logical drives, but physically everything is on RAID.
I have found a solution for this problem from Microsoft 3rd tier support if anybody wants to know it.
We had some users (2-3) who were storing PST files on their home drives which reside on File Server Cluster. If you have these PST files open in Outlook, it uses a lot of I/O and can make Cluster Resource fail like that.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial