The Feature(s) Specified Are Not Valid For This Edition Of SQL Server Error When Installing Management Tools On Win 2003 X64
May 23, 2007
I've successfully installed SQL Server 2005 Standard Edition on an Enterprise edition of Windows Server 2003 x64. I'm now (and also tried & failed during the install of the database engine) attempting to install the "Management Tools" component on the same server. However, in all my attempts to do so, I receive the following error:
---
The feature(s) specified are not valid for this edition of SQL Server
---
The message box does not list the features that are not valid but since the only item I've selected to install is the "Management Tools" option under "Client Components" it obviously points to something with that.
Am I missing something or are the Management Tools not supported in my config - most notably SQL Server 2005 Standard edition running on Windows Server 2003 x64?
I am attempting to install SQL Server 2005 on a Laptop with Windows 2003 Standard Edition.
The installation fails and the File Summary.txt has the following entries:
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790) Time : Fri Nov 30 09:36:53 2007
Machine : SAPDEMO Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : SAPDEMO Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : SAPDEMO Product : Microsoft SQL Server VSS Writer Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : SAPDEMO Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : SAPDEMO Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : SAPDEMO Product : Microsoft SQL Server 2005 Books Online (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_BOL_1.log -------------------------------------------------------------------------------- Machine : SAPDEMO Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLXML4_1.log -------------------------------------------------------------------------------- SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
I have been trying for 2 days now to get the SQL Server management tools installed on client machines. I'm starting to think it is not possible to do that the way we used to be able to with previous versions of SQL Server. I have installed 3rd party open source software on my own machine so that I can query the database without logging onto the server directly and would like for my co-workers to be able to do the same. As I mentioned we tried the SQL Server Management studio and all we get is a message saying to uninstall all the beta and Visual Studio *** on our machines. We stripped one machine all the way down to the OS and still kept getting that message so I'm guessing it is some new Windows Vista issue that makes SQL Server 2005 client tools completely incompatible with XP. However, we are not going to bow to Microsoft's evil ways and upgrade to their new OS just to use the SQL Server Studio. If need be I will write my own software to workaround this problem. In the meantime, can anyone recommend some good 3rd party tools that will allow us to query the SQL Server 2005 database on a server and preferably one that does not require all other software be removed first?
I'm having many many issues installing sql server management tools. i had visual studio 2005 installed first, but uninstalled and sql related things before trying to install sql server management tools again - i also deleted the program files/microsoft sql server/ folder so there are no references.
Firstly the system configuration check gives me a warning that the system doesn't meet the recommended hardware requirements - this is wrong... i've got 2.33Ghz dual core + 1gb of ram...
I select just management tools + client connectivity to install and click next -> the setup support files/native client/owc11 etc all install fine but workstation components etc fail and the setup log appears to either be empty and not available and MSXML6 fails... after clicking finish the installer appears to crash - : "Microsoft SQL Server 2005 Setup has encountered a problem and needs to close. We are sorry for the inconvenience"... I have tried all sorts of variations on this install and have had no problems in the past - please help!
The setup log from the MSXML6 failure - === Verbose logging started: 18/03/2008 12:34:09 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe === MSI (c) (5C:78) [12:34:09:067]: Resetting cached policy values MSI (c) (5C:78) [12:34:09:067]: Machine policy value 'Debug' is 0 MSI (c) (5C:78) [12:34:09:067]: ******* RunEngine: ******* Product: {AEB9948B-4FF2-47C9-990E-47014492A0FE} ******* Action: ******* CommandLine: ********** MSI (c) (5C:78) [12:34:09:067]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (5C:78) [12:34:09:067]: Grabbed execution mutex. MSI (c) (5C:78) [12:34:09:067]: Cloaking enabled. MSI (c) (5C:78) [12:34:09:067]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (5C:78) [12:34:09:067]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (28:E4) [12:34:09:113]: Grabbed execution mutex. MSI (s) (28:74) [12:34:09:113]: Resetting cached policy values MSI (s) (28:74) [12:34:09:113]: Machine policy value 'Debug' is 0 MSI (s) (28:74) [12:34:09:113]: ******* RunEngine: ******* Product: {AEB9948B-4FF2-47C9-990E-47014492A0FE} ******* Action: ******* CommandLine: ********** MSI (s) (28:74) [12:34:09:113]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (28:74) [12:34:09:113]: MainEngineThread is returning 1605 MSI (c) (5C:78) [12:34:09:113]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (5C:78) [12:34:09:113]: MainEngineThread is returning 1605 === Verbose logging stopped: 18/03/2008 12:34:09 ===
The log summary:
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Tue Mar 18 12:05:06 2008
EOC429 : The current system does not meet recommended hardware requirements for this SQL Server release. For detailed hardware requirements, see the readme file or SQL Server Books Online. Machine : EOC429 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : EOC429 Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : EOC429 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_OWC11_1.log -------------------------------------------------------------------------------- Machine : EOC429 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_BackwardsCompat_1.log --------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
I've installed Windows 2003 SP2 in a stand-alone cluster (will be adding a second node later). I'm now installing SQL Server 2005 Developer Edition 64-bit extended and would like to have the "Create a SQL Server Failover Cluster" box to not be grayed out. Even when I check the "SQL Server Database Services" box, it still has the cluster box grayed out.
Hopefully a simple question: Is it possible to use Maintenance Plans created on SQL Server Management Studio (installed as part of an instance of SQL Server 2005 Standard Ed.) to back up databases running on an instance of SQL Server Express Edition with Advanced Services? I don't need directions, just whether or not it is permitted.
I've been able to create the plans including establishing connections to from SSMS to the the SQL Express instance, but they keep erroring out. I just need to know if this is actually permitted since Maintenance Plans are not available on Management Studio Express Edition.
I just downloaded the SQL SERVER 2005 TRIAL EDITION. Where to I get the SQL Server Management Studio from? Can I use SQL Server Management Studio Express?
I am trying to install client tools on my desktop and I am getting the following error :
Edition Change Check (Warning)
Messages Edition Change Check
To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
This error , I am have seen in the logs.
The installation wizard is closing down with the above log error.
I get and error when installing MS SQL 2005 on Windows 2003 server with SP2. It bombs at the very end of the install and Microsoft notification program generated he message below to be sent to Microsoft. Please help. At a stand still. ------------------------------------------------------------------------------------------------------------------- EventType : sql90setup P1 : unknown P2 : 0x645 P3 : unknown P4 : 0x645 P5 : unknown P6 : unknown P7 : sqlserver2005_bc.msi@
Below is the summary.txt -------------------------------------
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790) Time : Thu Feb 28 22:52:28 2008
Machine : ESAPPS Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_2.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server VSS Writer Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_2.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_3.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_3.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_3.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server 2005 Books Online (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BOL_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_3.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLXML4_1.log -------------------------------------------------------------------------------- SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
hi .everyone ! i have ms visual studio 2005 with sql sever 2005 management tools
anyway .. i want to use and install sql server 2000 in this machine .. i tried to install it, but when i tried to connect to the server .. it gives me this error: "you must use sql server 2005 management tools to connect to this server"
I am having problems installing the SQL Server Compact Server Tools on my Vista laptop to allow me to connect my Mobile Device running SQL Server Compact directly to my SQL Server 2005 database through IIS.
I have done this successfully with an XP machine so I'm not sure if it is Vista problem or not.
I have installed SQL Server 2005 SP2. When I try to install the replication server tools (Sqlce30setupen.msi), in "System Configuration Check" window I get a failure on "SQL Server requirement" that says: "You must first install the Replication Components for SQL Server 2000 SP 3a or higher or the SQL Server 2005 Replication Components" and the client components are full instaled in my computer.
Yesterday I successfully installed Microsoft Visual Basic 2005 Express Edition which included SQL Server 2005 Express. Today I noticed I needed to download the Management Studio seperate download. I downloaded SQLServer2005_SSMSEE.msi and executed it and get the following error:
Error reading from file C:...SQLServer2005_SSMSEE.msi. Verify that the file exists and that you can access it..
Solved my own problem. Once I moved the msi to C: the installation worked. Apparently the path it was in was too long causing it to be unreadable. c:xxxxxxxxSQLServer2005_SSMSEE.msiSQLServer2005_SSMSEE.msi.
Hello, I hope someone knows the answer to this issue. I am trying to install SQL Server 2000 Developer Edition and once I get to the screen that is asking for the SQL Server instance and Login Information I receive the following error when trying to proceed.
(Report Server database is a different version and cannot be used for this installation)
I have installed reporting services 2000 developer edition many times and I have never seen this error.
I am trying to install sql server 2005 express edition.But i get an error stating that
sql server setup unexpectedly failed. For more information review the detup summary log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGsummary.txt
Summary.txt looks like this.It has only these 3 lines of information nothing else other this, which i have seen in many posts.
Microsoft SQL Server 2005 9.00.3042.00 ============================== OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600) Time : Tue Apr 03 22:36:33 2007
I am using windows xp. Probably many of you might have had this problem.Could anyone please provide me with some help.Thanks in advance.
I encountered an error when attempting to install Visual Basic Express Edition RTM. During the setup, I selected MSDN Express Edition and SQL Server 2005 Express Edition. Specifically, the SQL Server 2005 EE part of the installation failed. Here's the error I received:
Visual Basic 2005 Express Edition Setup Error occurred during setup Visual Basic 2005 Express Edition has been successfully installed. The following component failed to install: Microsoft SQL Server 2005 Express Edition x86
I had not installed any betas on this particular PC; however, I had already installed Visual Studio 2005 Pro and SQL Server 2005 Developer Edition.
(I selected SQL Server EE during the VBEE install because the VBEE readme said that the VSEE Editions (except for VWD) only work with SQL Server EE--so I figured I had to install SQL Server EE if I wanted to do any database work with VBEE. Is that the case?)
The following two log files were the only ones containing any error messages. How should I proceed?
C:Program Filesmicrosoft sql server90setup bootstraplogfilesSQLSetup0003_US05046_Core.log: Microsoft SQL Server 2005 Setup beginning at Mon Dec 19 14:40:32 2005 Process ID : 5824 c:211395ac6e4ed715363fsetup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2005/11/19 14:40:31 Complete: LoadResourcesAction at: 2005/11/19 14:40:31, returned true Running: ParseBootstrapOptionsAction at: 2005/11/19 14:40:31 Loaded DLL:c:211395ac6e4ed715363fxmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2005/11/19 14:40:32, returned true Running: ValidateWinNTAction at: 2005/11/19 14:40:32 Complete: ValidateWinNTAction at: 2005/11/19 14:40:32, returned true Running: ValidateMinOSAction at: 2005/11/19 14:40:32 Complete: ValidateMinOSAction at: 2005/11/19 14:40:32, returned true Running: PerformSCCAction at: 2005/11/19 14:40:32 Complete: PerformSCCAction at: 2005/11/19 14:40:32, returned true Running: ActivateLoggingAction at: 2005/11/19 14:40:32 Complete: ActivateLoggingAction at: 2005/11/19 14:40:32, returned true Running: DetectPatchedBootstrapAction at: 2005/11/19 14:40:32 Complete: DetectPatchedBootstrapAction at: 2005/11/19 14:40:32, returned true Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__5824" returned false. Running: PerformSCCAction2 at: 2005/11/19 14:40:32 Loaded DLL:C:WINNTsystem32msi.dll Version:3.1.4000.2435 Loaded DLL:C:WINNTsystem32msi.dll Version:3.1.4000.2435 Complete: PerformSCCAction2 at: 2005/11/19 14:40:33, returned true Running: PerformDotNetCheck at: 2005/11/19 14:40:33 Complete: PerformDotNetCheck at: 2005/11/19 14:40:33, returned true Running: ComponentUpdateAction at: 2005/11/19 14:40:33 Complete: ComponentUpdateAction at: 2005/11/19 14:41:6, returned true Running: DetectLocalBootstrapAction at: 2005/11/19 14:41:6 Complete: DetectLocalBootstrapAction at: 2005/11/19 14:41:6, returned true Running: LaunchLocalBootstrapAction at: 2005/11/19 14:41:6 Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1706 Aborting queue processing as nested installer has completed Message pump returning: 1706
C:Program Filesmicrosoft sql server90setup bootstraplogfilesSQLSetup0003_US05046_Core(Local).log: Microsoft SQL Server 2005 Setup beginning at Mon Dec 19 14:41:10 2005 Process ID : 5476 c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2005/11/19 14:41:9 Complete: LoadResourcesAction at: 2005/11/19 14:41:9, returned true Running: ParseBootstrapOptionsAction at: 2005/11/19 14:41:9 Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2005/11/19 14:41:9, returned true Running: ValidateWinNTAction at: 2005/11/19 14:41:9 Complete: ValidateWinNTAction at: 2005/11/19 14:41:9, returned true Running: ValidateMinOSAction at: 2005/11/19 14:41:9 Complete: ValidateMinOSAction at: 2005/11/19 14:41:9, returned true Running: PerformSCCAction at: 2005/11/19 14:41:9 Complete: PerformSCCAction at: 2005/11/19 14:41:9, returned true Running: ActivateLoggingAction at: 2005/11/19 14:41:9 Complete: ActivateLoggingAction at: 2005/11/19 14:41:10, returned true Running: DetectPatchedBootstrapAction at: 2005/11/19 14:41:10 Complete: DetectPatchedBootstrapAction at: 2005/11/19 14:41:10, returned true Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__5476" returned false. Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions: Condition "Setup is running locally." returned true. Running: PerformDotNetCheck2 at: 2005/11/19 14:41:10 Complete: PerformDotNetCheck2 at: 2005/11/19 14:41:12, returned true Running: InvokeSqlSetupDllAction at: 2005/11/19 14:41:12 Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.1399.0 <Func Name='DwLaunchMsiExec'> Examining 'sqlspars' globals to initialize 'SetupStateScope' Opening 'MachineConfigScope' for [US05046] Trying to find Product Code from command line or passed transform If possible, determine install id and type Trying to find Instance Name from command line. No Instance Name provided on the command line If possible, determine action Machine = US05046, Article = WMIServiceWin32OSWorking, Result = 0 (0x0) Machine = US05046, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0) Machine = US05046, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0) Machine = US05046, Article = WMIServiceReadRegWorking, Result = 0 (0x0) Machine = US05046, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0) Machine = US05046, Article = WMIServiceCIMDataWorking, Result = 0 (0x0) Machine = US05046, Article = XMLDomDocument, Result = 0 (0x0) Machine = US05046, Article = Processor, Result = 0 (0x0) Machine = US05046, Article = PhysicalMemory, Result = 0 (0x0) Machine = US05046, Article = DiskFreeSpace, Result = 0 (0x0) Machine = US05046, Article = OSVersion, Result = 0 (0x0) Machine = US05046, Article = OSServicePack, Result = 0 (0x0) Machine = US05046, Article = OSType, Result = 0 (0x0) Machine = US05046, Article = AdminShare, Result = 0 (0x0) Machine = US05046, Article = PendingReboot, Result = 0 (0x0) Machine = US05046, Article = IEVersion, Result = 0 (0x0) Machine = US05046, Article = DriveWriteAccess, Result = 0 (0x0) Machine = US05046, Article = COMPlus, Result = 0 (0x0) Machine = US05046, Article = ASPNETVersionRegistration, Result = 0 (0x0) ******************************************* Setup Consistency Check Report for Machine: US05046 ******************************************* Article: WMI Service Requirement, Result: CheckPassed Article: MSXML Requirement, Result: CheckPassed Article: Operating System Minimum Level Requirement, Result: CheckPassed Article: Operating System Service Pack Level Requirement, Result: CheckPassed Article: SQL Compatibility With Operating System, Result: CheckPassed Article: Minimum Hardware Requirement, Result: CheckPassed Article: Pending Reboot Requirement, Result: CheckPassed Article: Default Installation Path Permission Requirement, Result: CheckPassed Article: Internet Explorer Requirement, Result: CheckPassed Article: Check COM+ Catalogue, Result: CheckPassed Article: ASP.Net Registration Requirement, Result: CheckPassed <Func Name='PerformDetections'> 0 <EndFunc Name='PerformDetections' Return='0' GetLastError='0'> Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 <EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'> Complete: InvokeSqlSetupDllAction at: 2005/11/19 14:42:59, returned true Running: SetPackageInstallStateAction at: 2005/11/19 14:42:59 Complete: SetPackageInstallStateAction at: 2005/11/19 14:43:1, returned true Running: DeterminePackageTransformsAction at: 2005/11/19 14:43:1 Complete: DeterminePackageTransformsAction at: 2005/11/19 14:43:5, returned true Running: ValidateSetupPropertiesAction at: 2005/11/19 14:43:5 Complete: ValidateSetupPropertiesAction at: 2005/11/19 14:43:5, returned true Running: OpenPipeAction at: 2005/11/19 14:43:5 Complete: OpenPipeAction at: 2005/11/19 14:43:5, returned false Error: Action "OpenPipeAction" failed during execution. Running: CreatePipeAction at: 2005/11/19 14:43:5 Complete: CreatePipeAction at: 2005/11/19 14:43:5, returned false Error: Action "CreatePipeAction" failed during execution. Action "RunRemoteSetupAction" will be skipped due to the following restrictions: Condition "Action: CreatePipeAction has finished and passed." returned false. Running: PopulateMutatorDbAction at: 2005/11/19 14:43:5 Complete: PopulateMutatorDbAction at: 2005/11/19 14:43:5, returned true Running: GenerateRequestsAction at: 2005/11/19 14:43:5 SQL_Engine = 3 SQL_Data_Files = 3 SQL_Replication = 3 SQL_FullText = -1 SQL_SharedTools = 3 SQL_BC_DEP = -1 Analysis_Server = -1 AnalysisDataFiles = -1 AnalysisSharedTools = -1 RS_Server = -1 RS_Web_Interface = -1 RS_SharedTools = -1 Notification_Services = -1 NS_Engine = -1 NS_Client = -1 SQL_DTS = -1 Client_Components = 3 Connectivity = 3 SQL_Tools90 = -1 SQL_WarehouseDevWorkbench = -1 SDK = 3 SQLXML = -1 Tools_Legacy = -1 TOOLS_BC_DEP = -1 SQL_Documentation = -1 SQL_BooksOnline = -1 SQL_DatabaseSamples = -1 SQL_AdventureWorksSamples = -1 SQL_AdventureWorksDWSamples = -1 SQL_AdventureWorksASSamples = -1 SQL_Samples = -1 Complete: GenerateRequestsAction at: 2005/11/19 14:43:11, returned true Running: CreateProgressWindowAction at: 2005/11/19 14:43:11 Complete: CreateProgressWindowAction at: 2005/11/19 14:43:12, returned false Error: Action "CreateProgressWindowAction" failed during execution. Running: ScheduleActionAction at: 2005/11/19 14:43:12 Complete: ScheduleActionAction at: 2005/11/19 14:43:13, returned true Skipped: InstallASAction.11 Skipped: Action "InstallASAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.18 Skipped: Action "InstallASAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.22 Skipped: Action "InstallASAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.9 Skipped: Action "InstallASAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result. Skipped: InstallDTSAction Skipped: Action "InstallDTSAction" was not run. Information reported during analysis: No install request found for package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.11 Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.12 Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.18 Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.22 Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.9 Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result. Skipped: InstallNSAction Skipped: Action "InstallNSAction" was not run. Information reported during analysis: No install request found for package: "ns", install will be skipped as a result. Skipped: InstallNSAction.11 Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.12 Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.18 Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.22 Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.9 Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result. Skipped: InstallRSAction.11 Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.18 Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.22 Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result. Running: InstallSqlAction.11 at: 2005/11/19 14:43:14 Installing: sqlsupport on target: US05046 Complete: InstallSqlAction.11 at: 2005/11/19 14:43:26, returned true Running: InstallSqlAction.12 at: 2005/11/19 14:43:26 Installing: sqlncli on target: US05046 Complete: InstallSqlAction.12 at: 2005/11/19 14:43:40, returned true Skipped: InstallSqlAction.18 Skipped: Action "InstallSqlAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "sql", install will be skipped as a result. Running: InstallSqlAction.21 at: 2005/11/19 14:43:40 Installing: sqlwriter on target: US05046 Failed to install package Fatal error during installation. Setting package return code to: 1706 Complete: InstallSqlAction.21 at: 2005/11/19 14:43:50, returned false Error: Action "InstallSqlAction.21" failed during execution. Error information reported during run: Target collection includes the local machine. Invoking installPackage() on local machine. Skipped: InstallSqlAction.22 Skipped: Action "InstallSqlAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "sql", install will be skipped as a result. Running: InstallSqlAction.9 at: 2005/11/19 14:43:50 Installing: msxml6 on target: US05046 Complete: InstallSqlAction.9 at: 2005/11/19 14:43:54, returned true Running: InstallToolsAction.11 at: 2005/11/19 14:43:54 Installing: sqlsupport on target: US05046 Complete: InstallToolsAction.11 at: 2005/11/19 14:44:2, returned true Running: InstallToolsAction.12 at: 2005/11/19 14:44:2 Installing: sqlncli on target: US05046 Complete: InstallToolsAction.12 at: 2005/11/19 14:44:11, returned true Skipped: InstallToolsAction.13 Skipped: Action "InstallToolsAction.13" was not run. Information reported during analysis: No install request found for package: "PPESku", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.18 Skipped: Action "InstallToolsAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.20 Skipped: Action "InstallToolsAction.20" was not run. Information reported during analysis: No install request found for package: "BOL", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.22 Skipped: Action "InstallToolsAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "tools", install will be skipped as a result. Running: InstallToolsAction.9 at: 2005/11/19 14:44:11 Installing: msxml6 on target: US05046 Complete: InstallToolsAction.9 at: 2005/11/19 14:44:15, returned true Action "InstallSqlAction" will return false due to the following preconditions: Condition "Action: InstallSqlAction.21 has finished and failed." returned true. Installation of package: "sql" failed due to a precondition. Step "InstallSqlAction" was not able to run. Skipped: InstallNSAction.10 Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis: No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result. Running: InstallToolsAction at: 2005/11/19 14:44:15 Installing: tools on target: US05046 Complete: InstallToolsAction at: 2005/11/19 14:44:26, returned true Skipped: InstallToolsAction.10 Skipped: Action "InstallToolsAction.10" was not run. Information reported during analysis: No install request found for package: "sqlxml4", referred by package: "tools", install will be skipped as a result. Skipped: RepairForBackwardsCompatRedistAction Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis: Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run: Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchMSDE2000" failed due to a precondition. Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run: Action: "UninstallForSQLAction" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchLibertySql" failed due to a precondition. Skipped: InstallASAction Skipped: Action "InstallASAction" was not run. Information reported during analysis: No install request found for package: "as", install will be skipped as a result. Skipped: InstallRSAction Skipped: Action "InstallRSAction" was not run. Information reported during analysis: No install request found for package: "rs", install will be skipped as a result. Skipped: UninstallForRS2000Action Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis: Action: "UninstallForRS2000Action" will be skipped due to the following condition: Condition "Action: InstallRSAction was skipped." returned true. Running: ReportChainingResults at: 2005/11/19 14:44:27 Error: Action "ReportChainingResults" threw an exception during execution. One or more packages failed to install. Refer to logs for error details. : 1706 Error Code: 0x800706aa (1706) Windows Error Text: The endpoint format is invalid.
Source File Name: sqlchainingsqlchainingactions.cpp Compiler Timestamp: Thu Sep 1 22:23:05 2005 Function Name: sqls::ReportChainingResults::perform Source Line Number: 3097
I get the following error installing SQL Server 2005 Developer Edition
Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90DTSTasksMicrosoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087 Error message: Unknown error 0x80131501 Error description: You must have administrative credentials to perform this task. Contact your system administrator for assistance.
I am installing on Windows XP with Admin privs.
There is nothing listed in COM+ Services for SQL.
The Distributed Transaction Coordinator service is running.
There is a previous installation of SQL 2000 Developer Edition installed.
I have seen some pretty old posts with the same error.
I was wondering if there was a final resolution, service pack, etc. that solves this problem?
After installing SQL Server 2005 Express Edition on Windows Vista RC1, I wanted to install also the Managent Studio but I always receive the following error message:
"Bei der Installation dieses Pakets ist ein unerwarteter Fehler aufgetreten. Es liegt eventuell ein das Paket betreffendes Problem vor. Der Fehlercode ist 29506."
Where can I find more infos about this error-code?
I have recently installed the SQL Server Management Studio Express but I do not find Management Tools in order to create scheduled backups and shrinking of the databases. I was under the impression that this should be included in the Management Studio. I use the SQL 2005 Express for smaller customers who run the SQL on a desktop unit. I need a way to backup the data to a server machine for backup purposes. I have uninstalled and reinstalled to no avail.
Some of the individual installs on the "Feature Pack for Microsoft SQL Server 2005 Service Pack 2 - Community Technology Preview (CTP) November 2006" page available here:
I was successfully able to installing sql server 2005 developer edition all peices except the "Workstation Component, Book Online, Development Tool", the last item in the installation list. It gave errror for bad sql.cab file. Although this developer edition came directly of the box this error came up in many attempts. Upon "Ignore" it gives error 2350.
I am able to run sql server's all the services and able to access it via VS.Net server browser. I can create and change tables etc. but there is no "Management Studio" installed. There is no icon for it either on the desktop or in the Start->SQL Server 2005 menu.
Is it possible to get and copy sql.cab file or entire client component from somewhere else? --Freed download or something? I searched for sql.cab file but it was not in the CD. It could be inside some other file or cmpressed.
Hi, I have Vista Home premium edition and trying to install SQL Server developer edition 2005 as local administrator. I have already enabled IIS 7 and have Office Ultimate 2007 installed. When I run the set up program, I get a warning titled "Program Compatibility Assistant" that my Operating system may not be compatible with the version of sql server I am installing. It says after setup is complete, I should run SP2 of SQL Server 2005 with 3 buttons as "Check for solutions online", "run this program" and "cancel"...
My question, should I select "run this program" and after the setup completes, download SP2 and apply the patch?
I read some articles in forums that sounds like lot of issues to get sql server working on vista. Can some one direct me to correct options. This is my wife's machine so I dont want to experiment too much and blow her machine away. Please help.
I recently bought a Dell server with Windows 2003 enterprise edition. I wanted the X32 version and metnioned of the same to the sales people, but somehow they put the x64 edition on the server. The database I am planning to use does not work on X64 edition as of now. How do I downgrade the OS to X32 version? Do I need to send the system back to Dell? Machine not opened yet. Or is there a way I can get software CD and downgrade to X32 version?
I've tried to installed sql server 2005 developer edition on windows vista home premium but failed many times, almost giving up. I've installed and turned on all the features of IIS 7.0 but it still failed and I tried to test IIS 7 by running the local host and received this error " HTTP Error 500.0 - Internal Server Error." I even ran the windows update SP1 for Vista and MDAC 2.8 SP1
I really appreciate any comments and help.
----- Here are the messages in the windows system check for the sql server 2005 installation:
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
I've tried to installed sql server 2005 developer edition on windows vista home premium but failed many times, almost giving up. I've installed and turned on all the features of IIS 7.0 but it still failed and I tried to test IIS 7 by running the local host and received this error " HTTP Error 500.0 - Internal Server Error." I even ran the windows update SP1 for Vista and MDAC 2.8 SP1
I really appreciate any comments and help.
----- Here are the messages in the windows system check for the sql server 2005 installation:
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
Hi -I have istalled sql server 2005 standard edition , I want to install sql server 2005 enterprise edition on the same machine. Is it possible? I have Microsoft windows server 2003 SP2 and 1GB RAM. I want to use partition function with the enterprise edition, will the trial version of sql server work for me? -If I have already created a database and tables using the standard edition, will I be able to access and use the database using the installed trial version or will I have to start a fresh creating a new database? - Is it possible to access the same database with any of the installed versions?
BTW, I am prety new to sql server and databases , I am trying to learn by myself
The installation SQL 2008 R2 Management Tools on a Windows 7 workstation fails with the error, The specified account already exists.
Final result:Â SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
 Exit code (Decimal):          -2068052700  Exit facility code:           1212  Exit error code:              1316  [code]...
I have installed SQL server 2005 enterprise edition on Windows 2003 virtual PC (full installation). The installation went through successfully. However, after install completed, I cannot find any of the client tools under the start menu -> all programs -> Microsoft SQL server 2005 menu. The only item listed under the SQL server 2005 is Configuration Tools, which is used to configure the database server.
I have tried to install the client component again (in case I didn't install them at the first place) but the installation process cannot be started since it detected that the client components have been installed already. I can also see the sql server native client running in the services.
The server engine is working fine since I can connect to that sql server using another machine where I have the client tool (SQL server management studio).
One of my friends has exactly the same problem. He installed the sql server 2005 Standard edition on windows 2003 server (full installation), but the client tools are not showing up in the start menu either.
I also checked the location for the SQL server management studio (Microsoft SQL server/90/Tools/Binn/VSShell/Common7/IDE), there is only one folder called publicAssemblies listed under. Is this correct or something is missing?
