Full Text Repair

We had a customer request a full text installation after
the application of SP4 and the slammer hotfix. It throws
an error that refers to a re-installation of SP4, which
will not work with any hot fixes applied after the fact.
Does anyone have a different route to follow that
uninstall the hotfix, then reapply the SP4, and then
reapply the hot fix?
Thanks in advance for any information.
Emil
what is the exact error message you are getting?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Emil" <emilcaruthers@.hotmail.com> wrote in message
news:698301c4758b$4e941cd0$a301280a@.phx.gbl...
> We had a customer request a full text installation after
> the application of SP4 and the slammer hotfix. It throws
> an error that refers to a re-installation of SP4, which
> will not work with any hot fixes applied after the fact.
> Does anyone have a different route to follow that
> uninstall the hotfix, then reapply the SP4, and then
> reapply the hot fix?
> Thanks in advance for any information.
> Emil
|||use culture;
SELECT * from FREETEXTTABLE(tblMasterEvents,*,'art');
Get this:
Search on full-text catalog 'culture' for database ID 41, table ID
1381579960 with search condition 'art' failed with unknown result (565f9c4).
The name of the database is not relevant, as all return the error.
Thanks for looking.
Emil Caruthers
"Hilary Cotter" wrote:

> what is the exact error message you are getting?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Emil" <emilcaruthers@.hotmail.com> wrote in message
> news:698301c4758b$4e941cd0$a301280a@.phx.gbl...
>
>
|||Emil,
Since your customer has already applied SP4, I'm assuming that this is a SQL
Server 7.0 installation as there currently is no publicly released SP4 for
SQL Sever 2000.
For SQL Server 7.0 installations, there is a registry key and value that you
can change in order to successfully re-install SP4 after applying a post-SP4
hotfix. Specifically, registry key called
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQL Server\Current Version\
"CSDVersion"
It will contain your hotfix build version number such that 7.00.xxx is the
build number. Record this value and then change it to the SP4 build value of
7.00.1063 and then re-install SP4. If successful, then re-install your
hotfix and confirm that this registry key value has changed back to your
recorded hotfix build number.
BTW, the hex value in the unknown result below is a 'garbage' value as this
is a bug with SQL Server 7.0 FTS and is fixed by applying (or re-applying)
the latest service pack.
Regards,
John
"Emil" <Emil@.discussions.microsoft.com> wrote in message
news:76173F35-121A-4ED7-852F-3328824CEC69@.microsoft.com...
> use culture;
> SELECT * from FREETEXTTABLE(tblMasterEvents,*,'art');
> Get this:
> Search on full-text catalog 'culture' for database ID 41, table ID
> 1381579960 with search condition 'art' failed with unknown result
(565f9c4).[vbcol=seagreen]
>
> The name of the database is not relevant, as all return the error.
> Thanks for looking.
> --
> Emil Caruthers
>
> "Hilary Cotter" wrote:
|||Thank you kindly, and I will try this.
Emil
Emil Caruthers
"John Kane" wrote:

> Emil,
> Since your customer has already applied SP4, I'm assuming that this is a SQL
> Server 7.0 installation as there currently is no publicly released SP4 for
> SQL Sever 2000.
> For SQL Server 7.0 installations, there is a registry key and value that you
> can change in order to successfully re-install SP4 after applying a post-SP4
> hotfix. Specifically, registry key called
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQL Server\Current Version\
> "CSDVersion"
> It will contain your hotfix build version number such that 7.00.xxx is the
> build number. Record this value and then change it to the SP4 build value of
> 7.00.1063 and then re-install SP4. If successful, then re-install your
> hotfix and confirm that this registry key value has changed back to your
> recorded hotfix build number.
> BTW, the hex value in the unknown result below is a 'garbage' value as this
> is a bug with SQL Server 7.0 FTS and is fixed by applying (or re-applying)
> the latest service pack.
> Regards,
> John
>
> "Emil" <Emil@.discussions.microsoft.com> wrote in message
> news:76173F35-121A-4ED7-852F-3328824CEC69@.microsoft.com...
> (565f9c4).
>
>