May 10, 2017 at 1:05 am
Hi Experts,
I am facing this error in SQL Server 2008 R2 clustering environment, please read below mentioned log and let me know for further course of action.
Version=Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64) Aug 19 2014 12:21:34 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
APPLICATION LOGS from Event Viewer
===============================
ERRORS
----------------------
1- The client was unable to reuse a session with SPID 72, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
2- The client was unable to reuse a session with SPID 115, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
3- The client was unable to reuse a session with SPID 70, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
INFORMATION
----------------------
1- Service Broker manager has shut down.
2- SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
3- SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
ERRORS
--------------
SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: XXXXXXX]
SYSTEM LOGS FROM EVENT VIEWER
-=============================
Cluster file server resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' cannot be brought online. The resource failed to create file share 'Input' associated with network name 'ABCSQL'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.
Cluster file server resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' cannot be brought online. The resource failed to create file share 'Output' associated with network name 'ABCSQL'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.
May 10, 2017 at 8:23 am
Sandeep DBA - Wednesday, May 10, 2017 1:05 AMCluster file server resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' cannot be brought online. The resource failed to create file share 'Output' associated with network name 'ABCSQL'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.
The server did a shutdown, restart so you'd need to check the logs on why that happened - there could be something in the cluster log so you may want to generate the log to look through that. The last error is exactly what it is saying - the file share resource couldn't be brought online. So you need to check the resources and check however this file server share is setup, if the dependencies and possible owners are correct.
Sue
May 11, 2017 at 12:45 am
Sue_H - Wednesday, May 10, 2017 8:23 AMSandeep DBA - Wednesday, May 10, 2017 1:05 AMCluster file server resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' cannot be brought online. The resource failed to create file share 'Output' associated with network name 'ABCSQL'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.The server did a shutdown, restart so you'd need to check the logs on why that happened - there could be something in the cluster log so you may want to generate the log to look through that. The last error is exactly what it is saying - the file share resource couldn't be brought online. So you need to check the resources and check however this file server share is setup, if the dependencies and possible owners are correct.
Sue
HI Sue,
Thanks for the response but problem s that cluster errors are occurring frequently major problem is these below mentioned errors with failure ID 23 on that erros switch over occurred so please advise why these errors are occurred after 12 hours, clustering errors are occurring frequently means every hour or 2 hour.
1- The client was unable to reuse a session with SPID 72, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
2- The client was unable to reuse a session with SPID 115, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
3- The client was unable to reuse a session with SPID 70, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
Thanks
May 12, 2017 at 6:29 pm
Sandeep DBA - Thursday, May 11, 2017 12:45 AMSue_H - Wednesday, May 10, 2017 8:23 AMSandeep DBA - Wednesday, May 10, 2017 1:05 AMCluster file server resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' cannot be brought online. The resource failed to create file share 'Output' associated with network name 'ABCSQL'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.The server did a shutdown, restart so you'd need to check the logs on why that happened - there could be something in the cluster log so you may want to generate the log to look through that. The last error is exactly what it is saying - the file share resource couldn't be brought online. So you need to check the resources and check however this file server share is setup, if the dependencies and possible owners are correct.
Sue
HI Sue,
Thanks for the response but problem s that cluster errors are occurring frequently major problem is these below mentioned errors with failure ID 23 on that erros switch over occurred so please advise why these errors are occurred after 12 hours, clustering errors are occurring frequently means every hour or 2 hour.1- The client was unable to reuse a session with SPID 72, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
2- The client was unable to reuse a session with SPID 115, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
3- The client was unable to reuse a session with SPID 70, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
Thanks
Okay but in the first post you have a lot of shut down messages in the logs. Usually failure id 23 is that SQL Server is seen when the service is shutting down.
When you say "clustering errors are occurring frequently means every hour or 2 hour" what specific errors are you having with clustering? You said that the error client was unable to reuse a session error" is happening but that it's 12 hours after the failover. So then what are the other cluster errors you are having every one to two hours?
Do you still get an error that the file share resource couldn't be brought online?.
Did you check this resources, how it is setup, if the dependencies and possible owners are correct? Is the share accessible from this server?
Did you generate a cluster log so that you can check for errors in that log? The easiest way is from the server, open a command prompt and type: cluster log /g
It will use defaults to generate the cluster log to the %windir%\Cluster\Reports directory
Sue
May 18, 2017 at 2:43 pm
Hi Sue,
Actually i was facing these errors due to this on daily basis .
Cluster file server resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' cannot be brought online. The resource failed to create file share 'Input' associated with network name 'ABCSSQL'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.
Cluster file server resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' cannot be brought online. The resource failed to create file share 'Output' associated with network name 'ABCSSQL'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.
Cluster resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.
Cluster file server resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' cannot be brought online. The resource failed to create file share 'Input' associated with network name 'ABCSSQL'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.
Cluster file server resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' cannot be brought online. The resource failed to create file share 'Output' associated with network name 'ABCSSQL'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.
Cluster resource 'FileServer-(ABCSSQL)(Cluster Disk 1)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.
The Cluster service failed to bring clustered service or application 'SQL Server (MSSQLSERVER)' 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.
----------------------------------
these errors occurred then sql server stopped and switch over occurred due to this replication and backup was failing because policy and all things are configured on server 1 it creates big problem.
My question why these clustering errors are occurred this relevant to SQL server or Windows cluster because these server is working fine for 4 years but now this problem is occurring.
Please guide thi issue is on OS end or SQL server end what happen these problem comes one thing these errors are occurred frequently like every one or two hours but switch over occurred 3 or 4 times daily. In this fail over all resources are not moving properly.
Thanks
Sandeep
May 18, 2017 at 5:45 pm
Sandeep DBA - Thursday, May 18, 2017 2:43 PMMy question why these clustering errors are occurred this relevant to SQL server or Windows cluster because these server is working fine for 4 years but now this problem is occurring.
Please guide thi issue is on OS end or SQL server end what happen these problem comes one thing these errors are occurred frequently like every one or two hours but switch over occurred 3 or 4 times daily. In this fail over all resources are not moving properly.Thanks
Sandeep
I don't think anyone can tell you why this happens now since the root cause isn't known.
It's not a SQL Server issue, it's a Cluster issue. I would have thought you would have event 1558 in the system log - I'm pretty sure that is the text for that error. I don't know if you have a file share witness but I thought the error message was a bit different. Either way, you need to look for the event codes in the logs for the node where the problems are and look those up.
My first reply would still hold true and you need to do that. Did you check the resource? Is it available to all nodes? Did you check the permissions? Have any file system filter drivers been changed or added? Did you try to bring it online manually?
There were also suggestions in the errors that said:
Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'ABCSSQL' in this clustered service or application.
So you need to do all of those things.
Sue
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply