August 25, 2018 at 5:58 am
SQL Server 2014 SP1 Standard Edition
The following message is in the SQL Error Log on start up:
"Error: 30064, Severity: 17, State: 1.
SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of documents may fail until this issue is resolved. You will need to repair the SQL Server installation."
The references I have found for this error refer to a possible misconfiguration with the registry key at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<instance id>\Setup\FullTextDefaultPath
There is no FullTextDefaultPath entry in any SQL 2014 or SQL 2012 installation. However it is in SQL 2008 R2.
Security on the FTData folder looks OK.
Any suggestions where to go from here?
August 28, 2018 at 6:25 pm
claudio.l.gatto - Saturday, August 25, 2018 5:58 AMSQL Server 2014 SP1 Standard Edition
The following message is in the SQL Error Log on start up:"Error: 30064, Severity: 17, State: 1.
SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of documents may fail until this issue is resolved. You will need to repair the SQL Server installation."The references I have found for this error refer to a possible misconfiguration with the registry key at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<instance id>\Setup\FullTextDefaultPath
There is no FullTextDefaultPath entry in any SQL 2014 or SQL 2012 installation. However it is in SQL 2008 R2.
Security on the FTData folder looks OK.
Any suggestions where to go from here?
Did you move the FTData folder?
Sue
August 29, 2018 at 3:12 am
Sue_H - Tuesday, August 28, 2018 6:25 PMclaudio.l.gatto - Saturday, August 25, 2018 5:58 AMSQL Server 2014 SP1 Standard Edition
The following message is in the SQL Error Log on start up:"Error: 30064, Severity: 17, State: 1.
SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of documents may fail until this issue is resolved. You will need to repair the SQL Server installation."The references I have found for this error refer to a possible misconfiguration with the registry key at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<instance id>\Setup\FullTextDefaultPath
There is no FullTextDefaultPath entry in any SQL 2014 or SQL 2012 installation. However it is in SQL 2008 R2.
Security on the FTData folder looks OK.
Any suggestions where to go from here?
Did you move the FTData folder?
Sue
FTData was not moved.
August 29, 2018 at 5:57 am
So what does that Registry Key have as value in that FullTextDefaultPath?
Most likely the path does not point towards your SQL2014 Installation but your 2008R2 which was upgraded to 2014.
If you check C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log you should be able to get further Details what went wrong during the Upgrade.
October 31, 2018 at 1:07 am
To resolve the problem, check FTData folder path set in the registry – is the path valid, does the SQL Server Service has enough permissions on that folder, etc. The path to the registry key is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<instance id>\Setup\FullTextDefaultPath
In my case it was an invalid path in that folder. Unfortunately I was not aware of how this value got there after all the other paths were valid.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply