I was setting up a new SQL 2005 sp2 (x64) box and restoring dbs. I restored
DB1, then moved on to DB2. I was restoring from a file, so I added the
file, forgot to change the db name in the dropdown, so it still said DB1,
changed the file paths, and clicked ok. So of course when I clicked ok and
it started the restore, I got an error telling me the file contained a db
other than DB1. Realizing my mistake, I then selected DB2 from the
dropdown, and clicked ok. The db restored just fine, but the message I got
at the end told me that DB1 had been restored...when in fact it was DB2 that
was restored.
AndreAndre wrote:
> I was setting up a new SQL 2005 sp2 (x64) box and restoring dbs. I restor
ed
> DB1, then moved on to DB2. I was restoring from a file, so I added the
> file, forgot to change the db name in the dropdown, so it still said DB1,
> changed the file paths, and clicked ok. So of course when I clicked ok an
d
> it started the restore, I got an error telling me the file contained a db
> other than DB1. Realizing my mistake, I then selected DB2 from the
> dropdown, and clicked ok. The db restored just fine, but the message I go
t
> at the end told me that DB1 had been restored...when in fact it was DB2 th
at
> was restored.
> Andre
>
I think it's just a matter of a missing "refresh" of the GUI. I'm not
using the GUI for restores myself so I'm not familiar with how it
appears, but you can be quite sure that it is DB2 you've restored - and
not DB1. You'd only be able to restore DB2 on top of DB1 if you explicit
had told it to replace the database.
Regards
Steen Schlter Persson
Database Administrator / System Administrator
Showing posts with label sp2. Show all posts
Showing posts with label sp2. Show all posts
Friday, March 23, 2012
feature?
I was setting up a new SQL 2005 sp2 (x64) box and restoring dbs. I restored
DB1, then moved on to DB2. I was restoring from a file, so I added the
file, forgot to change the db name in the dropdown, so it still said DB1,
changed the file paths, and clicked ok. So of course when I clicked ok and
it started the restore, I got an error telling me the file contained a db
other than DB1. Realizing my mistake, I then selected DB2 from the
dropdown, and clicked ok. The db restored just fine, but the message I got
at the end told me that DB1 had been restored...when in fact it was DB2 that
was restored.
Andre
Andre wrote:
> I was setting up a new SQL 2005 sp2 (x64) box and restoring dbs. I restored
> DB1, then moved on to DB2. I was restoring from a file, so I added the
> file, forgot to change the db name in the dropdown, so it still said DB1,
> changed the file paths, and clicked ok. So of course when I clicked ok and
> it started the restore, I got an error telling me the file contained a db
> other than DB1. Realizing my mistake, I then selected DB2 from the
> dropdown, and clicked ok. The db restored just fine, but the message I got
> at the end told me that DB1 had been restored...when in fact it was DB2 that
> was restored.
> Andre
>
I think it's just a matter of a missing "refresh" of the GUI. I'm not
using the GUI for restores myself so I'm not familiar with how it
appears, but you can be quite sure that it is DB2 you've restored - and
not DB1. You'd only be able to restore DB2 on top of DB1 if you explicit
had told it to replace the database.
Regards
Steen Schlter Persson
Database Administrator / System Administrator
DB1, then moved on to DB2. I was restoring from a file, so I added the
file, forgot to change the db name in the dropdown, so it still said DB1,
changed the file paths, and clicked ok. So of course when I clicked ok and
it started the restore, I got an error telling me the file contained a db
other than DB1. Realizing my mistake, I then selected DB2 from the
dropdown, and clicked ok. The db restored just fine, but the message I got
at the end told me that DB1 had been restored...when in fact it was DB2 that
was restored.
Andre
Andre wrote:
> I was setting up a new SQL 2005 sp2 (x64) box and restoring dbs. I restored
> DB1, then moved on to DB2. I was restoring from a file, so I added the
> file, forgot to change the db name in the dropdown, so it still said DB1,
> changed the file paths, and clicked ok. So of course when I clicked ok and
> it started the restore, I got an error telling me the file contained a db
> other than DB1. Realizing my mistake, I then selected DB2 from the
> dropdown, and clicked ok. The db restored just fine, but the message I got
> at the end told me that DB1 had been restored...when in fact it was DB2 that
> was restored.
> Andre
>
I think it's just a matter of a missing "refresh" of the GUI. I'm not
using the GUI for restores myself so I'm not familiar with how it
appears, but you can be quite sure that it is DB2 you've restored - and
not DB1. You'd only be able to restore DB2 on top of DB1 if you explicit
had told it to replace the database.
Regards
Steen Schlter Persson
Database Administrator / System Administrator
feature?
I was setting up a new SQL 2005 sp2 (x64) box and restoring dbs. I restored
DB1, then moved on to DB2. I was restoring from a file, so I added the
file, forgot to change the db name in the dropdown, so it still said DB1,
changed the file paths, and clicked ok. So of course when I clicked ok and
it started the restore, I got an error telling me the file contained a db
other than DB1. Realizing my mistake, I then selected DB2 from the
dropdown, and clicked ok. The db restored just fine, but the message I got
at the end told me that DB1 had been restored...when in fact it was DB2 that
was restored.
AndreAndre wrote:
> I was setting up a new SQL 2005 sp2 (x64) box and restoring dbs. I restored
> DB1, then moved on to DB2. I was restoring from a file, so I added the
> file, forgot to change the db name in the dropdown, so it still said DB1,
> changed the file paths, and clicked ok. So of course when I clicked ok and
> it started the restore, I got an error telling me the file contained a db
> other than DB1. Realizing my mistake, I then selected DB2 from the
> dropdown, and clicked ok. The db restored just fine, but the message I got
> at the end told me that DB1 had been restored...when in fact it was DB2 that
> was restored.
> Andre
>
I think it's just a matter of a missing "refresh" of the GUI. I'm not
using the GUI for restores myself so I'm not familiar with how it
appears, but you can be quite sure that it is DB2 you've restored - and
not DB1. You'd only be able to restore DB2 on top of DB1 if you explicit
had told it to replace the database.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator
DB1, then moved on to DB2. I was restoring from a file, so I added the
file, forgot to change the db name in the dropdown, so it still said DB1,
changed the file paths, and clicked ok. So of course when I clicked ok and
it started the restore, I got an error telling me the file contained a db
other than DB1. Realizing my mistake, I then selected DB2 from the
dropdown, and clicked ok. The db restored just fine, but the message I got
at the end told me that DB1 had been restored...when in fact it was DB2 that
was restored.
AndreAndre wrote:
> I was setting up a new SQL 2005 sp2 (x64) box and restoring dbs. I restored
> DB1, then moved on to DB2. I was restoring from a file, so I added the
> file, forgot to change the db name in the dropdown, so it still said DB1,
> changed the file paths, and clicked ok. So of course when I clicked ok and
> it started the restore, I got an error telling me the file contained a db
> other than DB1. Realizing my mistake, I then selected DB2 from the
> dropdown, and clicked ok. The db restored just fine, but the message I got
> at the end told me that DB1 had been restored...when in fact it was DB2 that
> was restored.
> Andre
>
I think it's just a matter of a missing "refresh" of the GUI. I'm not
using the GUI for restores myself so I'm not familiar with how it
appears, but you can be quite sure that it is DB2 you've restored - and
not DB1. You'd only be able to restore DB2 on top of DB1 if you explicit
had told it to replace the database.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator
Feature Pack for SP2
I installed SP2 of SQL2005 onto my development machine for testing before using it on the live server.
I saw that MSXML 6 was part of the package and was updated, but what about the OLEDB for MS OLAP 9 driver? Will we see a Feature Pack SP2 soon? Or is it even available and I am just blind?
Or did the OLE DB for OLAP thing not change at all? What version is the latest for this component, and maybe even more important: Where does the dll hide? System32 I suppose, but...
Thanks for pointing out!
Feature pack is part of SP2 package. Here is the link to the new feature pack http://www.microsoft.com/downloads/details.aspx?familyid=50b97994-8453-4998-8226-fa42ec403d17&displaylang=en
You can also find the link on the main page of the SP2 http://www.microsoft.com/sql/sp2.mspx.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, February 24, 2012
Failure to install SQL Express SP2 on Vista Home Premium
Hi,
I have been trying to install SQL Express SP2 (SQLEXPR32.exe) on a Window Vista Home Premium for past 2 days 
SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
I have search through the forums. One of the possibilities is due to a WMI repository corruption. Tried fixing it, but the problem still persists. (Maybe I am doing it the wrong way 
Below is the installation summary:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Home Edition (Build 6000)
Time : Thu Mar 15 02:13:51 2007
ATLANTIS : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
Machine : ATLANTIS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQLSupport_1.log
--
Machine : ATLANTIS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQLNCLI_1.log
--
Machine : ATLANTIS
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SqlWriter_1.log
--
Machine : ATLANTIS
Product : SQL Server Database Services
Error : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
--
Machine : ATLANTIS
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error Number : 29513
--
What are the other possibilities and fixes? Please help.
Thanks a million.
This is a problem with WMI, either the repository is messed up or WMI is not correctly registered. You can find a post on how to repair WMI here and a blog posting about manually installing sqlmgmproviderxpsp2up.mof here.
Mike
|||Hi,
Thanks for the feedback. I have tried both methods.
Initially, it keep on showing "Access is Denied" and missing file command whenever I go to command prompt and use the "mofcomp" command.
However thanks to your advice, I realised the problem is due to WMI corruption or a missing sqlmgmproviderxp2up.mof file.
Hence I copied the sqlmgmproviderxp2up.mof file from my WindowXp laptop to my Vista Desktop, and then I ran the "mofcomp" command. And it works
Thanks again.
|||hello, i'm still having the same issue....i try on install sql express edition on windows vista home premium edition but get the following error any suggestions...
Failure to install SQL Express SP2 on Vista Home Premium
Hi,
I have been trying to install SQL Express SP2 (SQLEXPR32.exe) on a Window Vista Home Premium for past 2 days
SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
I have search through the forums. One of the possibilities is due to a WMI repository corruption. Tried fixing it, but the problem still persists. (Maybe I am doing it the wrong way
Below is the installation summary:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Home Edition (Build 6000)
Time : Thu Mar 15 02:13:51 2007
ATLANTIS : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
Machine : ATLANTIS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQLSupport_1.log
--
Machine : ATLANTIS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQLNCLI_1.log
--
Machine : ATLANTIS
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SqlWriter_1.log
--
Machine : ATLANTIS
Product : SQL Server Database Services
Error : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
--
Machine : ATLANTIS
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_ATLANTIS_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error Number : 29513
--
What are the other possibilities and fixes? Please help.
Thanks a million.
This is a problem with WMI, either the repository is messed up or WMI is not correctly registered. You can find a post on how to repair WMI here and a blog posting about manually installing sqlmgmproviderxpsp2up.mof here.
Mike
|||Hi,
Thanks for the feedback. I have tried both methods.
Initially, it keep on showing "Access is Denied" and missing file command whenever I go to command prompt and use the "mofcomp" command.
However thanks to your advice, I realised the problem is due to WMI corruption or a missing sqlmgmproviderxp2up.mof file.
Hence I copied the sqlmgmproviderxp2up.mof file from my WindowXp laptop to my Vista Desktop, and then I ran the "mofcomp" command. And it works
Thanks again.
|||hello, i'm still having the same issue....i try on install sql express edition on windows vista home premium edition but get the following error any suggestions...
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 sending mail: Cannot access a closed Stream
Running Report Server SP2 and can't get reliable Subscription emails sent.
Keep getting the error"Failure sending mail: Cannot access a closed Stream"
As a test I subscribed to a report to run every 2 minutes and let it run all
night. Surprisingly, the email succeeded and was sent to me two times every
four hours and then would fail for another four hours. (Example emailed ok at
6:00pm and 6:02pm but then failed every two minutes until it was again
successful at 10:00pm and 10:02pm) This cycle continued all night.
I have seen multiple strings on this same error in other newsgroups and
google searches but never any solutions. Does anyone have anything I can try?
I am getting desperate. Thanks in advance.Any luck with finding a solution to this problem? We are also suffering
through the same situation. It seems to occur mainly with subscriptions that
have mulitple recipients listed. It also only occurs only every now and
then. Very hard to troubleshoot. It began after application of SP2.
"Dan Varozza" wrote:
> Running Report Server SP2 and can't get reliable Subscription emails sent.
> Keep getting the error"Failure sending mail: Cannot access a closed Stream"
> As a test I subscribed to a report to run every 2 minutes and let it run all
> night. Surprisingly, the email succeeded and was sent to me two times every
> four hours and then would fail for another four hours. (Example emailed ok at
> 6:00pm and 6:02pm but then failed every two minutes until it was again
> successful at 10:00pm and 10:02pm) This cycle continued all night.
> I have seen multiple strings on this same error in other newsgroups and
> google searches but never any solutions. Does anyone have anything I can try?
> I am getting desperate. Thanks in advance.|||No I have had no luck finding a solution. I too noticed that it was happening
with reports that had multiple subscriptions and recipients. My solution for
now was to delete all subscriptions and replace them with one subscription
that contains all the recipients. This subscription now runs fine once per
day and sends out the email to all the recipients. It seems the mail delivery
only has a problem when there are a lot a mail jobs occuring at different
times for a given report. Funny thing is that I see this error reproted on
other posts and never any answers. It's like nobody at Microsoft wants to
acknowledge this issue so I guess we have to live with it.
"John Marks" wrote:
> Any luck with finding a solution to this problem? We are also suffering
> through the same situation. It seems to occur mainly with subscriptions that
> have mulitple recipients listed. It also only occurs only every now and
> then. Very hard to troubleshoot. It began after application of SP2.
>
> "Dan Varozza" wrote:
> > Running Report Server SP2 and can't get reliable Subscription emails sent.
> > Keep getting the error"Failure sending mail: Cannot access a closed Stream"
> >
> > As a test I subscribed to a report to run every 2 minutes and let it run all
> > night. Surprisingly, the email succeeded and was sent to me two times every
> > four hours and then would fail for another four hours. (Example emailed ok at
> > 6:00pm and 6:02pm but then failed every two minutes until it was again
> > successful at 10:00pm and 10:02pm) This cycle continued all night.
> >
> > I have seen multiple strings on this same error in other newsgroups and
> > google searches but never any solutions. Does anyone have anything I can try?
> > I am getting desperate. Thanks in advance.
Keep getting the error"Failure sending mail: Cannot access a closed Stream"
As a test I subscribed to a report to run every 2 minutes and let it run all
night. Surprisingly, the email succeeded and was sent to me two times every
four hours and then would fail for another four hours. (Example emailed ok at
6:00pm and 6:02pm but then failed every two minutes until it was again
successful at 10:00pm and 10:02pm) This cycle continued all night.
I have seen multiple strings on this same error in other newsgroups and
google searches but never any solutions. Does anyone have anything I can try?
I am getting desperate. Thanks in advance.Any luck with finding a solution to this problem? We are also suffering
through the same situation. It seems to occur mainly with subscriptions that
have mulitple recipients listed. It also only occurs only every now and
then. Very hard to troubleshoot. It began after application of SP2.
"Dan Varozza" wrote:
> Running Report Server SP2 and can't get reliable Subscription emails sent.
> Keep getting the error"Failure sending mail: Cannot access a closed Stream"
> As a test I subscribed to a report to run every 2 minutes and let it run all
> night. Surprisingly, the email succeeded and was sent to me two times every
> four hours and then would fail for another four hours. (Example emailed ok at
> 6:00pm and 6:02pm but then failed every two minutes until it was again
> successful at 10:00pm and 10:02pm) This cycle continued all night.
> I have seen multiple strings on this same error in other newsgroups and
> google searches but never any solutions. Does anyone have anything I can try?
> I am getting desperate. Thanks in advance.|||No I have had no luck finding a solution. I too noticed that it was happening
with reports that had multiple subscriptions and recipients. My solution for
now was to delete all subscriptions and replace them with one subscription
that contains all the recipients. This subscription now runs fine once per
day and sends out the email to all the recipients. It seems the mail delivery
only has a problem when there are a lot a mail jobs occuring at different
times for a given report. Funny thing is that I see this error reproted on
other posts and never any answers. It's like nobody at Microsoft wants to
acknowledge this issue so I guess we have to live with it.
"John Marks" wrote:
> Any luck with finding a solution to this problem? We are also suffering
> through the same situation. It seems to occur mainly with subscriptions that
> have mulitple recipients listed. It also only occurs only every now and
> then. Very hard to troubleshoot. It began after application of SP2.
>
> "Dan Varozza" wrote:
> > Running Report Server SP2 and can't get reliable Subscription emails sent.
> > Keep getting the error"Failure sending mail: Cannot access a closed Stream"
> >
> > As a test I subscribed to a report to run every 2 minutes and let it run all
> > night. Surprisingly, the email succeeded and was sent to me two times every
> > four hours and then would fail for another four hours. (Example emailed ok at
> > 6:00pm and 6:02pm but then failed every two minutes until it was again
> > successful at 10:00pm and 10:02pm) This cycle continued all night.
> >
> > I have seen multiple strings on this same error in other newsgroups and
> > google searches but never any solutions. Does anyone have anything I can try?
> > I am getting desperate. Thanks in advance.
Subscribe to:
Posts (Atom)