I recently inherited a Microsoft SharePoint Services 3.0 web application, in the form of a SQL Server backup file, that I needed to setup and run on our server. I was able to do this with the help of this article.
After I had the database up and running on my MS SQL Server 2005 system, I wasn't able to do a backup of the database without receiving the following error message:
"System.Data.SqlClient.SqlError: The backup of full-text catalog 'The only way I could do the backup was if I did a FILEGROUP and de-selected the file listed in single quotes.
Long story short, I believe this problem was caused by myself. I didn't like the database name that the previous DBA had used, so when I did a restore I used a different database name. In my test environment, if I used the same name, I didn't receive this error.
Additionally, the database was looking for a full-text file that wasn't on my system, not sure if that was caused by the way I did the restore (see previous paragraph) or it should have been sent along with the backup. In either case, the fix was easy.
- Open the SQL Server Management Studio
-
Right-click the
database, select Properties - Click on the Files page
- Verify that the "Use full-text indexing" option is set
-
Expand the
database - Expand the Storage node
- Expand the Full Text Catalogs
- Right-click on the full text file, select to delete it
- Right-click on the Full Text Catalogs node, select New Full-Text Catalog
- Provide a name for the full-text catalog file
- Provide a location for the full-text catalog file to be stored
- Click OK
- Right-click on the new full-text catalog file, select Rebuild All
No comments:
Post a Comment