A few days ago I wrote a blog about a cluster related issue where the configuration was not same on both the nodes, which was causing issues. SQL SERVER – Unable to bring resource online. Error – Data source name not found and no default driver specified. Let us learn how to fix error related to Unable to bring resource online.
After reading above article, one of my clients contacted me and said that he is seeing the same behavior but there is no issue with drivers. What else can be done? I have asked for Cluster log again and found below.
00000d64.00001098::2016/10/18-09:07:13.839 ERR [RES] SQL Server : [sqsrvres] Worker Thread (11FE840): Failed to retrieve the ftdata root registry value (hr = 2147942402, last error = 0). Full-text upgrade will be skipped.
00000d64.00001098::2016/10/18-09:07:13.839 WARN [RES] SQL Server : [sqsrvres] Worker Thread (11FE840): ReAclDirectory : Failed to apply security to H:\MSSQL12.MSSQLSERVER\MSSQL\Data (1008).
00000d64.00001098::2016/10/18-09:07:13.995 WARN [RES] SQL Server : [sqsrvres] Worker Thread (11FE840): DoREPLSharedDataUpgrade : Failed to create working directory.
00000d64.00001384::2016/10/18-09:07:13.995 ERR [RES] SQL Server : [sqsrvres] SQL Cluster shared data upgrade failed with error 0 (worker retval = 3). Please contact customer support
00000d64.00001384::2016/10/18-09:07:13.995 ERR [RES] SQL Server : [sqsrvres] Failed to prepare environment for online. See previous message for detail. Please contact customer support
It looks like there is some problem with the cluster shared data upgrade. My client informed that this happened after a service pack was installed. So we searched in the registry to see if there were any incorrect locations being pointed and found that Under [HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\Replication] we noticed that WorkingDirectory pointed to the invalid drive.
SOLUTION / WORKAROUND
We went ahead and corrected incorrect path in WorkingDirectory and then tried to bring the SQL Server resource online on node and it came online without any issues.
I was able to use Process Monitor to find the key which was needed. Have you ever used this tool?
Reference: Pinal Dave (https://blog.sqlauthority.com)