Re: SQL Server 7: Query fails with error 7607

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Ernie Limperis (ernie_at_dnai.com)
Date: 12/13/04

  • Next message: Ernie Limperis: "RESOLVED Re: SQL Server 7: Query fails with error 7607" 
    Date: Mon, 13 Dec 2004 11:28:30 -0800

    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
    > 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
    >
    >
    >
    >
    > "Ernie Limperis" <ernie@dnai.com> wrote in message
    > news:eW4r4GM4EHA.2016@TK2MSFTNGP15.phx.gbl...
    >
    >>The @@version output is
    >>
    >>Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86)
    >>May 29 2003 15:21:25
    >>Copyright (c) 1988-2002 Microsoft Corporation
    >>Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
    >>
    >>I think this indicates we're at SP4 in the server. I don't think
    >>we've applied any hotfixes.
    >>
    >>- ernie
    >>
    >>John Kane wrote:
    >>
    >>>Ernie,
    >>>What is the full output of -- SELECT @@version As this is especially
    >>>helpful in troubleshooting this error. This is most likely a bug with
    >
    > SQL
    >
    >>>Server 7.0 and I've seen this resolved via either applying or
    >
    > re-applying
    >
    >>>the latest Service Pack. You can re-apply your existing SP level,
    >
    > assuming
    >
    >>>you have not applied a post-<your_current_SP_level> hotfix
    >>>
    >>>Note, the data in the 'unknown result' (6fe9f950) is garbage data and is
    >
    > not
    >
    >>>significant nor meaningful. Re-apply your service pack or upgrade to SP4
    >>>(the latest SP for SQL Server 7.0) and be sure you're logged on as Admin
    >
    > or
    >
    >>>as a member of the server's Admin group and if that doesn't resolve this
    >>>error, I'd recommend opening a support case with Microsoft PSS SQL
    >
    > Server
    >
    >>>support.
    >>>
    >>>Regards,
    >>>John
    >>>
    >>>
    >>>
    >>>"Ernie Limperis" <ernie@dnai.com> wrote in message
    >>>news:#Stw9dK4EHA.3416@TK2MSFTNGP09.phx.gbl...
    >>>
    >>>
    >>>>Hello. This is my first experience with full-text indexing and
    >>>
    >>>immediately
    >>>
    >>>
    >>>>I'm having problems.
    >>>>
    >>>>I set up full-text indexing on the "referenceCompany" column of table
    >>>
    >>>"Reference"
    >>>
    >>>
    >>>>and ran the population routine. All queries against this table are
    >>>
    >>>failing:
    >>>
    >>>
    >>>>----------------------
    >>>>select * from Reference where contains(referenceCompany, 'insurance')
    >>>>
    >>>>Server: Msg 7607, Level 17, State 1, Line 1
    >>>>
    >>>>Search on full-text catalog 'refCatalog' for database ID 7, table ID
    >>>
    >>>1353771880 with
    >>>
    >>>
    >>>> search condition 'insurance' failed with unknown result (6fe9f950).
    >>>>----------------------
    >>>>
    >>>>The MSSearch.log shows that the catalog was created without error. The
    >>>
    >>>properties
    >>>
    >>>
    >>>>*** for the Reference table shows that FTS is enabled on the table and
    >>>
    >>>record.
    >>>
    >>>
    >>>>I have restarted SQL Server and the MSSearch process.
    >>>>
    >>>>This is SQL-Server 7.00 in Win2K 2000 Advanced Server SP4.
    >>>>
    >>>>--
    >>>>==============================================
    >>>>Ernie Limperis home 510-525-8801
    >>>>ernie@sonicREMOVE.net
    >>>>==============================================
    >>>>
    >>>
    >>>
    >>>
    >>
    >>--
    >>==============================================
    >>Ernie Limperis home 510-525-8801
    >>ernie@sonic.net cell 510-682-6373
    >>==============================================
    >>
    >
    >
    > 

    -- 
==============================================
Ernie Limperis               home 510-525-8801
ernie@sonic.net              cell 510-682-6373
==============================================
  • Next message: Ernie Limperis: "RESOLVED Re: SQL Server 7: Query fails with error 7607"
    • Quantcast