
Signature
==============================================
Ernie Limperis home 510-525-8801
ernie@sonic.net cell 510-682-6373
==============================================
Ernie,
First of all, thank you for providing the @@version info as this is most
helpful info!
Secondly, your SQL Server 7.0 build number (7.00.1094) indicates that you're
on a post-SP4 security roll-up feature that is documented in KB article
"MS03-031: Security Patch for SQL Server 7.0 Service Pack 4" at
http://support.microsoft.com/kb/821279. SQL Server 7.0 SP4 is build
7.00.1063.
Furthermore, I've applied this post-SP4 hotfix to my SQL Server 7.0 on a
Win2K server and I tested re-applying SP4 after this security hotfix had
been applied and changed various registry keys & values and I was
un-successful in getting SP4 to install after this security hotfix has been
applied. So, re-installing SP4 in your environment will not succeed unless
you're willing and able to either remove and re-install SQL Server 7.0 or
possibly upgrade to SQL Server 2000 and I know these are difficult choices.
Another alternative and one that I'd highly recommend is to open a support
case with Microsoft's PSS SQL Server support and have them walk you through
fixing this issue. I wish I could be of more help, but with this security
post-SP4 hotfix Microsoft has rightly put in additional safeguards to ensure
that the security patch cannot be easily removed via registry key changes.
Regards,
John
> The @@version output is
>
[quoted text clipped - 62 lines]
> >>
> >>This is SQL-Server 7.00 in Win2K 2000 Advanced Server SP4.
Ernie Limperis - 13 Dec 2004 19:28 GMT
John,
Looks like I misspoke. The build number on the machine in question
is 7.00.1063. The machine with 1094 is our production box and I
have't tried running FTS on it yet (can't build the index during
business hours, and anyhow nobody got around to installing FTS on
that machine). I know it's hard to say, but do you think the issue
would go away if I install the security patch on this machine?
ohn Kane wrote:
> Ernie,
> First of all, thank you for providing the @@version info as this is most
[quoted text clipped - 107 lines]
>>>>
>>>>This is SQL-Server 7.00 in Win2K 2000 Advanced Server SP4.

Signature
==============================================
Ernie Limperis home 510-525-8801
ernie@sonic.net cell 510-682-6373
==============================================
Ernie Limperis - 13 Dec 2004 21:04 GMT
It turned out that I had to reapply SP4 once I installed FTS over
a previously installed server. Now it works fine. Thanks for
your assistance.
> John,
>
[quoted text clipped - 132 lines]
>>>>>
>>>>> This is SQL-Server 7.00 in Win2K 2000 Advanced Server SP4.

Signature
==============================================
Ernie Limperis home 510-525-8801
ernie@sonic.net cell 510-682-6373
==============================================
John Kane - 14 Dec 2004 02:39 GMT
You're welcome, Ernie,
No, I don't think that just installing the post-SP4 security hotfix roll-up
would of resolved this issue, as hotfixes are specific and this one is
specific to security issues. However, this post-SP4 security hotfix roll-up
does prevent you from re-installing SP4 once the security hotfix is
installed.
I'm glad you were able to resolve this via my original recommendation and
that I asked you what exact build you were on and you provided the info
(@@version) is most important in resolving SQL FTS issues!
Regards,
John
> It turned out that I had to reapply SP4 once I installed FTS over
> a previously installed server. Now it works fine. Thanks for
[quoted text clipped - 136 lines]
> >>>>>
> >>>>> This is SQL-Server 7.00 in Win2K 2000 Advanced Server SP4.