A few days ago, I wrote a blog post about a cluster-related issue where the configuration was not the same on both nodes, causing issues with bringing the resource online. However, after reading the article, one of my clients reached out to me and mentioned that they were experiencing a similar problem, but it wasn’t related to drivers. So, what else could be causing this issue?

Upon further investigation and analysis of the cluster log, I found the following entries:

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 appears that there is a problem with the cluster shared data upgrade. Upon further discussion with the client, they mentioned that this issue occurred after installing a service pack. To investigate further, we searched the registry and found that under [HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\Replication], the WorkingDirectory value was pointing to an invalid drive.

The solution to this issue was to correct the incorrect path in the WorkingDirectory registry key. Once we made this correction, we were able to bring the SQL Server resource online on the node without any issues.

During the troubleshooting process, I utilized a tool called Process Monitor to identify the specific registry key that needed to be modified. This tool can be helpful in diagnosing various issues related to registry access and monitoring system activity.

Have you ever used Process Monitor or encountered a similar issue with cluster shared data upgrade? Let me know in the comments below!