Error '0x8000ffff' occurred during full-text index population

I have a nightly job scheduled by the SQL Agent scheduler to run full-text
creations nightly, and I have noticed that the following error message
appears during the process of trying to index a number of tables (but not
all).
can someone please provide some advice as to what might be causing this
error to occur - and what I should be looking at to resolve this issue.
Regards
Andy MBCS CITP
Andy,
Do the SQL logs report any more information, or the Windows Event Logs?
Error '0x8000FFFF' (2147549183) often means "Unexpected failure", so
additional information from the logs might help.
RLF
"Andy Knott" <AndyKnott@.discussions.microsoft.com> wrote in message
news:DC3B2B34-7A26-44F0-B75E-E02ADD4CE07C@.microsoft.com...
>I have a nightly job scheduled by the SQL Agent scheduler to run full-text
> creations nightly, and I have noticed that the following error message
> appears during the process of trying to index a number of tables (but not
> all).
> can someone please provide some advice as to what might be causing this
> error to occur - and what I should be looking at to resolve this issue.
>
> --
> Regards
> Andy MBCS CITP
|||Russell
Unfortuanately the event logs tell me to look at the full crawl logs - and
it is the full crawl logs which have this error code contained within them.
If, as you suggest the code is a non specific one, how on earth am I going
to track down what is causing the error to be thrown in the first place!!
Thanks for your response - any other suggestions very welcome
Regards
Andy
Regards
Andy MBCS CITP
"Russell Fields" wrote:

> Andy,
> Do the SQL logs report any more information, or the Windows Event Logs?
> Error '0x8000FFFF' (2147549183) often means "Unexpected failure", so
> additional information from the logs might help.
> RLF
> "Andy Knott" <AndyKnott@.discussions.microsoft.com> wrote in message
> news:DC3B2B34-7A26-44F0-B75E-E02ADD4CE07C@.microsoft.com...
>
>
|||Andy,
I scoured my various crawl logs to see if I ever got the same message, but I
have not. I see that missing iFilters are an 'expected' error and are
reported on properly, etc, etc. through the problems that came to my mind.
Do the files that produce these errors remain the same from day to day? Do
they share any characteristic in common, such as file type, length of file
name, directory nesting, embedded bitmaps, etc? I have not a clue as to
what is wrong, but any information that gives a hint would help.
RLF
"Andy Knott" <AndyKnott@.discussions.microsoft.com> wrote in message
news:94FF8204-9A4F-4841-BF8E-CF7724E1EAAF@.microsoft.com...[vbcol=seagreen]
> Russell
> Unfortuanately the event logs tell me to look at the full crawl logs - and
> it is the full crawl logs which have this error code contained within
> them.
> If, as you suggest the code is a non specific one, how on earth am I going
> to track down what is causing the error to be thrown in the first place!!
> Thanks for your response - any other suggestions very welcome
> Regards
> Andy
> --
> Regards
> Andy MBCS CITP
>
> "Russell Fields" wrote:
|||Please see the following article from Microsoft.
http://support.microsoft.com/default.aspx/kb/243349
"Russell Fields" wrote:

> Andy,
> I scoured my various crawl logs to see if I ever got the same message, but I
> have not. I see that missing iFilters are an 'expected' error and are
> reported on properly, etc, etc. through the problems that came to my mind.
> Do the files that produce these errors remain the same from day to day? Do
> they share any characteristic in common, such as file type, length of file
> name, directory nesting, embedded bitmaps, etc? I have not a clue as to
> what is wrong, but any information that gives a hint would help.
> RLF
> "Andy Knott" <AndyKnott@.discussions.microsoft.com> wrote in message
> news:94FF8204-9A4F-4841-BF8E-CF7724E1EAAF@.microsoft.com...
>
>