Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
anton
Starting Member
5 Posts |
 Posted - 2003-07-03 : 07:53:16
|
| I have the following scenario where i did a backup/restore from a dev machine to a server:The development machine had full text catalogs running from a D:\mssql directory and after restoring to the server machine i cannot get full text to work because there is no D:I'm stuck in a catch 22 situation because to delete a full text catalog from the database I need to first enable full text search, but i cannot enable it because the physical file which the catalog points to cannot be found eg:Server: Msg 7610, Level 16, State 1, Procedure sp_fulltext_database, Line 61Access is denied to 'D:\mssql\db', or the path is invalid. Full-text search was not installed properly.I have tried to import the registry (based on a KB article which seemed applicable) from the dev machine because that information contains the file path etc, but if i start and stop full-text then those registry keys are removed...Any ideas to fix this? |
|
|
anton
Starting Member
5 Posts |
Posted - 2003-07-10 : 09:44:36
|
| Yay! Learnt something new:Here is the answer-Right click on your server properties, goto the server settings tab and check the box that says 'Allow modifications to be made directly to the system catalogs' (I had to stop and start my sql for this to take effect)Now go to the affected database and open the sysfulltextcatalogs table and edit the file path that is displayed in your results to a directory that exists.Last step - go to the full text catalogs listing for the database, select the catalog, right click and rebuild it.voila! |
 |
|
|
|
|
|
Changing Full-Text physical file path