SQL Server 2005 Express Ed (KB 921896): errorcode 0x65B

Hi,

Can anyone help? The automatic update of my MS SQL Server 2005 Express
Edition (KB 921896) keeps on failing, giving errorcode 0x65B.

The log file summary.txt at C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix looks like (in double Dutch):

Time: 03/17/2007 16:15:56.984
KB Number: KB921896
Machine: ABC
OS Version: Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Package Language: 1043 (NLA)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
/quiet
/allinstances
Cluster Installation: No

************************************************** ********************************
Prerequisites Check & Status
SQLSupport: Passed

************************************************** ********************************
Products Detected Language Level Patch Level
Platform Edition
Express Database Services (SQLEXPRESS) NLD SP1 2005.090.2047.00
x86 EXPRESS
Express Database Services (SQLExpress) NLD SP2
x86 EXPRESS

************************************************** ********************************
Products Disqualified & Reason
Product Reason

************************************************** ********************************
Processes Locking Files
Process Name Feature Type User Name
PID

************************************************** ********************************
Product Installation Status
Product : Express Database Services (SQLEXPRESS)
Product Version (Previous): 2047
Product Version (Final) :
Status : Fout
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_SharedTools
Error Number : 1627
Error Description : Kan het MSI-bestand van Windows Installer niet
installere
----------------------------------------------------------------------------------
Product : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final) : 3042
Status : Voltooid
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE
SQL Express Features : Client_Components,Connectivity,SDK
Error Number : 0
Error Description
----------------------------------------------------------------------------------

************************************************** ********************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 1627

In the "C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE", there
should be one of more log files. Can you search these log files for the
"value 3". If you find "value 3", please copy/paste the 20 lines above to
the newsgroup.

Thanks,
Peter Saddow - Microsoft

"JoVL" <> wrote in message
news:B2EA08AB-E0C3-435E-BAB4-...
> Hi,
>
> Can anyone help? The automatic update of my MS SQL Server 2005 Express
> Edition (KB 921896) keeps on failing, giving errorcode 0x65B.
>
> The log file summary.txt at C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix looks like (in double Dutch):
>
> Time: 03/17/2007 16:15:56.984
> KB Number: KB921896
> Machine: ABC
> OS Version: Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
> Package Language: 1043 (NLA)
> Package Platform: x86
> Package SP Level: 2
> Package Version: 3042
> Command-line parameters specified:
> /quiet
> /allinstances
> Cluster Installation: No
>
> ************************************************** ********************************
> Prerequisites Check & Status
> SQLSupport: Passed
>
> ************************************************** ********************************
> Products Detected Language Level Patch Level
> Platform Edition
> Express Database Services (SQLEXPRESS) NLD SP1
> 2005.090.2047.00
> x86 EXPRESS
> Express Database Services (SQLExpress) NLD SP2
> x86 EXPRESS
>
> ************************************************** ********************************
> Products Disqualified & Reason
> Product Reason
>
> ************************************************** ********************************
> Processes Locking Files
> Process Name Feature Type User Name
> PID
>
> ************************************************** ********************************
> Product Installation Status
> Product : Express Database Services (SQLEXPRESS)
> Product Version (Previous): 2047
> Product Version (Final) :
> Status : Fout
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE
> SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_SharedTools
> Error Number : 1627
> Error Description : Kan het MSI-bestand van Windows Installer niet
> installeren
> ----------------------------------------------------------------------------------
> Product : Express Database Services (SQLExpress)
> Product Version (Previous):
> Product Version (Final) : 3042
> Status : Voltooid
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE
> SQL Express Features : Client_Components,Connectivity,SDK
> Error Number : 0
> Error Description :
> ----------------------------------------------------------------------------------
>
> ************************************************** ********************************
> Summary
> One or more products failed to install, see above for details
> Exit Code Returned: 1627
>
>

Thanks for the quick response.

This excerpt comes from Hotfix.txt. I couldn't find any "value 3" in any
file in the Hotfix directory and below.

03/17/2007 18:24:56.562
================================================== ==============================
03/17/2007 18:24:56.640 Hotfix package launched
03/17/2007 18:24:56.765 Registry: Opened registry key
"SOFTWARE\Microsoft\Windows\CurrentVersion"
03/17/2007 18:24:56.765 Registry: Read registry key value "CommonFilesDir",
string value = C:\Program Files\Common Files
03/17/2007 18:24:56.843 Registry: Opened registry key
"SOFTWARE\Microsoft\Windows\CurrentVersion"
03/17/2007 18:24:56.890 Registry: Read registry key value "ProgramFilesDir",
string value = C:\Program Files
03/17/2007 18:24:56.953 Local Computer:

....

03/17/2007 18:25:02.562 Product discovery completed during the install
process for SQLExpress
03/17/2007 18:25:02.609 SP Level check completed during the install process
for SQLExpress
03/17/2007 18:25:02.671 Product language check completed during the install
process for SQLExpress
03/17/2007 18:25:02.703 Product version check completed during the install
process for SQLExpress
03/17/2007 18:25:02.750 Command-line instance name check completed during
the install process
03/17/2007 18:25:02.781 SKU check completed during the install process for
SQLEXPRESS
03/17/2007 18:25:02.812 SKU check completed during the install process for
SQLExpress
03/17/2007 18:25:02.843 Baseline build check completed during the
installation process for SQLEXPRESS
03/17/2007 18:25:02.921 Baseline build check completed during the
installation process for SQLExpress
03/17/2007 18:25:02.968 Baseline build check completed during the install
process
03/17/2007 18:25:03.015 Product Enumeration Results:

....

03/17/2007 18:25:12.093 Installing product: SQL9Express
03/17/2007 18:25:12.515 Installing instance: SQLEXPRESS
03/17/2007 18:25:12.890 Installing target: ABC
03/17/2007 18:25:12.984 Validating database connections using Windows
Authentication
03/17/2007 18:25:13.671 Pre-script database connection check was successful
- proceeding with script execution
03/17/2007 18:25:17.593 Received list of RANU pid's
03/17/2007 18:25:17.750 Validating database connections using Windows
Authentication
03/17/2007 18:25:18.171 Pre-script database connection check was successful
- proceeding with script execution
03/17/2007 18:25:18.484 Stopping service: MSSQL$SQLEXPRESS
03/17/2007 18:25:27.593 Stopped service: MSSQL$SQLEXPRESS
03/17/2007 18:25:27.656 Installing file: SQLEXPR_NLA.EXE
03/17/2007 18:25:27.703 Copy Engine: Creating MSI install log file at:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE
03/17/2007 18:25:27.750 Registry: Opened registry key
"Software\Policies\Microsoft\Windows\Installer "
03/17/2007 18:25:27.781 Registry: Cannot read registry key value "Debug"
03/17/2007 18:30:08.015 EXE returned 1627: De functie is tijdens het
uitvoeren mislukt.
03/17/2007 18:30:08.062 Registry: Opened registry key
"Software\Policies\Microsoft\Windows\Installer "
03/17/2007 18:30:08.093 Registry: Cannot read registry key value "Debug"
03/17/2007 18:30:08.140 Copy Engine: Error, unable to install EXE file:
c:\46ffd1bb38efdb67e9fe80613f9267\HotFixExpress\Fi les\SQLEXPR_NLA.EXE
03/17/2007 18:30:08.171 The following exception occurred: Kan het
MSI-bestand van Windows Installer niet installeren Date: 03/17/2007
18:30:08.171 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\copyengine.cpp Line:
1653
03/17/2007 18:30:18.281 Watson: Param1 = Unknown
03/17/2007 18:30:18.453 Watson: Param2 = 0x65b
03/17/2007 18:30:18.531 Watson: Param3 = Unknown
03/17/2007 18:30:18.578 Watson: Param4 = 0x65b
03/17/2007 18:30:18.656 Watson: Param5 = copyengine.cpp@1653
03/17/2007 18:30:18.750 Watson: Param6 = Unknown
03/17/2007 18:30:18.828 Watson: Param7 = SQL9Express
03/17/2007 18:30:18.890 Watson: Param8 = @
03/17/2007 18:30:18.937 Watson: Param9 = x86
03/17/2007 18:30:18.968 Watson: Param10 = 3042
03/17/2007 18:30:19.031 Installed product: SQL9Express
03/17/2007 18:30:19.109 Installing product: SQL9Express
03/17/2007 18:30:19.343 Installing instance: SQLExpress
03/17/2007 18:30:19.718 Installing target: ABC
03/17/2007 18:30:19.812 Installing file: SQLEXPR_NLA.EXE
03/17/2007 18:30:19.843 Copy Engine: Creating MSI install log file at:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE
03/17/2007 18:30:19.906 Registry: Opened registry key
"Software\Policies\Microsoft\Windows\Installer "
03/17/2007 18:30:20.031 Registry: Cannot read registry key value "Debug"
03/17/2007 18:32:12.171 EXE returned 0: De actie is voltooid.
03/17/2007 18:32:12.218 Registry: Opened registry key
"Software\Policies\Microsoft\Windows\Installer "
03/17/2007 18:32:12.281 Registry: Cannot read registry key value "Debug"
03/17/2007 18:32:12.375 Copy Engine: Installed file:
c:\46ffd1bb38efdb67e9fe80613f9267\HotFixExpress\Fi les\SQLEXPR_NLA.EXE
03/17/2007 18:32:12.515 Installed target: ABC
03/17/2007 18:32:16.515 Installed instance: SQLExpress
03/17/2007 18:32:16.609 Installed product: SQL9Express
03/17/2007 18:32:16.703 Hotfix package completed
03/17/2007 18:32:16.734 Attempting to continue the 32 bit ngen queue


"PeterSadd" wrote:

> In the "C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE", there
> should be one of more log files. Can you search these log files for the
> "value 3". If you find "value 3", please copy/paste the 20 lines above to
> the newsgroup.
>
> Thanks,
> Peter Saddow - Microsoft
>
> "JoVL" <> wrote in message
> news:B2EA08AB-E0C3-435E-BAB4-...
> > Hi,
> >
> > Can anyone help? The automatic update of my MS SQL Server 2005 Express
> > Edition (KB 921896) keeps on failing, giving errorcode 0x65B.
> >
> > The log file summary.txt at C:\Program Files\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Hotfix looks like (in double Dutch):
> >
> > Time: 03/17/2007 16:15:56.984
> > KB Number: KB921896
> > Machine: ABC
> > OS Version: Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
> > Package Language: 1043 (NLA)
> > Package Platform: x86
> > Package SP Level: 2
> > Package Version: 3042
> > Command-line parameters specified:
> > /quiet
> > /allinstances
> > Cluster Installation: No
> >
> > ************************************************** ********************************
> > Prerequisites Check & Status
> > SQLSupport: Passed
> >
> > ************************************************** ********************************
> > Products Detected Language Level Patch Level
> > Platform Edition
> > Express Database Services (SQLEXPRESS) NLD SP1
> > 2005.090.2047.00
> > x86 EXPRESS
> > Express Database Services (SQLExpress) NLD SP2
> > x86 EXPRESS
> >
> > ************************************************** ********************************
> > Products Disqualified & Reason
> > Product Reason
> >
> > ************************************************** ********************************
> > Processes Locking Files
> > Process Name Feature Type User Name
> > PID
> >
> > ************************************************** ********************************
> > Product Installation Status
> > Product : Express Database Services (SQLEXPRESS)
> > Product Version (Previous): 2047
> > Product Version (Final) :
> > Status : Fout
> > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE
> > SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_SharedTools
> > Error Number : 1627
> > Error Description : Kan het MSI-bestand van Windows Installer niet
> > installeren
> > ----------------------------------------------------------------------------------
> > Product : Express Database Services (SQLExpress)
> > Product Version (Previous):
> > Product Version (Final) : 3042
> > Status : Voltooid
> > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR_NLA.EXE
> > SQL Express Features : Client_Components,Connectivity,SDK
> > Error Number : 0
> > Error Description :
> > ----------------------------------------------------------------------------------
> >
> > ************************************************** ********************************
> > Summary
> > One or more products failed to install, see above for details
> > Exit Code Returned: 1627
> >
> >
>
>

"JoVL" <> wrote in message
news:07376924-20EE-4789-8A4B-
....
> This excerpt comes from Hotfix.txt.
....

> 03/17/2007 18:25:27.750 Registry: Opened registry key
> "Software\Policies\Microsoft\Windows\Installer "
> 03/17/2007 18:25:27.781 Registry: Cannot read registry key value "Debug"
> 03/17/2007 18:30:08.015 EXE returned 1627: De functie is tijdens het
> uitvoeren mislukt.


Calc confirms 0x65B == 1627

<cmd_output command="net helpmsg 1627"
Function failed during execution.
</cmd_output>

So that wasn't too informative. But perhaps the previous line is telling us
something? E.g. possible permissions problem with that key?
Try running ProcMon to find out?


Good luck

Robert Aldwinckle
---

Please copy/paste the contents of summary.txt file located in
%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\hotfix

The error you are see in the hotfix.log likely is not the problem.

Thanks,
Peter Saddow - Microsoft



"Robert Aldwinckle" <> wrote in message
news:%...
> "JoVL" <> wrote in message
> news:07376924-20EE-4789-8A4B-
> ...
>> This excerpt comes from Hotfix.txt.
> ...
>
>> 03/17/2007 18:25:27.750 Registry: Opened registry key
>> "Software\Policies\Microsoft\Windows\Installer "
>> 03/17/2007 18:25:27.781 Registry: Cannot read registry key value "Debug"
>> 03/17/2007 18:30:08.015 EXE returned 1627: De functie is tijdens het
>> uitvoeren mislukt.
>
>
> Calc confirms 0x65B == 1627
>
> <cmd_output command="net helpmsg 1627"
> Function failed during execution.
> </cmd_output>
>
> So that wasn't too informative. But perhaps the previous line is telling
> us
> something? E.g. possible permissions problem with that key?
> Try running ProcMon to find out?
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>

I'm having the same error code; here's a copy of the log file error msg...

Product Installation Status
Product : Express Database Services (GOFIGURE)
Product Version (Previous): 2047
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_S QLEXPR.EXE
SQL Express Features :
SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_Shar edTools
Error Number : 1627
Error Description : Unable to install Windows Installer MSI fil
----------------------------------------------------------------------------------

"Peter Saddow" wrote:

> Please copy/paste the contents of summary.txt file located in
> %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\hotfix
>
> The error you are see in the hotfix.log likely is not the problem.
>
> Thanks,
> Peter Saddow - Microsoft
>
>
>
> "Robert Aldwinckle" <> wrote in message
> news:%...
> > "JoVL" <> wrote in message
> > news:07376924-20EE-4789-8A4B-
> > ...
> >> This excerpt comes from Hotfix.txt.
> > ...
> >
> >> 03/17/2007 18:25:27.750 Registry: Opened registry key
> >> "Software\Policies\Microsoft\Windows\Installer "
> >> 03/17/2007 18:25:27.781 Registry: Cannot read registry key value "Debug"
> >> 03/17/2007 18:30:08.015 EXE returned 1627: De functie is tijdens het
> >> uitvoeren mislukt.
> >
> >
> > Calc confirms 0x65B == 1627
> >
> > <cmd_output command="net helpmsg 1627"
> > Function failed during execution.
> > </cmd_output>
> >
> > So that wasn't too informative. But perhaps the previous line is telling
> > us
> > something? E.g. possible permissions problem with that key?
> > Try running ProcMon to find out?
> >
> >
> > Good luck
> >
> > Robert Aldwinckle
> > ---
> >
> >
>
>
>

Me too! Same error code, possibly different message though. Excerpt from
SQL.log file:

-------------------------------------------------------
SQL service MSSQL$SQLEXPRESS started successfully waiting for SQL service to
accept client connections
SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect
sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL
Native Client][SQL Server]Changed database context to 'master'.
sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL
Native Client][SQL Server]Changed language setting to us_english.

<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (F4!0C) [07:48:18:312]: Note: 1: 2259 2: 3: 4:
<Func Name='GetFileTargetPath'>
Error Code: 0x8007065b (1627)
Windows Error Text: Function failed during execution.
Source File Name: darlib\viewinstaller.cpp
Compiler Timestamp: Wed Jun 14 16:19:22 2006
Function Name: sqls::ViewInstaller::modify
Source Line Number: 137



---- Context -----------------------------------------------


Setting status of unmanaged components and removing unmanaged resources
Failed to modify installer view
1: 2259 2: 3: 4:



Error Code: 1627
MSI (s) (F4!0C) [07:48:18:468]: Product: Microsoft SQL Server 2005 -- Error
2259. The installer has encountered an unexpected error. The error code is
2259. Database: Table(s) Update failed

Error 2259. The installer has encountered an unexpected error. The error
code is 2259. Database: Table(s) Update failed
<Failure Type='Fatal' Error='1627'>
<EndFunc Name='LaunchFunction' Return='1627' GetLastError='203'>
Action ended 07:48:18: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882 C2.
Return value 3.
Action ended 07:48:18: INSTALL. Return value 3.

-------------------------------------------------------------

Regards,

Jon.

"Peter Saddow" wrote:

> Please copy/paste the contents of summary.txt file located in
> %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\hotfix
>
> The error you are see in the hotfix.log likely is not the problem.
>
> Thanks,
> Peter Saddow - Microsoft
>
>
>
> "Robert Aldwinckle" <> wrote in message
> news:%...
> > "JoVL" <> wrote in message
> > news:07376924-20EE-4789-8A4B-
> > ...
> >> This excerpt comes from Hotfix.txt.
> > ...
> >
> >> 03/17/2007 18:25:27.750 Registry: Opened registry key
> >> "Software\Policies\Microsoft\Windows\Installer "
> >> 03/17/2007 18:25:27.781 Registry: Cannot read registry key value "Debug"
> >> 03/17/2007 18:30:08.015 EXE returned 1627: De functie is tijdens het
> >> uitvoeren mislukt.
> >
> >
> > Calc confirms 0x65B == 1627
> >
> > <cmd_output command="net helpmsg 1627"
> > Function failed during execution.
> > </cmd_output>
> >
> > So that wasn't too informative. But perhaps the previous line is telling
> > us
> > something? E.g. possible permissions problem with that key?
> > Try running ProcMon to find out?
> >
> >
> > Good luck
> >
> > Robert Aldwinckle
> > ---
> >
> >
>
>
>

Hi Peter,

I'm sorry it took that long, I've been out of town.

You're absolutely right: the information in hotfix.log makes no sense, but
summary.txt included below does!

As far as I can understand, KB921896 can't connect to my SQLEXPRESS: I have
indeed "windows authentication" turned on (as recommended) instead of "SQL
and windows authentication". I can't imagine I'm the only one in this
situation, unless it has something to do with the fact that I'm running a
Dutch version.

Regards,

Jo


Time: 04/15/2007 08:24:45.703
KB Number: KB921896
Machine: ABC
OS Version: Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Package Language: 1043 (NLA)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
/quiet
/allinstances
Cluster Installation: No

************************************************** ********************************
Prerequisites Check & Status
SQLSupport: Passed

************************************************** ********************************
Products Detected Language Level Patch Level
Platform Edition
Express Database Services (SQLEXPRESS) NLD SP1 2005.090.2047.00
x86 EXPRESS
Express Database Services (SQLExpress) NLD SP2
x86 EXPRESS

************************************************** ********************************
Products Disqualified & Reason
Product Reason
Express Database Services (SQLEXPRESS) De gebruikersverificatie is
mislukt. Controleer of het opgegeven wachtwoord correct is of controleer of
de SQL Server-sessie is ingesteld op gemengde verificatie

************************************************** ********************************
Processes Locking Files
Process Name Feature Type User Name
PID

************************************************** ********************************
Product Installation Status
Product : Express Database Services (SQLEXPRESS)
Product Version (Previous): 2047
Product Version (Final) :
Status : Niet toegepast
Log File :
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_SharedTools
Error Number : 11046
Error Description : De gebruikersverificatie is mislukt. Controleer
of het opgegeven wachtwoord correct is of controleer of de SQL Server-sessie
is ingesteld op gemengde verificati
----------------------------------------------------------------------------------
Product : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final) :
Status : Niet toegepast
Log File :
SQL Express Features : Client_Components,Connectivity,SDK
Error Number : 0
Error Description
----------------------------------------------------------------------------------

************************************************** ********************************
Summary
De gebruikersverificatie is mislukt. Controleer of het opgegeven
wachtwoord correct is of controleer of de SQL Server-sessie is ingesteld op
gemengde verificatie
Exit Code Returned: 11046




"Peter Saddow" wrote:

> Please copy/paste the contents of summary.txt file located in
> %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\hotfix
>
> The error you are see in the hotfix.log likely is not the problem.
>
> Thanks,
> Peter Saddow - Microsoft
>
>
>
> "Robert Aldwinckle" <> wrote in message
> news:%...
> > "JoVL" <> wrote in message
> > news:07376924-20EE-4789-8A4B-
> > ...
> >> This excerpt comes from Hotfix.txt.
> > ...
> >
> >> 03/17/2007 18:25:27.750 Registry: Opened registry key
> >> "Software\Policies\Microsoft\Windows\Installer "
> >> 03/17/2007 18:25:27.781 Registry: Cannot read registry key value "Debug"
> >> 03/17/2007 18:30:08.015 EXE returned 1627: De functie is tijdens het
> >> uitvoeren mislukt.
> >
> >
> > Calc confirms 0x65B == 1627
> >
> > <cmd_output command="net helpmsg 1627"
> > Function failed during execution.
> > </cmd_output>
> >
> > So that wasn't too informative. But perhaps the previous line is telling
> > us
> > something? E.g. possible permissions problem with that key?
> > Try running ProcMon to find out?
> >
> >
> > Good luck
> >
> > Robert Aldwinckle
> > ---
> >
> >
>
>
>

Peter,

Forget about my previous reply: that particular summary.txt was the 1 out of
12 exception.
From all 12 installion trials, it failed only once because of
authentication. I tried to install the update with "mixed authentication"
and it made no difference with the initial problem as stated in my first post.

Let's forget forget about this exception, and focus on my initial question,
carrying the original summary.txt.

Regards,

Jo


"JoVL" wrote:

> Hi Peter,
>
> I'm sorry it took that long, I've been out of town.
>
> You're absolutely right: the information in hotfix.log makes no sense, but
> summary.txt included below does!
>
> As far as I can understand, KB921896 can't connect to my SQLEXPRESS: I have
> indeed "windows authentication" turned on (as recommended) instead of "SQL
> and windows authentication". I can't imagine I'm the only one in this
> situation, unless it has something to do with the fact that I'm running a
> Dutch version.
>
> Regards,
>
> Jo
>
>
> Time: 04/15/2007 08:24:45.703
> KB Number: KB921896
> Machine: ABC
> OS Version: Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
> Package Language: 1043 (NLA)
> Package Platform: x86
> Package SP Level: 2
> Package Version: 3042
> Command-line parameters specified:
> /quiet
> /allinstances
> Cluster Installation: No
>
> ************************************************** ********************************
> Prerequisites Check & Status
> SQLSupport: Passed
>
> ************************************************** ********************************
> Products Detected Language Level Patch Level
> Platform Edition
> Express Database Services (SQLEXPRESS) NLD SP1 2005.090.2047.00
> x86 EXPRESS
> Express Database Services (SQLExpress) NLD SP2
> x86 EXPRESS
>
> ************************************************** ********************************
> Products Disqualified & Reason
> Product Reason
> Express Database Services (SQLEXPRESS) De gebruikersverificatie is
> mislukt. Controleer of het opgegeven wachtwoord correct is of controleer of
> de SQL Server-sessie is ingesteld op gemengde verificatie
>
> ************************************************** ********************************
> Processes Locking Files
> Process Name Feature Type User Name
> PID
>
> ************************************************** ********************************
> Product Installation Status
> Product : Express Database Services (SQLEXPRESS)
> Product Version (Previous): 2047
> Product Version (Final) :
> Status : Niet toegepast
> Log File :
> SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_SharedTools
> Error Number : 11046
> Error Description : De gebruikersverificatie is mislukt. Controleer
> of het opgegeven wachtwoord correct is of controleer of de SQL Server-sessie
> is ingesteld op gemengde verificatie
> ----------------------------------------------------------------------------------
> Product : Express Database Services (SQLExpress)
> Product Version (Previous):
> Product Version (Final) :
> Status : Niet toegepast
> Log File :
> SQL Express Features : Client_Components,Connectivity,SDK
> Error Number : 0
> Error Description :
> ----------------------------------------------------------------------------------
>
> ************************************************** ********************************
> Summary
> De gebruikersverificatie is mislukt. Controleer of het opgegeven
> wachtwoord correct is of controleer of de SQL Server-sessie is ingesteld op
> gemengde verificatie
> Exit Code Returned: 11046
>
>
>
>
> "Peter Saddow" wrote:
>
> > Please copy/paste the contents of summary.txt file located in
> > %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\hotfix
> >
> > The error you are see in the hotfix.log likely is not the problem.
> >
> > Thanks,
> > Peter Saddow - Microsoft
> >
> >
> >
> > "Robert Aldwinckle" <> wrote in message
> > news:%...
> > > "JoVL" <> wrote in message
> > > news:07376924-20EE-4789-8A4B-
> > > ...
> > >> This excerpt comes from Hotfix.txt.
> > > ...
> > >
> > >> 03/17/2007 18:25:27.750 Registry: Opened registry key
> > >> "Software\Policies\Microsoft\Windows\Installer "
> > >> 03/17/2007 18:25:27.781 Registry: Cannot read registry key value "Debug"
> > >> 03/17/2007 18:30:08.015 EXE returned 1627: De functie is tijdens het
> > >> uitvoeren mislukt.
> > >
> > >
> > > Calc confirms 0x65B == 1627
> > >
> > > <cmd_output command="net helpmsg 1627"
> > > Function failed during execution.
> > > </cmd_output>
> > >
> > > So that wasn't too informative. But perhaps the previous line is telling
> > > us
> > > something? E.g. possible permissions problem with that key?
> > > Try running ProcMon to find out?
> > >
> > >
> > > Good luck
> > >
> > > Robert Aldwinckle
> > > ---
> > >
> > >
> >
> >
> >

Peter,

That summary.txt is in my initial post, and says in essence:
"Error Number : 1627
Error Description : Can't install MSI-file from windows installer"

Regards,

Jo

"Peter Saddow" wrote:

> Please copy/paste the contents of summary.txt file located in
> %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\hotfix
>
> The error you are see in the hotfix.log likely is not the problem.
>
> Thanks,
> Peter Saddow - Microsoft
>
>
>
> "Robert Aldwinckle" <> wrote in message
> news:%...
> > "JoVL" <> wrote in message
> > news:07376924-20EE-4789-8A4B-
> > ...
> >> This excerpt comes from Hotfix.txt.
> > ...
> >
> >> 03/17/2007 18:25:27.750 Registry: Opened registry key
> >> "Software\Policies\Microsoft\Windows\Installer "
> >> 03/17/2007 18:25:27.781 Registry: Cannot read registry key value "Debug"
> >> 03/17/2007 18:30:08.015 EXE returned 1627: De functie is tijdens het
> >> uitvoeren mislukt.
> >
> >
> > Calc confirms 0x65B == 1627
> >
> > <cmd_output command="net helpmsg 1627"
> > Function failed during execution.
> > </cmd_output>
> >
> > So that wasn't too informative. But perhaps the previous line is telling
> > us
> > something? E.g. possible permissions problem with that key?
> > Try running ProcMon to find out?
> >
> >
> > Good luck
> >
> > Robert Aldwinckle
> > ---
> >
> >
>
>
>