Problem With Sql2005-kb918222-x86-enu.exe (cumulative Hotfix, Build 2153)
Aug 10, 2006
Hello,
I do experiment a problem when trying to install the mentionned patch on my Windows XP SP2 machine (fully patched).
Interestingly, the patch works fine for the named instance, which is a "clean" install of SQL Server 2005 SP1, while it fails on the default instance, which is a SQL 2005 SP1 upgraded in place from SQL Server 2000 SP4. Both instances are Developer editions...
The error is along the following lines:
[snip]
08/10/2006 09:22:06.728 Unable to install MSP file: \DHDHY0Jc$1c7c01591e524f9a092159a233hotfixsqlFilessqlrun_sql.msp
08/10/2006 09:22:06.818 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/10/2006 09:22:06.818 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 856
08/10/2006 09:22:06.948
08/10/2006 09:22:06.998 Product Status Summary:
08/10/2006 09:22:07.048 Product: SQL Server Database Services 2005
08/10/2006 09:22:07.088 MSSQLSERVER - Failure
08/10/2006 09:22:07.138 Details: Unable to install Windows Installer MSP file
08/10/2006 09:22:07.228 SQL2K5 - Not Selected
08/10/2006 09:22:07.338
08/10/2006 09:22:42.409 Hotfix package closed
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================ 08/23/2006 15:03:44.608 Hotfix package launched 08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER 08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER 08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER 08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER 08/23/2006 15:03:45.920 Command-line instance name check completed during the install process 08/23/2006 15:03:45.936 Baseline build check completed during the install process 08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER 08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK 08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp 08/23/2006 15:03:52.232 Attempting to check for locked files: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp 08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.out 08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation. 08/23/2006 15:04:02.310 Successfully checked file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp 08/23/2006 15:04:02.326 Successfully opened registry key: SystemCurrentControlSetControlSession Manager 08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations 08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll 08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll 08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll 08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll.
-----------------------
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--------------------------
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedMicrosoft.SqlSac.Public.dll 08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp 08/23/2006 15:04:07.700 Attempting to install file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp 08/23/2006 15:04:07.716 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.log 08/23/2006 15:04:07.732 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 08/23/2006 15:04:07.747 Failed to read registry key: Debug 08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation. 08/23/2006 15:05:11.212 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 08/23/2006 15:05:11.244 Failed to read registry key: Debug 08/23/2006 15:05:11.259 Unable to install MSP file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp 08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 856 08/23/2006 15:05:11.322 08/23/2006 15:05:11.353 Product Status Summary: 08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit) 08/23/2006 15:05:11.384 MSSQLSERVER - Failure 08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
I believe that I mistakenly attempted to apply the Analysis Services component of this update before applying the SQL Server component. The update now fails continuously with the following message:
02/05/2007 17:58:24.990 ================================================================================ 02/05/2007 17:58:25.021 Hotfix package launched 02/05/2007 17:58:27.615 Product discovery successfully completed during the install process for MSSQLSERVER 02/05/2007 17:58:27.630 SP Level check successfully completed during the install process for MSSQLSERVER 02/05/2007 17:58:27.646 Product language check successfully completed during the install process for MSSQLSERVER 02/05/2007 17:58:27.661 Product version check successfully completed during the install process for MSSQLSERVER 02/05/2007 17:58:27.677 Command-line instance name check completed during the install process 02/05/2007 17:58:27.693 Baseline build check completed during the install process 02/05/2007 17:58:34.864 Attempting to install instance: MSSQLSERVER 02/05/2007 17:58:34.974 Attempting to install target: CHARLIDEVSRV 02/05/2007 17:58:35.005 Attempting to check for locked files: sqlrun_sql.msp 02/05/2007 17:58:35.052 Attempting to check for locked files: \CHARLIDEVSRVf$44923e05996203228c1608bea1hotfixsqlFilessqlrun_sql.msp 02/05/2007 17:58:35.067 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.out 02/05/2007 18:01:52.978 MSP returned 1635: This patch package could not be opened. Verify that the patch package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer patch package. 02/05/2007 18:01:53.009 Unable to check MSP file: \CHARLIDEVSRVf$44923e05996203228c1608bea1hotfixsqlFilessqlrun_sql.msp 02/05/2007 18:01:53.025 The following exception occurred: Unable to install Windows Installer MSP file Date: 02/05/2007 18:01:53.025 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 689 02/05/2007 18:01:53.212 Failed to install instance: MSSQLSERVER 02/05/2007 18:01:53.259 02/05/2007 18:01:53.259 Product Status Summary: 02/05/2007 18:01:53.290 Product: SQL Server Database Services 2005 02/05/2007 18:01:53.306 MSSQLSERVER - Failure 02/05/2007 18:01:53.321
The update fails although I have cleaned the registry of any reference to it. Another article indicated that the hotfix may delete registry keys required, for instance, to operated SSIS if applied in the wrong order. Here, it appears to be preventing the hotfix from being reapplied. I have ensured that all necessary permissions are available and the services are running in domain user accounts with the necessary rights. I'm the administrator on the machine.
Is there a way to get this hotfix applied without having to completely rip and rebuild my server instance?
I've read about this hotfix at http://www.kbalertz.com/Feedback_933097.aspx but I can't find anything on microsoft.com about it. It sounds like a worthwhile hotfix, but I'm wondering about the absence of an announcement on microsoft.com.
I am trying to install sql2005-kb918222-x86-enu.exe, first one in the x86 family. I am getting "This machine does not have a product that matches this installation package".
I have SP1 is installed. Version and patch level are 9.1.2047. on
I am trying to install sql2005-kb918222-x86-enu.exe, first one in the x86 family. I am getting "This machine does not have a product that matches this installation package".
I have SP1 is installed. Version and patch level are 9.1.2047. on
The Kb article says to install all component patches, even if you are not running them, to avoid errors...the reporting services hotfix would not install(obviously since reporting svcs is not installed).....now I get the following erro, when trying to connect to the SSIS on my sql server...oh, I am trying to connect locally on the server it self too....
Cannot connect to CRP-DAY1-SQLs1.
===================================
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------ Program Location:
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server) at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
Connect to SSIS Service on machine "CRP-DAY1-SQLs1" failed: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. .
------------------------------ Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion) at Microsoft.SqlServer.Dts.SmoEnum.DTSEnum.GetData(EnumResult erParent) at Microsoft.SqlServer.Management.Smo.Environment.GetData() at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci) at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
===================================
Connect to SSIS Service on machine "CRP-DAY1-SQLs1" failed: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. .
------------------------------ Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.GetServerInfo(String bstrMachineName, String& serverVersion) at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion)
Hi, I'm planning to install the cumulative hotfix (build 2187) on my sql 2000 clustering server (SP4, 2040). And I would like to know if the cumulative hotfix is able to roll back. If possible, please provide me any information about that. Thanks in advance.
I have recently applied the latest cumulative upgrade 3 for SP2 for SQL Server 2005 (KB939537) to have all the hotfixes needed since the SP2, and to correct a specific one : the 50001440 (SQL Server may fail to generate a plan for a complex query that involves cursors and error 8623 occurs - KB940128).
But it is not included in this latest cumulative upgrade package. I read the new policy about CU but I can not know if the 50001440 hotfix is candidate for the CU :
Cumulative update (CU)
€¢ The update can be requested by any customer, regardless of their support offering.
€¢ The update is released every 2 months.
€¢ The update contains the following:
€¢ All previous critical on-demand hotfixes to date.
Fixes for issues that meet hotfix acceptance criteria. These criteria include workaround availability, customer effect, reproducibility, the complexity of the code that must be changed, and so on.
Another bug, the 50001317 (You may receive error messages when you try to log in to an instance of SQL Server 2005 and SQL Server handles many concurrent connections - KB937745) : it is included in the upgrade 2 for SP2 but not in the upgrade3.
So, is it needed to apply each cumulative upgrade or only the latest CU ? And if it is only the latest CU, why are there missing hotfix ?
So today I decided I may as well put the latest hotfix package for Sql 2005 onto my laptop.
Unlike SP1 the hotfix actually seemed to know about SQL Express and attempt to install itself only to collapse in a big heap. The log file indicates it can't find a bunch of files it wants to patch.
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403) Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207) Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207) Get help: http://help/207
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368) Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036) Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @retcode = -1 and thus cannot obtain exclusive lock on resource
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
Cumulative Update 5 Build 9.00.3215 KB - Problem http://support.microsoft.com/kb/943656/
We contacted Microsoft and installed the update, but when I do a SELECT @@Version I still get build 3042.
I'm not sure if they sent us the wrong file or if the update didn't apply correctly. Under Add/Remove Programs SQL Native Client shows the new build 3215 though.
Microsoft sent us 335091_intl_i386_zip.exe This extracted to.. hotfix.txt sqlncli.msi
When I try to apply this post SP1 patch to SQL Server 2005 x 64 on a Windows 2003x64 R2 system it fails everytime. The following is the HOTFIX log:
07/12/2006 15:02:06.781 ================================================================================ 07/12/2006 15:02:06.781 Hotfix package launched 07/12/2006 15:02:08.046 Product discovery successfully completed during the install process for MSSQLSERVER 07/12/2006 15:02:08.046 SP Level check successfully completed during the install process for MSSQLSERVER 07/12/2006 15:02:08.046 Product language check successfully completed during the install process for MSSQLSERVER 07/12/2006 15:02:08.046 Product version check successfully completed during the install process for MSSQLSERVER 07/12/2006 15:02:08.046 Command-line instance name check completed during the install process 07/12/2006 15:02:08.046 Baseline build check completed during the install process 07/12/2006 15:02:13.875 Attempting to install instance: MSSQLSERVER 07/12/2006 15:02:13.875 Attempting to install target: <System Name> 07/12/2006 15:02:13.890 Attempting to stop service: SQLSERVERAGENT 07/12/2006 15:02:17.890 Successfully stopped service: SQLSERVERAGENT 07/12/2006 15:02:17.890 Attempting to stop service: MSSQLServer 07/12/2006 15:02:19.890 Successfully stopped service: MSSQLServer 07/12/2006 15:02:19.890 Attempting to check for locked files: sqlrun_sql.msp 07/12/2006 15:02:19.906 Attempting to check for locked files: \<System Name>E$SoftwareSQL2005sppostsp1hotfixsqlFilessqlrun_sql.msp 07/12/2006 15:02:19.906 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.out 07/12/2006 15:02:25.109 MSP returned 1603: A fatal error occurred during installation. 07/12/2006 15:02:25.125 Unable to check MSP file: \<System Name>E$SoftwareSQL2005sppostsp1hotfixsqlFilessqlrun_sql.msp 07/12/2006 15:02:25.125 The following exception occurred: Unable to install Windows Installer MSP file Date: 07/12/2006 15:02:25.125 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 689 07/12/2006 15:02:25.125 Restarting SQL Service MSSQLServer since it was previously running 07/12/2006 15:02:25.125 Attempting to start service: MSSQLServer 07/12/2006 15:02:30.031 Successfully started service: MSSQLServer 07/12/2006 15:02:30.031 Restarting SQL Agent Service SQLSERVERAGENT since it was previously running 07/12/2006 15:02:30.031 Attempting to start service: SQLSERVERAGENT 07/12/2006 15:02:31.312 Successfully started service: SQLSERVERAGENT 07/12/2006 15:02:31.312 Failed to install instance: MSSQLSERVER 07/12/2006 15:02:31.328 07/12/2006 15:02:31.328 Product Status Summary: 07/12/2006 15:02:31.328 Product: SQL Server Database Services 2005 (64-bit) 07/12/2006 15:02:31.343 MSSQLSERVER - Failure 07/12/2006 15:02:31.343
we have automated build on every night. In our solution is SSIS project, where each package is encrypted per password. We call build process per command line like this..
C:ProgrammeMicrosoft Visual Studio 8Common7IDEdevenv.exe (c:DevelopmentX3\X3.sln /build Release)' in 'c:DevelopmentProjectsDailyBuild
Through build process we get a error:
External Program Failed: C:ProgrammeMicrosoft Visual Studio 8Common7IDEdevenv.exe (return code was 1):
We think a reason is, that on build of SSIS project must be entered a password. You can wonder for what we need that SSIS packages are part of our build. We hope that on build process is also created Deployment Utility, if so set in dtproject.user. Is it so? Is there any way to create Deployment utility on automated build process? Can be a password provided pre command line?
I just upgraded my SQL 2000 server to SQL2005. I forked out all that money, and now it takes 4~5 seconds for a webpage to load. You can see for yourself. It's pathetic. When I ran SQL2000, i was getting instant results on any webpage. I can't find any tool to optimize the tables or databases. And when I used caused SQL Server to use 100% cpu and 500+MB of ram. I can't have this.Can anyone give me some tips as to why SQL 2005 is so slow?
We would like to apply a hotfix to solve the issue that brought our server down. The hotfix we are trying to apply is in Build 3175. But the latest Cumulative Update 3 Package is Build 3186. Should we apply 3175? Or we can go for the latest build 3186? Which is recommended?
Is there anyone know where to get the hotfix to put the "Select All" option back on multi-value parameter list after SP1? The reason why I didn't install SP2 because it requires to install print control on client side. At the moment our company try to avoid it. Or is there a way to avoid this print control? I hope to see some responses from MSFT support team.
I have SP1 on most of my servers. My users however do not. They have been developing using "select all" and are now ready to deploy a major project, I am in the process of installing the hotfix so my question is "they do not have SP1 and I have SP1 along with the hotfix" will that work or does this hot fix require that the client tools have SP1 and the hotfix applied as well"? They do not want to change their development environment since they are so close to deployment of their reports. Thank you!!
Iam at the completion of my project and iam facing a crash from the sql server 2005 .....Microsoft have agreed it to be their bug in the following article
I have searched for any fix in the site but unable to find that..........So please give me the fix Iam in emergency and also client is on my neck....Please help me out
Right now my SQL Server 2005 is on build 3054.I am trying to apply patch SQLServer2005-KB934459-x86-ENU.I am getting error like failed to apply hotfix.
Can you please tell me the exact steps so I can troubleshoot and I can upgrade sql server to build 3159.
I have two clustered server. (ms sql 2000 server, windows 2003 server) now i need to add one new server to the cluster and take the secondary node off. I have installed SP4 & hotfix in my SQL Server cluster before.
My question is do I still need to install SP4 & hotfix in my new server?
I am getting the following (MOM) error on 3 of my databases anytime I initiate a backup of the mdf. The database seems to backup as expected. The one thing that has recently changed is I implemented MS Hotfix 2187 on my SQl cluster over the weekend.
Severity: Critical Error
Status: New
Source: MSSQLSERVER
Name: Commit record has already been distributed. Check DBTABLE
Description: Unable to expand message 17055 [-1073724769] 18264 Database backed up: Database: XX03PLUS, creation date(time): 2005/12/06(18:38:50), pages dumped: 23026, first LSN: 18761:44:1, last LSN: 18761:46:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G: empar03PLUS_fromVCforK1.bak'}).
Post installation of Hotfix Update 8.00.0679 (for the slammer worm) we've encountered this error on our production server "2003-02-13 09:54:17.14 server Error: 17882, Severity: 18, State: 1 2003-02-13 09:54:17.14 server Error accepting connection request via Net-Library 'SSNETLIB'. Execution continuing..".
This appears to correlate with attempts to access our SQL7 server, which was also patched for the worm (Hotfix 7.00.1030) via any query analyzer linked server reference; in fact the linked server attempt fails on a 'general network failure'.
On the SQL2000 side, the SSNETLIB failure is followed by failures in "Stored function 'xp_enumerrorlogs' in the library 'xpstar.dll' generated an access violation" and then all backups fail on memory allocation failures and major database selects of 100K's records fail on "unable to allocate thread".
Anyone have any thoughts or experiences germane? I'm about to undo the security patch on both servers.
Hi. Was hoping to get some advice on applying a hotfix to a SQL Server 2005 failover Cluster.
The hotfix I am applying (KB933508) relates to a Maintenance Plans issue with Server 2005 Service Pack 2. During installation I'm advised that unless the SQL Server and other services are stopped a reboot will be required, although I can still install the hotfix. However the installation is failing. There are error details in the relevant logs created in C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix to the effect that the 'Debug' value in registry key 'SoftwarePoliciesMicrosoftWindowsInstaller' can't be read and that SQL Server was unable to add a user (the account under which SQL Server Agent and Analysis Services run) to a local group (the domain group in which SQL Server logins are contained).
Is this something simple like explicitly shutting down the services first before applying the hotfix or is there something else going on?
I've got a 4 node SQL 2008R2 cluster (configured 2 active - 2 passive), and 9 instances, of which all but one are on SP1 (the most recent addition is on SP2).
I need to apply a hotfix (Cumulative Update 6 for SP1) to just one instance. Can I do this by failing over the affected instance to one of the passive nodes, applying the hotfix, and failing it back again or do I need to apply the hotfix to all nodes as detailed in:
SQL Server failover cluster rolling patch and service pack process
i.e. will it involve a little downtime for all instances on the cluster?
