SQL 2000 Security Fix KB948110

  • maes.john

    SSC Rookie

    Points: 41

    When I try to install the new security fix (KB948110) I'm getting one or more sql server instances could not verify your account information. I've tried using NT authentication and using my 'SA" account and I get the same from both. I have used the sa account in query analyzer so I know the password is good. Any help would be great. Thanks John

  • Leeland

    SSCrazy Eights

    Points: 8957

    getting the same exact senario

  • Gail Shaw

    SSC Guru

    Points: 1004454

    A quick guess - have you removed Builtin\Administrators from the allowed logins? If so, put it back, make it sysadmin and try the patch again.

    No promises. That security patch breaks in a thousand ways and has twice as many fixes.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Leeland

    SSCrazy Eights

    Points: 8957

    GilaMonster (7/31/2008)


    A quick guess - have you removed Builtin\Administrators from the allowed logins? If so, put it back, make it sysadmin and try the patch again.

    No promises. That security patch breaks in a thousand ways and has twice as many fixes.

    Hi Gila,

    Well here is the funny thing...I haven't removed anything on this particular server...the BuiltIn\Administrators is still present...

    And I had read a lot of posts regarding that very question.

    At first I didn't give it much thought and attempted to re-run the patch...it failed.

    I know the sa account for the server so I decided to download the patch and attempt to install manually.

    When I ran the patch and it asks for verification (Windows vs. SQL)

    I entered the sa password I know works as I tested it in Q.A. and it gives an error saying something like "one or more instances cannot verify your account..."

    SO...it basically only allows for Windows auth...

    The account that I logged into the server initally wasn't set up as a sysadmin so I logged out and relogged in with the account that is running the services which IS a sysadmin on the server...

    Re-ran the patch, and used Windows Auth...

    Gets to the point in the patch execution where it says "spawning instances" and it hangs and does nothing, no progress...

    Then fails with some cryptic error message and requires a reboot...

    For this particular server I am on MSSQL 2000 - 8.00.2039

  • Kathy.Huang

    SSC Enthusiast

    Points: 144

    I got 'one or more server instances could not verify your account information' when I tried to install the new fix (KB948111) couple days ago. I chose SQL Server Authentication (actually we use mixed mode authentication) and provided the right password for SA since I just changed sa password and tested it on osql successfully.

    I'm still troubleshooting how to fix this problem to make this new fix installation finish smoothly. Anyone can help?

  • Kathy.Huang

    SSC Enthusiast

    Points: 144

    continue from previous post regarding 'one or more SQL Server instances could not verify your account'..

    Btw, my Builtln\Administrators is still present...

    Should I try to install as Window Authentication although we actually use Mixed mode Authentication ? Will it reject SQL Server logins if I install KB948111 as Window Authentication?

    Thanks in advance if someone can help!

    Kathy

  • Mr. SQL Guy

    Mr or Mrs. 500

    Points: 517

    Hey all,

    I know this is an old topic, but I just spent several hours solving this exact problem. I discovered that the Client Network Utility for SQL Server had incorrect aliases set up for it; deleting them fixed it for me. I'm using SQL Server 2000 SP4, and the particular patch for me was KB960082.

    Here's what I did to fix it:

    1. On your SQL Server, open up the Client Network Utility (Start-->Programs-->Microsoft SQL Server-->Client Network Utility)

    2. Click the "Alias" tab.

    3. If you have any aliases defined, delete them.

    Hopefully someone else will find this to be useful.

    --Mr. SQL Guy

  • Brian-1079680

    SSC Journeyman

    Points: 77

    I'm having the same issue for KB960083. I checked the client network utility and I did not have any alias' listed. So if anyone has any other helpful ideas as to how to bypass the common error we're having, please share! 🙂 Thanks!

  • Mr. SQL Guy

    Mr or Mrs. 500

    Points: 517

    Well, after reading this thread it looks like you also need to make sure that the "BUILTIN\Administrators" group has a login to SQL Server and make sure it is included in the sysadmin role. I guess this assumes you need to configure your SQL Server for mixed authentication mode.

    I double checked both SQL Server network utilities and this is the way mine are set up:

    SQL Server Client Network Utility:

    --Enabled protocols: TCP/IP, Named Pipes (in that order)

    --Alias tab: (none defined)

    SQL Server Network Utility:

    Enabled protocols: Named Pipes, TCP/IP

    --Mr. SQL Guy

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply