MS SQL Server 2005 (KB 921896)

I'm having a problem with authentication.

Can someone please tell me what DEFAULT username/password combination MS SQL
Server 2005 uses? This way I can create the Username and Password, add the
user to the appropriate group and set this as the default within SQL Server
2005 Server Configuration Panel.

I have full control of SQL Server 2005 Express as far as what auth method it
will use, and creation of user/pass combinations.

I just need to know what the default is.

Even when I set to Network Service, or Local System it doesnt' work.

Someone knowing please tell me the default so I can install this damn update
already. Thanks!

--Chris

I do not have the answer, but you are not alone in having trouble with this
download. So far, the MS SQL Server 2005 has "successfully" installed itself
on my machine three times. This is the first really serious problem I have
seen with the Microsoft Update process (other than a few really strange
optional downloads).
--
FWhiting



"ChrisMan" wrote:

> I'm having a problem with authentication.
>
> Can someone please tell me what DEFAULT username/password combination MS SQL
> Server 2005 uses? This way I can create the Username and Password, add the
> user to the appropriate group and set this as the default within SQL Server
> 2005 Server Configuration Panel.
>
> I have full control of SQL Server 2005 Express as far as what auth method it
> will use, and creation of user/pass combinations.
>
> I just need to know what the default is.
>
> Even when I set to Network Service, or Local System it doesnt' work.
>
> Someone knowing please tell me the default so I can install this damn update
> already. Thanks!
>
> --Chris

Please post the contents of summary.txt file located at
%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\Log\hotfix

Thanks,
Peter Saddow

--
This posting is provided "AS IS" with no warranties, and confers no rights.



"FWhiting" <> wrote in message
news:1B20B42B-7270-4F96-8426-...
>I do not have the answer, but you are not alone in having trouble with this
> download. So far, the MS SQL Server 2005 has "successfully" installed
> itself
> on my machine three times. This is the first really serious problem I
> have
> seen with the Microsoft Update process (other than a few really strange
> optional downloads).
> --
> FWhiting
>
>
>
> "ChrisMan" wrote:
>
>> I'm having a problem with authentication.
>>
>> Can someone please tell me what DEFAULT username/password combination MS
>> SQL
>> Server 2005 uses? This way I can create the Username and Password, add
>> the
>> user to the appropriate group and set this as the default within SQL
>> Server
>> 2005 Server Configuration Panel.
>>
>> I have full control of SQL Server 2005 Express as far as what auth method
>> it
>> will use, and creation of user/pass combinations.
>>
>> I just need to know what the default is.
>>
>> Even when I set to Network Service, or Local System it doesnt' work.
>>
>> Someone knowing please tell me the default so I can install this damn
>> update
>> already. Thanks!
>>
>> --Chris

I have had to remove MS SQL Server on the XP side of this machine for the
moment. (at least that stopped the repeat installs). Could this have
anything to do with the repeat message from One Care that a critical download
was required again and again? Anyway, here is the latest file (there are a
number of them):

03/20/2007 10:17:57.046
================================================== ==============================
03/20/2007 10:17:57.281 Hotfix package launched
03/20/2007 10:17:57.328 Registry: Opened registry key
"SOFTWARE\Microsoft\Windows\CurrentVersion"
03/20/2007 10:17:57.359 Registry: Read registry key value "CommonFilesDir",
string value = C:\Program Files\Common Files
03/20/2007 10:17:57.375 Registry: Opened registry key
"SOFTWARE\Microsoft\Windows\CurrentVersion"
03/20/2007 10:17:57.390 Registry: Read registry key value "ProgramFilesDir",
string value = C:\Program Files
03/20/2007 10:17:57.406 Local Computer:
03/20/2007 10:17:57.437 Target Details: HHFMAIN
03/20/2007 10:17:57.468 commonfilesdir = C:\Program Files\Common Files
03/20/2007 10:17:57.500 lcidsupportdir = d:\64b4b83cf1d249093838e88c77\1033
03/20/2007 10:17:57.515 programfilesdir = C:\Program Files
03/20/2007 10:17:57.531 programfilesdir_wow = C:\Program Files
03/20/2007 10:17:57.531 supportdir = d:\64b4b83cf1d249093838e88c77
03/20/2007 10:17:57.593 supportdirlocal = d:\64b4b83cf1d249093838e88c77
03/20/2007 10:17:57.640 windir = C:\WINDOWS
03/20/2007 10:17:57.671 winsysdir = C:\WINDOWS\system32
03/20/2007 10:17:57.718 winsysdir_wow = C:\WINDOWS\SysWOW64
03/20/2007 10:17:57.765
03/20/2007 10:17:57.828 Enumerating applicable products for this patch
03/20/2007 10:17:57.875 Found SQL 2005 Express product definition
03/20/2007 10:17:58.812 Enumeration: Determining QFE level for product
instance SQLEXPRESS
03/20/2007 10:17:58.843 Enumeration: Associated hotfix build information not
found for the following file: C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
03/20/2007 10:17:58.875 Enumeration: Found following QFE level for product
instance SQLEXPRESS: 1399
03/20/2007 10:17:58.906 Enumeration: Determining GDR branching Hotfix for
product instance SQLEXPRESS
03/20/2007 10:17:58.937 Enumeration: Associated hotfix build information not
found for the following file: C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
03/20/2007 10:17:58.968 Enumeration: No GDR branch Hotfix found for product
instance SQLEXPRESS
03/20/2007 10:17:59.000 Enumeration: Determining QFE level for product
instance
03/20/2007 10:17:59.015 Enumeration: Cannot find following key file for
product instance : C:\Program Files\Microsoft SQL
Server\90\Tools\\Binn\SQLServr.exe
03/20/2007 10:17:59.046 Enumeration: Determining GDR branching Hotfix for
product instance
03/20/2007 10:17:59.078 Enumeration: Cannot find following key file for
product instance : C:\Program Files\Microsoft SQL
Server\90\Tools\\Binn\SQLServr.exe
03/20/2007 10:17:59.093 Registry: Opened registry key
"SOFTWARE\Microsoft\Windows\CurrentVersion"
03/20/2007 10:17:59.125 Registry: Read registry key value "CommonFilesDir",
string value = C:\Program Files\Common Files
03/20/2007 10:17:59.156 Registry: Opened registry key
"SOFTWARE\Microsoft\Windows\CurrentVersion"
03/20/2007 10:17:59.187 Registry: Read registry key value "ProgramFilesDir",
string value = C:\Program Files
03/20/2007 10:17:59.203 Product discovery completed during the install
process for SQLEXPRESS
03/20/2007 10:17:59.218 SP Level check completed during the install process
for SQLEXPRESS
03/20/2007 10:17:59.234 Product language check completed during the install
process for SQLEXPRESS
03/20/2007 10:17:59.265 Product version check completed during the install
process for SQLEXPRESS
03/20/2007 10:17:59.281 Registry: Opened registry key
"SOFTWARE\Microsoft\Windows\CurrentVersion"
03/20/2007 10:17:59.312 Registry: Read registry key value "CommonFilesDir",
string value = C:\Program Files\Common Files
03/20/2007 10:17:59.343 Registry: Opened registry key
"SOFTWARE\Microsoft\Windows\CurrentVersion"
03/20/2007 10:17:59.375 Registry: Read registry key value "ProgramFilesDir",
string value = C:\Program Files
03/20/2007 10:17:59.437 Product discovery completed during the install
process for SQLExpress
03/20/2007 10:17:59.484 SP Level check completed during the install process
for SQLExpress
03/20/2007 10:17:59.515 Product language check completed during the install
process for SQLExpress
03/20/2007 10:17:59.546 Product version check completed during the install
process for SQLExpress
03/20/2007 10:17:59.609 Command-line instance name check completed during
the install process
03/20/2007 10:17:59.625 SKU check completed during the install process for
SQLEXPRESS
03/20/2007 10:17:59.640 SKU check completed during the install process for
SQLExpress
03/20/2007 10:17:59.656 Baseline build check completed during the
installation process for SQLEXPRESS
03/20/2007 10:17:59.671 Baseline build check completed during the
installation process for SQLExpress
03/20/2007 10:17:59.703 Baseline build check completed during the install
process
03/20/2007 10:17:59.765 Product Enumeration Results:
03/20/2007 10:17:59.828 INF File Name:
d:\64b4b83cf1d249093838e88c77\HotFixExpress.inf
03/20/2007 10:17:59.859 baselinebuild = 1399
03/20/2007 10:17:59.875 build = 3042
03/20/2007 10:17:59.906 description = Express Database Services
03/20/2007 10:17:59.937 details = Service Pack for the SQL Server database
engine, and the tools for managing relational and XML data, Replication, and
Full-Text Search.
03/20/2007 10:17:59.968 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL
Server\90\Setup Bootstrap\LOG\Hotfix
03/20/2007 10:18:00.000 kbarticle = KB921896
03/20/2007 10:18:00.015 kbarticlehyperlink =
http://support.microsoft.com/?kbid=921896
03/20/2007 10:18:00.015 lcid = 1033
03/20/2007 10:18:00.031 legalproductname = SQL Server Express Database
Services 2005
03/20/2007 10:18:00.078 machinetype = x86
03/20/2007 10:18:00.109 package = HotFixExpress
03/20/2007 10:18:00.125 packagetype = SP
03/20/2007 10:18:00.125 productname = SQL9Express
03/20/2007 10:18:00.140 relatedlinks =
<LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
03/20/2007 10:18:00.156 servicepackname = Microsoft SQL Server 2005
Service Pack 2 Setup
03/20/2007 10:18:00.171 sku = EXPRESS
03/20/2007 10:18:00.187 splevel = 2
03/20/2007 10:18:00.203 sqlutility = sqlcmd.exe
03/20/2007 10:18:00.234 supportdir = d:\64b4b83cf1d249093838e88c77
03/20/2007 10:18:00.250 validateauthentication = true
03/20/2007 10:18:00.250 version = 9
03/20/2007 10:18:00.281
03/20/2007 10:18:00.281 File Group Details: EXE
03/20/2007 10:18:00.296 parameters = INSTANCENAME=<NAME>
03/20/2007 10:18:00.312 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
03/20/2007 10:18:00.328 File Details: SQLEXPR.EXE
03/20/2007 10:18:00.343
03/20/2007 10:18:00.359 Instance Details: SQLEXPRESS
03/20/2007 10:18:00.375 clustername =
03/20/2007 10:18:00.390 fullversion = 2005.090.1399.00
03/20/2007 10:18:00.421 hiveregpath = Software\Microsoft\Microsoft SQL
Server\MSSQL.1
03/20/2007 10:18:00.421 id = MSSQL.1
03/20/2007 10:18:00.468 installsqldatadir = C:\Program Files\Microsoft
SQL Server\MSSQL.1\MSSQL
03/20/2007 10:18:00.484 installsqldir = C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL
03/20/2007 10:18:00.500 lcid = 1033
03/20/2007 10:18:00.531 name = SQLEXPRESS
03/20/2007 10:18:00.562 productcode =
{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
03/20/2007 10:18:00.578 qfelevel = 1399
03/20/2007 10:18:00.609 servicename = MSSQL$SQLEXPRESS
03/20/2007 10:18:00.640 sku = EXPRESS
03/20/2007 10:18:00.671 sp = 0
03/20/2007 10:18:00.687 type = SQL Server Standalone Product
03/20/2007 10:18:00.765 vermajbld = 1399
03/20/2007 10:18:00.828 version = 9
03/20/2007 10:18:00.843
03/20/2007 10:18:00.875 Instance Details: SQLExpress
03/20/2007 10:18:00.937 clustername =
03/20/2007 10:18:00.968 expressrsstandalone = true
03/20/2007 10:18:01.015 hiveregpath = Software\Microsoft\Microsoft SQL
Server\90\Tools
03/20/2007 10:18:01.031 id =
03/20/2007 10:18:01.046 installsqldatadir =
03/20/2007 10:18:01.062 installsqldir = C:\Program Files\Microsoft SQL
Server\90\Tools\
03/20/2007 10:18:01.062 lcid = 1033
03/20/2007 10:18:01.109 name =
03/20/2007 10:18:01.125 productcode =
{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
03/20/2007 10:18:01.156 servicename = MSSQL$
03/20/2007 10:18:01.187 sku = EXPRESS
03/20/2007 10:18:01.218 sp = 0
03/20/2007 10:18:01.234 type = Tools Only
03/20/2007 10:18:01.250 vermajbld = 1399
03/20/2007 10:18:01.296 version = 9
03/20/2007 10:18:01.328
03/20/2007 10:18:01.375 Authenticating user using Windows Authentication
03/20/2007 10:18:01.406 SQL Service MSSQL$SQLEXPRESS was previously running,
ready for authentication
03/20/2007 10:18:02.531 Registry: Opened registry key
"System\CurrentControlSet\Control\Session Manager"
03/20/2007 10:18:02.578 Registry: Cannot read registry key value
"PendingFileRenameOperations"
03/20/2007 10:18:02.593 Locked file: Checking for locked files
03/20/2007 10:18:02.625 Attempting to pause the 32 bit ngen queue
03/20/2007 10:18:03.578 Installing product: SQL9Express
03/20/2007 10:18:03.593 Installing instance: SQLEXPRESS
03/20/2007 10:18:03.609 Installing target: HHFMAIN
03/20/2007 10:18:03.625 Validating database connections using Windows
Authentication
03/20/2007 10:18:03.843 Pre-script database connection check was successful
- proceeding with script execution
03/20/2007 10:18:04.500 Received list of RANU pid's
03/20/2007 10:18:04.515 Validating database connections using Windows
Authentication
03/20/2007 10:18:04.734 Pre-script database connection check was successful
- proceeding with script execution
03/20/2007 10:18:04.750 Stopping service: MSSQL$SQLEXPRESS
03/20/2007 10:18:06.765 Stopped service: MSSQL$SQLEXPRESS
03/20/2007 10:18:06.781 Installing file: SQLEXPR.EXE
03/20/2007 10:18:06.781 Copy Engine: Creating MSI install log file at:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR.EXE
03/20/2007 10:18:06.796 Registry: Opened registry key
"Software\Policies\Microsoft\Windows\Installer "
03/20/2007 10:18:06.812 Registry: Cannot read registry key value "Debug"
03/20/2007 10:18:39.156 EXE returned 0: The action completed successfully.
03/20/2007 10:18:39.171 Registry: Opened registry key
"Software\Policies\Microsoft\Windows\Installer "
03/20/2007 10:18:39.187 Registry: Cannot read registry key value "Debug"
03/20/2007 10:18:39.203 Copy Engine: Installed file:
d:\64b4b83cf1d249093838e88c77\HotFixExpress\Files\ SQLEXPR.EXE
03/20/2007 10:18:39.203 Restarting SQL Service MSSQL$SQLEXPRESS since it was
previously running
03/20/2007 10:18:39.218 Starting service: MSSQL$SQLEXPRESS
03/20/2007 10:18:42.359 Started service: MSSQL$SQLEXPRESS
03/20/2007 10:18:42.359 Installed target: HHFMAIN
03/20/2007 10:18:43.046 Installed instance: SQLEXPRESS
03/20/2007 10:18:43.062 Installed product: SQL9Express
03/20/2007 10:18:43.078 Installing product: SQL9Express
03/20/2007 10:18:43.093 Installing instance: SQLExpress
03/20/2007 10:18:43.093 Installing target: HHFMAIN
03/20/2007 10:18:43.109 Installing file: SQLEXPR.EXE
03/20/2007 10:18:43.125 Copy Engine: Creating MSI install log file at:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR.EXE
03/20/2007 10:18:43.140 Registry: Opened registry key
"Software\Policies\Microsoft\Windows\Installer "
03/20/2007 10:18:43.156 Registry: Cannot read registry key value "Debug"
03/20/2007 10:19:09.640 EXE returned 0: The action completed successfully.
03/20/2007 10:19:09.656 Registry: Opened registry key
"Software\Policies\Microsoft\Windows\Installer "
03/20/2007 10:19:09.671 Registry: Cannot read registry key value "Debug"
03/20/2007 10:19:09.687 Copy Engine: Installed file:
d:\64b4b83cf1d249093838e88c77\HotFixExpress\Files\ SQLEXPR.EXE
03/20/2007 10:19:09.703 Installed target: HHFMAIN
03/20/2007 10:19:10.390 Installed instance: SQLExpress
03/20/2007 10:19:10.406 Installed product: SQL9Express
03/20/2007 10:19:10.406 Hotfix package completed
03/20/2007 10:19:10.421 Attempting to continue the 32 bit ngen queue
03/20/2007 10:19:11.515 Hotfix package closed
--
FWhiting



"PeterSadd" wrote:

> Please post the contents of summary.txt file located at
> %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\Log\hotfix
>
> Thanks,
> Peter Saddow
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "FWhiting" <> wrote in message
> news:1B20B42B-7270-4F96-8426-...
> >I do not have the answer, but you are not alone in having trouble with this
> > download. So far, the MS SQL Server 2005 has "successfully" installed
> > itself
> > on my machine three times. This is the first really serious problem I
> > have
> > seen with the Microsoft Update process (other than a few really strange
> > optional downloads).
> > --
> > FWhiting
> >
> >
> >
> > "ChrisMan" wrote:
> >
> >> I'm having a problem with authentication.
> >>
> >> Can someone please tell me what DEFAULT username/password combination MS
> >> SQL
> >> Server 2005 uses? This way I can create the Username and Password, add
> >> the
> >> user to the appropriate group and set this as the default within SQL
> >> Server
> >> 2005 Server Configuration Panel.
> >>
> >> I have full control of SQL Server 2005 Express as far as what auth method
> >> it
> >> will use, and creation of user/pass combinations.
> >>
> >> I just need to know what the default is.
> >>
> >> Even when I set to Network Service, or Local System it doesnt' work.
> >>
> >> Someone knowing please tell me the default so I can install this damn
> >> update
> >> already. Thanks!
> >>
> >> --Chris
>
>

"FWhiting" <> wrote in message
news:65408F02-09DB-4E95-A48D-...
>I have had to remove MS SQL Server on the XP side of this machine for the
> moment. (at least that stopped the repeat installs).


Did you try just declining the update?


> Could this have
> anything to do with the repeat message from One Care that a critical download
> was required again and again? Anyway, here is the latest file (there are a
> number of them):
....


I don't think that this helps. If the update is being repeatedly reinstalled
you need to get a diagnostic which shows why. E.g. it should show you
what modules are being updated and why. It would also show you what
registry items were being checked and what their values were.
Then you would be able to check on why those modules were not being
replaced or why the registry items were not being updated, etc.

I don't have any trust that the provided diagnostics provide that kind of
necessary detail. E.g. I think that they are at best adequate for someone
who has access to internal descriptions of how the update is supposed to work
and hence the traces that we see are only very rough outlines of the path
which has been taken through the update. E.g., the details that we would need
to know what was going on could have been omitted because they could be
implied by checkpoint information (such as line numbers in .inf files, etc.)

Instead, what I recommend users try in these circumstances is:
1. activate maximum logging
2. trace the update with ProcMon

Maximum logging depends on what the update documents and how it is constructed. E.g. if this is being distributed as an .msi
file you could
perhaps use the msiexec /? command to see clues that its /L*vx switch
could do that. Etc.

ProcMon would show you all registry and file accesses made by the update.
In particular, it would show you the writes of each diagnostics file's records
interleaved and preceded by the registry and file accesses which related
to the information being logged.


HTH

Robert Aldwinckle
---

Please post the contents of summary.txt file located at
%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\Log\hotfix so I can
see what is installed and why the update is failing

Thanks,
Peter Saddow - Microsoft

"Robert Aldwinckle" <> wrote in message
news:...
> "FWhiting" <> wrote in message
> news:65408F02-09DB-4E95-A48D-...
>>I have had to remove MS SQL Server on the XP side of this machine for the
>> moment. (at least that stopped the repeat installs).
>
>
> Did you try just declining the update?
>
>
>> Could this have
>> anything to do with the repeat message from One Care that a critical
>> download
>> was required again and again? Anyway, here is the latest file (there
>> are a
>> number of them):
> ...
>
>
> I don't think that this helps. If the update is being repeatedly
> reinstalled
> you need to get a diagnostic which shows why. E.g. it should show you
> what modules are being updated and why. It would also show you what
> registry items were being checked and what their values were.
> Then you would be able to check on why those modules were not being
> replaced or why the registry items were not being updated, etc.
>
> I don't have any trust that the provided diagnostics provide that kind of
> necessary detail. E.g. I think that they are at best adequate for
> someone
> who has access to internal descriptions of how the update is supposed to
> work
> and hence the traces that we see are only very rough outlines of the path
> which has been taken through the update. E.g., the details that we would
> need
> to know what was going on could have been omitted because they could be
> implied by checkpoint information (such as line numbers in .inf files,
> etc.)
>
> Instead, what I recommend users try in these circumstances is:
> 1. activate maximum logging
> 2. trace the update with ProcMon
>
> Maximum logging depends on what the update documents and how it is
> constructed. E.g. if this is being distributed as an .msi file you
> could
> perhaps use the msiexec /? command to see clues that its /L*vx
> switch
> could do that. Etc.
>
> ProcMon would show you all registry and file accesses made by the update.
> In particular, it would show you the writes of each diagnostics file's
> records
> interleaved and preceded by the registry and file accesses which related
> to the information being logged.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>

Download the update and install it manually. You WILL need the original
install CD.

--
tbark


"ChrisMan" wrote:

> I'm having a problem with authentication.
>
> Can someone please tell me what DEFAULT username/password combination MS SQL
> Server 2005 uses? This way I can create the Username and Password, add the
> user to the appropriate group and set this as the default within SQL Server
> 2005 Server Configuration Panel.
>
> I have full control of SQL Server 2005 Express as far as what auth method it
> will use, and creation of user/pass combinations.
>
> I just need to know what the default is.
>
> Even when I set to Network Service, or Local System it doesnt' work.
>
> Someone knowing please tell me the default so I can install this damn update
> already. Thanks!
>
> --Chris