SQL 2005 Failed to PAUSE\RESUME Errors

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Woo - 13 Sep 2006 09:56 GMT

Hiya,

I have several database on a SQL2005 server. They have fuill text indexing
enabled. They all have one catalog referred to one table. Currently they
have not been populated so are therefore empty.

Problem is, everytime we do a backup of these databases it tries to PAUSE
and RESUME the full-text catalog but cant. There are the errors we get at
every backup of every database:

Changing the status to PAUSE for full-text catalog "KnowlegeBaseCatalog" (5)
in database "INTERNATIONAL" (9). This is an informational message only. No
user action is required.

Warning: Failed to change the status to PAUSE for full-text catalog
"KnowlegeBaseCatalog" (5) in database "INTERNATIONAL" (9). Error:
0x8001010e(The application called an interface that was marshalled for a
different thread.).

Changing the status to RESUME for full-text catalog "KnowlegeBaseCatalog"
(5) in database "INTERNATIONAL" (9). This is an informational message only.
No user action is required.

Warning: Failed to change the status to RESUME for full-text catalog
"KnowlegeBaseCatalog" (5) in database "INTERNATIONAL" (9). Error:
0x8001010e(The application called an interface that was marshalled for a
different thread.).

Any ideas?
Wendy

Reply to this Message

Hilary Cotter - 13 Sep 2006 13:17 GMT

Is there any history to this server? Was it an upgrade? Does this apply?
http://support.microsoft.com/kb/923355/en-us

I had similar error myself and all I can do is a file group backup. I hate
to open a support incident and have Microsoft tell me to rebuild when my
configuration does not meet the description in this kb article.

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

> Hiya,
>
[quoted text clipped - 29 lines]
> Any ideas?
> Wendy

Reply to this Message

Woo - 13 Sep 2006 13:47 GMT

Hiya,

Yes this server was upgraded from SQL2000 to SQL2005.

This article doesnt apply because my backup still works ok but it just fires
out this error message everytime.

I have one database on this server where the full text catalogs dont cause
any issues during backups. The rest of the databases all have this problem.

Also, I have another server that was upgraded in the same way and none of
the databases have this problem.

Any suggestions are most welcome!
Wendy

> Is there any history to this server? Was it an upgrade? Does this apply?
> http://support.microsoft.com/kb/923355/en-us
[quoted text clipped - 36 lines]
> > Any ideas?
> > Wendy

Reply to this Message

Hilary Cotter - 13 Sep 2006 14:34 GMT

If you create a new database with a full text table in it does it give this
error when backing it up?

Signature

> Hiya,
>
[quoted text clipped - 63 lines]
>> > Any ideas?
>> > Wendy

Reply to this Message

Woo - 13 Sep 2006 15:04 GMT

I cant create a new database just now as it is production but we did restore
from a backup of one of the problem databases and the problem copied over.

Do you think it is something to do with the upgrade process?

> If you create a new database with a full text table in it does it give this
> error when backing it up?
[quoted text clipped - 66 lines]
> >> > Any ideas?
> >> > Wendy

Reply to this Message

Hilary Cotter - 13 Sep 2006 20:41 GMT

That's what it sounds like. I am not sure if it is a problem with a binary
or with the database paths.

Signature

>I cant create a new database just now as it is production but we did
>restore
[quoted text clipped - 83 lines]
>> >> > Any ideas?
>> >> > Wendy

Reply to this Message