SP2 Didn't Upgrade SQL Server Tools And Workstation Components
Mar 13, 2007
Greetings,
I thought I had applied sp2 successfully but I discovered when I tried to apply the hotfix ( sqlserver2005-kb933097-x86-enu.exe), that the SQL Server Tools and Workstation Components wasn't at the 3042 level.
The recommendation in the log file is to:
"Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch."
Does anyone know where I find the prerequisite patch?
Any help would be appreciated.
Regards Noel
Time: 03/13/2007 18:05:39.045
KB Number: KB933097
Machine: NOEL_EVO
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3152
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 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER
SQL Server Analysis Services 2005 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER
SQL Server Reporting Services 2005 (SQL2005) ENU SP1 9.00.3042.00 x86 DEVELOPER
SQL Server Notification Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER
SQL Server Integration Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER
SQL Server Tools and Workstation Components 2005 ENU SP1 9.1.2153 x86 DEVELOPER
**********************************************************************************
Products Disqualified & Reason
Product Reason
SQL Server Tools and Workstation Components 2005 The product instance SQL Tools does not have prerequisite update 3042 installed. Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation.
I have installed successfully Microsoft SQL server 2005 in MSCS.
However the set up did not install Workstation components (client tools - SSMS etc).
I have successfully installed workstation components in one node of cluster.
However setup is giving following error while installing workstation components on other node. (From this node MS SQL server 2005 was installed).
Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
I did "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, /setup".
It executed but no error, no output.
Any gues, help in isolating issue?
Any more information required.(Media is ok. Setup has been tried after reboot. There is enough disk space.)
Regards.
Mahesh =========== Setup
1) Microsoft Cluster of two nodes. 2) Hardare - HP Blade servers 3) OS - Windows 2003 EE with SP2 4) SQL Server 2005 Standard Edition with SP2.
=============================
MSI (s) (B0:7C) [17:40:20:390]: Note: 1: 1722 2: SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A 3: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe 4: /setup MSI (s) (B0:7C) [17:47:23:609]: Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
MSI (s) (B0:7C) [17:47:35:921]: Note: 1: 1729 MSI (s) (B0:7C) [17:47:35:921]: Product: Microsoft SQL Server 2005 Tools -- Configuration failed.
MSI (s) (B0:7C) [17:47:35:953]: Cleaning up uninstalled install packages, if any exist MSI (s) (B0:7C) [17:47:35:953]: MainEngineThread is returning 1603 MSI (s) (B0:A0) [17:47:36:062]: Destroying RemoteAPI object. MSI (s) (B0:80) [17:47:36:062]: Custom Action Manager thread ending.
When I install SQL Server 2005, it all goes well except that it fails to install these two:
- SQLXML 4
- workstation components and tools
When I try to install these two from the CD in the Setup folder of the CD 2 with the files sqlxml4.msi and sqlRun_Tools.msi (if I remember these names correctly), it gives me an error:
'Ce package d'installation n'est pas pris en charge par ce type de processeur'
Sorry. My SQL CDs are in french, but it roughly translates to the message:
This installation package is not taken by this processor.
I thought that my hardware configuration does not meet the requirements. But I have a Pentium 4, 2Gig RAM, over 100Gig free HD space. Also I tried to install on other computers to no avail. This is a fresh install, that is, there is no previous SQL Server 2000 in it, no VS.NET 2005 or before. Nothing. I have just a fresh, new computer.
Everytime I do an install of SQL Server 2005 and I don't select to install all components (even if I make sure Workstation components and all sub components are selected) SQL Management Studio never loads. The setup completes without error however there is no SQL Management Studio anywhere on the system. I know I have searched hard for it. Has anyone else had this problem? Am I missing something?
I've got VS 2008 Pro installed, as well as SQL Sever 200 (which I must keep installed). When I run the install for SQL Server 2005 developer edition, it continually fails to install
I had a perfectly good working copy of SQL Server 2005 installed. However, at some point I needed the Report Services Designer so I could edit my reports in Visual Studio. I inserted the CD and selected the feature from the list and it installed. Only problem being that it has completely removed my Management Studio and practically every other tool I didnt explicitly checked when installing the RS Designer.
When I tried to run the same Setup again and check everything, it tells me that there is no change between what I have selected and what is installed, which sounds like total bs to me, since my pc doesnt have a management studio etc anymore.
Out of pure misery I decided to remove my entire SQL Server installation, inc Instance, hoping to start anew and achieve the result I wanted with the least amount of frustration. I ended up here and followed it all the way: http://support.microsoft.com/kb/909967
When I started reinstalling, I ran into something new. The installer refuses to let me install anything but the Workstation components, books online and development tools. All the other options are greyed out and not even available.
Someone please help me get my SQL Server back up and running because I'm getting hopeless.
It appears that there is no way to install SQL Server 2005 Workstation Components on an x86 operating system (XP in this case) if you have the x64 install disks (Standard Edition). Can someone verify this?
I am finding it hard to believe that workstation components for a standard Windows client environment are not distributed with the version of SQL Server that matches Windows 2003 x64.
Hey yall. I'm a DBA in a company where I do NOT have the ability tocontrol who logs into my SQL servers as administrator, so I'm lookingfor a way to uninstall the workstation components WITHOUT completelyuninstalling all of my instances. Does anyone know how to do this?All I can find is the complete removal option in add/remove, and theinstall cd setup doesn't have a remove function that I can find. Anyidea's?The reason for wanting to do this is so that every tom dick and harrythat logs in as administrator doesn't have the ability to just open EMand do what they please. I want to force people to log in fromanother box so I can get tighter control over who can access mydatabases. Any help is awesome, thanks!Joshua Austill
Hello. I am trying to install only the Workstation Components portion of SQL Server 2005 and I get about halfway through and the installation errors out. The error is:
This happens after the second disk of the installation is about halfway through installing and then it throws an error stating that "The wrong volume is in the drive. Please insert volume SQLSRVRS into drive D. Cancel, Try Again, Continue" I replace the disc with the first disc and if I pick "Continue" it will display the error above. If I pick "Try again" the installation finishes, but there are components missing from Visual Studio.
I have installed the Workstation components on my local PC, which also contains VS 2005 and SQL Express. I installed the WS components so that I could run the full blown version of SQL Management Studio from my PC, to remove SQL 2005 servers.
I tried to update the Workstation components to SP1, but the SP1 package stops at the Setup Support Files, step and terminates claiming the package does not support SQL Express. I realize the package is not intended for Express, I simply need to update Management studio.
I tried running the Post SP1 Tools hotfix and it complains that it will not update SP0 of the tools.
I have successfully updated Express to SP1 and applied the Post hotfixes as well. Is there any way to patch just Management studio on a system with Express installed?
I have Vista Ultimate (IIS Enabled), SQL Server 2005 Developer Edition (downloaded and ran the SP2 Update), Visual Studio 2008. VS2008 installs no problem. When I install SQL Server 2005, I get an error when it trys to install the last part( Workstation Components, Management Studio, etc). I have tried FULLY, MANUALLY removing all SQL products and registry entries. I have used Windows Installer Cleanup Utility. I have tried Microsoft's recommended way of manually removing SQL Server 2005. If I manually run SqlRun_Tools.msi the error comes up right away.
The error is: "A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component."
Here's the Setup Error log: http://toby.pastebin.com/f63405e24 Any help?! Thanks! -Toby
I am having trouble installing disc number 2 on sql standard 2005( I installed disc one) I get the message my workstation components are already installed etc.It will not allow me to go any further It seem like everything installed Here is my summary.... I unistalled vs 2 express 2005---I never used it...... Here is my list on my vista ultimate computer sql server business intelligence, sql server management studio, analysis services installed configuration tools documentation pefmorance tools Did I need to install disc 2 instead of disc 1? one I am using vista Please help ? I tried opening business intelligence studio it says it has compability issues Here is my log: Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Professional (Build 6000) Time : Tue Apr 29 14:13:59 2008
Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_3.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_3.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_3.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_4.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_4.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_4.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_5.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_3.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_5.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server VSS Writer Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_5.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_6.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_4.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Visual Studio 2005 Premier Partner Edition - ENU Product Version : 8.0.50727.42 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_PPESku_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_6.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Books Online (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BOL_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_6.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Integration Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_DTS.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLXML4_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQL.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLXML4_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Analysis Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_AS.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Notification Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_NS.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Reporting Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_RS.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Tools Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_Tools.log --------------------------------------------------------------------------------
I'm trying to upgrade from the SCE 3.0 server tools to the 3.5 server tools. I've uninstalled the 3.0 tools and while trying to install the 3.5 tools I get an error on the IIS requirement indicating that with IIS 7.0 I need to install the backward compatibily components and can not proceed with the install.
Searching Microsoft I get hits that mention the IIS backward compatibility components, but no links on where to download them. This might be a useful link to add to the sticky with the downloads for SCE 3.5. Also, one of the requirements referneces on the SCE3.5 server tools download, indicates that the backward IIS compatibility components were supported on 32 bit OSs, no mention of 64; this also has me concerened.
I'm running Visual Studio 2008 and SQL Server 2005 on my workstation. My device has SCE 2.0, 3.0 & 3.5 on it; these all are working fine. I'm trying to upgrade everything to 3.5 so I can get rid of prior versions. From within VS2008 I can connect to SCE3.5 SDFs and have updated a couple of databases to 3.5. What I want to do is connect to the 3.5 SDFs from SQL Server 2005; which is why I am trying to install the server tools.
I've got SQL 2008 installed on a VM and am able to connect to 3.5 SDFs but I'm trying to avoid the hassle of firing the VM and schlepping files across the VM boundary to work with the 3.5 SDFs. It's becoming a pain. Which is why I am trying to install the server tools.
Is there a resolution to this? Can I get the server tools installed on a 64 bit Vista box? Is there a link for the backward compatibility tools?
We've been trying to use CozyRoc components in SQL server Data Tools. It seems like way to insert Cozy Components has been changed for SSDt as we're not getting CHOOSE ITEMS option in ToolBox(Right Click on Toolbox).link or Video where SSDT was used to Cozy Components.
I have SQL Server 2005 installed on a machine that was recently upgraded to SP2 (build 3042). The server never had the replication feature installed on it. I attempt to add replication to it and I get an error because (I think) I am installing from the initial version media (CD-ROM, build 1399) and the setup appears to want an MSI file for SP2. Any help is appreciated.
I followed the exact procedures in online help How to: Change Components in an Existing Instance of SQL Server 2005 (Setup), but after I get the Ready to Update page, I get the error box:
An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package €˜SqlRun_SQL.msi€™.
Here is a partial output of the SQLSetupxxxx_ComputerName_Core.log file:
Action 17:44:25: ResolveSource. Action start 17:44:25: ResolveSource. MSI (c) (E4!D4) [17:44:25:200]: Resolving source. MSI (c) (E4!D4) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu' MSI (c) (E4!D4) [17:44:25:200]: User policy value 'DisableMedia' is 0 MSI (c) (E4!D4) [17:44:25:200]: Machine policy value 'AllowLockdownMedia' is 0 MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Looking for sourcelist for product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Adding {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}; to potential sourcelist list (pcode;disk;relpath). MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media is enabled for product. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing net source list. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2 MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing media source list. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Trying media source H:ServersSetup. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 2203 2: H:ServersSetupSqlRun_SQL.msi 3: -2147287037 MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Source is invalid due to missing/inaccessible package. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing URL source list. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2 MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu' MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Prompting user for a valid source. MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'DisableBrowse' is 0 MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'AllowLockdownBrowse' is 0 MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Browsing is enabled. MSI (c) (E4:7C) [17:44:25:200]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media is enabled for product. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing net source list. MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2 MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing media source list. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Trying media source SQLSTDSEL;. MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing URL source list. MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2 MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:44:388]: SOURCEMGMT: Trying source H:SetupSqlRun_SQL.msi. MSI (c) (E4:7C) [17:44:44:388]: Cloaking enabled. MSI (c) (E4:7C) [17:44:44:388]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (E4:7C) [17:44:44:403]: SOURCEMGMT: Resolved source to: 'H:Setup' MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Media is enabled for product. MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (c) (E4!D4) [17:44:44:403]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Failed to resolve source MSI (c) (E4!D4) [17:44:44:419]: Transforming table Error.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038 Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'. MSI (c) (E4!D4) [17:45:02:731]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4!D4) [17:45:02:747]: Product: Microsoft SQL Server 2005 -- Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'.
Upgrade Advisor could not detect SQL Server components on the server.
===================================
The network path was not found. (mscorlib)
------------------------------ Program Location:
at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName) at Microsoft.SqlServer.UpgradeAdvisor.SqlDetection.GetClusterInfo() at Microsoft.SqlServer.UpgradeAdvisor.SqlDetection.DetectComponents() at Microsoft.SqlServer.UpgradeAdvisor.FormDetectComponents.Detect()
I've got SQL Server 2014 Developer installed, and working.  After rebooting, the event log looks like it's working fine.  However, ever since I uninstalled Visual Studio 2013 Premier and installed Visual Studio 2015 Professional, both with SQL Server Data Tools, whenever I try to start SQL Server 2014 Management Studio, I get "Cannot find one or more components. Please reinstall the application."Is there any way I can avoid uninstalling SQL Server?
I managed to solve this, based on a recommendation (at URL...).  I ran SQL Server's setup.exe, and chose Repair, and now it appears that all is well.
I am having a problem when trying to add the Client Components to an existing installation of SQL 2005 Standard Edition SP1 running on Windows 2003 Standard. The server was originally built with SQL 2005 Standard Edition and had SP1 installed at a later date. I am using the CD that SQL was originally installed with which is not a service packed copy of SQL. The reason given when clicking the details button is as follows:
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Build version check:
Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.
I am planning to Upgrade from sql server 2008 R2 to SQL 2014.
I ran Upgrade advisor 2014 on the database which i want to upgrade and the result was clean with no issues spotted.
But when i run profiler on 2008 R2 to find events like deprecation final support i see many of those in the DB which are not captured by Upgrade Advisor 2014.
Eg: Deprecation Final support in Profiler trace:SET ROWCOUNT will be removed in a future version of SQL Server.
This was not caught in Ugrade Advisor.If 2014 upgrade Advisor didn't show any issues on a database, Am i good to go with code like SP's, Triggers, Functions etc?
I "upgraded" to Windows 10 (I was installing a new c: drive anyway). Â I installed SQL Server & SSIS, Visual Studio 2012, SQL Server Data Tools 2012, etc. When I try to load up my project (.sln) in SQL Data Tools I get the following warnings/errors:
Warning 1 Warning loading DataImport.dtproj: Warning: Failed to decrypt an encrypted XML node. Verify that the project was created by the same user. Project load will attempt to continue without the encrypted information.
Warning 2 Warning loading DataImport.dtproj: Warning: Failed to decrypt sensitive data in project with a user key. You may not be the user who encrypted this project, or you are not using the same machine that was used to save the project. If the sensitive data is a parameter value, the value may be required to run the package on the Integration Services server.
Error 3 Error loading ImportFiles.dtsx: The version number in the package is not valid. The version number cannot be greater than current version number. Â
Error 4 Error loading ImportFiles.dtsx: Package migration from version 8 to version 6 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.". Â
Error 5 Error loading ImportFiles.dtsx: Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">8</DTS:Property>" from node "DTS:Property". Â
Error 6 Error loading 'ImportFiles.dtsx' : The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.Â
As well as installing Windows 10, I had also renamed by computer. Â I have tried renaming it back (I noticed some references to the computer name in the xml), but no difference.Have I installed the wrong versions of one of the software? Â If so, how could I check which one I need to install (to match the VS project/dts package)? Â
Login failed for user 'TOSHIBA-USERASPNET' I know that the file persmission for the web application have to include aspnet, so i keep resetting the folder permission for aspnet in file manager, but the login failed keeps coming back every day or two problem is after working with VS05 Pro, SQL Server Management Studio CTP, somehow the aspnet persmission get changed, use alot of sqldatasource wizards and often there is a conflict/hang between the datasource wizard and the need to have the mdf in a dettached state within VS server explorer, not sure but the procedure to fix this seems to be to reboot, detach and re-attach the mdf in the Sql server Studio tool, re-apply the aspnet file permission on the web app folders (wonder should i be doing this in IIS instead), make sure the mdf within server explorer is detached, the it works anyway, getting real tired of the resulting delays and design time derailment, clues greatly appreciated, thanks sometimes i can use View in Browser when in VS05 form view and i wont get the aspnet folder permission error and other times i do. last thing, is it a bad idea to give aspnet full permission for the entire web applicaiton??
Everything I've read says that custom data flow components are built by inheriting from the Microsoft.SqlServer.Dts.Pipeline.PipelineComponent class.
But the stock components such as the Derived Column data flow transformation must each be implemented by their own class. So how do I base my custom components on those classes? The documentation for the PipelineComponent class doesn't list any such subclasses.
In another thread Jamie Thomson very informatively said "The components in SSIS are deliberately atomic (i.e. they do something very specific) so that its easy to put them together to build something greater than the sum of the parts". Which does make a lot of sense. However, I've been finding that I end up having to create exactly the same "pattern" of combined transform components again and again in order to solve the same problem but in different dataflows (or even within the same dataflow). Cut-and-paste-tastic! In order to obtain real re-use, it seems to me like SSIS is crying out for an easy way to create new components by using composition - i.e. the ability to take commonly-used combinations of existing components and create new "super" components (without having to write Custom Transform Components in C#/VB.Net and handle everything in code).
Does anyone know if this sort of functionality is likely to make it into SSIS in the forseeable future?
I recently installed VB6.0 Enterprise on my system. As a part of the installation is the option to install SQL Server 6.5 Development. I elected to install SQL. The install went without any glitches. Upon going into SQL Enterprise Manager, I was asked to register the server where SQL was running. My understanding was that SQL would allow me to register the name of my host system. (This is a stand alone system with VB6.0 and Sql development 6.5 installed - no network attached). SQL will not allow me to register my server's name as the host server. It says that if cannot connect to the named server. SQLSERVER and SQL EXEC services appear to be running without any problems. Anyone have any idea where I should start or what could be disallowing my connection/registeration of my server. Any help would be greatly appreciated..... Thanks... Tom
Developers wanting to access sql server developer edition on XP workstation in small office network (workgroup) will have problems using windows authentication (trusted connection) if the XP "server" machine has "simple file sharing" enabled.
Simple file sharing in XP can be disabled in control panel - folder options.
For this sneak mode to work accounts with the same user and password should exist on both "client" and "server".
I have the following connection string in my Windows app that works fine on the Server: workstation id=SCSXP;packet size=4096;integrated security=SSPI;data source=scsxp;persist security info=False;initial catalog=nala But when I use that string on a workstation, it times out. I do have a Network connection to the Server. How should I modify the connection string to work on the workstation? Thanks, Bill
I am running SQL 7 (SP3) on a 2000 Server. When I configure the server as part of the Workgroup I have no problems connecting from the workstation. However, if I join the server to our 2000 domain, I cannot connect and/or register the server from the workstation through EM.
Is this a security issue? If so, what are the minimum requirements or what else am I missing. Any suggestions would be appreciated.
Could someone please tell me what I have to set at the Server side so that I will be able to STOP and START the SQL Server using Enterprise Manager and `sa` login remotely, say from the workstation.
This might not be a SQL Server question, might be something else. Ihave a workstation on a LAN that can't connect to the SQL Server. WhenI try to configure a User DSN to connect to it, the server name I wantappears TWICE in the list of possible servers. No matter which one Iselect, it can't get the connection.The workstation also can't connect through EM or QA.We've checked the user's permissions, we've re-installed some serverpacks, re-installed the Client Tools, we've even hunted through theregistry, everything looks OK, but we still can't connect. This is theonly machine on the LAN that can't connect. Everybody else connectsfine.I'm stumped. Any ideas? Anybody ever seen the server name appeartwice like that?-Emily
Hello,Is it necessary to upgrade the Client Connectivity Tools on all clientmachines after the SQL Server database server is upgraded from Version7.0 to 2000?Thank you in advance!Eddy
