Workstation Components Not Available At All On SS 2005 X64 CD For X86 XP?
Aug 9, 2006
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.
Thanks,
Chris
View 1 Replies
ADVERTISEMENT
Mar 20, 2006
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:
EventType: sql90setup
P1: installtoolsaction
P2: 0xc0000006
P3: 0x78158a35
P4: 0xc0000006
P5: setup_sqlactionenginelistener.cpp@198
P6: setup.exe@2005.90.1399.0
P7: none
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.
---------------------------------------------------------------------------------
Here is the log file:
=== Verbose logging started: 3/16/2006 14:03:49 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (58:00) [14:03:49:483]: Resetting cached policy values
MSI (c) (58:00) [14:03:49:483]: Machine policy value 'Debug' is 0
MSI (c) (58:00) [14:03:49:483]: ******* RunEngine:
******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapSetupSqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (c) (58:00) [14:03:49:483]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (58:00) [14:03:49:483]: Grabbed execution mutex.
MSI (c) (58:00) [14:03:49:483]: Cloaking enabled.
MSI (c) (58:00) [14:03:49:483]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (58:00) [14:03:49:483]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (D4:80) [14:03:49:499]: Grabbed execution mutex.
MSI (s) (D4:BC) [14:03:49:499]: Resetting cached policy values
MSI (s) (D4:BC) [14:03:49:499]: Machine policy value 'Debug' is 0
MSI (s) (D4:BC) [14:03:49:499]: ******* RunEngine:
******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapSetupSqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (s) (D4:BC) [14:03:49:499]: Note: 1: 2203 2: C:Program FilesMicrosoft SQL Server90Setup BootstrapSetupSqlRun_Tools.msi 3: -2147287037
MSI (s) (D4:BC) [14:03:49:499]: MainEngineThread is returning 3
MSI (c) (58:00) [14:03:49:499]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (58:00) [14:03:49:499]: MainEngineThread is returning 3
=== Verbose logging stopped: 3/16/2006 14:03:49 ===
Thank you very much,
BJ
View 7 Replies
View Related
Aug 7, 2006
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?
Thank,
Jim
View 2 Replies
View Related
Feb 15, 2007
Hello.
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.
Can anyone help, please?
Jean
View 10 Replies
View Related
Apr 29, 2008
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
--------------------------------------------------------------------------------
View 6 Replies
View Related
Apr 27, 2008
Hello,
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.
View 1 Replies
View Related
Mar 10, 2008
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
SQL Setup Support Files
SQL Native Client
Backward Compatability Files
SQLXML4
Workstation Components
I'm at a complete loss here. I've googled the problem, and apparently this is not uncommon. Is there a good resolution to this?
View 6 Replies
View Related
Mar 4, 2008
Hi,
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.
-DeV
View 5 Replies
View Related
Mar 28, 2008
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
View 2 Replies
View Related
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.
View 1 Replies
View Related
Jul 11, 2007
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?
Thanks.
View 7 Replies
View Related
Feb 27, 2008
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
View 11 Replies
View Related
Sep 18, 2006
I'm having some problems debugging SQL Server stored procedures on a SQL Server 2005 server. I have installed Visual Studio 2005 on a workstation running Windows XP, now I'm trying to debug a ASP.Net web application that has some code that executes the stored procedures on a Windows 2003 Server running SQL Server 2005.
I opened VS2005 ... created a connection to the SQL Server 2005 instance ... open the Stored procedure ... right click the stored procedure name and selected Step into Stored Procedure and the following message is displayed:
Unable to start T-SQL debugging.Could not attach to SQL Server process on 'ServerName'.
Any ideas.
Thanks,
View 2 Replies
View Related
Apr 26, 2007
I'm trying to use SQL Management Studio to connect from a Vista SQL 2005 client w/ SP2 over to a Windows XP workstation running SQL server developer edition (non-sp2) using windows authentication.
I'm already preauthenticated by network shares to the xp workstation. This worked just fine in windows xp but stop working in vista.
After searching around, i found out that vista handles trusted authentication differently than windows xp due to changes in the SSPI. Logging in as sql authentication works fine. Logging in as windows authentication does not.
UPDATE: I found out that two workstations running vista and sql 2005 sp2 cannot connect to each other using windows trusted authentication!!!
What the heck?
UPDATE: I found out that my IIS 7.0 using ASP.NET and connecting to SQL 2005 (non sp2) on a Windows 2003 server (SP1) WILL connect to the database using trusted authentication... apparently IIS can access the credentials and pass them to the sql 2005 box just fine. My Sql 2K5 SP2 tools cannot. I'm forced to use SQL authentication to the box.
Same thing applies with a Windows XP SP2 box running SQL 2005 (non sp2).
Here is my sql server error log off of the windows xp workstation:
2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2.
2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100]
2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1.
2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]
How can i Fix this issue?
[1] Client side:
What is the connection string in you app or DSN?
N/A
If client fails to connect, what is the client error messages?
Is the client remote or local to the SQL server machine?
Remote
Can you ping your server?
YES
Can you telnet to your SQL Server?
YES
What is your client database provider?
SQL Management Studio
Is your client computer in the same domain as the Server computer?
WorkGroup
What protocol the client enabled?
Shared Memory & TCPIP
Do you have aliases configured that match the server name portion of your connection string?
NO
Do you select force encryption on server and/or client?
NO
[2] Server side:
What is the MS SQL version?
SQL Server 2005
What is the SKU of MS SQL?
Developer
What is the SQL Server Protocol enabled?
Shared Memory & TCPIP
Does the server start successfully?
YES
If SQL Server is a named instance, is the SQL browser enabled?
N/A
What is the account that the SQL Server is running under?
Network Service
Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider?
YES
Do you make firewall exception for SQL Browser UDP port 1434?
N/A
[3] Platform:
What is the OS version?
Client - Windows Vista Final w/ SQL Server 2005 SP2 & Network Client SP2
Server - Windows XP Professional SP2 w/ SQL 2005 Server Developer Edition
Do you have third party antivirus, anti-spareware software installed?
None
[4] Misc:
If you have certificate configuration issue: Please use €œcertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question.
N/A
Tips:
1. Find SQL Server Errorlog: Default to C:Program FilesMicrosoft SQL ServerMSSQL.#MSSQLLOG
2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2.
2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100]
2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1.
2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]
[1] Client side:
What is the connection string in you app or DSN?
N/A
If client fails to connect, what is the client error messages?
Is the client remote or local to the SQL server machine?
Remote
Can you ping your server?
YES
Can you telnet to your SQL Server?
YES
What is your client database provider?
SQL Management Studio
Is your client computer in the same domain as the Server computer?
WorkGroup
What protocol the client enabled?
Shared Memory & TCPIP
Do you have aliases configured that match the server name portion of your connection string?
NO
Do you select force encryption on server and/or client?
NO
[2] Server side:
What is the MS SQL version?
SQL Server 2005
What is the SKU of MS SQL?
Developer
What is the SQL Server Protocol enabled?
Shared Memory & TCPIP
Does the server start successfully?
YES
If SQL Server is a named instance, is the SQL browser enabled?
N/A
What is the account that the SQL Server is running under?
Network Service
Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider?
YES
Do you make firewall exception for SQL Browser UDP port 1434?
N/A
[3] Platform:
What is the OS version?
Client - Windows Vista Final w/ SQL Server 2005 SP2 & Network Client SP2
Server - Windows XP Professional SP2 w/ SQL 2005 Server Developer Edition
Do you have third party antivirus, anti-spareware software installed?
None
[4] Misc:
If you have certificate configuration issue: Please use €œcertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question.
N/A
Tips:
1. Find SQL Server Errorlog: Default to C:Program FilesMicrosoft SQL ServerMSSQL.#MSSQLLOG
2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2.
2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100]
2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1.
2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]
View 48 Replies
View Related
Feb 22, 2006
We have a couple XP machines with only 256Mb of RAM and have Windows 2000 client tools installed. What are the minimum hardware requirements for SQL 2005 (Workstation) on an XP desktop?
My boss thinks since we have been blissfully ignorant and running fine with 256Mb then their is no need to upgrade memory in these machines.
I need a link to backup my argument.
This link wont help
http://www.microsoft.com/sql/editions/standard/sysreqs.mspx
As it doesn't specify workstation requirments to run SQL 2005.
View 2 Replies
View Related
Sep 7, 2006
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.
View 1 Replies
View Related
Jun 30, 2006
Hi,
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?
Regards,
Lawrie
View 6 Replies
View Related
Jan 23, 2007
I have a new customer who I am trying to document his SQL 2005 server only I am haveing a hard time telling what components are installed such as:
Replication, Full-Text Search, Analysis Services, Reporting Services, Notification Services, Integration Services, Ect.
Anyone know an easy way to check what was installed?
Shaun
View 1 Replies
View Related
Jul 31, 2006
When attempting to install SQL Server 2005 SP1, I receive the error, "a recently applied update, KB913090, failed to install." The Installation complete dialog shows the Client Components product Status as "Failure" with the description detail, "Unable to install Windows Installer MSP file". My Operating System is Windows Server 2003 SP1.
Please advise as to risks and fix.
Thanks,
Rob
View 1 Replies
View Related
Mar 22, 2008
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!D4) [17:44:44:419]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4:7C) [17:44:44:435]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:435]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
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:731]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: 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]: 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]: 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'.
Action ended 17:45:02: ResolveSource. Return value 3.
<EndFunc Name='ResolveInstallMediaPath' Return='1602' GetLastError='0'>
<EndFunc Name='BackToBootstrap' Return='1602' GetLastError='0'>
PerfTime Stop: BackToBootstrap : Fri Mar 21 17:45:02 2008
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='1602' GetLastError='0'>
Action ended 17:45:03: BackToBootstrap.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 2.
MSI (c) (E4:98) [17:45:03:013]: Doing action: UserExit
Action 17:45:03: UserExit.
Action start 17:45:03: UserExit.
MSI (c) (E4:98) [17:45:03:013]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:013]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:98) [17:45:03:028]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:7C) [17:45:03:044]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:044]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038
Action 17:45:03: UserExit. Dialog created
Action ended 17:45:04: UserExit. Return value 2.
Action ended 17:45:04: INSTALL. Return value 2.
MSI (c) (E4:98) [17:45:04:622]: Destroying RemoteAPI object.
MSI (c) (E4:64) [17:45:04:637]: Custom Action Manager thread ending.
Property(C): ProductCode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
Property(C): ProductLanguage = 1033
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductVersion = 9.2.3042.00
Property(C): MEDIAPACKAGEPATH = Setup
Property(C): ALLUSERS = 1
Property(C): NULLGUID = {00000000-0000-0000-0000-000000000000}
Property(C): ASPNetVersion = 2.0.50727
Property(C): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52152
Property(C): ARPPRODUCTICON = ARPIcon.ico
Property(C): ARPNOREPAIR = 1
Property(C): ARPSYSTEMCOMPONENT = 1
View 6 Replies
View Related
Nov 2, 2006
We have serveral app groups that have installed SQL 2005 Express, but each group have installed different components. How can I determine, specifically if the following components were previously installed.
ADDLOCAL=SQL_Engine
ADDLOCAL=SQL_FullText
ADDLOCAL=RS_Server
And if not installed re-install with the missing component??
Thanks
Tony Z
View 1 Replies
View Related
Oct 30, 2006
Hi,
I learned this from one of SSIS book-Migrating from Data Transformation Services to Integration Services in SQL.
For the design time components, Microsoft has created a special distribution called the Microsoft SQL Server 2005 DTS Designer Components. The Designer Components distribution replaces the components that get uninstalled when you upgrade your last instance of SQL Server 2000. If you want to upgrade all your SQL Server 2000 instances, this is the best and only option for recovering the DTS designer.
Is anybody heard of this 2005 DTS Designer component?
Where to download? How it works? Any experience to will be appreciated.
Thanks,
Charley
View 3 Replies
View Related
Feb 29, 2008
I was studying the SQL Server 2005 Surface Area Configuration tool to see how i could increase security.
I cannot find some of the components in “Surface area Configuration of Features�.
For example DAC appears to be missing. This is a dedicated administrator connection that allows an administrator to connect to a server.
Is this because I have SQL 2005 express instead of the professional version or could it even be to do with the operating system (XP home)
Only the following components are listed under "Database Engine":
Ad Hoc Remote Queries
CLR Integration
Native XML Web Services
OLE Automation
Service Broker
Xp_cmdshell
Thanks
View 1 Replies
View Related
Sep 28, 2006
Name: Microsoft SQL Server 2005 Tools
Hello,
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.
Any help would be greatly appreciated.
Regards
Steve
View 23 Replies
View Related
Jan 17, 2006
Please can someone give me a url or even their own list of support / unsupported components in SQL server 2005 Standard edition.
I know fuzzy lookup is not supported. Is a slowly changing dimension supported?
Its a bit difficult to tell when I get bizzare "Product level is insufficient" error for even a basic derived column transformation when executing a package using SSIS unless it is executed using a scheduled job....
thanks,
Nicole
View 3 Replies
View Related
May 25, 2007
I have Windows XP Professional Version 2002 Service Pack2.
I Have:
Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600
Service Pack is failing to Install CLIENT COMPONENTS; message is:
Product : Client Components
Product Version (Previous): 2047
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
Error Number : 29549
Error Description : MSP Error: 29549 Failed to install and configure assemblies c:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894
Error message: The system cannot find the file specified.
Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
This situation, I am guessing, also preventing me to run import/export from the SQLServer Client.
Any help is appreciated. Thanks.
View 6 Replies
View Related
Feb 11, 2008
This is a fresh install of SQL Server 2005 (64bit) on a Windows 2003 R2 SP2 64bit OS. The Cluster has been built and SQL 2005 has been installed (Database Engine(clustered), Analysis Server(clustered), Notification Server, Integration Server, Reporting Services). SQL 2005 SP2 has been installed.
Now, I want to install Notification Server, Integration Server and Reporting Services on the second node for high availability.
When I select 'Install New Components' from Add/Remove Programs, the System Configuation Checker tells me theres a version difference and to:
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.
I'm using the same binaries as the original install. Could this be a result of installing SQL 2005 SP2?
Can someone help me out with this. I'd prefer using the setup interface instead of a command line script.
View 4 Replies
View Related
Dec 14, 2007
Hi all,
I have downloaded Microsoft SQL Server 2005 Enterprise Evaluation Edition ISO from the following site and burned it onto a DVD.
http://www.microsoft.com/downloads/details.aspx?FamilyId=6931FA7F-C094-49A2-A050-2D07993566EC&displaylang=en
Prior to this I have installed Visual Studio 2005 Professional Edtion. During setup I have selected all the native client components i.e. Management Studio, Business Intelligense Studio. But after the install I am not able to see them under All Programs-> Microsoft SQL Server 2005. On further searching I have come across this link
http://channel9.msdn.com/ShowPost.aspx?PostID=142941
First of all, there is no sqlrun_tools.msi under setup folder of the dvd. And also when I tried to change component from Add/Remove programs and following the instructions as specified on clicking Change Installed components all that I see are: Connectivity Components and Software Development kit.
Could someone tell me how can I install Management Studio/ Business Intelligence Studio seperately? I don't want to go through the process of re-installation.
View 4 Replies
View Related
Oct 21, 2005
Hi all,
Yesterday, I just downloaded the SQL Server 2005 Express (SQLEXPR.EXE) and tried to install it in my Windows XP Pro PC that is on Microsoft NT 4 LAN System. I got the following error: Microsoft SQL Server 2005 CTP setup The Microfost .NET Framework 2.0 is not installed. Please install before running setup.
This morning, I downloaded the NET Framework Version 2.0 Redistributable Package Beta 2 (x86) from the Microsoft Download Center and installed it in my Windows XP Pro PC. Then I tried to install the SQL Server 2005 Express (SQLEXPR.EXE) again. This time I got a new error: SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use ADD or Remove Programs to remove these components, and then run SQL Server 2005 Setup again.
I am confused and lost in this installation problem. Was the .NET Framework Version 2.0 Redistributable Package Beta 2 (x86) a wrong Microsoft .NET Framework 2.0 I downloaded and installed in my PC? Where is the right Microsoft .NET Framework 2.0 for the SQL Server 2005 Express? Please help and advise.
Thanks in advance,
Scott Chang
View 23 Replies
View Related
May 29, 2008
Hi,
Pls let me know if SQL Server 2005 Management Studio (client tools only) is compatible with Windows Server 2000 or not?
Thanks in advance.
Regards,
Bhuvana
View 1 Replies
View Related
Dec 14, 1999
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
View 1 Replies
View Related
Jan 7, 2004
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".
At least it worked for me!
View 1 Replies
View Related
Jan 31, 2006
Hi all!Is there any function in SQL that I can use to get current date fromworkstation? All functions which I tried (now(), getdate() etc.)returns current date from server but I need date from workstation.Regards,Mirnes Lemes
View 3 Replies
View Related