Friday, February 24, 2012

file or filegroup not online? "sysft_ftcat_documentindex"

Just upgraded from SQL 2000 to 2005 and I created a backup maintenance plan
but I am getting the following error everytime the maintenance plan runs:
Error number: -1073548784
Executing the query "BACKUP DATABASE [Clarke_MSCRM] TO DISK = N'C:\\Program
Files\\Microsoft SQL
Server\\MSSQL\\BACKUP\\Clarke_MSCRM\\Clarke_MSCRM_backup_200607270400.bak'
WITH NOFORMAT, NOINIT, NAME = N'Clarke_MSCRM_backup_20060727040005', SKIP,
REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The backup of the file or filegroup
"sysft_ftcat_documentindex" is not permitted because it is not online. BACKUP
can be performed by using the FILEGROUP or FILE clauses to restrict the
selection to include only online data.
BACKUP DATABASE is terminating abnormally.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
I'm not sure where to start looking.Try rebuilding or repopulating your full-text catalog. This is included in 2005 backup and is most
probably your problem.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Matt M" <MattM@.discussions.microsoft.com> wrote in message
news:0222672A-806B-4EA0-BC3C-957050488734@.microsoft.com...
> Just upgraded from SQL 2000 to 2005 and I created a backup maintenance plan
> but I am getting the following error everytime the maintenance plan runs:
> Error number: -1073548784
> Executing the query "BACKUP DATABASE [Clarke_MSCRM] TO DISK = N'C:\\Program
> Files\\Microsoft SQL
> Server\\MSSQL\\BACKUP\\Clarke_MSCRM\\Clarke_MSCRM_backup_200607270400.bak'
> WITH NOFORMAT, NOINIT, NAME = N'Clarke_MSCRM_backup_20060727040005', SKIP,
> REWIND, NOUNLOAD, STATS = 10
> " failed with the following error: "The backup of the file or filegroup
> "sysft_ftcat_documentindex" is not permitted because it is not online. BACKUP
> can be performed by using the FILEGROUP or FILE clauses to restrict the
> selection to include only online data.
> BACKUP DATABASE is terminating abnormally.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
>
> I'm not sure where to start looking.
>|||I tried the Rebuild Index task and that didnt seem to work. How would I go
about repopulating?
"Tibor Karaszi" wrote:
> Try rebuilding or repopulating your full-text catalog. This is included in 2005 backup and is most
> probably your problem.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Matt M" <MattM@.discussions.microsoft.com> wrote in message
> news:0222672A-806B-4EA0-BC3C-957050488734@.microsoft.com...
> > Just upgraded from SQL 2000 to 2005 and I created a backup maintenance plan
> > but I am getting the following error everytime the maintenance plan runs:
> >
> > Error number: -1073548784
> >
> > Executing the query "BACKUP DATABASE [Clarke_MSCRM] TO DISK = N'C:\\Program
> > Files\\Microsoft SQL
> > Server\\MSSQL\\BACKUP\\Clarke_MSCRM\\Clarke_MSCRM_backup_200607270400.bak'
> > WITH NOFORMAT, NOINIT, NAME = N'Clarke_MSCRM_backup_20060727040005', SKIP,
> > REWIND, NOUNLOAD, STATS = 10
> > " failed with the following error: "The backup of the file or filegroup
> > "sysft_ftcat_documentindex" is not permitted because it is not online. BACKUP
> > can be performed by using the FILEGROUP or FILE clauses to restrict the
> > selection to include only online data.
> > BACKUP DATABASE is terminating abnormally.". Possible failure reasons:
> > Problems with the query, "ResultSet" property not set correctly, parameters
> > not set correctly, or connection not established correctly.
> >
> >
> > I'm not sure where to start looking.
> >
> >
>|||I'm not talking about regular indexes, I'm talking about full text indexes. I don't do much
fulltext, so try at microsoft.public.sqlserver.fulltext.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Matt M" <MattM@.discussions.microsoft.com> wrote in message
news:82F9483C-93C4-48E9-B65B-D002AFF24700@.microsoft.com...
>I tried the Rebuild Index task and that didnt seem to work. How would I go
> about repopulating?
> "Tibor Karaszi" wrote:
>> Try rebuilding or repopulating your full-text catalog. This is included in 2005 backup and is
>> most
>> probably your problem.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Matt M" <MattM@.discussions.microsoft.com> wrote in message
>> news:0222672A-806B-4EA0-BC3C-957050488734@.microsoft.com...
>> > Just upgraded from SQL 2000 to 2005 and I created a backup maintenance plan
>> > but I am getting the following error everytime the maintenance plan runs:
>> >
>> > Error number: -1073548784
>> >
>> > Executing the query "BACKUP DATABASE [Clarke_MSCRM] TO DISK = N'C:\\Program
>> > Files\\Microsoft SQL
>> > Server\\MSSQL\\BACKUP\\Clarke_MSCRM\\Clarke_MSCRM_backup_200607270400.bak'
>> > WITH NOFORMAT, NOINIT, NAME = N'Clarke_MSCRM_backup_20060727040005', SKIP,
>> > REWIND, NOUNLOAD, STATS = 10
>> > " failed with the following error: "The backup of the file or filegroup
>> > "sysft_ftcat_documentindex" is not permitted because it is not online. BACKUP
>> > can be performed by using the FILEGROUP or FILE clauses to restrict the
>> > selection to include only online data.
>> > BACKUP DATABASE is terminating abnormally.". Possible failure reasons:
>> > Problems with the query, "ResultSet" property not set correctly, parameters
>> > not set correctly, or connection not established correctly.
>> >
>> >
>> > I'm not sure where to start looking.
>> >
>> >
>>|||I realized I misunderstood you after I posted. I looked into it and found
where to rebuild full text and it is running on a test box right now (Its a
slow machine so its taking a long time) I will try in production after hours.
"Tibor Karaszi" wrote:
> I'm not talking about regular indexes, I'm talking about full text indexes. I don't do much
> fulltext, so try at microsoft.public.sqlserver.fulltext.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Matt M" <MattM@.discussions.microsoft.com> wrote in message
> news:82F9483C-93C4-48E9-B65B-D002AFF24700@.microsoft.com...
> >I tried the Rebuild Index task and that didnt seem to work. How would I go
> > about repopulating?
> >
> > "Tibor Karaszi" wrote:
> >
> >> Try rebuilding or repopulating your full-text catalog. This is included in 2005 backup and is
> >> most
> >> probably your problem.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "Matt M" <MattM@.discussions.microsoft.com> wrote in message
> >> news:0222672A-806B-4EA0-BC3C-957050488734@.microsoft.com...
> >> > Just upgraded from SQL 2000 to 2005 and I created a backup maintenance plan
> >> > but I am getting the following error everytime the maintenance plan runs:
> >> >
> >> > Error number: -1073548784
> >> >
> >> > Executing the query "BACKUP DATABASE [Clarke_MSCRM] TO DISK = N'C:\\Program
> >> > Files\\Microsoft SQL
> >> > Server\\MSSQL\\BACKUP\\Clarke_MSCRM\\Clarke_MSCRM_backup_200607270400.bak'
> >> > WITH NOFORMAT, NOINIT, NAME = N'Clarke_MSCRM_backup_20060727040005', SKIP,
> >> > REWIND, NOUNLOAD, STATS = 10
> >> > " failed with the following error: "The backup of the file or filegroup
> >> > "sysft_ftcat_documentindex" is not permitted because it is not online. BACKUP
> >> > can be performed by using the FILEGROUP or FILE clauses to restrict the
> >> > selection to include only online data.
> >> > BACKUP DATABASE is terminating abnormally.". Possible failure reasons:
> >> > Problems with the query, "ResultSet" property not set correctly, parameters
> >> > not set correctly, or connection not established correctly.
> >> >
> >> >
> >> > I'm not sure where to start looking.
> >> >
> >> >
> >>
> >>
>

No comments:

Post a Comment