Trying to update my local developer version of SQL Server 2005 SP1 to SP2. The setup program terminates with the following information dumped from the logs. Not sure if it is related, but I recently installed the SQL Server 2005 Compact Edition (tools, runtime, etc) on the same development machine. It is a little too deep for me to figure out
Darryl
Here are the last few lines of the HotFix.Log
04/24/2007 14:46:48.374 MSP Error: 29527 The setup has encountered an unexpected error in datastore. The action is RestoreSetupParams. The error is : Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
04/24/2007 14:46:48.822 The following exception occurred: Unable to install Windows Installer MSP file Date: 04/24/2007 14:46:48.822 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 800
Now the SQL9_Hotfix_KB921896_sqlrun_sql.msp.log shows this as the last few lines
MSI (s) (A4:38) [14:46:48:630]: Product: Microsoft SQL Server 2005 - Update 'Service Pack 2 for SQL Server Database Services 2005 ENU (KB921896)' could not be installed. Error code 1603. Additional information is available in the log file C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log.
MSI (s) (A4:38) [14:46:48:630]: Note: 1: 1729 MSI (s) (A4:38) [14:46:48:630]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:630]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (A4:38) [14:46:48:646]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:646]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:646]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (A4:38) [14:46:48:646]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:646]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (A4:38) [14:46:48:646]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:646]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (A4:38) [14:46:48:646]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:646]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (A4:38) [14:46:48:662]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:678]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:678]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (A4:38) [14:46:48:678]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:678]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (A4:38) [14:46:48:678]: Transforming table Error.
MSI (s) (A4:38) [14:46:48:678]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (A4:38) [14:46:48:678]: Product: Microsoft SQL Server 2005 -- Configuration failed.
MSI (s) (A4:38) [14:46:48:678]: Attempting to delete file c:WINDOWSInstaller6749ee3.msp MSI (s) (A4:38) [14:46:48:678]: Unable to delete the file. LastError = 32 MSI (s) (A4:38) [14:46:48:694]: Cleaning up uninstalled install packages, if any exist MSI (s) (A4:38) [14:46:48:694]: MainEngineThread is returning 1603 MSI (s) (A4:2C) [14:46:48:694]: Destroying RemoteAPI object. MSI (s) (A4:04) [14:46:48:694]: Custom Action Manager thread ending. === Logging stopped: 4/24/2007 14:46:48 === MSI (c) (58:E4) [14:46:48:694]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (58:E4) [14:46:48:694]: MainEngineThread is returning 1603 === Verbose logging stopped: 4/24/2007 14:46:48 ===
Time: 04/24/2007 14:46:48.854 KB Number: KB921896 Machine: DUTTONDARRYL1 OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Failed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Database Services (MSSQLSERVER) ENU SP1 2005.090.2047.00 x86 DEVELOPER Analysis Services (MSSQLSERVER) ENU SP1 2005.090.2047.00 x86 DEVELOPER Reporting Services (MSSQLSERVER) ENU SP1 9.00.2047.00 x86 DEVELOPER Notification Services ENU SP1 9.00.2047.00 x86 DEVELOPER Integration Services ENU SP1 9.00.2047.00 x86 DEVELOPER SQL Server Native Client ENU 9.00.2047.00 x86 Client Components ENU SP1 9.1.2047 x86 DEVELOPER MSXML 6.0 Parser ENU 6.00.3890.0 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
I've had a workstation running Windows NT 4.0 and SQL 7.0 successfully and this has just been upgraded to Windows 2000. Althogh the s/w is still on disc in the correct plance, SQL Server is no longer in the Program group from the Start menu, the SQL Server servicess aren't visible in Service Manager and the SQL Enterprise Manager icon in the folder produces an MMC error I don't recocnise or understand - Help ! What's happened where and does anyone know how I resolve this
I am trying to upgrade my MSDE 2000 (SP3)to SP4, but it is giving an error of "invalid instance".
Here is what is on the machine (before running any commands):
I do not see any SQL Server installation on my machine under Start-All Programs. But, I have a directory for SQL Server under: C:Program FilesMicrosoft SQL ServerMSSQL
The sqlserver.exe is in C:Program FilesMicrosoft SQL ServerMSSQLBinn and version = 2000.80.760.0
To upgrade MSDE 2000 (SP3) to MSDE SP4, I downloaded this file from Microsoft's website: SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE
I ran the above .exe and extracted the files on my hard drive. Now, I have the C:SQL2KSP4MSDE directory and the Setup.exe is in the MSDE directory.
I looked in the services and stopped the following service: MSSQLSERVER
I tried running: setup /upgradesp sqlrun /L*v C:MSDELog.log This command ran and did not show any error. I then rebooted the machine, checked that the MSSQLSERVER service is running and checked the version of sqlserver.exe but it was still the same (2000.80.760.0). It should have been 8.00.2039
I am not sure what am I missing. All I want to do is update the MSDE Service Pack on our company machines to SP4.
I have a request from one of our researchers to upgrade to CTP SP2. I am getting the error message:
MSP Error: 29506 SQL Server Setup failed to modify security permissions on file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData 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 added serveradministrators - full control to the permissions of Data, but it still does not work.
Has anyone else ran into this, and how do I fix it?
MSI (c) (64:F8) [11:44:29:713]: Grabbed execution mutex. MSI (c) (64:F8) [11:44:29:713]: Cleaning up uninstalled install packages, if any exist MSI (c) (64:F8) [11:44:29:713]: MainEngineThread is returning 1603 === Verbose logging stopped: 08/05/15 11:44:29 ===
the only other error I can see is this:
Action start 11:44:29: RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. MSI (s) (A8:B4) [11:44:29:651]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI19E.tmp, Entrypoint: RestoreSetupParams SOFTWAREMicrosoftMicrosoft SQL Server Setup.{FE7E950B-220A-4182-B5CA-19397244DCFD} Entering Function MyMsiEvaluateCondition MsiEvaluateCondition for SQLMSDEInstalled returned TRUE End Function MyMsiEvaluateCondition Error reading setup parameters Action ended 11:44:29: RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3. Action ended 11:44:29: INSTALL. Return value 3.
SYNTAX Used is : setup.exe /upgradesp sqlrun INSTANCENAME= SECURITYMODE=SQL UPGRADEUSER=sa UPGRADEPWD=MyPwd BLANKSAPWD=1 /L*v D:MSDE.log
Please note that I am using BLANKSAPWD=1 because BUILTINAdministrators right is not present, the above syntax is working for one named instance but is failing in second named instance.:eek:
We are in the process of going through all test steps for upgrading one of our servers with SQL 2000 to SQL 2005. Currently Server 2000, which we will be upgrading as well after SQL is upgraded and running properly. We have Reporting Services installed as well. I am using a test server which is an exact mirrored image of the live server but is not added to the domain.
I am going through the steps of selecting the components, selecting the instance, and then selecting the installed components I want to upgrade (SQL Server 8.0.??? and Reporting Services 8.0.???) and click next.
The upgrade analysis begins. Everything is ok through the SQL Server analysis but when I click next to start the upgrade analysis on Reporting Services I get this error message, "SQL Server Setup requires administrator permissions for the upgraded SQL Server instance. To continue, log in with an administrator account." I am logged in as the local admin which should have the required permissions to upgrade Reporting Services, plus the local admin was ok for the SQL Server upgrade anaylis
I have no idea what could be causing this permissions issue. I did run the SQL 2005 Updrade Analyzer utility and performed all the "before" steps. What could be the issue?
[Background] Upgraded SQL Server Express to Advanced and I started getting a user instance error. I followed the advice on some posts (most notably: http://blogs.msdn.com/sqlexpress/). I deleted the User Template Data as the instructions say but now get the error below when trying to run my application. I've tried setting User Instance = False with no luck. Also noticed after rebooting that the Template Data file was recreated but the folder is empty. Have tried re-installing the update but it says there's nothing to update! Has anyone else had this problem? Any fixes? Any help will be greatly appreciated...
Many thanx, Milt
The details:
Failed to generate a user instance of SQL Server due to a failure in copying database files. The connection will be closed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Failed to generate a user instance of SQL Server due to a failure in copying database files. The connection will be closed.
Source Error:
Line 88: /// <returns></returns> Line 89: public static ShoppingCart GetCart() { Line 90: IDataReader rdr = ShoppingCartProvider.Instance.CartGetCurrentCart(GetUserName()); Line 91: ShoppingCart cart = new ShoppingCart(); Line 92: cart.Load(rdr);
It seems like the upgrade tries to use Windows authentification although I've told it to use SQL Server authentification. Or did I miss a parameter in my command line?
If I do the upgrade manually it works without needing Windows authentification.
I upgraded a SQL 2000 installation to SQL 2005 this past weekend. Minimal issues overall, but one that did crop up relates to a linked server to an Oracle database. The linked server worked before the upgrade, and stopped working immediately after.
We're running on Windows 2003 x64, latest service pack. The linked server is set up using the MSDAORA provider. The error I'm getting post-upgrade is:
=====================
OLE DB provider "MSDAORA" for linked server "PROD" returned message "ORA-06413: Connection not open.".
Msg 7303, Level 16, State 1, Procedure RDM_GET_REP_LIST_SP, Line 12
Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "PROD".
=====================
A tnsping from the server works fine. I've also tried recreating the linked server. Any help would be appreciated. Let me know what other information would be useful.
I am attempting to upgrade a 2005 Standard Edtion to Enterprise Edition. This is a default instance. All components are upgraded successfully except the Database Engine. I receive the following error:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]The certificate cannot be dropped because one or more entities are either signed or encrypted using it.. To continue, correct the problem, and then run SQL Server Setup again.
This installation does not have encryption enabled, so I do not undersand the error or how to correct it.
After rebooting the SQL instance appears to be upgraded to Enterprise, but it cannot be upgraded to SP2.
We're going to be upgrading our Server from 6.5 to 7.0. In addition we're getting a new SQL Server Box.
Which of the following is better: a) Install SQL 6.5 on the new box, restore the DB from old box to the new box, then install 7.0 on the new box and use the upgrade wizard to upsize the DB. (We'll have room to leave the 6.5 devices on the box after upgrading.) or b) Install SQL 7.0 on the new box and upsize the db across the network (100megabit network cards).
Thanks,
Kevin M. Tupper EZLinks Golf, Inc. http://www.ezlinksgolf.com
I'm following a white paper and have run chkupg65 and am stuck at resolving keyword conflicts. I see many TechNet references about fixing them...but none about how. A little help? Below are the conflicts: Keyword conflicts Column name: SyncModification.ACTION[SQL-92 keyword] Column name: Jobs.EXPIREDATE[SQL-92 keyword] Column name: SqlStoreTable.SIZE[SQL-92 keyword] Column name: JobDetails.TIME[SQL-92 keyword] Column name: SchedulerSafeDelete.TIME[SQL-92 keyword] Column name: SMSEvent.TIME[SQL-92 keyword] Column name: SyncModification.TIME[SQL-92 keyword] Column name: vJobDetails.TIME[SQL-92 keyword] Column name: vSMSEvent.TIME[SQL-92 keyword] Column name: Sites.TIMESTAMP[SQL-92 keyword] Column name: QueryExpressions.VALUE[SQL-92 keyword]
Does anyone know of a good book or resource on what's the best way to upgrade 6.5 to 2k? Or generally how would you do that considering you need to do on more then 50 servers?
So I'm using Visual Studio's one click deployment to install/update software for users. SQL Express 2005 is the default, and I need to get all current and new users to update to SQL Express 2005 SP2. Ontop of that, I need to change the sa password for all current users (I should be able to manually set it for the new guys).
The problem I'm having is that instead of just updating the current SQL Express engine installed, it creates a new instance of the SQL Express engine when installing SQL Express SP2.
Is there anyway to just update SQL Express to SP2? Is there an easy way to change the sa password when doing so?
I have an application which installs MySQL 3.23. It's hard-coded. Irealize there are newer versions, so I am thinking, what's easiest:1) install the application with its default 3.23 and then run a scriptto convert 3.23 to 4.1 or later,or2) modify the application to install a newer version of MySQL from thestart.
I'm in the process of upgrading a gazillion apps from using .MDB files to using SQLCE 3.5. (Or, at least planning the upgrade). Is there an easy way to save existing .MDB files as .SDFs? Also, we have an occasional app that's web based (eg. certification exam, where we have 10 people take it online at the same time, in one day, and the database keeps the score, questions, etc.); is it a good idea to move that kind of app to SQLCE from MDB?
Hey, I have a SQL Server 2005 Express Edition installed, and I want to upgrade to SP2. Is there a way to configure (using the setup ini file maybe?) the installer to install only the SP2?
When I run SP3 & SP4 for SQL Server it runs okay. I get no errors after the installation & both installations call for a reboot which I do with no problems.
But yet when I get back into my machine, go to the Query Analyzer & run "Select @@version" and execute it, it's still showing v8.00.194 (Original release). It should be showing 8.00.2039.
We are upgrading our servers from 6.5 to 7.0 SQL servers. I used the same configurations on both 6.5 server and 7.0 server like ANSI and the others. But SQL7.0 server turns out to have different data on some tables. Here is the example on one table. Why?
WT_PAY_PERIOD_DATE WT_RDC_HOURS WT_RDC_EXPENSE WT_MS_SUB_HOURS WT_MS_APPR_IND WT_NEW_EMPL_FLAG ------------------------------------- -------------------------- --------------------------------- -------------------------------- ----------------------------- -------------------------------- 2002-04-20 00:00:00.000 23.50 135.2050 23.50 Y X
WT_ASSOC_OTH_EXPENSE WT_ASSOC_TOT_EXP WT_MS_TOT_EXP WT_MS_MILE_LIM ------------------------------------------- ----------------------------------- -------------------------- --------------------------- 3.7600 135.2050 135.2050 373 ************************************************** ************************************************** ************************************************** ********************** I have checked the datatypes that are transferred from SQL6.5. They are the same types as SQL6.5. Plus the configurations are the same on both 6.5 and 7.0. The question is that why the values are different? What the way is to fix it?
Well there's always a first for everything!! I have a SQL 7.0 server on sP1 and ran upgrade to sp3 and recieved error 'error in upgrade script' retry or cancel. When I retried the upgrade ended. I tried to run the upgrade again and it tries continue where it ended before, but the upgrade ends unsucessfully. I even tried extracted the sp3 exe to a diffrent folder and ran the sp3 upgrade with same results.
I started the MSSQL service ok but not able to use Query Analyzer, DTS, EM.
Get the following message:ISQL.EXE - Entry Point not found. The procedure entry point?DeleteRow@CDataCTLStorage@@UAEJJPAPAG@Z could not be located in the dynamic link library SQLGUI.dll
I get similar msgs when trying to open DTS, Enterprise manager from the server. The user databases and appear to be ok. I am able to get to Query Analyzer, etc. from my worksation fine.
Has anyone encountered this before? Is there a fix for it or do I need to rebuild the server from SP1 and restore the databases, etc.??
Has anyone attempted an upgrade from sql7 to 2000? is it a difficult process? what happens to the users. Is there a good site i can go to to get this info ?
Does anyone know how to upgrade a sql driver. Or where to get the driver dll from. The client machine is running 3.70.06.23 and needs 3.70.08.20 to connect to the sql server!
One of my students' company is doing an upgrade from SQL 6.5 to SQL 7.0 and everything converts fine except one veiw. Does anyone know what would cause this to happen? If they run the script in SQL 7.0 it works fine. Any thoughts?
CREATE VIEW dbo.vewRptWooActiveList AS SELECT vewRptWooActiveListSub1.wotUserValue1, vewRptWooActiveListSub1.wooNum, vewRptWooActiveListSub1.wooCreatedWhen, vewRptWooActiveListSub1.wooDispatchedWhen, vewRptWooActiveListSub2.MaxOfwslInsertedWhen AS wooLastStatusWhen, vewRptWooActiveListSub1.wosUserValue1, vewRptWooActiveListSub1.sitName, vewRptWooActiveListSub1.empFullName_Cp, vewRptWooActiveListSub1.Company, vewRptWooActiveListSub1.Region, vewRptWooActiveListSub1.ServiceCenter, vewRptWooActiveListSub1.Zone FROM vewRptWooActiveListSub1 INNER JOIN vewRptWooActiveListSub2 ON vewRptWooActiveListSub1.wooID = vewRptWooActiveListSub2.wsl_WooIDFk
I have a couple of 6.5 installations with different codepages/sort orders, when I come to upgrade these databases, is it possible to change the code pages/sort order during the upgrade of my existing databases so that I have the same sort order/codepages across all my sites?
The databases don't actually have any extended characters in.
All the documentation I have read talks about upgrading from SQL Server 6.x. I presume I can use the upgrade wizard to upgrade my 6.0 system directly to 7.0 without having to upgrade to 6.5 first.
Any thoughts, comments or help would be much appreciated.
Does the upgrade wizard in 7.0 help me upgrade ALL the database objects in SQL 6.5 (including stored procedures, triggers) to 7.0? Has anyone encountered any problems?
Have you ever faced a problem like this. I am running MS SQL Server 6.5 on Windows NT 4.0 computer whose name is with dashes (hou-is). Now, I try to update to version 7.0 and it gives me error message: @@nameserver from export 6.5 is not valid. Use sp_addserver and sp_netname. How you can change a sql server name to non-dash name in order to complete the upgrade sql server? I know this is a challenging tech question. I appreciate your tech expertise.
Currently running SQL Server 7, and have databases. I want to upgrade to SQL Server 2000. How can achieve it without delete or losing my databases. This is NOT a production server, BUT I still want to keep my databases. Ideally I would like to uninstall and reinstall so that there are no SQL Server 7 files lying around when I have SQL 2000 running. Thanks.
We are trying to upgrade from SQL Server v7.0 to SQL Server 2000. Here's our set up,
Current Server: Win NT, SQL Server v7.0 New Server : Win 2000, SQL Server 2000 Client (my PC): Win XP, SQL Server 2000
The New Server is designated SQL Server machine -- company-wide. That is, all the apps/projects uses this machine as the SQL Server. It only has one instance of SQL Server running.
Different project are assigned a dedicated 'Drive' (logical only) and allocated certain disk size as the work space. We (my team) will be the new entry for this server.
Q: When doing the Copy Wizard (from my PC) to upgrade/copy the existing v7.0 db (from Current Server) to New SQL Server 2000, do I need to specify the physicall 'Data' folder? Or, can I copy the database to the selected path -- which is my dedicated drive?