Server 2008 Cluster Random failover occuring on Fileserver Resource

We have a 2 node active/passive 2008 Sql Cluster that also has a fileshare on it that randomly fails over. We get events
Events from Cluster Admin
Event ID 1230
cluster resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)' (resource type '', DLL 'clusres.dll') either crashed or deadlocked. The Resource Hosting Subsystem (RHS) process will now attempt to terminate, and the resource will be marked to run in a separate monitor.
Event2
EventID 1146
the cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due to a problem in a resource DLL. Please determine which resource DLL is causing the issue and report the problem to the resource vendor.
Event 3
EventID 1069
Cluster resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)' in clustered service or application 'SQL Server (SQLPRODA)' failed.
Event 4
Event ID 1205
The Cluster service failed to bring clustered service or application 'SQL Server (SQLPRODA)' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
We have updated the NIC drivers on each node, the Drivers and Bios have been updated on the HBA's. We have updated the srv.sys and the srv2.sys files thinking it might be an SMB issue. TCP offloading is disabled on the the Nics. We are running SP2 on both nodes and all the windows updates are current. In the cluster logs we are seeing what is listed below.
HYSQL02
========
00000cc8.00001364::2010/02/17-18:23:32.352 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:24:32.353 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:25:32.356 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:26:32.414 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_ImportFiles), status 2114. Tolerating...
00000cc8.00001364::2010/02/17-18:29:32.369 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:32:32.431 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
00000cc8.00001364::2010/02/17-18:35:32.387 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:37:32.392 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:42:32.408 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:43:32.410 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:44:32.425 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:48:32.798 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:51:32.949 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:54:33.045 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-18:58:33.158 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
00000cc8.00001364::2010/02/17-19:01:33.192 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
00000cc8.00001364::2010/02/17-19:05:33.166 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-19:10:33.182 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-19:11:33.184 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
00000cc8.00001364::2010/02/17-19:13:33.190 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-19:22:33.218 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-19:26:33.229 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-19:27:33.232 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
00000cc8.00001364::2010/02/17-19:28:33.236 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 64. Tolerating...
00000cc8.00001364::2010/02/17-19:29:33.238 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_ImportFiles), status 64. Tolerating...
00000cc8.00001364::2010/02/17-19:30:33.241 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_ReportImages), status 64. Tolerating...
00000cc8.00000cd4::2010/02/17-19:30:34.000 ERR [RHS] RhsCall::DeadlockMonitor: Call ISALIVE timed out for resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)'.
00000cc8.00000cd4::2010/02/17-19:30:34.000 ERR [RHS] Resource FileServer-(MSCS3)(Cluster Disk 4- Database) handling deadlock. Cleaning current operation and terminaiting RHS process.
000009ec.0000174c::2010/02/17-19:30:34.000 INFO [RCM] HandleMonitorReply: FAILURENOTIFICATION for 'FileServer-(MSCS3)(Cluster Disk 4- Database)', gen(0) result 4.
000009ec.0000174c::2010/02/17-19:30:34.000 INFO [RCM] rcm::RcmResource::HandleMonitorReply: Resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)' consecutive failure count 1.
000009ec.0000174c::2010/02/17-19:30:34.002 ERR [RCM] rcm::RcmMonitor::RecoverProcess: Recovering monitor process 3272 / 0xcc8
000009ec.0000174c::2010/02/17-19:30:34.004 INFO [RCM] Created monitor process 2248 / 0x8c8
000008c8.000010c8::2010/02/17-19:30:34.019 INFO [RHS] Initializing.
000009ec.0000174c::2010/02/17-19:30:34.030 INFO [RCM] rcm::RcmResource::ReattachToMonitorProcess: (FileServer-(MSCS3)(Cluster Disk 4- Database), Online)
000009ec.0000174c::2010/02/17-19:30:34.030 INFO [RCM] TransitionToState(FileServer-(MSCS3)(Cluster Disk 4- Database)) Initializing-->OpenCallIssued.
000009ec.0000174c::2010/02/17-19:30:34.030 INFO [RCM] rcm::RcmGroup::ProcessStateChange: (SQL Server (SQLPRODA), Online --> PartialOnline)
000009ec.0000174c::2010/02/17-19:30:34.055 INFO [RCM] TransitionToState(FileServer-(MSCS3)(Cluster Disk 4- Database)) Online-->ProcessingFailure.
000009ec.0000174c::2010/02/17-19:30:34.055 INFO [RCM] rcm::RcmGroup::ProcessStateChange: (SQL Server (SQLPRODA), PartialOnline --> Failed)
000009ec.0000174c::2010/02/17-19:30:34.055 ERR [RCM] rcm::RcmResource::HandleFailure: (FileServer-(MSCS3)(Cluster Disk 4- Database))
000009ec.0000174c::2010/02/17-19:30:34.055 INFO [RCM] resource FileServer-(MSCS3)(Cluster Disk 4- Database): failure count: 1, restartAction: 2.
000009ec.0000174c::2010/02/17-19:30:34.055 INFO [RCM] Will restart resource in 500 milliseconds.
000009ec.0000174c::2010/02/17-19:30:34.055 INFO [RCM] TransitionToState(FileServer-(MSCS3)(Cluster Disk 4- Database)) ProcessingFailure-->[Terminating to DelayRestartingResource].
000009ec.0000174c::2010/02/17-19:30:34.055 INFO [RCM] rcm::RcmGroup::ProcessStateChange: (SQL Server (SQLPRODA), Failed --> Pending)
000008c8.00001784::2010/02/17-19:30:34.112 INFO [RES] File Server : FileServerDoTerminate: Terminate called... !!!
000009ec.0000126c::2010/02/17-19:30:34.119 INFO [RCM] TransitionToState(FileServer-(MSCS3)(Cluster Disk 4- Database)) [Terminating to DelayRestartingResource]-->DelayRestartingResource.
000009ec.0000174c::2010/02/17-19:30:34.619 INFO [RCM] Delay-restarting FileServer-(MSCS3)(Cluster Disk 4- Database) and any waiting dependents.
000009ec.0000174c::2010/02/17-19:30:34.619 INFO [RCM] TransitionToState(FileServer-(MSCS3)(Cluster Disk 4- Database)) DelayRestartingResource-->OnlineCallIssued.
000009ec.0000126c::2010/02/17-19:30:34.620 INFO [RCM] HandleMonitorReply: ONLINERESOURCE for 'FileServer-(MSCS3)(Cluster Disk 4- Database)', gen(1) result 997.
000009ec.0000126c::2010/02/17-19:30:34.620 INFO [RCM] TransitionToState(FileServer-(MSCS3)(Cluster Disk 4- Database)) OnlineCallIssued-->OnlinePending.
000008c8.000016cc::2010/02/17-19:30:34.657 INFO [RES] File Server : Shares 'are being scoped to virtual name MSCS3
HYSQL01
=========
000015ac.00001200::2010/02/17-21:42:54.976 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-21:47:51.082 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-21:51:51.094 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-21:56:51.056 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000015ac.00001200::2010/02/17-22:06:51.139 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-22:09:51.148 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000009e0.00001b08::2010/02/17-22:17:51.431 INFO [NM] Received request from client address 10.1.0.220.
000015ac.00001200::2010/02/17-22:21:51.184 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-22:25:31.804 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-22:30:34.959 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000015ac.00001200::2010/02/17-22:31:36.518 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 2114. Tolerating...
000015ac.00001200::2010/02/17-22:34:41.036 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-22:39:48.514 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000015ac.00001200::2010/02/17-22:42:51.247 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000009e0.0000132c::2010/02/17-22:44:16.801 INFO [NM] Received request from client address 10.1.0.220.
000015ac.00001200::2010/02/17-22:47:51.209 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000015ac.00001200::2010/02/17-22:49:51.215 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
000009e0.000015f4::2010/02/17-22:51:27.511 INFO [NM] Received request from client address 10.1.0.220.
000015ac.00001200::2010/02/17-22:52:51.277 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-22:55:51.286 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-23:06:51.319 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000015ac.00001200::2010/02/17-23:12:51.284 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000015ac.00001200::2010/02/17-23:13:51.340 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 2114. Tolerating...
000015ac.00001200::2010/02/17-23:16:51.349 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
2nd Issues
000018f0.0000137c::2010/02/16-18:03:23.988 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 2114. Tolerating...
000018f0.0000137c::2010/02/16-18:07:23.947 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:11:23.959 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:13:23.965 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:14:24.021 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 2114. Tolerating...
000018f0.0000137c::2010/02/16-18:20:23.986 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:23:23.996 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:26:24.005 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:27:24.007 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:28:24.063 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 2114. Tolerating...
000018f0.0000137c::2010/02/16-18:37:24.038 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:38:24.094 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 2114. Tolerating...
000018f0.0000137c::2010/02/16-18:41:24.102 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000018f0.0000137c::2010/02/16-18:44:24.059 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:50:24.129 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000018f0.0000137c::2010/02/16-18:54:24.089 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:55:24.091 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:56:24.095 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-18:57:24.151 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_ImportFiles), status 2114. Tolerating...
000009e0.00000d2c::2010/02/16-19:13:04.903 INFO [NM] Received request from client address 10.1.0.220.
000018f0.0000137c::2010/02/16-19:18:24.213 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
000018f0.0000137c::2010/02/16-19:22:24.172 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
000018f0.0000137c::2010/02/16-19:24:24.178 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
000018f0.000012dc::2010/02/16-19:25:25.000 ERR [RHS] RhsCall::DeadlockMonitor: Call ISALIVE timed out for resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)'.
000018f0.000012dc::2010/02/16-19:25:25.000 ERR [RHS] Resource FileServer-(MSCS3)(Cluster Disk 4- Database) handling deadlock. Cleaning current operation and terminaiting RHS process.
000009e0.00000f48::2010/02/16-19:25:25.000 INFO [RCM] HandleMonitorReply: FAILURENOTIFICATION for 'FileServer-(MSCS3)(Cluster Disk 4- Database)', gen(1) result 4.
000009e0.00000f48::2010/02/16-19:25:25.000 INFO [RCM] rcm::RcmResource::HandleMonitorReply: Resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)' consecutive failure count 1.
000009e0.00000f48::2010/02/16-19:25:25.002 ERR [RCM] rcm::RcmMonitor::RecoverProcess: Recovering monitor process 6384 / 0x18f0
000009e0.00000f48::2010/02/16-19:25:25.003 INFO [RCM] Created monitor process 6020 / 0x1784
00001784.00001b1c::2010/02/16-19:25:25.012 INFO [RHS] Initializing.
000009e0.00000f48::2010/02/16-19:25:25.023 INFO [RCM] rcm::RcmResource::ReattachToMonitorProcess: (FileServer-(MSCS3)(Cluster Disk 4- Database), Online)
000009e0.00000f48::2010/02/16-19:25:25.023 INFO [RCM] TransitionToState(FileServer-(MSCS3)(Cluster Disk 4- Database)) Initializing-->OpenCallIssued.
000009e0.00000f48::2010/02/16-19:25:25.023 INFO [RCM] rcm::RcmGroup::ProcessStateChange: (SQL Server (SQLPRODA), Online --> PartialOnline)
3)
00000d80.00000388::2010/02/16-12:15:13.281 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
00000d80.00000388::2010/02/16-12:19:19.253 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000d80.00000388::2010/02/16-12:24:22.132 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000d80.00000388::2010/02/16-12:25:22.187 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 2114. Tolerating...
00000d80.00000388::2010/02/16-12:29:22.146 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000d80.00000388::2010/02/16-12:42:22.185 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000d80.00000388::2010/02/16-12:50:22.209 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000d80.00000388::2010/02/16-12:51:22.212 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
00000d80.00000388::2010/02/16-12:53:22.218 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 64. Tolerating...
00000d80.00000388::2010/02/16-12:54:22.274 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_ImportFiles), status 2114. Tolerating...
00000d80.00000388::2010/02/16-13:01:31.308 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
00000d80.00000388::2010/02/16-13:10:22.322 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 2114. Tolerating...
00000d80.00000388::2010/02/16-13:13:22.279 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000d80.00000388::2010/02/16-13:17:22.291 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000d80.00000388::2010/02/16-13:20:22.300 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00000d80.00000388::2010/02/16-13:22:22.305 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
00000d80.00000388::2010/02/16-13:24:22.311 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 64. Tolerating...
00000d80.00000d8c::2010/02/16-13:24:23.000 ERR [RHS] RhsCall::DeadlockMonitor: Call ISALIVE timed out for resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)'.
00000d80.00000d8c::2010/02/16-13:24:23.000 ERR [RHS] Resource FileServer-(MSCS3)(Cluster Disk 4- Database) handling deadlock. Cleaning current operation and terminaiting RHS process.
000009e0.000015dc::2010/02/16-13:24:23.000 INFO [RCM] HandleMonitorReply: FAILURENOTIFICATION for 'FileServer-(MSCS3)(Cluster Disk 4- Database)', gen(0) result 4.
000009e0.000015dc::2010/02/16-13:24:23.000 INFO [RCM] rcm::RcmResource::HandleMonitorReply: Resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)' consecutive failure count 1.
000009e0.000015dc::2010/02/16-13:24:23.002 ERR [RCM] rcm::RcmMonitor::RecoverProcess: Recovering monitor process 3456 / 0xd80
4)
00001770.00001594::2010/02/09-16:01:06.362 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_ReportImages), status 2114. Tolerating...
00000aa4.0000183c::2010/02/09-16:01:15.630 INFO [RES] Physical Disk: HardDiskpGetDiskInfo: Disk is of type MBR, signature 0x3ba33338
00000aa4.0000183c::2010/02/09-16:01:19.036 INFO [RES] Physical Disk: HardDiskpGetDiskInfo: Disk is of type MBR, signature 0x3ba3333f
00000aa4.0000183c::2010/02/09-16:01:19.040 INFO [RES] Physical Disk: HardDiskpGetDiskInfo: Disk is of type MBR, signature 0x3ba3333a
00000aa4.0000183c::2010/02/09-16:01:19.044 INFO [RES] Physical Disk: HardDiskpGetDiskInfo: Disk is of type MBR, signature 0x3ba33339
00001770.00001910::2010/02/09-16:05:06.311 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, HelpSystem), status 64. Tolerating...
00001770.00001910::2010/02/09-16:06:06.314 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, ImportFiles), status 64. Tolerating...
00001770.00001910::2010/02/09-16:07:06.317 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_HelpSystem), status 64. Tolerating...
00001770.00001910::2010/02/09-16:08:06.320 WARN [RES] File Server : Failed in NetShareGetInfo(MSCS3, PreProd_ImportFiles), status 64. Tolerating...
00001770.00000d14::2010/02/09-16:08:07.000 ERR [RHS] RhsCall::DeadlockMonitor: Call ISALIVE timed out for resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)'.
00001770.00000d14::2010/02/09-16:08:07.000 ERR [RHS] Resource FileServer-(MSCS3)(Cluster Disk 4- Database) handling deadlock. Cleaning current operation and terminaiting RHS process.
000009f0.00001324::2010/02/09-16:08:07.000 INFO [RCM] HandleMonitorReply: FAILURENOTIFICATION for 'FileServer-(MSCS3)(Cluster Disk 4- Database)', gen(4) result 4.
000009f0.00001324::2010/02/09-16:08:07.000 INFO [RCM] rcm::RcmResource::HandleMonitorReply: Resource 'FileServer-(MSCS3)(Cluster Disk 4- Database)' consecutive failure count 1.
000009f0.00001324::2010/02/09-16:08:07.002 ERR [RCM] rcm::RcmMonitor::RecoverProcess: Recovering monitor process 6000 / 0x1770
000009f0.00001324::2010/02/09-16:08:07.003 INFO [RCM] Created monitor process 4748 / 0x128c
Analysis
We are getting Error 64 and 2114 and the File share is failing with a Deadlock Error
Status 64 = the specified network name is no longer available.
Status 2114 = The Server service is not started.
We setup Netmon and ran traces yesterday when the issue happened and they did not show anything. The Server service does not seem to get any errors.
We have also engaged EMC into the issue and MS has escalated the case but wanted to see if anyone else has experienced this issue or found any resolution. We have run out of options.

Here you go!
KB950811
why not this one:
http://support.microsoft.com/kb/2231728
/* Server Support Specialist */

Similar Messages

Failover of ASCS takes very long on a Windows Server 2008 Cluster

Hello everybody,
I have configured a ABAP SCS (NetWeaver 7.0) running on a Windows Server 2008 Cluster. The database runs on SQL Server 2008 which is also configured for use in the MSCS. The ASCS and the database run fine in the Cluster. So far so good.
When I want to move the SAP Group which contains the ASCS from on node the other node, then the failover will take very long (approximately 2-3 minutes). The Service of the group will go offline in a few seconds, but the Instance needs about 1 minute to go offline and on the other node it needs more then one minute to become online.
The failover of the databaseinstance will take only about 10 seconds.
Have you got any ideas why the failover of the SAP Group will take so long?
Thanks for your help in advance!
Kind Regards,
Wolfgang

One minute would be somewhat long if you are running a faster server and just the ABAP environment. But I've seen ABAP/JAVA systems take up to 10 minutes to restart on a win 2005 clustered system.
Have you looked through the developer traces?
J. Haynes

Reporting Services will not automatically use a different replica for the report server databases when a failover occurs. How to overcome this issue

Reporting Services offers limited support for using AlwaysOn Availability Groups with report server databases. The report server databases can be configured in AG to be part of a replica; however Reporting Services will not automatically use a different
replica for the report server databases when a failover occurs. How to overcome this issue? is there any workaround for that..
Rahul

Hi.
With the AlwaysOn listener you should have a single DNS name to connect to regardless of which cluster node is active. Are you using the listener service? If not, please refer to the link below.
http://msdn.microsoft.com/en-us/library/hh213417.aspx#AGlisteners

Apply monthly Windows 2008 r2 updates within SQL Server 2008 cluster

Hello is applying Windows updates within 2 node SQL Server 2008 cluster (active-passive) as simple as download/install the windows update on the passive node, then failover, then apply on other node, and then fail back over ?...or are there other needed/recommended
steps ? Thanks in advance.

Thanks for your reply Shanky_621 much appreciated.
In your link provided http://support.microsoft.com/kb/174799 it looks like the steps order is slightly different from this link of
http://technet.microsoft.com/en-us/library/cc731291.aspx which mentions...
"...where the recommended sequence is to move all services and applications off of the node, pause the node, then apply software updates to the node."
...does it matter which is done first ('Pause' or 'move Services/Application') or can I simply go to the Passive node (say 'B' where there are no Services or Applications currently on it), 'Pause' it, apply the Windows updates, then 'Resume' it, &
reboot ?

Prepositioning files on a Server 2008 Cluster

I recently replaced a Server 2003 cluster with a server 2008 cluster. After the migration my prepostioning stopped functioning. The virtual servers are named the same and all the credentials, etc are the same. If I go into one of the preposition definitions and click browse I get a could not access cifs://<servername>. If I point to any of the other servers I am able to browse. Doesn't matter if they are server 2003 or 2008. The clustered servers are domain controllers. The version is 4.1.1c

Could you elaborate on this,as I am having the same issues? Our prepositioning works on the 2003 boxes but not the new 2008 ones.
Where abouts did you turn off the server signing .My serevr team say they have done this,but i would like to check myself.Is there anything else you changed? I can browse the files and select them fine,its just that once the schedule has started,no files get copied.
thanks,
Nick

Server 2008 Hyper-V Failover Cluster Error on Domain Controller Reboot

I am pretty new to Hyper-V virtual but I have 2 Hyper-V Clusters, each with 2 Nodes and a SAN, 1 Physical Domain Controller for failover cluster management and 1 virtual domain controller as backup. All is running well, no issues. I installed
windows updates on the physical DC and upon reboot, got an error 5120 on cluster 2 that says "Cluster Shared Volume 'Volume1' ('Cluster Disk 1') is no longer available on this node because of 'STATUS_CONNECTION_DISCONNECTED(c000020c)'. All I/O will
temporarily be queued until a path to the volume is reestablished. It pointed to the 2nd node in that cluster as being the issue but when I look at it, it is online and all healthy so I don't understand why the error was triggered and if the DC would
go down for a failure, would that node not be able to access the CSV permanently.
Appreciate any help anyone can provide.

Hi mtnbikediver,
In theory, if you has the correct configuration of cluster the DC restart will not cause the CSV down, does your shared storage installed on your DC? Did you run
the cluster validation before you install the cluster? We strongly recommend you run the cluster validation before you build the cluster, same time please install the recommend update of 2008 cluster first.
Recommended hotfixes for Windows Server 2008-based server clusters
http://support.microsoft.com/kb/957311
I found a similar scenario issue the DC restart will effect the cluster network name resource offline, but it is for 2008R2.
Cluster network name resource cannot be brought online when one of the domain controllers is partly down in Windows Server 2008 R2
http://support2.microsoft.com/?id=2860142
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

SQL Server 2008 R2 { An Error occured when attaching database(s) }

Hello Guys!
I just installed SQL Server 2008 R2 a couple of days ago, on the first day use i can attach database(.mdf) with out any problem.
on the day 2, i keep getting this error:
http://img515.imageshack.us/img515/14/1212i.png
TITLE: Microsoft SQL Server Management Studio
An error occurred when attaching the database(s). Click the hyperlink in the Message column for details.
BUTTONS:
OK
after clicking the Hyperlink this window open:
http://img34.imageshack.us/img34/8766/hyperg.png
TITLE: Microsoft SQL Server Management Studio
Attach database failed for Server 'STARGAZER-PC\SQLSTARMAX'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Unable to open the physical file "E:\New folder\DataBase.MDF". Operating system error 5: "5(Access is denied.)". (Microsoft SQL Server, Error: 5120)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=5120&LinkId=20476
BUTTONS:
OK
in that day i reinstall SQL Server 2008 R2, because I'm so confused. after that i try to attach i still got the same error, what i did is i share the folder where the database is.
i open SSMS and try to attach and i attached without any error...
i think this is the 4rth day, untill now everytime i want to attach a database i got this error, and even i try to share the folder where the database is i still got that error.
any advice guys?
Thanks a lot
jhules
if you want to be happy, find something you love to do and do it for free, then find someone to to you for it.

The Error clearly shows that MDF files and LDF files are not matching or LDF file is corrupted.
You can follow either of the one option below
1. Restore a recent backup rather attaching the MDF file
2. Attach single MDF file without LOG File( Warning: All the log transactions will be gone and new log file will be created)
EXEC sp_attach_single_file_db @dbname = 'AdventureWorks2008R2',
@physname = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\AdventureWorks2008R2_Data.mdf';
Thanks, Aditya Badramraju, _______________________________________________________ Please mark answered if your question is completely answered; vote it as helpful to help others find a solution quicker. This posting is provided AS IS with no warranties
and confers no rights. _______________________________________________________

Windows Server 2008 SP2 randomly reboots due to lsass.exe failed with status code 255

Hello,
Any help on this issue would be greatly appreciated. I have an older Windows Server 2008 SP2 (I don't believe it is R2) (running SQL Server 2008 and SSRS 2008 on the machine) that is crashing randomly
during business hours. Looking into the event logs, I have found the following:
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066d9669a3e1c.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.
The process wininit.exe has initiated the restart of computer RIDEDB02 on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
I found a Hot Fix for a similar issue (https://support.microsoft.com/en-us/kb/2732595?wa=wsignin1.0), but it appeared to only be applicable to Windows Server 2008 R2 and Windows 7.
A few hours later, the crash happened again, with a slightly different error:
The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819. The system will now shut down and restart.
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066fa9d74c5d7.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted.
The security package Kerberos generated an exception. The exception information is the data
I have been unable to find a reason for these exceptions and the server rebooting. Any thoughts or ideas on how I can correct this error so it doesn't reboot our server again? .
Thank you,
Ben

Hello,
Any help on this issue would be greatly appreciated. I have an older Windows Server 2008 SP2 (I don't believe it is R2) (running SQL Server 2008 and SSRS 2008 on the machine) that is crashing randomly
during business hours. Looking into the event logs, I have found the following:
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066d9669a3e1c.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.
The process wininit.exe has initiated the restart of computer RIDEDB02 on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
I found a Hot Fix for a similar issue (https://support.microsoft.com/en-us/kb/2732595?wa=wsignin1.0), but it appeared to only be applicable to Windows Server 2008 R2 and Windows 7.
A few hours later, the crash happened again, with a slightly different error:
The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819. The system will now shut down and restart.
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066fa9d74c5d7.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted.
The security package Kerberos generated an exception. The exception information is the data
I have been unable to find a reason for these exceptions and the server rebooting. Any thoughts or ideas on how I can correct this error so it doesn't reboot our server again? .
Thank you,
Ben

Oracle 10g R2 whitout RAC in a cluster hw (Windows Server 2008 cluster)

Hi,
Is this possible?
I ask it 'cause my customer wants to improve this solution.
I know that Oracle 10gR2 vs Windows Server 2008 is not supported and Oracle Standalone vs Hardware Cluster, neither too, but it's possible or will be a source of big problems?
Thanks in advance.
JRC.

Hi lain;
Please check Re: oracle10g on linux cluster
In my issue we were working on linux cluster. Our aim is
we have 3 server and they are linux cluster OS level. Let us call those server A,B and C... We want to make oracle10g works on server A and when server A is gone oracle10g on B server take place of A, if server B gone too, oracle10g on C server take place of B.... In each server we had different numver of database. I mean on machine a we have 3 database, on server B we have 4 database and on server C we have 7
What i do for this:
1. I install 10g database software only (not created database)
2. using netca and create listener for each database
3. using dbca and create database for each server.While on dbca wizard i gave SAN path for dbf
4. Linux admin arrange all other stuff(I mean when db1 on server A crash server B take responsibility of Server A and db1 keep working)
I hope it helps you
Regard
Helios

Server 2008 Cluster - OSX 10.5.5

Hi
I am creating a Windows Server 2008 HA filesystem cluster which has been setup and is working perfectly. I have a OSX 10.5.5 build laptop running and trying to access the shares on the cluster. It can successfully ping/see/connect to the cluster and authenticate correctly, yet after all of that no shares are published
I have the NFS protocol enabled and have tried sharing using both SMB and NFS, and the mac client is not able to connect. Ive tried connecting over cifs:// smb:// nfs:// through DNS and through IP, but all return the same problem
Ive looked around and it seems this is not an uncommon situation but does anyone have any tips/clues/etc to solve this?? Apple...anyone??
Its not mission critical for my mac clients to use these filesystem but it would (and should work) be ideal for 100% interoperability and get my osx clients viewing the same files as the windows people
Any thoughts?

To anyone who is having this issue:
I found a resolution in a Microsoft forum, and the resolution comes from Apple
Connect using the following method:
smb://netbiosname:139/sharename
Hopefully this issue will be permanently fixed in future Apple updates or MS KB articles
Message was edited by: thelostwayfarer

Hi I am trying to install SQL Server 2008 R2 Express edition, I am getting error like "unhandled exception has occurred in your application"

In that system Microsoft Framework 4.o and 3.5.1 is installed even then i am getting the error then i uninstalled and again installed framework same error occurring.

Hi Chandra,
As other post, please help to post the summary and detail logs for analysis.
Based on my knowledge, the error “unhandled exception has occurred in your application” always happens along with the following message when installing SQL Server 2008 R2:
“An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
or one of its dependencies. The system cannot find the file specified. “
If you encounter such issue, please perform the following steps to solve it.
1.Go to your app data directory by going to start > run > %appdata% .
2.This will by default take you to the "roaming" folder, go up one directory and move into the "Local" folder.
3. Go to the "Microsoft_Corporation" folder.
4. Delete the relevant folders from the "Microsoft_Corporation" folder.
For more details, please review the following blog.
SQL Server 2008 R2 will not install - Unhandled Exception has occurred in your application
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

SCOM 2012 SP1 SQL Server 2008 R2 Clustering Monitoring?

We have a new print management system that was setup using SQL server 2008 R2 clustering. Right now we have SQL MP (monitoring)(discover) 6.3.173.1. They had a failover occur a week ago and SCOM didnt throw any alerts. As a temporary
fix, I found some correlated events and setup a monitor for those events on the servers. However, the system owner wants to know if there is a MP that will monitor for a SQL cluster failover event. I have looked and looked and cant seem to find
anything that gives a whole lot of detail on this.
Thanks
EFD
Warm Fuzzies!

Yes, you can monitor SQL Cluster 2008 using SCOM 2012 SP1. but you need to install SQL MP and Windows Cluster MP and Enable proxy Agent on physical nodes.
You can refer below link {it's same for SCOM 2012}
http://blogs.technet.com/b/birojitn/archive/2010/04/14/sql-server-2008-cluster-monitoring.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

MSDTC set up in SQL Server 2008 failover cluster

Hi Guys,
I am in the process of setting up failover cluster using SQL Server 2008 (64Bit) Enterprise on Windows Server 2008 R2 (64Bit) I have completed almost all the works but I got few questions regarding MSDTC configuration whether the MSDTC disk should
be assigned from SAN or it should be local to the disk , Separate disk for each nodes in the cluter or 1 disk to be used across all the servers for MSDTC in windows fail over cluster.
With regards, Gopinath.

Hi Gopinath,
Please review the following similar blogs to get more details about configuring MDTC and pros & cons of different options.
How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008
http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
How to configure DTC for SQL Server in a Windows 2008 cluster
http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

MS DTC not coming online on SQL Server 2008 R2 failover cluster

Dear Experts,
On a SQL Server 2008 R2 failover cluster, MS DTC cluster service is not coming online. It fails with below error message.
"The DTC cluster resource's log file path was originally configured at: E:. Attempting to change that to: M:. This indicates a change in the path of the DTC cluster resource's dependent disk resource. This is not supported. The error code
returned: 0x8000FFFF".
From the Component Services, we can see under the clustered DTCs, in the properties of the log file that it is configured for E drive. The 'Transaction list' and 'Transaction Statistics' are empty. When I try to change the log file path to
point to M drive I get this warning message.
"An MSDTC log file already exists in the selected directory. Resetting an existing MS DTC log file may cause your databases and other transactional resource managers to become inconistent. Please review the MSDTC Administrator's manual before
proceeding. Do you wish to reset the existing MS DTC log"
Could you please advise if this is safe to proceed with this warning as the 'Transaction list' and 'Transaction Statistics' are empty or would it cause any other issue.
Thanks,
MM

Tauseef
Did you tried using wmi....win32_share
$path = "location where to create the folder"
$share = $Shares=[WMICLASS]'WIN32_Share' # class in wmi for share
$Sharename = 'Sharename'
New-Item -type directory -Path $Path
$Shares.Create($Path,$Sharename,0,255,$Sharename)
$Acl = Get-Acl $Path # cmdlet for getting access control list
$Access = New-Object system.security.accesscontrol.filesystemaccessrule("Username","FullControl","ContainerInherit, ObjectInherit", "None", "Allow")
$Acl.AddAccessRule($Access)
Set-Acl $Path $Acl
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

Server 2008 R2 Failover cluster network configuration

Hi
We have a customer with a Server 2008 R2 Hyper-V failover cluster. They have 2 cluster networks, "Cluster Network 1" and "Cluster Network 2".
"Cluster Network 1": NIC team on 172.16.1.0/24 for private cluster network communication
"Cluster Network 2": NIC team on 192.168.1.0/24 for production network communication
I can see that "Cluster Network 1" is configured to "Allow cluster network communication on this network" and "Allow clients to connect through this network".
If "Cluster Network 1" is ONLY for communication between the to cluster nodes then I assume the selection in "Allow clients to connect through this network" should be removed?
/Lasse

It will cause a lost network connection for any client that is accessing through that network. Those clients would need to reconnect.
Did you configure both IPs on the cluster resource name that clients are accessing? If you only configured the one you want, there should be no issue. If you configured both, then it is possible some clients might be connected via the private
network.
Another thing you should, and if you have already done this you will most likely not have issues at all, is that you should disable DNS registration on any network you do not want client access coming through. If the clients can only find the resource
through the DNS name registered, that is the way they will be coming in. In my clusters, which often have 7 or more NICs, there is only one with a published DNS record.
. : | : . : | : . tim

Server 2008 Cluster Random failover occuring on Fileserver Resource

Similar Messages

Maybe you are looking for