Errow whilst initializing report server!

I have an urgent problem which I hope someone can help me with.
After installation, I was told by the wizard that I needed to initialize the report server manually...
So I went to:
http://uacl-sql2/reports
It redirects to:
http://uacl-sql2/reports/Pages/Folder.aspx
And I get the following error:
An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help The system cannot find the file specified.
Does anyone know how to fix this...I have ensured that my Reports folder allows everyone to have full access...so I do not believe it is a security issue'?
Help!
*****************************************
* This message was posted via http://www.sqlmonster.com
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=c26e67c885b3477087ec7fc247396beb
*****************************************I can only think that you may have to use rsactivate (a command line utility
installed with Reporting Services). The syntax would be:
rsactivate -m RSServerName -u Username -p Password.
where username and password is the Windows account with admin priveleges to
the Reporting Services Service. This command would be run on the dbserver.
If this does not work you may need to use rsconfig (another installed
command line tool) prior to using rsactivate. rsconfig sets the connection
to the ReportServer database and the options can be viewed with rsconfig /?.
This should add the symetric keys in and activate or initialize the server.
Hope this helps.
Rodney Landrum, Author "Pro SQL Reporting Services" (Apress)
www.apress.com
"Jared Smith via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:c26e67c885b3477087ec7fc247396beb@.SQLMonster.com...
>I have an urgent problem which I hope someone can help me with.
> After installation, I was told by the wizard that I needed to initialize
> the report server manually...
> So I went to:
> http://uacl-sql2/reports
> It redirects to:
> http://uacl-sql2/reports/Pages/Folder.aspx
> And I get the following error:
>
> An internal error occurred on the report server. See the error log for
> more details. (rsInternalError) Get Online Help The system cannot find the
> file specified.
>
> Does anyone know how to fix this...I have ensured that my Reports folder
> allows everyone to have full access...so I do not believe it is a
> security issue'?
> Help!
> *****************************************
> * This message was posted via http://www.sqlmonster.com
> *
> * Report spam or abuse by clicking the following URL:
> *
> http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=c26e67c885b3477087ec7fc247396beb
> *****************************************|||I ran the rsactivate utility as you suggested and was returned with:
"Unable to find Reporting Services WMI namespace =on <machinename>. Reporting Services may not be installed"
Very odd...any suggestions?
*****************************************
* A copy of the whole thread can be found at:
* http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server-reporting/4819
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=48b8b00053c34af6b32f676a46089d07
*****************************************|||Jared,
I would check the ReportServer service on the Report Server through
Administrative Tools\Services to see if it is started. If not, try to start
it and record any errors. Also, check to see if that service is set to logon
at NT Authority\NetworkService on the Log On ta in the properties of the
ReportServer Service itself. You may need to reinstall and one of the
options during install is how you want the service to start. Have you tried
rsconfig on the Report Server? Also, I assume that the Report Server and
ReportServer database are on the same system (from the name you specified in
the URL it appears to be the case but I am only assuming)?
Rodney Landrum, Author "Pro SQL Server Reporting Services" (Apress)
www.apress.com
"Jared Smith via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:48b8b00053c34af6b32f676a46089d07@.SQLMonster.com...
>I ran the rsactivate utility as you suggested and was returned with:
> "Unable to find Reporting Services WMI namespace => on <machinename>. Reporting Services may not be installed"
> Very odd...any suggestions?
> *****************************************
> * A copy of the whole thread can be found at:
> * http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server-reporting/4819
> *
> * Report spam or abuse by clicking the following URL:
> *
> http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=48b8b00053c34af6b32f676a46089d07
> *****************************************|||Hi Rodney,
The rsconfig appeares to run fine. The service is also running fine, however I changed the login details to be an administrator, and restarted it....
Something odd i did notice in the logs was the same error I get when attempting to initialize the report server i.e. The system cannot find the file specified.
I have pasted the log details below...any ideas?
<Header>
<Product>Microsoft SQL Server Reporting Services Version 8.00.743.00</Product>
<Locale>en-US</Locale>
<TimeZone>New Zealand Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\LogFiles\ReportServerService__11_08_2004_13_41_25.log</Path>
<SystemName>UACL-SQL2</SystemName>
<OSName>Microsoft Windows NT 5.0.2195.0</OSName>
<OSVersion>5.0.2195.0</OSVersion>
</Header>
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing InstanceName to 'MSSQLSERVER' as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
ReportingServicesService!library!c38!11/8/2004-13:41:25:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
ReportingServicesService!resourceutilities!c38!11/8/2004-13:41:25:: i
INFO: Running on 2 physical processors, 4 logical processors
ReportingServicesService!resourceutilities!c38!11/8/2004-13:41:25:: i
INFO: Reporting Services starting SKU: Standard
ReportingServicesService!runningjobs!c38!11/8/2004-13:41:25:: i INFO: Database Cleanup (NT Service) timer enabled: Cycle: 600 seconds
ReportingServicesService!runningjobs!c38!11/8/2004-13:41:25:: i INFO: Running Requests Scavenger timer enabled: Cycle: 60 seconds
ReportingServicesService!runningjobs!c38!11/8/2004-13:41:25:: i INFO: Running Requests DB timer enabled: Cycle: 60 seconds
ReportingServicesService!runningjobs!c38!11/8/2004-13:41:25:: i INFO: Execution Log Entry Expiration timer enabled: Cycle: 44314 seconds
ReportingServicesService!runningjobs!c38!11/8/2004-13:41:25:: i INFO: Memory stats update timer enabled: Cycle: 60 seconds
ReportingServicesService!crypto!1140!11/8/2004-13:41:25:: i INFO: Initializing crypto as user: UACL-SQL2\Administrator
ReportingServicesService!crypto!1140!11/8/2004-13:41:25:: i INFO: Exporting public key
ReportingServicesService!library!1140!11/8/2004-13:41:25:: Exception caught while starting service. Error: System.IO.FileNotFoundException: The system cannot find the file specified.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
at RSManagedCrypto.RSCrypto.ExportPublicKey()
at
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at
Microsoft.ReportingServices.Library.ConnectionManager.VerifyConnection()
at
Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread()
ReportingServicesService!library!1140!11/8/2004-13:41:25:: Attempting to start service again...
*****************************************
* A copy of the whole thread can be found at:
* http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server-reporting/4819
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=03200d71bc3149edb4cc19ae7dd1db2f
*****************************************

Errors when uploading DDL and Data file created by Database Publishing Wizard

Hi,

I needed to recreate/publish a DDL and data file(of a database) that was produced using Database Publishing Wizard. The size of the file is 4G. I receive the following error when I try to open it up in the new query window of sql server 2005 (sp2)for execution.

"The operation could not be completed. Not enough storage is available to complete this operation."

I know my server has 829G of free storage space available. i receive no errors when I open up a smaller file also created by database publishing wizard.

What possibly is causing this?

Thanks in advance

Hi Hamdaweh,

When you attempt to open this in QA, it is attempting to load the entire 4GB+ into system RAM, that's why you are receiving this error. Try opening it with a specialist text editior and chunking it down into smaller files, and then run each via QA.

Cheers,

Rob

|||Thanks. So can i say the database publishing wizard is good for only DDLs and small data?

Errors Upsizing an access 2002 Database to SQL server 2005

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

MrKim wrote:

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

Regrading the 4 tables that fail; Are you sure you don't have other errors? 'Table was skipped, or export failed' Is not clear enough

The other message is just a warning telling you that at some point a certain column in the dataflow is not used anymore; the intention is to suggest to remove it if it is no necessary....only you can answer that question.

|||

No, that is is. When you use the Access upsizing wizard that is all the info it gives on the report. More useful maybe is the error messages given when trying to import the data through SQL server. I did finally import the data. There were bad dates which had to be fixed first.

I did it by turning of the SQL atuonumber/Prim Key, then writing a progam to import one record at a time, and noting the ID on the ones that fail - they all had bad dates.

Errors Upsizing an access 2002 Database to SQL server 2005

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

MrKim wrote:

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

Regrading the 4 tables that fail; Are you sure you don't have other errors? 'Table was skipped, or export failed' Is not clear enough

The other message is just a warning telling you that at some point a certain column in the dataflow is not used anymore; the intention is to suggest to remove it if it is no necessary....only you can answer that question.

|||

No, that is is. When you use the Access upsizing wizard that is all the info it gives on the report. More useful maybe is the error messages given when trying to import the data through SQL server. I did finally import the data. There were bad dates which had to be fixed first.

I did it by turning of the SQL atuonumber/Prim Key, then writing a progam to import one record at a time, and noting the ID on the ones that fail - they all had bad dates.

sql

Error: The backup of the file or filegroup "sysft_XXXX_FT" is not permitted because it

Hi There,

I am trying to do a full back up of a user database which has full text indexing on it. I use the maintenance plan wizard to set up a full backup. For some reason, I get this error.

=================

Executing the query "BACKUP DATABASE [XXXX] TO [XXXX]
WITH NOFORMAT, NOINIT, NAME = N'XXXX_backup_20060819040020', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error:
"The backup of the file or filegroup "sysft_XXXX_FT" 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.

===============

Can anybody please suggest me what I should do?

Thanks.

Is the database accessable and online ? i.e. : not suspect ?|||I get the same error message. I have a total of 10 databases & two of them give me the same error message when I try to backup using the maintenance utility. The d/b are used by the SharePoint Portal. If anyone has found a solution, please send my way. thank you|||

The immediate cause of the error is obvious: The fulltext catalog is offline.

What needs some work is figuring out why the catalog went offline and wnat to do about it.

The simplest courses of action are to either drop the catalog if it's not needed, or to rebuild it if it is needed. As soon as the rebuid starts, you should be able to successfully back up the database. You don't need to wait for the rebuild to complete.

|||

This can also happen for...
64bit 2005 Standard Cluster w/ SP1 (my configuration)
I found out that it was improperly reporting the "offline" full-text index. By improperly, I mean, that the error was reporting our current "Good" index when it should have been reporting one that had a different name that was in fact "offline".

Our problem:
You should look to see if you have any "old" indices from restores. Ours happened during a backup and restore from a single 32bit box moving to 64bit cluster. Took forever to find out how to get rid of the old index...Go to SQL Server Management Studio > <machine/instance> > <databasename> > Storage > Full Text Catalogs

...and delete the offending full text catalog definitions there. Mine didn't really exist (defined on a "d:\" drive that isn't even present in the new clustered system). You CANNOT make ad hoc queries to the db sys tables anymore in 2005. This will allow you to remove "hanging" full-text index definitions from the sys tables...allowing the backup to successfully kick off.

...our site Used Textbooks

|||Our error was:
"The backup of the file or filegroup "sysft_Keywords" is not permitted because it is not online."[SQLSTATE 42000] (Error 3007) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed. Sql Severity 16; Sql Message ID 3013.
This database was restored/converted from SQL2000. We did initially use SQL Full Text to perform searches before developing our own contextual tool.
Solution: In SQL Studio,Delete the items under the Full Text Catalogs==> Storage. This is the same ask12math's solution.|||

I'm thinking that solution is only relevant to the fully featured SQL Management Studio... is there any way to do this either in Studio Management Express or interactively? I've been using SQL Express (advanced version) for about a month now; last night's backup went fine, then today I get the "not permitted" error cited above. And only in this one database... the 15 or so others continue to backup normally.

BTW: I too restored these databases from SQL 2000 backups, and this one database had one column of one table marked for Full Text indexing at the time of the restore. I really don't need it, but apparently I didn't install the full text feature, so I can't remove it because I get an error that says the feature is not installed.

Any manual way around this problem? Thanks in advance.

Gordon

|||Are you sure that Express supports Full Text? ...and no as of about 6 months ago there was no way to remove full text index definitions manually (per Microsoft). That may have changed but if it has I am not aware of it. Good luck. My suggestion is to reimport the backup from 2000 after removing the definition (in 2000). Which probably isn't an option now because there is probably new data right? Let us know if you find anything.|||

k12math: Yes, you are right about the reimport... no longer an option because of a month of use. BUT: I did find a solution after several hours, so I'll share it with you!

1) Put the database into single user mode.

2) Start to detach the database. But before clicking OK for the detach, UNCHECK the box that says "Keep..." (the rest of the line is not immediately visible... what it says is, Keep fulltext catalogs. Get rid of that). Now OK the detach.

3) Reattach the database, and the backup works. Just like that.

Good luck everyone!

Gordon

|||This worked well for me. Good job Gordonh.

Neil.

Error: The backup of the file or filegroup "sysft_XXXX_FT" is not permitted because it

Hi There,

I am trying to do a full back up of a user database which has full text indexing on it. I use the maintenance plan wizard to set up a full backup. For some reason, I get this error.

=================

Executing the query "BACKUP DATABASE [XXXX] TO [XXXX]
WITH NOFORMAT, NOINIT, NAME = N'XXXX_backup_20060819040020', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error:
"The backup of the file or filegroup "sysft_XXXX_FT" 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.

===============

Can anybody please suggest me what I should do?

Thanks.

Is the database accessable and online ? i.e. : not suspect ?|||I get the same error message. I have a total of 10 databases & two of them give me the same error message when I try to backup using the maintenance utility. The d/b are used by the SharePoint Portal. If anyone has found a solution, please send my way. thank you|||

The immediate cause of the error is obvious: The fulltext catalog is offline.

What needs some work is figuring out why the catalog went offline and wnat to do about it.

The simplest courses of action are to either drop the catalog if it's not needed, or to rebuild it if it is needed. As soon as the rebuid starts, you should be able to successfully back up the database. You don't need to wait for the rebuild to complete.

|||

This can also happen for...
64bit 2005 Standard Cluster w/ SP1 (my configuration)
I found out that it was improperly reporting the "offline" full-text index. By improperly, I mean, that the error was reporting our current "Good" index when it should have been reporting one that had a different name that was in fact "offline".

Our problem:
You should look to see if you have any "old" indices from restores. Ours happened during a backup and restore from a single 32bit box moving to 64bit cluster. Took forever to find out how to get rid of the old index...Go to SQL Server Management Studio > <machine/instance> > <databasename> > Storage > Full Text Catalogs

...and delete the offending full text catalog definitions there. Mine didn't really exist (defined on a "d:\" drive that isn't even present in the new clustered system). You CANNOT make ad hoc queries to the db sys tables anymore in 2005. This will allow you to remove "hanging" full-text index definitions from the sys tables...allowing the backup to successfully kick off.

...our site Used Textbooks

|||Our error was:
"The backup of the file or filegroup "sysft_Keywords" is not permitted because it is not online."[SQLSTATE 42000] (Error 3007) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed. Sql Severity 16; Sql Message ID 3013.
This database was restored/converted from SQL2000. We did initially use SQL Full Text to perform searches before developing our own contextual tool.
Solution: In SQL Studio, Delete the items under the Full Text Catalogs ==> Storage. This is the same as k12math's solution.|||

I'm thinking that solution is only relevant to the fully featured SQL Management Studio... is there any way to do this either in Studio Management Express or interactively? I've been using SQL Express (advanced version) for about a month now; last night's backup went fine, then today I get the "not permitted" error cited above. And only in this one database... the 15 or so others continue to backup normally.

BTW: I too restored these databases from SQL 2000 backups, and this one database had one column of one table marked for Full Text indexing at the time of the restore. I really don't need it, but apparently I didn't install the full text feature, so I can't remove it because I get an error that says the feature is not installed.

Any manual way around this problem? Thanks in advance.

Gordon

|||Are you sure that Express supports Full Text? ...and no as of about 6 months ago there was no way to remove full text index definitions manually (per Microsoft). That may have changed but if it has I am not aware of it. Good luck. My suggestion is to reimport the backup from 2000 after removing the definition (in 2000). Which probably isn't an option now because there is probably new data right? Let us know if you find anything.|||

k12math: Yes, you are right about the reimport... no longer an option because of a month of use. BUT: I did find a solution after several hours, so I'll share it with you!

1) Put the database into single user mode.

2) Start to detach the database. But before clicking OK for the detach, UNCHECK the box that says "Keep..." (the rest of the line is not immediately visible... what it says is, Keep fulltext catalogs. Get rid of that). Now OK the detach.

3) Reattach the database, and the backup works. Just like that.

Good luck everyone!

Gordon

|||This worked well for me. Good job

Gordonh.

Neil.

Error: The backup of the file or filegroup "sysft_XXXX_FT" is not permitted because it

Hi There,

I am trying to do a full back up of a user database which has full text indexing on it. I use the maintenance plan wizard to set up a full backup. For some reason, I get this error.

=================

Executing the query "BACKUP DATABASE [XXXX] TO [XXXX]
WITH NOFORMAT, NOINIT, NAME = N'XXXX_backup_20060819040020', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error:
"The backup of the file or filegroup "sysft_XXXX_FT" 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.

===============

Can anybody please suggest me what I should do?

Thanks.

Is the database accessable and online ? i.e. : not suspect ?|||I get the same error message. I have a total of 10 databases & two of them give me the same error message when I try to backup using the maintenance utility. The d/b are used by the SharePoint Portal. If anyone has found a solution, please send my way. thank you|||

The immediate cause of the error is obvious: The fulltext catalog is offline.

What needs some work is figuring out why the catalog went offline and wnat to do about it.

The simplest courses of action are to either drop the catalog if it's not needed, or to rebuild it if it is needed. As soon as the rebuid starts, you should be able to successfully back up the database. You don't need to wait for the rebuild to complete.

|||

This can also happen for...
64bit 2005 Standard Cluster w/ SP1 (my configuration)
I found out that it was improperly reporting the "offline" full-text index. By improperly, I mean, that the error was reporting our current "Good" index when it should have been reporting one that had a different name that was in fact "offline".

Our problem:
You should look to see if you have any "old" indices from restores. Ours happened during a backup and restore from a single 32bit box moving to 64bit cluster. Took forever to find out how to get rid of the old index...Go to SQL Server Management Studio > <machine/instance> > <databasename> > Storage > Full Text Catalogs

...and delete the offending full text catalog definitions there. Mine didn't really exist (defined on a "d:\" drive that isn't even present in the new clustered system). You CANNOT make ad hoc queries to the db sys tables anymore in 2005. This will allow you to remove "hanging" full-text index definitions from the sys tables...allowing the backup to successfully kick off.

...our site Used Textbooks

|||Our error was:
"The backup of the file or filegroup "sysft_Keywords" is not permitted because it is not online."[SQLSTATE 42000] (Error 3007) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed. Sql Severity 16; Sql Message ID 3013.
This database was restored/converted from SQL2000. We did initially use SQL Full Text to perform searches before developing our own contextual tool.
Solution: In SQL Studio, Delete the items under the Full Text Catalogs ==> Storage. This is the same as k12math's solution.|||

I'm thinking that solution is only relevant to the fully featured SQL Management Studio... is there any way to do this either in Studio Management Express or interactively? I've been using SQL Express (advanced version) for about a month now; last night's backup went fine, then today I get the "not permitted" error cited above. And only in this one database... the 15 or so others continue to backup normally.

BTW: I too restored these databases from SQL 2000 backups, and this one database had one column of one table marked for Full Text indexing at the time of the restore. I really don't need it, but apparently I didn't install the full text feature, so I can't remove it because I get an error that says the feature is not installed.

Any manual way around this problem? Thanks in advance.

Gordon

|||Are you sure that Express supports Full Text? ...and no as of about 6 months ago there was no way to remove full text index definitions manually (per Microsoft). That may have changed but if it has I am not aware of it. Good luck. My suggestion is to reimport the backup from 2000 after removing the definition (in 2000). Which probably isn't an option now because there is probably new data right? Let us know if you find anything.|||

k12math: Yes, you are right about the reimport... no longer an option because of a month of use. BUT: I did find a solution after several hours, so I'll share it with you!

1) Put the database into single user mode.

2) Start to detach the database. But before clicking OK for the detach, UNCHECK the box that says "Keep..." (the rest of the line is not immediately visible... what it says is, Keep fulltext catalogs. Get rid of that). Now OK the detach.

3) Reattach the database, and the backup works. Just like that.

Good luck everyone!

Gordon

|||This worked well for me. Good job

Gordonh.

Neil.

Error: The backup of the file or filegroup "sysft_XXXX_FT" is not permitted because it

Hi There,

I am trying to do a full back up of a user database which has full text indexing on it. I use the maintenance plan wizard to set up a full backup. For some reason, I get this error.

=================

Executing the query "BACKUP DATABASE [XXXX] TO [XXXX]
WITH NOFORMAT, NOINIT, NAME = N'XXXX_backup_20060819040020', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error:
"The backup of the file or filegroup "sysft_XXXX_FT" 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.

===============

Can anybody please suggest me what I should do?

Thanks.

Is the database accessable and online ? i.e. : not suspect ?|||I get the same error message. I have a total of 10 databases & two of them give me the same error message when I try to backup using the maintenance utility. The d/b are used by the SharePoint Portal. If anyone has found a solution, please send my way. thank you|||

The immediate cause of the error is obvious: The fulltext catalog is offline.

What needs some work is figuring out why the catalog went offline and wnat to do about it.

The simplest courses of action are to either drop the catalog if it's not needed, or to rebuild it if it is needed. As soon as the rebuid starts, you should be able to successfully back up the database. You don't need to wait for the rebuild to complete.

|||

This can also happen for...
64bit 2005 Standard Cluster w/ SP1 (my configuration)
I found out that it was improperly reporting the "offline" full-text index. By improperly, I mean, that the error was reporting our current "Good" index when it should have been reporting one that had a different name that was in fact "offline".

Our problem:
You should look to see if you have any "old" indices from restores. Ours happened during a backup and restore from a single 32bit box moving to 64bit cluster. Took forever to find out how to get rid of the old index...Go to SQL Server Management Studio > <machine/instance> > <databasename> > Storage > Full Text Catalogs

...and delete the offending full text catalog definitions there. Mine didn't really exist (defined on a "d:\" drive that isn't even present in the new clustered system). You CANNOT make ad hoc queries to the db sys tables anymore in 2005. This will allow you to remove "hanging" full-text index definitions from the sys tables...allowing the backup to successfully kick off.

...our site Used Textbooks

|||Our error was:
"The backup of the file or filegroup "sysft_Keywords" is not permitted because it is not online."[SQLSTATE 42000] (Error 3007) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed. Sql Severity 16; Sql Message ID 3013.
This database was restored/converted from SQL2000. We did initially use SQL Full Text to perform searches before developing our own contextual tool.
Solution: In SQL Studio, Delete the items under the Full Text Catalogs ==> Storage. This is the same as k12math's solution.|||

I'm thinking that solution is only relevant to the fully featured SQL Management Studio... is there any way to do this either in Studio Management Express or interactively? I've been using SQL Express (advanced version) for about a month now; last night's backup went fine, then today I get the "not permitted" error cited above. And only in this one database... the 15 or so others continue to backup normally.

BTW: I too restored these databases from SQL 2000 backups, and this one database had one column of one table marked for Full Text indexing at the time of the restore. I really don't need it, but apparently I didn't install the full text feature, so I can't remove it because I get an error that says the feature is not installed.

Any manual way around this problem? Thanks in advance.

Gordon

|||Are you sure that Express supports Full Text? ...and no as of about 6 months ago there was no way to remove full text index definitions manually (per Microsoft). That may have changed but if it has I am not aware of it. Good luck. My suggestion is to reimport the backup from 2000 after removing the definition (in 2000). Which probably isn't an option now because there is probably new data right? Let us know if you find anything.|||

k12math: Yes, you are right about the reimport... no longer an option because of a month of use. BUT: I did find a solution after several hours, so I'll share it with you!

1) Put the database into single user mode.

2) Start to detach the database. But before clicking OK for the detach, UNCHECK the box that says "Keep..." (the rest of the line is not immediately visible... what it says is, Keep fulltext catalogs. Get rid of that). Now OK the detach.

3) Reattach the database, and the backup works. Just like that.

Good luck everyone!

Gordon

|||This worked well for me. Good job

Gordonh.

Neil.

Error: The backup of the file or filegroup "sysft_XXXX_FT" is not permitted becaus

Hi There,

I am trying to do a full back up of a user database which has full text indexing on it. I use the maintenance plan wizard to set up a full backup. For some reason, I get this error.

=================

Executing the query "BACKUP DATABASE [XXXX] TO [XXXX]
WITH NOFORMAT, NOINIT, NAME = N'XXXX_backup_20060819040020', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error:
"The backup of the file or filegroup "sysft_XXXX_FT" 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.

===============

Can anybody please suggest me what I should do?

Thanks.

Is the database accessable and online ? i.e. : not suspect ?|||I get the same error message. I have a total of 10 databases & two of them give me the same error message when I try to backup using the maintenance utility. The d/b are used by the SharePoint Portal. If anyone has found a solution, please send my way. thank you|||

The immediate cause of the error is obvious: The fulltext catalog is offline.

What needs some work is figuring out why the catalog went offline and wnat to do about it.

The simplest courses of action are to either drop the catalog if it's not needed, or to rebuild it if it is needed. As soon as the rebuid starts, you should be able to successfully back up the database. You don't need to wait for the rebuild to complete.

|||

This can also happen for...
64bit 2005 Standard Cluster w/ SP1 (my configuration)
I found out that it was improperly reporting the "offline" full-text index. By improperly, I mean, that the error was reporting our current "Good" index when it should have been reporting one that had a different name that was in fact "offline".

Our problem:
You should look to see if you have any "old" indices from restores. Ours happened during a backup and restore from a single 32bit box moving to 64bit cluster. Took forever to find out how to get rid of the old index...Go to SQL Server Management Studio > <machine/instance> > <databasename> > Storage > Full Text Catalogs

...and delete the offending full text catalog definitions there. Mine didn't really exist (defined on a "d:\" drive that isn't even present in the new clustered system). You CANNOT make ad hoc queries to the db sys tables anymore in 2005. This will allow you to remove "hanging" full-text index definitions from the sys tables...allowing the backup to successfully kick off.

...our site Used Textbooks

|||Our error was:
"The backup of the file or filegroup "sysft_Keywords" is not permitted because it is not online."[SQLSTATE 42000] (Error 3007) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed. Sql Severity 16; Sql Message ID 3013.
This database was restored/converted from SQL2000. We did initially use SQL Full Text to perform searches before developing our own contextual tool.
Solution: In SQL Studio, Delete the items under the Full Text Catalogs ==> Storage. This is the same as k12math's solution.|||

I'm thinking that solution is only relevant to the fully featured SQL Management Studio... is there any way to do this either in Studio Management Express or interactively? I've been using SQL Express (advanced version) for about a month now; last night's backup went fine, then today I get the "not permitted" error cited above. And only in this one database... the 15 or so others continue to backup normally.

BTW: I too restored these databases from SQL 2000 backups, and this one database had one column of one table marked for Full Text indexing at the time of the restore. I really don't need it, but apparently I didn't install the full text feature, so I can't remove it because I get an error that says the feature is not installed.

Any manual way around this problem? Thanks in advance.

Gordon

|||Are you sure that Express supports Full Text? ...and no as of about 6 months ago there was no way to remove full text index definitions manually (per Microsoft). That may have changed but if it has I am not aware of it. Good luck. My suggestion is to reimport the backup from 2000 after removing the definition (in 2000). Which probably isn't an option now because there is probably new data right? Let us know if you find anything.|||

k12math: Yes, you are right about the reimport... no longer an option because of a month of use. BUT: I did find a solution after several hours, so I'll share it with you!

1) Put the database into single user mode.

2) Start to detach the database. But before clicking OK for the detach, UNCHECK the box that says "Keep..." (the rest of the line is not immediately visible... what it says is, Keep fulltext catalogs. Get rid of that). Now OK the detach.

3) Reattach the database, and the backup works. Just like that.

Good luck everyone!

Gordon

|||This worked well for me. Good job

Gordonh.

Neil.

Error: The backup of the file or filegroup "sysft_XXXX_FT" is not permitted becaus

Hi There,

I am trying to do a full back up of a user database which has full text indexing on it. I use the maintenance plan wizard to set up a full backup. For some reason, I get this error.

=================

Executing the query "BACKUP DATABASE [XXXX] TO [XXXX]
WITH NOFORMAT, NOINIT, NAME = N'XXXX_backup_20060819040020', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error:
"The backup of the file or filegroup "sysft_XXXX_FT" 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.

===============

Can anybody please suggest me what I should do?

Thanks.

Is the database accessable and online ? i.e. : not suspect ?|||I get the same error message. I have a total of 10 databases & two of them give me the same error message when I try to backup using the maintenance utility. The d/b are used by the SharePoint Portal. If anyone has found a solution, please send my way. thank you|||

The immediate cause of the error is obvious: The fulltext catalog is offline.

What needs some work is figuring out why the catalog went offline and wnat to do about it.

The simplest courses of action are to either drop the catalog if it's not needed, or to rebuild it if it is needed. As soon as the rebuid starts, you should be able to successfully back up the database. You don't need to wait for the rebuild to complete.

|||

This can also happen for...
64bit 2005 Standard Cluster w/ SP1 (my configuration)
I found out that it was improperly reporting the "offline" full-text index. By improperly, I mean, that the error was reporting our current "Good" index when it should have been reporting one that had a different name that was in fact "offline".

Our problem:
You should look to see if you have any "old" indices from restores. Ours happened during a backup and restore from a single 32bit box moving to 64bit cluster. Took forever to find out how to get rid of the old index...Go to SQL Server Management Studio > <machine/instance> > <databasename> > Storage > Full Text Catalogs

...and delete the offending full text catalog definitions there. Mine didn't really exist (defined on a "d:\" drive that isn't even present in the new clustered system). You CANNOT make ad hoc queries to the db sys tables anymore in 2005. This will allow you to remove "hanging" full-text index definitions from the sys tables...allowing the backup to successfully kick off.

...our site Used Textbooks

|||Our error was:
"The backup of the file or filegroup "sysft_Keywords" is not permitted because it is not online."[SQLSTATE 42000] (Error 3007) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed. Sql Severity 16; Sql Message ID 3013.
This database was restored/converted from SQL2000. We did initially use SQL Full Text to perform searches before developing our own contextual tool.
Solution: In SQL Studio, Delete the items under the Full Text Catalogs ==> Storage. This is the same as k12math's solution.|||

I'm thinking that solution is only relevant to the fully featured SQL Management Studio... is there any way to do this either in Studio Management Express or interactively? I've been using SQL Express (advanced version) for about a month now; last night's backup went fine, then today I get the "not permitted" error cited above. And only in this one database... the 15 or so others continue to backup normally.

BTW: I too restored these databases from SQL 2000 backups, and this one database had one column of one table marked for Full Text indexing at the time of the restore. I really don't need it, but apparently I didn't install the full text feature, so I can't remove it because I get an error that says the feature is not installed.

Any manual way around this problem? Thanks in advance.

Gordon

|||Are you sure that Express supports Full Text? ...and no as of about 6 months ago there was no way to remove full text index definitions manually (per Microsoft). That may have changed but if it has I am not aware of it. Good luck. My suggestion is to reimport the backup from 2000 after removing the definition (in 2000). Which probably isn't an option now because there is probably new data right? Let us know if you find anything.|||

k12math: Yes, you are right about the reimport... no longer an option because of a month of use. BUT: I did find a solution after several hours, so I'll share it with you!

1) Put the database into single user mode.

2) Start to detach the database. But before clicking OK for the detach, UNCHECK the box that says "Keep..." (the rest of the line is not immediately visible... what it says is, Keep fulltext catalogs. Get rid of that). Now OK the detach.

3) Reattach the database, and the backup works. Just like that.

Good luck everyone!

Gordon

|||This worked well for me. Good job

Gordonh.

Neil.

Error: The backup of the file or filegroup "sysft_XXXX_FT" is not permitted becaus

Hi There,

I am trying to do a full back up of a user database which has full text indexing on it. I use the maintenance plan wizard to set up a full backup. For some reason, I get this error.

=================

Executing the query "BACKUP DATABASE [XXXX] TO [XXXX]
WITH NOFORMAT, NOINIT, NAME = N'XXXX_backup_20060819040020', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error:
"The backup of the file or filegroup "sysft_XXXX_FT" 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.

===============

Can anybody please suggest me what I should do?

Thanks.

Is the database accessable and online ? i.e. : not suspect ?|||I get the same error message. I have a total of 10 databases & two of them give me the same error message when I try to backup using the maintenance utility. The d/b are used by the SharePoint Portal. If anyone has found a solution, please send my way. thank you|||

The immediate cause of the error is obvious: The fulltext catalog is offline.

What needs some work is figuring out why the catalog went offline and wnat to do about it.

The simplest courses of action are to either drop the catalog if it's not needed, or to rebuild it if it is needed. As soon as the rebuid starts, you should be able to successfully back up the database. You don't need to wait for the rebuild to complete.

|||

This can also happen for...
64bit 2005 Standard Cluster w/ SP1 (my configuration)
I found out that it was improperly reporting the "offline" full-text index. By improperly, I mean, that the error was reporting our current "Good" index when it should have been reporting one that had a different name that was in fact "offline".

Our problem:
You should look to see if you have any "old" indices from restores. Ours happened during a backup and restore from a single 32bit box moving to 64bit cluster. Took forever to find out how to get rid of the old index...Go to SQL Server Management Studio > <machine/instance> > <databasename> > Storage > Full Text Catalogs

...and delete the offending full text catalog definitions there. Mine didn't really exist (defined on a "d:\" drive that isn't even present in the new clustered system). You CANNOT make ad hoc queries to the db sys tables anymore in 2005. This will allow you to remove "hanging" full-text index definitions from the sys tables...allowing the backup to successfully kick off.

...our site Used Textbooks

|||Our error was:
"The backup of the file or filegroup "sysft_Keywords" is not permitted because it is not online."[SQLSTATE 42000] (Error 3007) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed. Sql Severity 16; Sql Message ID 3013.
This database was restored/converted from SQL2000. We did initially use SQL Full Text to perform searches before developing our own contextual tool.
Solution: In SQL Studio, Delete the items under the Full Text Catalogs ==> Storage. This is the same as k12math's solution.|||

I'm thinking that solution is only relevant to the fully featured SQL Management Studio... is there any way to do this either in Studio Management Express or interactively? I've been using SQL Express (advanced version) for about a month now; last night's backup went fine, then today I get the "not permitted" error cited above. And only in this one database... the 15 or so others continue to backup normally.

BTW: I too restored these databases from SQL 2000 backups, and this one database had one column of one table marked for Full Text indexing at the time of the restore. I really don't need it, but apparently I didn't install the full text feature, so I can't remove it because I get an error that says the feature is not installed.

Any manual way around this problem? Thanks in advance.

Gordon

|||Are you sure that Express supports Full Text? ...and no as of about 6 months ago there was no way to remove full text index definitions manually (per Microsoft). That may have changed but if it has I am not aware of it. Good luck. My suggestion is to reimport the backup from 2000 after removing the definition (in 2000). Which probably isn't an option now because there is probably new data right? Let us know if you find anything.|||

k12math: Yes, you are right about the reimport... no longer an option because of a month of use. BUT: I did find a solution after several hours, so I'll share it with you!

1) Put the database into single user mode.

2) Start to detach the database. But before clicking OK for the detach, UNCHECK the box that says "Keep..." (the rest of the line is not immediately visible... what it says is, Keep fulltext catalogs. Get rid of that). Now OK the detach.

3) Reattach the database, and the backup works. Just like that.

Good luck everyone!

Gordon

|||This worked well for me. Good job

Gordonh.

Neil.