Groups | Blog | Home
all groups > sql server full text search > july 2003 >

sql server full text search : Unexpected NULL value returned for the column


Hilary Cotter
7/31/2003 5:20:38 PM
can you post any messages you are getting in your event log - preferably
mssci, or mssearch related errors.

Also post your gatherer log here.

This sounds like something wrong with your environment. Can you give us any
details about your system - ie it was working, but I installed ....... Was
it ever working?

Did you change the SQL Server service account using control panel? Is the
builtin\admin account in the server administrator role?

Did you apply an sp recently? Does sharepoint run on this machine? Office
XP search (this is only significant if you are running NT 4).


[quoted text, click to view]

Jason Davis
7/31/2003 11:40:46 PM
Hilary, John, SOS!

I had a major crisis with my sql server today.
After applying Hilary's great advice from here: http://tinyurl.com/inyn I
was able to get things in order.

I'm getting this new error now. It disappers after I try to re-build, but as
soon as I populate (full/incremenet) - I get it again:

ODBC Error Code = 01000 (General warning
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace
[Non-interface error: Unexpected NULL value returned for the column:
ProviderName='Full-text Search Engine', TableName='[FULLTEXT:FT]',
ColumnName='KEY'].

Hilary, I tried your suggestion from here:

=======================
here is a radical idea. Try to determine the row where you are getting this
problem and then update it.
For instance if you find it occurs on a row where the PK is 234523, do
update tablename set textcol=textcol
where pk=234523, do a full population to see if this fixes the problem.
==============

It doesn't help, it happens on all of my tables and catalogs, and they are
not null.

Any help?

Jason Davis
8/1/2003 10:10:38 AM
Hilary hi,

[quoted text, click to view]

Everything looks fine here:
The Search service has added project <SQL0001400005>.
The Search service has loaded project <SQLServer SQL0001400005>.
The crawl on project <SQLServer SQL0001400005> has started.
The end of crawl for project <SQLServer SQL0001400005> has been detected.
The Gatherer successfully processed 2046 documents totaling 0K. It failed to
filter 0 documents. 0 URLs could not be reached or were denied access.
Master merge has completed on e:\sqlfts\sql0001400005\build\indexer\cifiles.

[quoted text, click to view]

My GatherLogs (E:\SQLFTS\Config\GatherLogs) is empty.
I do have Build\Indexer and Build\Nlfiles - Where else can I look?

[quoted text, click to view]

Yes, it was working flawleslly. I then detach/attach databases from one
location to another, and couldn't get FTS to work.

[quoted text, click to view]

It was changed back a long time ago, SQL Server, SQLServeragent and MSSearch
works.
MSSearch uses the LocalSystem account.

[quoted text, click to view]

Using Windows 2000 SP4.
I applied a SQL SP3 about a month ago, the fulltext search worked great
afterwards.

YES!! I've installed Office XP on the server and might got the XP search as
well.

When I tried re-applying SP3, it was stuck on "Validating User..." - I
didn't see that error before and I tried all of the possible solutions from
MS (changing to single mode, changing registry).

I tried re-installing only FTS from \x86\fulltext\mssearch\search (SP3
release and original SQL cd) - It didn't work (tried SearchStp.exe,
ftsetup.exe)

Tell me what else do you need, I hate to go and re-install everything from
scratch.

J.

[quoted text, click to view]

AddThis Social Bookmark Button