Wednesday, March 21, 2012
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
expand a data file by 4 GB - it does not report any error. The windows
explorer shows the new size. But the enterpise manager and sp_helpdb show the
old size and there is an entry in the SQL error log that says..
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Has any one come across this before? What is the solution?
Sounds like you have some serious issues with your disk. 27 is an OS error, "Cannot find requested
sector". Is the file compressed? If so, this isn't supported, and things like these are expected
(although I'm not sure whether this particular error message is expected). If not, I'd run a
comprehensive check at the file system/disk level.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:0AD05B12-0C6F-4A1E-9B73-C39BB1BDD360@.microsoft.com...
> Hi,
> I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
> expand a data file by 4 GB - it does not report any error. The windows
> explorer shows the new size. But the enterpise manager and sp_helpdb show the
> old size and there is an entry in the SQL error log that says..
> fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
> Has any one come across this before? What is the solution?
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
expand a data file by 4 GB - it does not report any error. The windows
explorer shows the new size. But the enterpise manager and sp_helpdb show th
e
old size and there is an entry in the SQL error log that says..
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Has any one come across this before? What is the solution?Sounds like you have some serious issues with your disk. 27 is an OS error,
"Cannot find requested
sector". Is the file compressed? If so, this isn't supported, and things lik
e these are expected
(although I'm not sure whether this particular error message is expected). I
f not, I'd run a
comprehensive check at the file system/disk level.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:0AD05B12-0C6F-4A1E-9B73-C39BB1BDD360@.microsoft.com...
> Hi,
> I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try
to
> expand a data file by 4 GB - it does not report any error. The windows
> explorer shows the new size. But the enterpise manager and sp_helpdb show
the
> old size and there is an entry in the SQL error log that says..
> fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
> Has any one come across this before? What is the solution?sql
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
expand a data file by 4 GB - it does not report any error. The windows
explorer shows the new size. But the enterpise manager and sp_helpdb show the
old size and there is an entry in the SQL error log that says..
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Has any one come across this before? What is the solution?Sounds like you have some serious issues with your disk. 27 is an OS error, "Cannot find requested
sector". Is the file compressed? If so, this isn't supported, and things like these are expected
(although I'm not sure whether this particular error message is expected). If not, I'd run a
comprehensive check at the file system/disk level.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:0AD05B12-0C6F-4A1E-9B73-C39BB1BDD360@.microsoft.com...
> Hi,
> I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
> expand a data file by 4 GB - it does not report any error. The windows
> explorer shows the new size. But the enterpise manager and sp_helpdb show the
> old size and there is an entry in the SQL error log that says..
> fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
> Has any one come across this before? What is the solution?
FCB::Open failed: Could not open device for virtual dev
I am trying to connect to one oof my databases in SQL 2000 server through ASP using similasr coode:
<% @.LANGUAGE = VBSCRIPT %>
<% Option Explicit %>
<html>
<head>
<title>testing our connection</title>
</head>
<body>
<%
Dim adOpenForwardOnly, adLockReadOnly, adCmdTable
adOpenForwardOnly = 0
adLockReadOnly = 1
adCmdTable = 2
Dim objConn, objRS
Set objConn = Server.CreateObject("ADODB.Connection")
Set objRS = Server.CreateObject("ADODB.Recordset")
' the following connection string is for connecting to a local SQL Server 2000 database
objConn.Open "Provider=SQLOLEDB.1;Persist Security Info=False;" & _
"User ID=sa;Password=tdmes102;Initial Catalog=CustomerProfile;" & _
"Data Source=dani;" & _
"Initial File Name=D:\DB\TDMECustomer_Data.MDF"
' the following connection string is for connecting to a remote SQL Server 2000 database
objRS.Open "CustomerProfile", objConn, adOpenForwardOnly, adLockReadOnly, adCmdTable
While Not objRS.EOF
Response.Write objRS("Principal") & "<BR>"
objRS.MoveNext
Wend
objRS.Close
objConn.Close
Set objRS = Nothing
Set objConn = Nothing
%>
</body>
</html>
I have tried several diferent ways and I keep getting this foollowing messages the same in the log file.
I tried relocating the database,reinstalling SQL , sp2.
HTTP error:
FCB::Open failed: Could not open device D:\DB\TDMECustomer_Data.MDF for virtual device number (VDN) 0.
SQL log file:
udopen: Operating system error 32(The process cannot access the file because it is being used by another process.) during the creation/opening of physical device D:\DB\TDMECustomer_Data.MDF.
2002-07-15 09:46:59.11 spid51 FCB::Open failed: Could not open device D:\DB\TDMECustomer_Data.MDF for virtual device number (VDN) 0.You don't supply an Initial File Name, maybe something you use for Access but not for SQL Server. At our site we don't even use the Data Source parameter, we add a Server parameter instead.
Here is a website that has connection examples
ConnectionString (http://www.connectionstrings.com/index.htm)
Example
Standard Security:
"Provider=sqloledb;Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=asdasd;")
Trusted Connection:
"Provider=sqloledb;Data Source=Aron1;Initial Catalog=pubs;Integrated Security=SSPI;"
Provider=SQLOLEDB.1;Persist Security Info=False;" & _
"User ID=sa;Password=tdmes102;Initial Catalog=CustomerProfile;" & _
"Data Source=dani;
Friday, February 24, 2012
Failure when installing SQL 2005 SP1 on Windows 2003 Server
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.Thanks,
Sam Lester (MSFT)|||
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.
It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.
|||That did the trick!
Many thanks for the help.
|||I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.
What's strange is there is nothing that should've set this to registry entry to 2.
Failure when installing SQL 2005 SP1 on Windows 2003 Server
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.Thanks,
Sam Lester (MSFT)|||
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.
It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.
|||That did the trick!
Many thanks for the help.
|||I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.
What's strange is there is nothing that should've set this to registry entry to 2.
Failure when installing SQL 2005 SP1 on Windows 2003 Server
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.Thanks,
Sam Lester (MSFT)|||
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.
It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.
|||That did the trick!
Many thanks for the help.
|||I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.
What's strange is there is nothing that should've set this to registry entry to 2.
Failure to install SQL 2005 SP2 standard on cluster
Hi,
While I installed on the active node I got the following error: A recently applied update, KB921896, failed to install
After that installation finished , but query the server version I get:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
9.00.1399.06 RTM Standard Edition
On the Visual Studion Manager Help About I get 9.00.3042
Error logs are below. Can you please tell me how can I overcome this?
TIA.
I paste here the summary and the hotfix logs of the primary node.
There is also the Redist9_Hotfix_KB921896_SqlSupport.msi.log but it is too long to paste here.
summary.txt:
Time: 07/29/2007 02:46:28.253
KB Number: KB921896
Machine: DB1
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: Yes
Log Location on Passive Nodes:
(DB1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
(DB2) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.1.2047 x86
Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD
Integration Services ENU SP1 9.00.2047.00 x86 STANDARD
SQL Server Native Client ENU 9.00.2047.00 x86
Client Components ENU SP1 9.1.2047 x86 STANDARD
MSXML 6.0 Parser ENU 6.00.3883.8 x86
SQLXML4 ENU 9.00.2047.00 x86
Backward Compatibility ENU 8.05.1704 x86
Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 0
Error Description :
-
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File :
Error Number : 11009
Error Description : No passive nodes were successfully patched
-
Product : Integration Services
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log
Error Number : 0
Error Description :
-
Product : SQL Server Native Client
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Reboot Required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlncli.msi.log
Error Number : 3010
Error Description :
-
Product : Client Components
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
Error Number : 0
Error Description :
-
Product : MSXML 6.0 Parser
Product Version (Previous): 3883
Product Version (Final) : 6.10.1129.0
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_msxml6.msi.log
Error Number : 0
Error Description :
-
Product : SQLXML4
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlxml4.msi.log
Error Number : 0
Error Description :
-
Product : Backward Compatibility
Product Version (Previous): 1704
Product Version (Final) : 2004
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
-
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlWriter.msi.log
Error Number : 0
Error Description :
-
**********************************************************************************
Summary
No passive nodes were successfully patched
Exit Code Returned: 11009
hotfix log:
I paste here only part of the file were I think I see errors (because the post fails on complete logs)
07/29/2007 02:24:37.934 ================================================================================
07/29/2007 02:24:37.949 Hotfix package launched
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:37.980 Local Computer:
07/29/2007 02:24:37.980 Target Details: DB1
07/29/2007 02:24:37.980 commonfilesdir = C:\Program Files\Common Files
07/29/2007 02:24:37.980 lcidsupportdir = f:\33a341363e4f5937131539f1\1033
07/29/2007 02:24:37.980 programfilesdir = C:\Program Files
07/29/2007 02:24:37.980 programfilesdir_wow = C:\Program Files
07/29/2007 02:24:37.980 supportdir = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 supportdirlocal = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 windir = C:\WINDOWS
07/29/2007 02:24:37.996 winsysdir = C:\WINDOWS\system32
07/29/2007 02:24:37.996 winsysdir_wow = C:\WINDOWS\SysWOW64
07/29/2007 02:24:37.996
07/29/2007 02:24:38.012 Enumerating applicable products for this patch
07/29/2007 02:24:38.027 Found Redist 2005 product definition
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:40.105 Found Redist 2005 product definition
07/29/2007 02:24:40.137 Found Redist 2005 product definition
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:56.168 Found SQL 2005 product definition
07/29/2007 02:25:00.293 Enumeration: Determining QFE level for product instance MSSQLSERVER
07/29/2007 02:25:00.309 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
07/29/2007 02:25:00.309 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
...
07/29/2007 02:30:06.090 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlagent90.exe (SQLSERVERAGENT [SQLAGENT90.EXE] - 3284)
07/29/2007 02:30:06.387 Locked file: C:\Program Files\microsoft sql server\90\shared\sqlbrowser.exe (SQLBrowser [sqlbrowser.exe] - 1480)
07/29/2007 02:30:58.137 Attempting to pause the 32 bit ngen queue
07/29/2007 02:30:58.902 Installing product: Redist9
07/29/2007 02:30:58.918 Installing instance: Setup Support Files
07/29/2007 02:30:58.934 Installing target: DB1
07/29/2007 02:30:58.934 Installing file: SqlSupport.msi
07/29/2007 02:30:59.027 Copy Engine: Creating MSI install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
07/29/2007 02:30:59.027 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:30:59.027 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.730 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:31:29.746 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.762 Copy Engine: Installed file: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
07/29/2007 02:31:29.762 Installed target: DB1
07/29/2007 02:31:30.027 Installed instance: Setup Support Files
07/29/2007 02:31:30.043 Installed product: Redist9
07/29/2007 02:31:30.043 Installing product: SQL9
07/29/2007 02:31:30.043 Installing instance: MSSQLSERVER
07/29/2007 02:31:30.059 Enumerating passive cluster nodes
07/29/2007 02:31:30.574 Patching available passive node: DB2
07/29/2007 02:31:30.574 Patching passive node: DB2
07/29/2007 02:31:30.590 Waiting for first completed passive node
07/29/2007 02:31:30.934 Task Scheduler: Created remote folder for product instance target \\DB2
07/29/2007 02:31:49.387 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.402 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.574 Task Scheduler: Error, cannot create scheduled task for product instance target \\DB2
07/29/2007 02:31:50.449 Task Scheduler: Removed remote folder for product instance target \\DB2
07/29/2007 02:31:50.449 Error, remote process failed for product instance target
07/29/2007 02:31:50.449 Exit code for passive node: DB2 = 1603
07/29/2007 02:31:50.590 The following exception occurred: No passive nodes were successfully patched Date: 07/29/2007 02:31:50.590 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\instance.cpp Line: 3422
07/29/2007 02:31:51.449 Watson: Param1 = Unknown
07/29/2007 02:31:51.465 Watson: Param2 = 0x2b01
07/29/2007 02:31:51.465 Watson: Param3 = Unknown
07/29/2007 02:31:51.465 Watson: Param4 = 0x0
07/29/2007 02:31:51.465 Watson: Param5 = instance.cpp@.3422
07/29/2007 02:31:51.465 Watson: Param6 = Unknown
07/29/2007 02:31:51.480 Watson: Param7 = SQL9
07/29/2007 02:31:51.480 Watson: Param8 = Hotfix@.
07/29/2007 02:31:51.480 Watson: Param9 = x86
07/29/2007 02:31:51.480 Watson: Param10 = 3042
07/29/2007 02:31:51.480 Installed product: SQL9
07/29/2007 02:31:51.480 Installing product: DTS9
07/29/2007 02:31:51.496 Installing instance: Integration Services
07/29/2007 02:31:51.496 Installing target: DB1
07/29/2007 02:31:51.512 Installing file: sqlrun_dts.msp
07/29/2007 02:31:51.512 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log
...
Hey, did you resolve this? I'm running into the same issue.
Thanks,
RJ
Failure to install SQL 2005 SP2 standard on cluster
Hi,
While I installed on the active node I got the following error: A recently applied update, KB921896, failed to install
After that installation finished , but query the server version I get:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
9.00.1399.06 RTM Standard Edition
On the Visual Studion Manager Help About I get 9.00.3042
Error logs are below. Can you please tell me how can I overcome this?
TIA.
I paste here the summary and the hotfix logs of the primary node.
There is also the Redist9_Hotfix_KB921896_SqlSupport.msi.log but it is too long to paste here.
summary.txt:
Time: 07/29/2007 02:46:28.253
KB Number: KB921896
Machine: DB1
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: Yes
Log Location on Passive Nodes:
(DB1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
(DB2) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.1.2047 x86
Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD
Integration Services ENU SP1 9.00.2047.00 x86 STANDARD
SQL Server Native Client ENU 9.00.2047.00 x86
Client Components ENU SP1 9.1.2047 x86 STANDARD
MSXML 6.0 Parser ENU 6.00.3883.8 x86
SQLXML4 ENU 9.00.2047.00 x86
Backward Compatibility ENU 8.05.1704 x86
Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 0
Error Description :
-
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File :
Error Number : 11009
Error Description : No passive nodes were successfully patched
-
Product : Integration Services
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log
Error Number : 0
Error Description :
-
Product : SQL Server Native Client
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Reboot Required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlncli.msi.log
Error Number : 3010
Error Description :
-
Product : Client Components
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
Error Number : 0
Error Description :
-
Product : MSXML 6.0 Parser
Product Version (Previous): 3883
Product Version (Final) : 6.10.1129.0
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_msxml6.msi.log
Error Number : 0
Error Description :
-
Product : SQLXML4
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlxml4.msi.log
Error Number : 0
Error Description :
-
Product : Backward Compatibility
Product Version (Previous): 1704
Product Version (Final) : 2004
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
-
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlWriter.msi.log
Error Number : 0
Error Description :
-
**********************************************************************************
Summary
No passive nodes were successfully patched
Exit Code Returned: 11009
hotfix log:
I paste here only part of the file were I think I see errors (because the post fails on complete logs)
07/29/2007 02:24:37.934 ================================================================================
07/29/2007 02:24:37.949 Hotfix package launched
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:37.980 Local Computer:
07/29/2007 02:24:37.980 Target Details: DB1
07/29/2007 02:24:37.980 commonfilesdir = C:\Program Files\Common Files
07/29/2007 02:24:37.980 lcidsupportdir = f:\33a341363e4f5937131539f1\1033
07/29/2007 02:24:37.980 programfilesdir = C:\Program Files
07/29/2007 02:24:37.980 programfilesdir_wow = C:\Program Files
07/29/2007 02:24:37.980 supportdir = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 supportdirlocal = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 windir = C:\WINDOWS
07/29/2007 02:24:37.996 winsysdir = C:\WINDOWS\system32
07/29/2007 02:24:37.996 winsysdir_wow = C:\WINDOWS\SysWOW64
07/29/2007 02:24:37.996
07/29/2007 02:24:38.012 Enumerating applicable products for this patch
07/29/2007 02:24:38.027 Found Redist 2005 product definition
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:40.105 Found Redist 2005 product definition
07/29/2007 02:24:40.137 Found Redist 2005 product definition
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:56.168 Found SQL 2005 product definition
07/29/2007 02:25:00.293 Enumeration: Determining QFE level for product instance MSSQLSERVER
07/29/2007 02:25:00.309 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
07/29/2007 02:25:00.309 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
...
07/29/2007 02:30:06.090 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlagent90.exe (SQLSERVERAGENT [SQLAGENT90.EXE] - 3284)
07/29/2007 02:30:06.387 Locked file: C:\Program Files\microsoft sql server\90\shared\sqlbrowser.exe (SQLBrowser [sqlbrowser.exe] - 1480)
07/29/2007 02:30:58.137 Attempting to pause the 32 bit ngen queue
07/29/2007 02:30:58.902 Installing product: Redist9
07/29/2007 02:30:58.918 Installing instance: Setup Support Files
07/29/2007 02:30:58.934 Installing target: DB1
07/29/2007 02:30:58.934 Installing file: SqlSupport.msi
07/29/2007 02:30:59.027 Copy Engine: Creating MSI install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
07/29/2007 02:30:59.027 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:30:59.027 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.730 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:31:29.746 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.762 Copy Engine: Installed file: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
07/29/2007 02:31:29.762 Installed target: DB1
07/29/2007 02:31:30.027 Installed instance: Setup Support Files
07/29/2007 02:31:30.043 Installed product: Redist9
07/29/2007 02:31:30.043 Installing product: SQL9
07/29/2007 02:31:30.043 Installing instance: MSSQLSERVER
07/29/2007 02:31:30.059 Enumerating passive cluster nodes
07/29/2007 02:31:30.574 Patching available passive node: DB2
07/29/2007 02:31:30.574 Patching passive node: DB2
07/29/2007 02:31:30.590 Waiting for first completed passive node
07/29/2007 02:31:30.934 Task Scheduler: Created remote folder for product instance target \\DB2
07/29/2007 02:31:49.387 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.402 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.574 Task Scheduler: Error, cannot create scheduled task for product instance target \\DB2
07/29/2007 02:31:50.449 Task Scheduler: Removed remote folder for product instance target \\DB2
07/29/2007 02:31:50.449 Error, remote process failed for product instance target
07/29/2007 02:31:50.449 Exit code for passive node: DB2 = 1603
07/29/2007 02:31:50.590 The following exception occurred: No passive nodes were successfully patched Date: 07/29/2007 02:31:50.590 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\instance.cpp Line: 3422
07/29/2007 02:31:51.449 Watson: Param1 = Unknown
07/29/2007 02:31:51.465 Watson: Param2 = 0x2b01
07/29/2007 02:31:51.465 Watson: Param3 = Unknown
07/29/2007 02:31:51.465 Watson: Param4 = 0x0
07/29/2007 02:31:51.465 Watson: Param5 = instance.cpp@.3422
07/29/2007 02:31:51.465 Watson: Param6 = Unknown
07/29/2007 02:31:51.480 Watson: Param7 = SQL9
07/29/2007 02:31:51.480 Watson: Param8 = Hotfix@.
07/29/2007 02:31:51.480 Watson: Param9 = x86
07/29/2007 02:31:51.480 Watson: Param10 = 3042
07/29/2007 02:31:51.480 Installed product: SQL9
07/29/2007 02:31:51.480 Installing product: DTS9
07/29/2007 02:31:51.496 Installing instance: Integration Services
07/29/2007 02:31:51.496 Installing target: DB1
07/29/2007 02:31:51.512 Installing file: sqlrun_dts.msp
07/29/2007 02:31:51.512 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log
...
Hey, did you resolve this? I'm running into the same issue.
Thanks,
RJ
Sunday, February 19, 2012
Failure during insatallation of the SQL Express
Hello,
I am getting this message:
Setup failed because Service MSSQL$SQLExpress is disabled for the current hardware profile.Services must be set with the current Hardware Profile logon property profile enabled.
Any idea how to resolve this problem?
Thanks,
Eitan
Here are a few prior suggestions that seem to fix this problem:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=881197&SiteID=1
Thanks,
Sam Lester (MSFT)