Server: Msg 2526, Level 16, State 3, Procedure sp_fulltext

Server: Msg 2526, Level 16, State 3, Procedure sp_fulltext_table,

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Support - 17 Aug 2005 14:08 GMT

Hello:
running SQL2000 SP3 (8.00.818)
first
1) when we upgraded our hardware, ie,rebuilt SQL on a new machine, we
noticed several system stored procedures were missing, including,
master..sp_fulltext_table
--I found a copy on our test machine and transfered it to production server
where it is now seen as dbo owner but not a system table rather a user
table....
2) when running...

EXEC sp_fulltext_table 'DOC', 'create', 'DOC', 'indx_intDOCunid'I get
Server: Msg 2526, Level 16, State 3, Procedure sp_fulltext_table, Line 122
Incorrect DBCC statement. Check the documentation for the correct DBCC
syntax and options.

.. which is:
-- ADD TO CATALOG
DBCC CALLFULLTEXT ( 5, @ftcatid, @objid ) -- FTAddURL( @ftcatid, db_id(),
@objid )

QUESTION: how do I get out of this mess.
Thanks
Terry

Reply to this Message

John Kane - 17 Aug 2005 15:39 GMT

Terry,
How did you "rebuild" SQL on the new machine? Did you install it from the
SQL Server CD or install it as a disk image?
You should NEVER be missing "several" or any system stored proc's, some that
call internal system extended system procs that are in fact dll's and need
to be registered on your new machine. DBCC CALLFULLTEXT is one such internal
system stored proc and if this is not working correctly, then all of your
Full-text Search (FTS) functionality is suspect.

As how to get out if this mess... That would depend upon the level of
missing stored procs, if it is just MSSearch / FTS, you can use the
procedures in the following KB article to manually re-install FTS /
MSSearch:

827449 How to manually reinstall the Microsoft Search service for an
instance of SQL 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827449

Hope that helps!
John

Signature

SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/

> Hello:
> running SQL2000 SP3 (8.00.818)
[quoted text clipped - 21 lines]
> Thanks
> Terry

Reply to this Message

Support - 17 Aug 2005 18:18 GMT

John:
Thanks
we installed SQL from scratch and applied all the service packs and then ran
the "Copy Database Wizard"
So far, we have missed:

master..sp_addrole
master..sp_fullText_Table
master..sp_grantdbaccess

I will read the article.
Thanks

> Terry,
> How did you "rebuild" SQL on the new machine? Did you install it from the
[quoted text clipped - 41 lines]
> > Thanks
> > Terry

Reply to this Message

John Kane - 18 Aug 2005 06:00 GMT

You're welcome, Terry,
What you may be able to do is to use "ProcSyst.SQL" (in the \MSSQL\Install\
folder) and search for each of the below system stored procs and copy out
the code that creates these systems stored procs and create them
individually.

A service pack does not re-install these system stored procs, at best they
may update them, but unless there is a fix for these procs, most SP's don't
re-create them. If this fails resolve this problem, you may have to remove &
re-install SQL Server and be sure to be logged on as Admin or as a member of
the machine's Administrators group.

Hope that helps!
John

Signature

SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/

> John:
> Thanks
[quoted text clipped - 60 lines]
>> > Thanks
>> > Terry

Reply to this Message

Hilary Cotter - 17 Aug 2005 16:12 GMT

There have been cases where for some reason the service pack is incompletely
applied, but the upgrade process appears to complete successfully.

I would advise you to reapply the SP and watch to see if this proc is now
marked as a system object. This should indicate successful application.

Signature

Hilary Cotter
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

> Hello:
> running SQL2000 SP3 (8.00.818)
[quoted text clipped - 20 lines]
> Thanks
> Terry

Reply to this Message