SQL Server 2005 SP 2 December CTP authentication fails

Hi,

if I try to install SP 2 using SQL Server authentification (sa) it fails. The following lines appear in the file "Hotfix.log":

01/03/2007 14:08:23.859 Authenticating user using SAPWD
01/03/2007 14:08:23.875 Validating database connections using Windows Authentication
01/03/2007 14:08:24.171 Pre-script database connection failed - continuing to wait for SQL service to become responsive to connection requests
... repeated 60 times ...
01/03/2007 14:13:33.625 The following exception occurred: SQL Server reagiert nicht vor der Skriptausfuhrung Date: 01/03/2007 14:13:33.609 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\instance.cpp Line: 1411

Why does it try to use Windows Authentification although I have told it to use SQL Server Authentification (Windows Authentification has been disabled in this Database Instance)

We use Windows authentication to verify the active status of the SQL server prior to running authentication checks and scripts, to help avoid failures.

Can you re-establish Windows authentication and retry applying SP2 If this works, we can log a bug for further consideration within SP2 in terms of our requirements for Windows authentication.

Samuel Lester - MSFT wrote:

How did you disable Windows Auth on the instance I'd like to try to repro this.

By using

DROP LOGIN [VORDEFINIERT\Administratoren]

(which would be something like DROP LOGIN [BUILTIN\Administrators] in the english version; BTW: the localization of these names is IMHO a very bad design idea).

Dave Young - MSFT wrote:

Can you re-establish Windows authentication and retry applying SP2 If this works, we can log a bug for further consideration within SP2 in terms of our requirements for Windows authentication.

Yes, if I recreate the login for Administrators SP2 works.

Peter Saddow MSFT wrote:

To clarify, dropping the "BUILTIN\Administrators" group does not disable Windows Authentication. This only prevents Windows admins which don't have an explicit login from connecting to SQL Server.

Well, that's exactly what I wanted to achieve. ;-)

Sorry for giving it the wrong name...

Peter Saddow MSFT wrote:

When you run SP2 with the "BUILTIN\Administrators" group removed, do you get a clear error message on the Authentication dialog within setup If not, we can look at improving the message.

After showing for approx. 5 minutes the message "Ihre Authentifizierung wird uberpruft." (Your Authentification will be validated), with no abort button or any other reaction (!), this message is displayed:

Ihre Kontoinformationen konnten nicht uberpruft werden.
Klicken Sie auf 'OK', um zum Fenster 'Authentifizierungmodus' zuruckzukehren und die Fehlerursache zu ermitteln.
Damit Setup die Anmeldeinformationen uberprufen kann, mussen die Dienste gestartet werden konnen, es muss eine Verbindung zu den Diensten hergestellt werden konnen, und Sie mussen ein SQL Server-Administrator sein.

Your login information could not be validated.
Click 'OK' to return to the dialog 'Authentification mode' and to find out the cause of the error.
For setup to check the login information, it must be able to start the services and to connect to the services and you must be a SQL Server administrator.

Peter Saddow MSFT wrote:

Otherwise, the behavior is by design as this would similiar to the error you would see if you connect using Management Studio or SQLCMD.

But it did work before (with SP 1).

So will this "newly designed behavior" be used in every upcoming service pack Then I will have to write a wrapper for it, which creates the login, executes the service pack and then drops the login again !

This is the second annoying thing about SQL 2005 (the first was that I had to write a replacement for sqlmangr.exe, which was dropped form SQL 2000 to SQL 2005).

Sorry, but I don't understand your question.

Of course I do have the "sa" SQL account. And this was all what was needed to install SP1.

But SP2 now also needs Windows authentification (see the answer by Dave Young in this thread).

Sigh...

Of course I DO select "SQL Authentication" (and enter my SA password in the edit control).

But nevertheless the service pack also tries to open a connection via Windows Authentication (see my first post), which of course fails.

Was this issue ever resolved Am facing similar issues while upgrading from MSDE to SQL Server 2005 Express edition SP2, where-in the setup does not allow me to upgrade using SA authentication (prompts me to use Windows Authentication for upgrade) and when I use Windows authentication, setup fails with an error "Could not connect using <my domain>\<User> ID".

Sahil Girotra