Our update of KB 934458 to SQL Server 2005 SP2 has failed on a Windows 2003 SP2 server. This is a standard version of SQL Server.
The error reported is:
Error Number : 29506
Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file e:MSQLMSSQLData for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
I have verified that Administrator has full control permissions for the folder indicated in the error message. The SQL Server Service account also has full control permissions on the folder.
I have run the update as administrator without any access restriction.
I am having trouble getting the Critical Update for SQL Server 2005 Service Pack 2 (KB 934458) to install successfully. Message simply states the updates was unsuccessful. After that I am unable to connect to SQL Server via SSMS. Only rebooting the computer allows me to reconnect. Then Automatic updates won't leave me alone and wants to try it again. Hmmmmm.
I then tried to download (SQLServer2005-KB934458-x86-ENU.exe) and try it again. While running the update I noticed it was now referred to as "Microsoft SQL Server 2005 Service Pack 2 Cumulative Hotfix 3054". Are these the same thing? Any hoot, it still fails to install. As each component failed, for what looks to be the same reason (See below), I allowed the installation wizard to report it's findings back to Microsoft.
Oh and one other observation. It appears as though Microsoft had a similar issue when they release SS2k5 SP1. They issed a workaround. See http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B918357. If this is the same problem, why wouldn' t they try to fix it before releasing SP2?
Any way back to my current issue, clicking on the View Summary at the Installation Complete dialog reveals the following. Can someone help?
Thanks!!!
Time: 04/06/2007 10:04:01.859 KB Number: KB934458 Machine: PEPE OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3054 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition SQL Server Database Services 2005 (MSSQLSERVER) ENU SP2 2005.090.3050.00 x86 DEVELOPER SQL Server Analysis Services 2005 (MSSQLSERVER) ENU SP2 2005.090.3050.00 x86 DEVELOPER SQL Server Reporting Services 2005 (MSSQLSERVER) ENU SP2 9.00.3050.00 x86 DEVELOPER SQL Server Notification Services 2005 ENU SP2 9.00.3050.00 x86 DEVELOPER SQL Server Integration Services 2005 ENU SP2 9.00.3050.00 x86 DEVELOPER SQL Server Tools and Workstation Components 2005 ENU SP2 9.2.3050 x86 DEVELOPER
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID
********************************************************************************** Product Installation Status Product : SQL Server Database Services 2005 (MSSQLSERVER) Product Version (Previous): 3050 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log Error Number : 1635 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Product : SQL Server Analysis Services 2005 (MSSQLSERVER) Product Version (Previous): 3050 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB934458_sqlrun_as.msp.log Error Number : 1635 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Product : SQL Server Reporting Services 2005 (MSSQLSERVER) Product Version (Previous): 3050 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRS9_Hotfix_KB934458_sqlrun_rs.msp.log Error Number : 1635 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Product : SQL Server Notification Services 2005 Product Version (Previous): 3050 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixNS9_Hotfix_KB934458_sqlrun_ns.msp.log Error Number : 1635 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Product : SQL Server Integration Services 2005 Product Version (Previous): 3050 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB934458_sqlrun_dts.msp.log Error Number : 1635 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Product : SQL Server Tools and Workstation Components 2005 Product Version (Previous): 3050 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB934458_sqlrun_tools.msp.log Error Number : 1635 Error Description : Unable to install Windows Installer MSP file ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 1635
-------------------------------------- End of View Summary ---------------------------------------
For information purposes I went ahead and included below the tail end of the first failing process where it looks to go cattywhompus. The end of the log file (highlighted in yellow above) looks like this:
...
MSI (s) (10C) [09:51:23:343]: Opening existing patch 'C:WINDOWSInstaller2a6c7048.msp'. MSI (s) (10C) [09:51:23:343]: Note: 1: 2203 2: C:WINDOWSInstaller2a6c7048.msp 3: -2147287038 MSI (s) (10C) [09:51:23:343]: Couldn't find local patch 'C:WINDOWSInstaller2a6c7048.msp'. Looking for it at its source. MSI (s) (10C) [09:51:23:343]: Resolving Patch source. MSI (s) (10C) [09:51:23:343]: User policy value 'SearchOrder' is 'nmu' MSI (s) (10C) [09:51:23:343]: User policy value 'DisableMedia' is 0 MSI (s) (10C) [09:51:23:343]: Machine policy value 'AllowLockdownMedia' is 0 MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Media enabled only if package is safe. MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Looking for sourcelist for product {4A35EF4A-D868-4B15-A84D-3E8925AA9558} MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Adding {4A35EF4A-D868-4B15-A84D-3E8925AA9558}; to potential sourcelist list (pcode;disk;relpath). MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Now checking product {4A35EF4A-D868-4B15-A84D-3E8925AA9558} MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Media is enabled for product. MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Trying source d:e2ba478890840dab90ccafHotFixSQLFiles. MSI (s) (10C) [09:51:23:343]: Note: 1: 2203 2: d:e2ba478890840dab90ccafHotFixSQLFilessqlrun_sql.msp 3: -2147287037 MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Source is invalid due to missing/inaccessible package. MSI (s) (10C) [09:51:23:343]: Note: 1: 1706 2: -2147483647 3: sqlrun_sql.msp MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Processing net source list. MSI (s) (10C) [09:51:23:343]: Note: 1: 1706 2: -2147483647 3: sqlrun_sql.msp MSI (s) (10C) [09:51:23:343]: SOURCEMGMT: Processing media source list. MSI (s) (10C) [09:51:23:359]: SOURCEMGMT: Resolved source to: 'sqlrun_sql.msp' MSI (s) (10C) [09:53:21:359]: Note: 1: 1314 2: sqlrun_sql.msp MSI (s) (10C) [09:53:21:359]: Unable to create a temp copy of patch 'sqlrun_sql.msp'. MSI (s) (10C) [09:53:21:390]: Note: 1: 1708 MSI (s) (10C) [09:53:21:390]: Note: 1: 2729 MSI (s) (10C) [09:53:21:406]: Note: 1: 2729 MSI (s) (10C) [09:53:21:406]: Product: Microsoft SQL Server 2005 -- Installation failed.
MSI (s) (10C) [09:53:21:437]: MainEngineThread is returning 1635 This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package. C:WINDOWSInstaller9b7a85.msi MSI (c) (C0:90) [09:53:21:437]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (C0:90) [09:53:21:437]: MainEngineThread is returning 1635 === Verbose logging stopped: 4/6/2007 9:53:21 ===
Hi. Has anyone else had any problem with their SQL Server 2005 going nuts after installing the SP2 + the above hotfix?
We reboot the SQL Server and as soon as SQL receives a command of any sort, the SCSI RAID 5 hard drives light up and start trashing. Therefore every query and even Windows response time is painfully slow or fails to respond. When we look at the Activity Monitor and sp_who2 there is a process running a Select Into from Microsoft SQL Server Management Studio using the sa account from the last database name in our system. So we can't kill the process as it says "Cannot use KILL to kill your own process. Microsoft SQL Server, Error: 6104)".
The last Transact-SQL command from this process is: create table #tmpDBCCinputbuffer ((Event Type) nvarchar(512), [Parameters] int, [Event Info] nvarchar(512)) insert into #tmpDBCCinputbuffer exec ('DBCC INPUTBUFFER(56)') select [Event Info] from #tmpDBCCinputbuffer
The only other issue I should mention is that we had to uninstall and reinstall SQL Server yesterday as SP2 only half installed. The SP2 install log indicated that SQL SP1 wasn't in a good state as we previously (3 months ago) performed an upgrade from Windows 2000 Server to Windows 2003 R2 Server.
Our other 3 Windows 2003 R2 Servers which were a clean install of both Windows and SQL are running fine.
I've been insisting that we do a new clean Windows and SQL install, but the other team members insist that it's been fine until we installed SQL Server SP2.
So can anyone provide and help or evidence to say who is right either way?
I have a SQL Server 2005 x64 bit with SP2 applied and patched to KB934458-x64-ENU (9.0.3054) I am unable to create a maintenance plan via Management Studio or save a plan in Management Studio using the wizard.
If I just try and create a new maintenance plan, then I get the following problem: "An OLE DB error 0x80004005 (Login timeout expired) occurred while enumerating packages. A SQL statement was issued and failed."
If I try and create any maintenance plan via the wizard, I get the following problem: "The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed."
I've doen a bit of digging on this and had initially thought it was related to the fact that I have two instances installed on 1 server. I've since updated the MsDtsSrvr.ini.xml file to point at both instances, as I thought that might have been causing the problem. That hasn't helped at all. Edited example of xml file is below:
We have a server instance on SQL Server 2005 SP2 build 3042. We have a 32 bit x86 server. We attempted to upgrade to SP2 build 3054 KB934458. And we got the following error as stated in the Summary.txt file.
Code Snippet ********************************************************************************** Product Installation Status Product : SQL Server Database Services 2005 (MSSQLSERVER) Product Version (Previous): 3042 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log Error Number : 29538 Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again. ----------------------------------------------------------------------------------
The client tools and workstation components were successfully installed. The server is still reporting build 3042.
Here is the portions of the HotFix.log file.
Code Snippet 05/12/2008 09:19:09.041 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log 05/12/2008 09:19:09.072 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller" 05/12/2008 09:19:09.103 Registry: Cannot read registry key value "Debug" 05/12/2008 09:21:29.382 MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again. 05/12/2008 09:22:33.678 MSP returned 1603: A fatal error occurred during installation. 05/12/2008 09:22:33.724 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
I am using ODBC to connect SQL Server 2000 + SP4 server runnig on Windows 2003 standard edition Server +SP1. But, sporadically my application server connectivity to DB fails and i receive the following error messages
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (WrapperWrite()). [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.) In D:de.cpp 702 Apr 12 2006 20:34:47 [Microsoft][ODBC SQL Server Driver]Communication link failure) In D:de.cpp 702 Apr 12 2006 20:34:47 20071017 08:23:10 TID (00000ff0) Sev (3) Err (0) Msg (Read failure. General SQL error.
Strange thing is that i receive this error only sporadically, Please Please advice !
I am basically a sybase guy but unfortunately I need to patch a SQL server with SP3. This is the first time I will be doing that. So I am not sure that after applying SP3, if I would need to rebuild all databases again.
Could anybody tell me what and where is the impact when we install SP3..??
In my package i have column called "optinout" coming from source file which has the value "start" and "stop", now in my destination table i have a column called "contact permission code" to which i need to apply a business rule based on the value in column "optinout" the rule is as stated "Contact Permission Code" is OptOut if "OptInOut" value is "STOP" else OptIn.
Hi guys, ive search high and low for info regarding the "-UseInprocLoader" (in-process BULK INSERT command ) though to no avail. Their are only brief overviews on this property.
does anyone know or have detailed info on the "-UseInprocLoader" Property
I am trying to install the eval version of Reporting Services. One of the requirements for installing this is to have SQL Server 2000 with service pack 3a. I've downloaded the service pack and followed the instructions documented by Microsoft (applying SQL2KSP3.exe, then SQL2KASP3.exe).
It appears that the application of the service packs did nothing. No errors where returned after the executable was run. But, after having applied these service packs, the version has not changed. I have restarted the service, and the server with no success. The version that is returned is 'Microsoft SQL Server 2000 - 8.00.194'.
I am running MSSQL server Developer Edition, running on Windows 2000 Professional (service pack 4).
Any suggestions. I have even uninstalled the SQL server and re-applied the service packs, so I really am having trouble trying to figure out what to do next.
When I try to run SQL Server 6.5 Service Pack 5a, I consistently receive the error message
"Setup initialization could not be successfully completed. cfgchar.exe could not be executed. Please check the relevant out file."
I am currently at Service Pack 3.
1) I have insured that the PATH environment variable does not contain quotes. 2) I have no other applications running at the same time as the service pack is running.
The contents of the cfgchar.out file appear as follows:
Are there any guidelines or best practices for deploying or testing Service Packs? What types of tests should be performed prior to upgrading or do I just trust Microsoft?
I need to modify an already existing stored procedure, which takes three parameters. Currently it uses exclusively "or" logic to apply the parameters to a select statement. e.g.
and (adid = @adID or (editorID = @editorID and aa.editorTypeID = 1))
What I need it to do is to apply a different "and/or" logic depending on what is supplied. If two or three parameters are supplied then it needs to use "and" logic to join them. Howver, if just one parameter is supplied then it should search on that parameter alone - which it won't do if I just join them all together using "and" by default.
The work has to be done inside the T-SQL, not in the calling code. I only know two ways of doing this. Firstly to create different stored procedures and use the calling code to pick one or the other depending on supplied parameters. The other is to do if/or login inside the SP itself on the values of the parameters. Either way presents something of a maintenance nightmare. Is there any other way to do this?
Hello, I have setup web sync from wm 5.0 and it seems to crash when applying the snapshot. Looking at the column definitions it seems fine. Am I missing something? Thanks in advance.
John
The identity column must be either an integer or big integer data type and cannot be NULL. HRESULT 0x80004005 (25551)
I have never applied a service pack to sql server 2000. Someone tells me that you have an option of supplying the SA password but do not have to and the service pack is applied just as if you did supply the SA password. This sounds odd to me. So, is it true? I am asking because our server instance shows "SP4" but a fix that was supposed to be included in SP4 was apparently not as the problem persists (link from sql server 2005 to 2000 fails when referenced in sql2005). I was thinking that whoever ran the service pack may not have provided the SA password so some of the SP4 was not applied???
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "s-1". The provider supports the interface, but returns a failure code when it is used.
Ok I already have a database layed out with several tables and relationships set up, and i went ahead and built a bunch of pages that I was planning on using. While i was doing this I ran into 2 problems, the first was i wrote some SQL statements to insert data from input boxes into some tables i have in my database, i used a catch exception statement as well as a if/else statement to handle the transfer to diffirent pages like a signup succeded or failed, the problem im having is that the data isnt saving into the database. (I was modeling my code after the Video 8 in the Learning SQL server 2005 Express Edition for Beginners Video Series.... I actually got them to work......sorta....) When i test it no exceptions are thrown and it continues on like nothing went wrong. The other Problem i ran into was i realized i wanted to use the memberships and roles provided by ASP.NET 2.0, and since i already created the pages for the site, i was wondering if there was a way to add them in. This site isnt anything fancy at all, i wanted to try and create a app where users sign up and create an account on the site, but i also wanted to have the flexability to insert and retrieve data from the database with out having to be stuck in the templates. Sorry for the long story im trying to give all the info possible. Any help on this would be great! Thanks!
I have some C# code written a little while that imports data nightly into a database. Most of the data is typically deleted from the tables and imported again. There are some tables where data is never deleted and references other tables. Because there are constraints between these tables, the code processes the import in the following sequence.
get constraints from database->drop constraints->delete data->apply constaints->import data
I was curious how I can accomplish similiar results in SSIS. I know I can execute a process task to manage the constraints, but I was wondering if there is any other way.
I'm retrieving data from a cube using a datareader, all the measures have format string, but when retrieve from Integration services it's lost.
I know there is a way to get the format string as columns using extended properties of the conection. I haven't tried this yet, but is there any way of reapplying this format to the columns using this format strings??
I am DBA and have worked for 3 years on sql Server 7 production servers. I briefly looked at SQL 2000 on desktop edition.
Should I be worried about applying for dba positions which have SQL 2000 production server environment. Companies will ask how much SQL 2000 experiance I have. I feel a little nervous as I have not the exposure to a live SQL 2000 production server environment. From what I have seen the bread and butter DBA tasks have not changed between sql 7 and sql 2000. I am hoping to get the opinion of fellow DBA's on this subject. Thanks Pargat
We need to apply the transactional log for business hours (9-5) everyday to a oracle instance which will be seeded with SQL Data for once. And then every day the transactional log would be applied.
We need to do this as eventually this server is moving to oracle.
At this point if somebody could help me to read the transactional log that would be great.
I am DBA and have worked for 3 years on sql Server 7 production servers. I briefly looked at SQL 2000 on desktop edition.
Should I be worried about applying for dba positions which have SQL 2000 production server environment. Companies will ask how much SQL 2000 experiance I have. I feel a little nervous as I have not the exposure to a live SQL 2000 production server environment. From what I have seen the bread and butter DBA tasks have not changed between sql 7 and sql 2000. I am hoping to get the opinion of fellow DBA's on this subject. Thanks Pargat
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?
I have a 2 way cluster and I want to apply SP4 on it.
Basically, I have 2 servers. Server A runs a default instance and another instance. While the default services is disabled and the other instance is running, Server B runs the default instance and has the other instance disabled. This basically acts like a 2 way cluster (active/passive).
How can I apply SQL Server 2000 SP4 on the 2 servers and have all the nodes come up the correct way? What are the steps to achieve this?
Hi, i have created a rdl file with 10 columns.Also i have an aspx page which will list the ten columns. The user can select some columns and on clicking report button report will be generated in PDF format(Using the rdl file). Now i want to apply style sheet to the report dynamically from aspx page.. how to do that..Help me. Thanks in advance
Apologies if this question is similar to one posted under "Click once deployment" but I got no replies and I REALLY need to know the answer to my problem!
I am using VB on VS 2005 Express and SQL Server 2005 Express.
My application is nearing the stage where I can start to use real data (from the end user) for testing purposes. Once I am as happy as I can be, I will install the application on the user's machine and he will use the application for a few weeks, with real data, before giving me a list of problems/suggested improvements etc.
I will then need to make the changes and re-install the application on his machine without losing all the changes he has made to the DB in those weeks.
Presumably, there must be a way of updating the executables without making changes to the DB on the client machine.
This is a very serious issue for me as the data will be around 2,000 records each of over 60 fields and the raw data will come from a variety of sources including paper so the data inputting will be a massive task that I do not want to repeat!
Also, if the application were ever to be sold, then other users would want to apply updates to the software whilst keeping their own data secure.
I have tried re-publishing and installing the application after setting the Publish Status of the DB files to "Exclude" but the newly installed application fails to connect to the old version of the DB.
I would very much appreciate any help in this matter as I hope I haven't just wasted several months of coding!
A failure occurred when accessing 'MSmerge_contents_table290_forall.bcp' due to an operating system error [3='The system cannot find the path specified.'] during Web synchronization. Ensure that the -InternetLogin user when using basic authentication and the user running the merge when using Windows integrated authentication has been granted access to the snapshot share.
A failure occurred when accessing 'MSmerge_contents_table290_forall.bcp' due to an operating system error [3='The system cannot find the path specified.'] during Web synchronization. Ensure that the -InternetLogin user when using basic authentication and the user running the merge when using Windows integrated authentication has been granted access to the snapshot share.
The processing of the response message failed.
I've tried compressing the snapshot, and can see the bcp file in the snapshot.
