Error - Installing SQL Server 2005 Client Tools

Jan 5, 2007

Hello

I am trying to install sql server 2005 client tools and I get the following error:



Error code 2356 : Could not locate cabinet in stream : sql.cab

How can I go about this

Thanks

View 5 Replies


ADVERTISEMENT

Error - Installing Client Tools - Sql Server 2005

Jan 4, 2007

Hello

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.

Thanks

View 3 Replies View Related

Error Installing SQL 2005 Client Tools On Windows Vista Ultimate

Feb 29, 2008

Hi,

I am getting the following error:

0:Watson 1:1304 2treamSupportFiles 3treamBinaryToDisk
4:5 5:tyukonsqlsetupdarwinsqlcastubstreamca.cpp 6:238
7qlcastub.dll 8qlrun.msi

While installing "SqlRunTools.msi" on a Microsoft SQL Server 2005 Developer's Edition Disc 2 on Windows Vista Ultimate.

I am trying to install the Sql Server 2005 Client Tools, Enterprise Manager, Query Analyzer, on Windows Vista Ultimate.

Any ideas as to what is causing this error and how to fix it?

Thanks,

Mark

View 12 Replies View Related

Problems Installing SQL 2005 Client Tools

Mar 13, 2008

HI
I have recently installed a copy of SQL server 2005 on to a windows 2003 server. During the install I selected to install the client tools (management studio and all that) all seemed to install ok no errors but after the install there is no management studio in the start menu. I have tried uninstalling the client tools and reinstalling them again I have also tried to launch management studio by browsing to the SqlWb.exe but the program fails to initialise any ideas?

(both SQL and Windows are at SP2)

Thanks
Jon

View 2 Replies View Related

Warning Messages && Failure Installing MSSQL 2005 Enterprise Client Tools

Jul 5, 2006

I am trying to install the client tools for management purposes only on a IBM T42 laptop which meets all the hardware and software requirements listed on MS support including the HCL list, the Readme, the forums and MSDN but the install still shows the following log messages when the install fails.

AdminMessage = Setup requires user to be in the administrator group in order to continue the installation process. Setup is aborting as the current user is not in the administrator group.

(I am an adminsistrator on this machine)


Property(S): SupportedOSMessage = Installation of this product failed because it is not supported on this operating system. For information on supported configurations, see the product documentation.

Property(S): SupportedProcTypeMessage = This Microsoft SQL Server Native Client package is not supported on the current processor type.



Any help would be appreciated.

View 3 Replies View Related

Problem Installing SSQL Server 2000 Client Tools

Sep 13, 2007

Hi,

I'm trying to re-install SQL Server 2000 Desktop Engine andSQL Server client tools. I have succesfully re-installed the desktop engine,but I am getting the following error message when attempting to re-install theclient tools.

"Setup has detected an existing client tools only installation.
Please use the maintenance mode to add client components"

Unfortunately the Upgrade/Add/Remove option is greyed out as
an install option.

I attempted the registry hive rebuild option and the install appeared
to succeed. However, I cannot access any tools (Enterprise Manager
comes up with the message "The selected file cannot be found").

At this point, the desktop engine appears in Add/Remove programs
Window, but no other SQL Server components.

Any help very much appreciated!

Eric Yeoman.

View 1 Replies View Related

Problems Installing Client Tools And BOL

Jul 26, 2006

I have tried several times to install SQL Server 2005 Enterprise Edition on a cluster. SQL Server, SQL browser and SQL Agent installs ok but when the installer start to setup Books on line and client tools (BIDS) and SS Management Studio the installer stops and end the installation.

I get this error (from SQLSetup0021_WBOGSQL01_Core(Local).log)

Remote setup(s) are ready
Notify package to begin: 29539
Notify package to commit: 29539
Waiting for remote setup(s) to get ready to end
Remote setup(s) are ready
Notify package to end: 29539
Error: Action "UninstallForRS2000Action" failed during execution. Error information reported during run:
Action: "UninstallForRS2000Action" will be marked as failed due to the following condition:
Condition "rs was successfully upgraded." returned false.
Installation of package: "patchRS2000" failed due to a precondition.
Waiting for actions from remote setup(s)
Remote setup(s) are ready
Notify package action is determined: 0
Running: InstallToolsAction.10 at: 2006/6/23 2:3:42
Error: Action "InstallToolsAction.10" threw an exception during execution. Error information reported during run:
Target collection includes the local machine.
Fatal Exception caught while installing package: "10"
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: sqlchainingsqlprereqpackagemutator.cpp
Compiler Timestamp: Tue Aug 9 01:14:20 2005
Function Name: sqls::SqlPreReqPackageMutator::modifyRequest
Source Line Number: 196
---- Context -----------------------------------------------
sqls::InstallPackageAction::perform
sqls::InstallPackageAction::getReferringPackageId
ch::installA
WinException caught while installing package. : 1603
Error Code: 0x80070643 (1603)
Windows Error Text: Fatal error during installation.
Source File Name: packageengineinstallpackageaction.cpp
Compiler Timestamp: Fri Jul 1 01:28:25 2005
Function Name: sqls::InstallPackageAction::perform
Source Line Number: 167
---- Context -----------------------------------------------
sqls::InstallPackageAction::perform
sqls::InstallPackageAction::getReferringPackageId
ch::installA
Cancelling setup due to failure on remote machine: 1603
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0021_WBOGSQL01_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0021_WBOGSQL01_.NET Framework 2.0 LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0021_WBOGSQL01_.NET Framework Upgrade Advisor.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0021_WBOGSQL01_.NET Framework Upgrade Advisor LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0021_WBOGSQL01_.NET Framework Windows Installer.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0021_WBOGSQL01_.NET Framework Windows Installer LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0021.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2006/6/23 2:6:2
Message pump returning: 1603

Why does the installation process stop there and what can I do next?

Best regards

Andres

View 2 Replies View Related

Need To Execute Dtsrun Without Installing Client Tools.

Jul 20, 2005

I have an application that needs to execute dtsrun from a remotemachine. Basically I have a batch file on the remote box, whichhandles the execute. This works fine on a machine with client toolsinstalled. My problem is that I can't install the client tools on theremote box.Does anyone know what I need to install on the remote machine to getthis to execute, without installing the client tools? I've triedcopying dtsrun.exe and dtsrun.rll, but that didn't work

View 1 Replies View Related

SQL Server 2005 Client Tools

Oct 15, 2007

What is the quickest and easiest way to use client tools for 2005 like 2000....
?

View 4 Replies View Related

SQL Server 2005 Installation Woes For Workstation Components And Client Tools

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

SQL Server 2005 Client Tools Not Shown Up In Start Menu On Windows 2003 Server

Jul 18, 2007

Hello,



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?



Thanks

View 11 Replies View Related

Installing SQL Server 2005 Management Tools - Setup Crashing Repeatedly

Mar 18, 2008

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.


Time : Tue Mar 18 12:19:20 2008


List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_OWC11_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_BackwardsCompat_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_SNAC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_SCC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_WI.log

View 3 Replies View Related

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?



Thanks.



- Lance

Colorado State University



View 6 Replies View Related

Getting Tons Of Log In EventLog After Installing SQL Server 2005 And Client

Sep 8, 2007

Hi Guys  I have installed SqlServer2005 and client on my machine and just after the installation / configuration I am getting tons of log in Event Logs of .NET Runtime Optimization Service as following:  .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.SqlTDiagM, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91  .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.msxml6_interop, Version=6.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.msxml6_interop, Version=6.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.DTSRuntimeWrap, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.DTSRuntimeWrap, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.ManagedDTS, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91  .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.ManagedDTS, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.ForEachSMOEnumerator, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.ForEachSMOEnumerator, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.DtsMsg, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.DtsMsg, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.DTSPipelineWrap, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.DTSPipelineWrap, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.PipelineHost, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.PipelineHost, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91  .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.SqlTDiagM, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.SqlTDiagM, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.msxml6_interop, Version=6.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 Almost 10 message in each seconds....Any Body please help me to get rid of this. Thanks & RegardsVishal Sharma   

View 2 Replies View Related

Sql 2005 Client Tools

Sep 14, 2006

I have installed SQL 2005 on a new machine and cannot find any of theclient tools I am used to having: query analyzer, enterprise mgr.,profiler. Shouldn't they be included in a default installation if Ichose to install client tools? Where do I go to find them?*** Sent via Developersdex http://www.developersdex.com ***

View 1 Replies View Related

MS SQLServer 2005 - Client Tools

Nov 27, 2007

Hi there,
When I try and install the client tools on my SQLServer 2005 SP2 installation I get the following message:


Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The Transaction Manager is not available. (Exception from HRESULT: 0x8004D01


I have tried to uninstall and reinstall the Client Tools, but I keep on getting the same message.

Any suggestions?

Regards

Dawid

View 5 Replies View Related

Server Tools Or Client Tools?

Jun 16, 2008

Dear All,
how can we know that wether we had server tools or client tools on my machine?

Arnav
Even you learn 1%, Learn it with 100% confidence.

View 1 Replies View Related

SQL 2005 Client Tools Install Fails

Feb 2, 2007

Hi all... assisting with mass deployment of SQL 2005 Client Tools.

Multiple users are able to pass the System Configuration Check, and click Next. It is on the next screen they see the following:

Microsoft SQL Server 2005 Setup                              [_][X]
-------------------------------------------------------------------
Microsoft SQL Server Installation
  Setup is preparing to continue with the installation.
-------------------------------------------------------------------
Please wait while setup prepares to continue with the installation.

Status: Extracting custom action file from stream
       ________________________________________________
      [________________________________________________]

[Help]                                  [< Back] [Next >]  [Cancel]

After eight minutes, the install bombs, and sends an error report to Microsoft.

I saw a similar post here, but these are XP machines and Administrators appear to have the proper permissions. I also do not get the error message "Error writing to file".

Here is a section of the _WI log file generated by the install..

MSI (c) (48:A4) [09:20:49:208]: PROPERTY CHANGE: Adding ENABLERANU property. Its value is '1'.
Action ended 9:20:49: SetEnableRanuUI. Return value 1.
MSI (c) (48:A4) [09:20:49:208]: Skipping action: UnsetEnableRanuUI (condition is false)
MSI (c) (48:A4) [09:20:49:208]: Skipping action: SetSharedVolumePath (condition is false)
MSI (c) (48:A4) [09:20:49:208]: Skipping action: UnsetINSTALLSQLDATADIR (condition is false)
MSI (c) (48:A4) [09:20:49:208]: Doing action: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action 9:20:49: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2. Extracting custom action file from stream
Action start 9:20:49: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2.
MSI (c) (48:44) [09:20:49:223]: Invoking remote custom action. DLL: C:DOCUME~1axn4835aLOCALS~1TempMSI117.tmp, Entrypoint: StreamSupportFiles
MSI (c) (48:70) [09:20:49:223]: Cloaking enabled.
MSI (c) (48:70) [09:20:49:223]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (48:70) [09:20:49:223]: Connected to service for CA interface.
Action ended 9:20:49: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
MSI (c) (48:A4) [09:20:49:301]: Skipping action: FatalError (condition is false)
Action ended 9:20:49: INSTALL. Return value 3.
MSI (c) (48:44) [09:28:50:859]: Destroying RemoteAPI object.
MSI (c) (48:70) [09:28:50:859]: Custom Action Manager thread ending.

And here is a section of the _Core(Local).log

Running: ReportChainingResults at: 2007/0/29 9:28:57
Error: Action "ReportChainingResults" threw an exception during execution.
DwLaunchMsiExec() returned : 1603
        Error Code: 0x80070643 (1603)
Windows Error Text: Fatal error during installation.

  Source File Name: sqlchainingsqlchainingactions.cpp
Compiler Timestamp: Thu Sep  1 22:23:05 2005
     Function Name: sqls::ReportChainingResults::perform
Source Line Number: 2992

A section of _Core.log:

Running: LaunchLocalBootstrapAction at: 2007/0/29 9:19:37
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution.  Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1603
Aborting queue processing as nested installer has completed

When the install fails, this is the event signature:

EventType: sql90setup
P1: unknown
P2: 0x643
P3: unknown
P4: 0x643
P5: unknown
P6: unknown
P7: sqlrun.msi@9.00.1399.06

View 5 Replies View Related

2000 DTS Packages Corrupted By 2005 Client Tools?

Jan 12, 2006

Hi,

I have many sql 2000 DTS packages that I support from my development workstation  running v2000 sp4. Packages are altered on the development machine and then go through a normal release mechanisms to production via testing servers etc.

I have recently installed the client tools for SQL Server 2005 on my desktop to evaluate the product.  The 2005 DB instance is running on a seperate server.

So, I have dev edition of sql 2000 and 2005 client tools (including BI Dev studio etc) on my workstation.

I have recently had to make changes to a 2000 DTS package and used my 2000 enterprise manager to do so. No Problem- saved and tested fine on my workstation. 

But when I try and release it to another server, or open the package using enterprise manager from another machine that does not have sql 2005 installed - I get an error message 'Unspecified error'.  This I've seen before when trying to open packages created in v2000 , using v7 or where the service packs are different between machines.

Digging around my workstation and comparing some of the DLLs I know to be required to distribute DTS  packages (from RDIST.txt) it seems that some of the SQL 2000 dll files have been updated by my 2005 installation. 

E.g

DTSFFILE.DLL on my machine is 2000.85.1054.0 whilst on any 'clean' 2000 machine is at version v2000.80.760.0

Surely it cant be right that SQL 2005 has newer versions of components for SQL 2000 than is available with the latest SP for the actual product! Especially considering that the installation of 2005 does not even allow you to edit 2000 DTS packages through the management studio without a 'special' download' of the feature pack,(whihc by the way does not work very well either)

So am I to conclude that you can not run side by side installations of SQL 2000 and 2005 on a single machine and expect 2000 to run as it did previously

View 11 Replies View Related

Problem Installing SQL Mobile 2005 Tools

Jan 13, 2006

I'm trying to install the SQL Mobile 2005 Server tools on a Windows 2003
Server with IIS & MSSQL 2000 sp4.


I've stuck .NET 2.0 on already, but the installer for the server tools
Sqlce30setupen.msi just goes straight to the last page of the wizard and says
the install was interrupted.


I've run the install with logging turned on and this is the last portion of
the trace. Can anyone shed any light on whats going wrong.


-------------------------------><-------------------------------------


MSI (c) (9C:14) [14:12:35:912]: Doing action: FindRelatedProducts
Action start 14:12:35: FindRelatedProducts.
Action ended 14:12:35: FindRelatedProducts. Return value 1.
MSI (c) (9C:14) [14:12:35:912]: Doing action: AppSearch
Action start 14:12:35: AppSearch.
MSI (c) (9C:14) [14:12:35:912]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (9C:14) [14:12:35:912]: PROPERTY CHANGE: Adding IISROOTFOLDER
property. Its value is 'C:Inetpubwwwroot'.
MSI (c) (9C:14) [14:12:35:912]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (9C:14) [14:12:35:912]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL
Server90ToolsShellServices{CA8A686A-0882-4e79-BCA3-AF3F3AB3EB8A} 3: 2
MSI (c) (9C:14) [14:12:35:912]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (9C:14) [14:12:35:912]: PROPERTY CHANGE: Adding MDACFOUND property.
Its value is '2.80.1022.0'.
MSI (c) (9C:14) [14:12:35:912]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (9C:14) [14:12:35:912]: PROPERTY CHANGE: Adding ISIISINSTALLED
property. Its value is 'LocalSystem'.
MSI (c) (9C:14) [14:12:35:912]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (9C:14) [14:12:35:912]: PROPERTY CHANGE: Adding SQL2KREPLCLIENT
property. Its value is '{2FAD19D0-E309-11D2-B6E5-00C04F688E8F}'.
MSI (c) (9C:14) [14:12:35:928]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (9C:14) [14:12:35:928]: Note: 1: 2262 2: Signature 3: -2147287038
Action ended 14:12:35: AppSearch. Return value 1.
MSI (c) (9C:14) [14:12:35:928]: Skipping action: CheckOSVersion (condition
is false)
MSI (c) (9C:14) [14:12:35:928]: Doing action: CA_CheckInstalledSQL
Action start 14:12:35: CA_CheckInstalledSQL.
MSI (c) (9C:94) [14:12:35:943]: Invoking remote custom action. DLL:
C:DOCUME~1CharlieLOCALS~1Temp1MSIB.tmp, Entrypoint: CheckInstalledSQL
MSI (c) (9C:88) [14:12:35:943]: Cloaking enabled.
MSI (c) (9C:88) [14:12:35:943]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (9C:88) [14:12:35:943]: Connected to service for CA interface.
Action ended 14:12:36: CA_CheckInstalledSQL. Return value 3.
MSI (c) (9C:14) [14:12:36:005]: Doing action: SetupCompleteError
Action start 14:12:36: SetupCompleteError.
MSI (c) (9C:54) [14:12:36:082]: Note: 1: 2731 2: 0
Action ended 14:13:33: SetupCompleteError. Return value 2.
Action ended 14:12:32: INSTALL. Return value 3.
MSI (c) (EC:00) [14:19:35:619]: Destroying RemoteAPI object.
MSI (c) (EC:0C) [14:19:35:619]: Custom Action Manager thread ending.
=== Logging stopped: 11/01/2006  14:19:35 ===
MSI (c) (EC:34) [14:19:35:619]: Note: 1: 1708
MSI (c) (EC:34) [14:19:35:619]: Product: Microsoft SQL Server 2005 Mobile
[ENU] Server Tools -- Installation operation failed.


-------------------------------><-------------------------------------


thanks


// charlie

View 3 Replies View Related

Updates To SQLServer 2000 DLL's When 2005 Client Tools Installed

Jan 12, 2006

Hi,

I have many sql 2000 DTS packages that I support from my development workstation  running v2000 sp4. Packages are altered on the development machine and then go through a normal release mechanisms to production via testing servers etc.

I have recently installed the client tools for SQL Server 2005 on my desktop to evaluate the product.  The 2005 DB instance is running on a seperate server.

So, I have dev edition of sql 2000 and 2005 client tools (including BI Dev studio etc) on my workstation.

I have recently had to make changes to a 2000 DTS package and used my 2000 enterprise manager to do so. No Problem- saved and tested fine on my workstation. 

But when I try and release it to another server, or open the package using enterprise manager from another machine that does not have sql 2005 installed - I get an error message 'Unspecified error'.  This I've seen before when trying to open packages created in v2000 , using v7 or where the service packs are different between machines.

Digging around my workstation and comparing some of the DLLs I know to be required to distribute DTS  packages (from RDIST.txt) it seems that some of the SQL 2000 dll files have been updated by my 2005 installation. 

E.g

DTSFFILE.DLL on my machine is 2000.85.1054.0 whilst on any 'clean' 2000 machine is at version v2000.80.760.0

Surely it cant be right that SQL 2005 has newer versions of components for SQL 2000 than is available with the latest SP for the actual product! Especially considering that the installation of 2005 does not even allow you to edit 2000 DTS packages through the management studio without a 'special' download' of the feature pack,(whihc by the way does not work very well either)

So am I to conclude that you can not run side by side installations of SQL 2000 and 2005 on a single machine and expect 2000 to run as it did previously !!!

View 2 Replies View Related

Unable To Install Client Tools (SQL 2005) On Windows Vista

Mar 21, 2007

have removed bsn contact manager and all sql related files from previous installation attempts, rebooted so should be a clean install - but still it fails

what did I miss or what am I doing wrong?

here are the logs with ref to the two items that fail

~~~

Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Professional (Build 6000)
Time : Tue Mar 20 18:30:20 2007

Product : OWC11
Error : Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:Program FilesMicrosoft OfficeOFFICE111033SETUP.CHM.
--------------------------------------------------------------------------------

Product : Microsoft Office 2003 Web Components
Product Version : 11.0.8003.0
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_PATRICES-XPS_OWC11_1.log
Last Action : InstallExecute
Error String : Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:Program FilesMicrosoft OfficeOFFICE111033SETUP.CHM.
Error Number : 1706

thanks for any help/light/suggestions you can share

View 2 Replies View Related

Error Running Script: 80sp4-tools.sql Installing Sql 2000 SP4

Apr 13, 2007

Hello there,



I hope someone can help me with an annoying failure.



While installing sp4, the last running script is going very wrong.



"Error running script: 80sp4-tools.sql"



in the sqlsp.log, there is only an item with Process Exit Code: (1) after 80sp4-tools.sql



this is the log file.



14:15:05 Begin Setup
14:15:05 Version on Media: 8.00.2039
14:15:05 Mode = Normal
14:15:05 ModeType = NORMAL
14:15:06 Loading library - sqlsut.dll (#L1)
14:15:06 Begin: SetupInitialize()
14:15:06 End: SetupInitialize()
14:15:06 Begin: CheckFixedRequirements()
14:15:06 Platform ID: 0xf000
14:15:06 Version: 5.2.3790
14:15:06 File Version - C:WINDOWSsystem32shdocvw.dll: 6.0.3790.2858
14:15:06 End: CheckFixedRequirements()
14:15:06 Begin Action: CheckRequirements
14:15:06 Processor Architecture: x86 (Pentium)
14:15:06 Service Pack: 256
14:15:06 ComputerName: SERVER01
14:15:06 User Name: administrator
14:15:06 IsAllAccessAllowed returned: 1
14:15:06 OS Language: 0x409
14:15:06 End Action CheckRequirements
14:15:06 CreateSetupTopology(SERVER01), Handle : 0x14d46c8, returned : 0
14:15:06 CreateSetupTopology returned : 0, Handle : 0x14d46c8
14:15:06 Topology Type : 1, Return Value : 0
14:15:06 ST_GetPhysicalNode returned : 0, PNHandle : 0x14d4708
14:15:06 PN_EnumerateEx returned : 0
14:15:06 PN_GetSQLStates returned : 0, SqlStates : 0x88020024
14:15:06 PN_StartScan [0x14d4708] returned : 0
14:15:06 PN_GetNext [0x14d4708] returned : 0, Handle: [0x14d55c0]
14:15:06 SQLI_GetPackageId [0x14d55c0] returned : 0, PackageId = 0x2
14:15:06 SQLI_GetVersion [0x14d55c0] returned : 0, Version = 8.00.194
14:15:06 PN_GetNext [0x14d4708] returned : 0, Handle: [0x14d5f48]
14:15:06 PN_GetNext [0x14d4708] returned : 0, Handle: [0x14d6878]
14:15:06 PN_GetNext [0x14d4708] returned : 0, Handle: [0x14d7180]
14:15:06 PN_GetNext [0x14d4708] returned : 18, Handle: [0x0]
14:15:06 ReleaseSetupTopology
14:15:06 This combination of Package and Operating System allows a full product install.
14:15:06 Begin: SetupInstall()
14:15:06 Reading SoftwareMicrosoftWindowsCurrentVersionCommonFilesDir ...
14:15:06 CommonFilesDir=C:Program FilesCommon Files
14:15:06 Windows Directory=C:WINDOWS
14:15:06 Program Files=C:Program Files
14:15:06 TEMPDIR=C:DOCUME~1ADMINI~1LOCALS~1Temp
14:15:06 End: SetupInstall()
14:15:06 Begin: ShowDialogs()
14:15:06 Initial Dialog Mask: 0x8300037, Disable Back=0x1
14:15:06 Begin Action ShowDialogsHlpr: 0x1
14:15:06 Begin Action: DialogShowSdWelcome
14:15:07 End Action DialogShowSdWelcome
14:15:07 Dialog 0x1 returned: 1
14:15:07 End Action ShowDialogsHlpr
14:15:07 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
14:15:07 Begin Action ShowDialogsHlpr: 0x2
14:15:07 Begin Action: DialogShowSdMachineName
14:15:07 ShowDlgMachine returned: 1
14:15:07 Name = SERVER01, Type = 0x1
14:15:07 End Action DialogShowSdMachineName
14:15:07 begin ShowDialogsUpdateMask
14:15:07 nFullMask = 0x8300037, nCurrent = 0x2, nDirection = 0
14:15:07 Updated Dialog Mask: 0xbf00035, Disable Back = 0x1
14:15:07 Dialog 0x2 returned: 0
14:15:07 End Action ShowDialogsHlpr
14:15:07 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
14:15:07 Begin Action ShowDialogsHlpr: 0x4
14:15:07 Begin Action: DialogShowSdInstallMode
14:15:07 ShowDlgInstallMode returned: 1
14:15:07 InstallMode : 0x2
14:15:07 End Action DialogShowSdInstallMode
14:15:07 begin ShowDialogsUpdateMask
14:15:07 nFullMask = 0xbf00035, nCurrent = 0x4, nDirection = 1
14:15:07 Updated Dialog Mask: 0xb000627, Disable Back = 0x1
14:15:07 Dialog 0x4 returned: 1
14:15:07 End Action ShowDialogsHlpr
14:15:07 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
14:15:07 Begin Action ShowDialogsHlpr: 0x20
14:15:07 Begin Action: DialogShowSdLicense
14:15:08 End Action DialogShowSdLicense
14:15:08 Dialog 0x20 returned: 1
14:15:08 End Action ShowDialogsHlpr
14:15:08 ShowDialogsGetDialog returned: nCurrent=0x200,index=9
14:15:08 Begin Action ShowDialogsHlpr: 0x200
14:15:08 Begin Action: DialogShowSdInstanceName
14:15:08 Begin Action: ShowDlgInstanceName
14:15:09 This machine has SQL Server 2000 SP3 already installed
14:15:09 Version of installed Service Pack: 8.00.761
14:15:09 The language on the CD is 1033 and installed is 1033
14:15:09 End Action : Verify Language
14:15:09 SKU is : Standard Edition
14:15:09 End Action: ShowDlgInstanceName
14:15:09 ShowDlgInstanceName returned : 0
14:15:09 InstanceName : INSTNAME
14:15:09 End Action DialogShowSdInstanceName
14:15:09 begin ShowDialogsUpdateMask
14:15:09 nFullMask = 0xb000627, nCurrent = 0x200, nDirection = 0
14:15:09 Updated Dialog Mask: 0xbc00627, Disable Back = 0x1
14:15:09 Dialog 0x200 returned: 0
14:15:09 End Action ShowDialogsHlpr
14:15:09 ShowDialogsGetDialog returned: nCurrent=0x400,index=10
14:15:09 Begin Action ShowDialogsHlpr: 0x400
14:15:09 Begin Action: DialogShowSdMaintain
14:15:09 ShowDlgMaintainInstall returned : 1
14:15:09 Type : 0xc
14:15:09 CreateSetupTopology(SERVER01), Handle : 0x14d5f08, returned : 0
14:15:09 CreateSetupTopology returned : 0, Handle : 0x14d5f08
14:15:09 Topology Type : 1, Return Value : 0
14:15:09 ST_GetPhysicalNode returned : 0, PNHandle : 0x14d46c8
14:15:09 PN_EnumerateEx returned : 0
14:15:09 PN_GetSQLStates returned : 0, SqlStates : 0x88020024
14:15:09 PN_GetInstance for INSTNAME [0x14d46c8] returned : 0
14:15:09 SQLI_GetPackageId [0x14d55c0] returned : 0, PackageId = 0x2
14:15:09 SQLI_GetVersion [0x14d55c0] returned : 0, Version = 8.00.194
14:15:09 SQLI_GetSQLStates for INSTNAME [0x14d55c0] returned : 0, SQLStates: 0xc20804
14:15:09 SQLI_GetInstallPath [0x14d55c0] returned : 0, Path = C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAME
14:15:09 SQLI_GetDataPath [0x14d55c0] returned : 0, DataPath = C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAME
14:15:09 SQLI_GetVersion [0x14d55c0] returned : 0, Version = 8.00.194
14:15:09 SQLI_GetRegKeyRoot [0x14d55c0] returned : 0, RegKeyRoot = SoftwareMicrosoftMicrosoft SQL ServerINSTNAME
14:15:09 SQLI_GetPackageName [0x14d55c0] returned : 0, szPackage = Standard Edition
14:15:09 SQLI_GetPackageId [0x14d55c0] returned : 0, PackageId = 0x2
14:15:09 Previous Install Path: C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAME
14:15:09 Previous Install Data: C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAME
14:15:09 Previous Install Version: 8.00.194
14:15:09 ReleaseSetupTopology
14:15:09 End Action DialogShowSdMaintain
14:15:09 begin ShowDialogsUpdateMask
14:15:09 nFullMask = 0xbc00627, nCurrent = 0x400, nDirection = 1
14:15:09 Updated Dialog Mask: 0xb002627, Disable Back = 0x1
14:15:09 Dialog 0x400 returned: 1
14:15:10 End Action ShowDialogsHlpr
14:15:10 ShowDialogsGetDialog returned: nCurrent=0x2000,index=13
14:15:10 Begin Action ShowDialogsHlpr: 0x2000
14:15:10 Begin Action: DialogShowSdUpgrade
14:15:10 ShowDlgUpgrade returned : 1
14:15:10 Checking databases on instance 'INSTNAME'
14:15:10 Authenticate access
14:15:10 Begin SDPassword Dialog
14:15:13 End SDPassword Dialog
14:15:13 C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBinscm.exe -Silent 1 -Action 6 -Service MSSQL$INSTNAME
14:15:13 Process Exit Code: (0)
14:15:13 C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBinscm.exe -Silent 1 -Action 1 -Service MSSQL$INSTNAME -StartupOptions -T4022
14:16:03 Process Exit Code: (0)
14:16:03 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -n -d master -Q "exit" -o "C:DOCUME~1ADMINI~1LOCALS~1Tempsqlsp.out" -Usa -P"
14:16:04 Process Exit Code: (0)
14:16:04 Begin: CheckSAPassword
14:16:04 Begin: LogOnUsingBlankSA
14:16:04 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -n -d master -o "C:DOCUME~1ADMINI~1LOCALS~1Tempsqlsp.out" -Q"Exit(declare @ret int if (select count(*) from master..syslogins where name='sa' AND ( (1 = pwdcompare(N'', password)) OR password IS NULL )) = 0 Set @ret=0 else Set @ret=9000 Select @ret)" -Usa -P"
14:16:04 Process Exit Code: (0)
14:16:04 End: LogOnUsingBlankSA
14:16:04 Begin: SdBlankPwd
14:16:04 End: SdBlankPwd
14:16:04 End: CheckSAPassword
14:16:04 Begin : SdErrorReportingDlg
14:16:14 End: SdErrorReportingDlg
14:16:14 Access authenticated
14:16:14 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -n -b -d master -o "C:DOCUME~1ADMINI~1LOCALS~1Temp~sqldb0.txt" -i "C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBindbverify.sql" -Usa -P"
14:16:37 Process Exit Code: (0)
14:16:37 C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBinscm.exe -Silent 1 -Action 6 -Service MSSQL$INSTNAME
14:17:17 Process Exit Code: (0)
14:17:17 Setup Type: Custom (303)
14:17:18 Processing: SQLProg
14:17:18 Processing: SQLProgSQLServr
14:17:18 Processing: SQLProgUpgTools
14:17:18 Processing: SQLProgReplSupp
14:17:18 Processing: SQLProgInstall
14:17:18 Processing: SQLProgSystem
14:17:18 Processing: SQLProgSvrExt
14:17:18 Processing: SQLProgDat
14:17:18 Processing: SQLProgDatSmpl
14:17:18 Processing: SQLProgBaseSys
14:17:18 Processing: SQLProgBaseBinn
14:17:18 Processing: SQLProgMSSearch
14:17:18 Processing: SQLProgBaseInst
14:17:18 Processing: SQLProgUI
14:17:18 Processing: SQLProgSymbols
14:17:18 Processing: SQLProgPerfmon
14:17:18 Processing: SQLProgRoot
14:17:18 Processing: SQLProgEXE
14:17:18 Processing: SQLProgDLL
14:17:18 Processing: MgtTool
14:17:18 Processing: MgtToolSEM
14:17:18 Processing: MgtToolProfiler
14:17:18 Processing: MgtToolQryanlz
14:17:18 Processing: MgtToolDTCCLi
14:17:18 Processing: MgtToolWzcnflct
14:17:18 Processing: MgtToolUtilSys
14:17:18 Processing: MgtToolUtilBinn
14:17:18 Processing: Connect
14:17:18 Processing: ConnectConnSys
14:17:18 Processing: Books
14:17:18 Processing: BooksBookso
14:17:18 Processing: DevTools
14:17:18 Processing: DevToolsHeaders and Libraries
14:17:18 Processing: DevToolsMDAC SDKs
14:17:18 Processing: DevToolsVDI
14:17:18 Processing: DevToolsDbg Int
14:17:18 Processing: Samples
14:17:18 Processing: SamplesADO
14:17:18 Processing: SamplesDBLIB
14:17:18 Processing: SamplesDesktop
14:17:18 Processing: SamplesDTS
14:17:18 Processing: SamplesESQLC
14:17:18 Processing: SamplesMisc
14:17:18 Processing: SamplesMSDTC
14:17:18 Processing: SamplesODBC
14:17:18 Processing: SamplesODS
14:17:18 Processing: SamplesOLEAut
14:17:18 Processing: SamplesRepl
14:17:18 Processing: SamplesSilverstoneDB
14:17:18 Processing: SamplesSQLDMO
14:17:18 Processing: SamplesSQLNS
14:17:18 Processing: SamplesUtils
14:17:18 Processing: SamplesXML
14:17:18 Processing: CoreRepl
14:17:18 Processing: CoreReplRes1033
14:17:18 Processing: CoreReplResIntl
14:17:18 Processing: Core
14:17:18 Processing: CoreRes1033
14:17:18 Processing: CoreResOther
14:17:18 Processing: Repostry
14:17:18 Processing: RepostryRepstSys
14:17:18 Processing: RepostryRes1033
14:17:18 Processing: RepostryResIntl
14:17:18 Processing: CoreMisc
14:17:18 Processing: CoreMiscActiveX
14:17:18 Processing: CoreMiscRes1033
14:17:18 Processing: Monarch
14:17:18 Processing: MonarchMonr1033
14:17:18 Processing: MonarchMonrIntl
14:17:18 Processing: Jet
14:17:18 Processing: CoreInst
14:17:18 Processing: CoreCOM
14:17:18 Processing: CoreCOMRes1033
14:17:18 Processing: CoreCOMResIntl
14:17:18 Processing: CoreTool
14:17:18 Processing: CoreToolRes1033
14:17:18 Processing: CoreToolResOther
14:17:18 Processing: DBLibCli
14:17:18 Processing: SFExt
14:17:18 Processing: SFExtActiveX
14:17:18 Processing: SFExtRes1033
14:17:18 Processing: SFExtResIntl
14:17:18 Processing: Trace
14:17:18 Processing: TraceRes1033
14:17:18 Processing: TraceResOther
14:17:18 Processing: CnctBinn
14:17:18 Processing: MiscCore
14:17:18 Processing: MC
14:17:18 Processing: MCMC1033
14:17:18 Processing: MCMCIntl
14:17:18 Processing: MCHelp
14:17:18 Processing: UI
14:17:18 Processing: UIUIHlp
14:17:18 Processing: UIUI1033
14:17:18 Processing: UIUIIntl
14:17:18 Processing: ClstSys
14:17:18 Processing: SQLMgr
14:17:18 Processing: SQLMgrRes1033
14:17:18 Processing: SQLMgrResIntl
14:17:18 Processing: SvrTool
14:17:18 Processing: SvrToolRes1033
14:17:18 Processing: SvrToolResIntl
14:17:18 Processing: DTSUI
14:17:18 Processing: DTSUIRes1033
14:17:18 Processing: DTSUIResIntl
14:17:18 Processing: ClFTSys
14:17:18 Processing: ClFtdata
14:17:18 Processing: MSOlap
14:17:18 Processing: MSOlapRes1033
14:17:18 Processing: MSOlapResIntl
14:17:18 Processing: ATL
14:17:18 Processing: ATLwinnt
14:17:18 Processing: ATLwin9x
14:17:18 Processing: MFC42U
14:17:18 Processing: VC
14:17:18 Processing: VB
14:17:18 Processing: OCX1
14:17:18 Processing: SQLAdHlp
14:17:18 Processing: SQLAdHlpRes1033
14:17:18 Processing: SQLAdHlpResOther
14:17:18 Setup type: Custom
14:17:18 End Action DialogShowSdUpgrade
14:17:18 begin ShowDialogsUpdateMask
14:17:18 nFullMask = 0xb002627, nCurrent = 0x2000, nDirection = 1
14:17:18 Updated Dialog Mask: 0xb002627, Disable Back = 0x1
14:17:18 Dialog 0x2000 returned: 1
14:17:18 End Action ShowDialogsHlpr
14:17:18 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
14:17:18 Begin Action ShowDialogsHlpr: 0x1000000
14:17:18 Begin Action: DlgCollation
14:17:18 ShowDlgCollation returned: 1
14:17:18 collation_name = SQL_Latin1_General_CP1_CI_AS,locale_name = Latin1_General,lcid = 0x409,SortId = 52,dwCompFlags = 0x30001
14:17:18 End Action DlgCollation
14:17:18 begin ShowDialogsUpdateMask
14:17:18 nFullMask = 0xb002627, nCurrent = 0x1000000, nDirection = 1
14:17:18 Updated Dialog Mask: 0xb002627, Disable Back = 0x1
14:17:18 Dialog 0x1000000 returned: 1
14:17:18 End Action ShowDialogsHlpr
14:17:18 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
14:17:18 Begin Action ShowDialogsHlpr: 0x2000000
14:17:18 Begin Action: DlgNetwork
14:17:18 ShowDlgNetwork returned: 1
14:17:18 [DlgServerNetwork]
14:17:18 NetworkLibs = 255
14:17:18 TCPPort = 0
14:17:18 TCPPrxy = Default
14:17:18 NMPPipeName = \.pipeMSSQL$INSTNAMEsqlquery
14:17:18 Result = 1
14:17:18 End Action DlgNetwork
14:17:18 begin ShowDialogsUpdateMask
14:17:18 nFullMask = 0xb002627, nCurrent = 0x2000000, nDirection = 1
14:17:18 Updated Dialog Mask: 0xb002627, Disable Back = 0x1
14:17:18 Dialog 0x2000000 returned: 1
14:17:18 End Action ShowDialogsHlpr
14:17:18 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
14:17:18 Begin Action ShowDialogsHlpr: 0x8000000
14:17:18 Begin Action: DialogShowSdStartCopy
14:17:34 End Action DialogShowSdStartCopy
14:17:34 begin ShowDialogsUpdateMask
14:17:34 nFullMask = 0xb002627, nCurrent = 0x8000000, nDirection = 1
14:17:34 Updated Dialog Mask: 0xb002627, Disable Back = 0x1
14:17:34 Dialog 0x8000000 returned: 1
14:17:34 End Action ShowDialogsHlpr
14:17:34 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
14:17:34 End: ShowDialogs()
14:17:34 Initializing Event Log
14:17:34 Begin Action : LogEvent
14:17:34 End Action : LogEvent
14:17:34 Begin: ProcessBeforeDataMove()
14:17:35 DeinstallStart returned (C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAME): 0
14:17:35 End: ProcessBeforeDataMove()
14:17:35 Begin: SetToolsComponentSelection()
14:17:35 CreateSetupTopology(SERVER01), Handle : 0x14d5ee8, returned : 0
14:17:35 CreateSetupTopology returned : 0, Handle : 0x14d5ee8
14:17:35 Topology Type : 1, Return Value : 0
14:17:35 ST_GetPhysicalNode returned : 0, PNHandle : 0x14d46c8
14:17:35 PN_EnumerateEx returned : 0
14:17:35 PN_GetSQLStates returned : 0, SqlStates : 0x88020024
14:17:35 PN_StartScan [0x14d46c8] returned : 0
14:17:35 PN_GetNext [0x14d46c8] returned : 18, Handle: [0x0]
14:17:35 No more items in enumeration.
14:17:35 ReleaseSetupTopology
14:17:35 End: SetToolsComponentSelection()
14:17:35 Begin: ProcessComponentSelection()
14:17:35 End: ProcessComponentSelection()
14:17:35 Begin: LogSelectedComponents()
14:17:35 Processing: SQLProg
14:17:35 Selected: SQLProg
14:17:35 Processing: SQLProgSQLServr
14:17:35 Selected: SQLProgSQLServr
14:17:35 Processing: SQLProgSQLServrHelp
14:17:35 Selected: SQLProgSQLServrHelp
14:17:35 Processing: SQLProgSQLServrSCMDev
14:17:35 Selected: SQLProgSQLServrSCMDev
14:17:35 Processing: SQLProgSQLServrSCMDevSCMh
14:17:35 Selected: SQLProgSQLServrSCMDevSCMh
14:17:35 Processing: SQLProgSQLServrSCMDevSCMX86Lb
14:17:35 Selected: SQLProgSQLServrSCMDevSCMX86Lb
14:17:35 Processing: SQLProgSQLServrSCMDevSCMALb
14:17:35 Selected: SQLProgSQLServrSCMDevSCMALb
14:17:35 Processing: SQLProgSQLServrRs1033
14:17:35 Selected: SQLProgSQLServrRs1033
14:17:35 Processing: SQLProgSQLServrRsIntl
14:17:35 Selected: SQLProgSQLServrRsIntl
14:17:35 Processing: SQLProgSQLServrActiveX
14:17:35 Selected: SQLProgSQLServrActiveX
14:17:35 Processing: SQLProgSQLServrSystem
14:17:35 Selected: SQLProgSQLServrSystem
14:17:35 Processing: SQLProgSQLServrWatson
14:17:35 Selected: SQLProgSQLServrWatson
14:17:35 Processing: SQLProgSQLServrWatsonWatson1033
14:17:35 Selected: SQLProgSQLServrWatsonWatson1033
14:17:35 Processing: SQLProgSQLServrWatsonWatsonOther
14:17:35 Selected: SQLProgSQLServrWatsonWatsonOther
14:17:35 Processing: SQLProgSQLServrMSXMLSQL
14:17:35 Selected: SQLProgSQLServrMSXMLSQL
14:17:35 Processing: SQLProgSQLServrMSXMLSQLRes1033
14:17:35 Selected: SQLProgSQLServrMSXMLSQLRes1033
14:17:35 Processing: SQLProgSQLServrMSXMLSQLResIntl
14:17:35 Selected: SQLProgSQLServrMSXMLSQLResIntl
14:17:35 Processing: SQLProgUpgTools
14:17:35 Processing: SQLProgUpgToolsUpgSys
14:17:35 Processing: SQLProgUpgToolsActiveX
14:17:35 Processing: SQLProgUpgToolsRes1033
14:17:35 Processing: SQLProgUpgToolsResOther
14:17:35 Processing: SQLProgUpgToolsResld
14:17:35 Processing: SQLProgReplSupp
14:17:35 Selected: SQLProgReplSupp
14:17:35 Processing: SQLProgReplSuppReplDat
14:17:35 Selected: SQLProgReplSuppReplDat
14:17:35 Processing: SQLProgReplSuppRepComm
14:17:35 Selected: SQLProgReplSuppRepComm
14:17:35 Processing: SQLProgReplSuppRepNoDk
14:17:35 Selected: SQLProgReplSuppRepNoDk
14:17:35 Processing: SQLProgReplSuppActiveX
14:17:35 Selected: SQLProgReplSuppActiveX
14:17:35 Processing: SQLProgInstall
14:17:35 Selected: SQLProgInstall
14:17:35 Processing: SQLProgSystem
14:17:35 Selected: SQLProgSystem
14:17:35 Processing: SQLProgSvrExt
14:17:35 Selected: SQLProgSvrExt
14:17:35 Processing: SQLProgSvrExtHelp
14:17:35 Selected: SQLProgSvrExtHelp
14:17:35 Processing: SQLProgSvrExtSvrExtRs
14:17:35 Selected: SQLProgSvrExtSvrExtRs
14:17:35 Processing: SQLProgSvrExtResIntl
14:17:35 Selected: SQLProgSvrExtResIntl
14:17:35 Processing: SQLProgDat
14:17:35 Processing: SQLProgDatSmpl
14:17:35 Processing: SQLProgBaseSys
14:17:35 Selected: SQLProgBaseSys
14:17:35 Processing: SQLProgBaseBinn
14:17:35 Selected: SQLProgBaseBinn
14:17:35 Processing: SQLProgMSSearch
14:17:35 Selected: SQLProgMSSearch
14:17:35 Processing: SQLProgMSSearchHelp
14:17:35 Selected: SQLProgMSSearchHelp
14:17:35 Processing: SQLProgMSSearchActiveX
14:17:35 Selected: SQLProgMSSearchActiveX
14:17:35 Processing: SQLProgBaseInst
14:17:35 Selected: SQLProgBaseInst
14:17:35 Processing: SQLProgUI
14:17:35 Processing: SQLProgSymbols
14:17:35 Selected: SQLProgSymbols
14:17:35 Processing: SQLProgSymbolsEXE
14:17:35 Selected: SQLProgSymbolsEXE
14:17:35 Processing: SQLProgSymbolsDLL
14:17:35 Selected: SQLProgSymbolsDLL
14:17:35 Processing: SQLProgPerfmon
14:17:35 Selected: SQLProgPerfmon
14:17:35 Processing: SQLProgPerfmonSystem
14:17:35 Selected: SQLProgPerfmonSystem
14:17:35 Processing: SQLProgRoot
14:17:35 Processing: SQLProgEXE
14:17:35 Processing: SQLProgDLL
14:17:35 Processing: MgtTool
14:17:35 Selected: MgtTool
14:17:35 Processing: MgtToolSEM
14:17:35 Selected: MgtToolSEM
14:17:35 Processing: MgtToolSEMHTML
14:17:35 Selected: MgtToolSEMHTML
14:17:35 Processing: MgtToolSEMMSD98
14:17:35 Selected: MgtToolSEMMSD98
14:17:35 Processing: MgtToolSEMMSD98SYS
14:17:35 Selected: MgtToolSEMMSD98SYS
14:17:35 Processing: MgtToolSEMMSD98Res
14:17:35 Selected: MgtToolSEMMSD98Res
14:17:35 Processing: MgtToolSEMMSD98Hlp
14:17:35 Selected: MgtToolSEMMSD98Hlp
14:17:35 Processing: MgtToolSEMHelp
14:17:35 Selected: MgtToolSEMHelp
14:17:35 Processing: MgtToolSEMRes1033
14:17:35 Selected: MgtToolSEMRes1033
14:17:35 Processing: MgtToolSEMResIntl
14:17:35 Selected: MgtToolSEMResIntl
14:17:35 Processing: MgtToolSEMMSD98RsI
14:17:35 Selected: MgtToolSEMMSD98RsI
14:17:35 Processing: MgtToolSEMActiveX
14:17:35 Selected: MgtToolSEMActiveX
14:17:35 Processing: MgtToolSEMActiveXRes1033
14:17:35 Selected: MgtToolSEMActiveXRes1033
14:17:35 Processing: MgtToolSEMActiveXResIntl
14:17:35 Selected: MgtToolSEMActiveXResIntl
14:17:35 Processing: MgtToolSEMScripts
14:17:35 Selected: MgtToolSEMScripts
14:17:35 Processing: MgtToolSEMOLEDB
14:17:35 Selected: MgtToolSEMOLEDB
14:17:35 Processing: MgtToolSEMOLEDBRes1033
14:17:35 Selected: MgtToolSEMOLEDBRes1033
14:17:35 Processing: MgtToolSEMOLEDBResIntl
14:17:35 Selected: MgtToolSEMOLEDBResIntl
14:17:35 Processing: MgtToolSEMMSD7
14:17:35 Selected: MgtToolSEMMSD7
14:17:35 Processing: MgtToolSEMMSD7Res
14:17:35 Selected: MgtToolSEMMSD7Res
14:17:35 Processing: MgtToolSEMMSD7RsI
14:17:35 Selected: MgtToolSEMMSD7RsI
14:17:35 Processing: MgtToolProfiler
14:17:35 Selected: MgtToolProfiler
14:17:35 Processing: MgtToolProfilerHelp
14:17:35 Selected: MgtToolProfilerHelp
14:17:35 Processing: MgtToolProfilerRes1033
14:17:35 Selected: MgtToolProfilerRes1033
14:17:35 Processing: MgtToolProfilerResIntl
14:17:35 Selected: MgtToolProfilerResIntl
14:17:35 Processing: MgtToolQryanlz
14:17:35 Selected: MgtToolQryanlz
14:17:35 Processing: MgtToolQryanlzHelp
14:17:35 Selected: MgtToolQryanlzHelp
14:17:35 Processing: MgtToolQryanlzRes1033
14:17:35 Selected: MgtToolQryanlzRes1033
14:17:35 Processing: MgtToolQryanlzResIntl
14:17:35 Selected: MgtToolQryanlzResIntl
14:17:35 Processing: MgtToolDTCCLi
14:17:35 Selected: MgtToolDTCCLi
14:17:35 Processing: MgtToolWzcnflct
14:17:35 Selected: MgtToolWzcnflct
14:17:35 Processing: MgtToolWzcnflctWzcnHlp
14:17:35 Selected: MgtToolWzcnflctWzcnHlp
14:17:35 Processing: MgtToolWzcnflctWzcn1033
14:17:35 Selected: MgtToolWzcnflctWzcn1033
14:17:35 Processing: MgtToolWzcnflctWzcnOthr
14:17:35 Selected: MgtToolWzcnflctWzcnOthr
14:17:35 Processing: MgtToolWzcnflctWzcnCmn
14:17:35 Selected: MgtToolWzcnflctWzcnCmn
14:17:35 Processing: MgtToolUtilSys
14:17:35 Selected: MgtToolUtilSys
14:17:35 Processing: MgtToolUtilBinn
14:17:35 Selected: MgtToolUtilBinn
14:17:35 Processing: Connect
14:17:35 Selected: Connect
14:17:35 Processing: ConnectConnSys
14:17:35 Selected: ConnectConnSys
14:17:35 Processing: Books
14:17:35 Selected: Books
14:17:35 Processing: BooksBookso
14:17:35 Selected: BooksBookso
14:17:35 Processing: BooksBooksoUtils
14:17:35 Selected: BooksBooksoUtils
14:17:35 Processing: DevTools
14:17:35 Selected: DevTools
14:17:35 Processing: DevToolsHeaders and Libraries
14:17:35 Processing: DevToolsHeaders and LibrariesInclude
14:17:35 Processing: DevToolsHeaders and LibrariesLibx86
14:17:35 Processing: DevToolsHeaders and LibrariesLibAlpha
14:17:35 Processing: DevToolsHeaders and LibrariesESQLC
14:17:35 Processing: DevToolsMDAC SDKs
14:17:35 Processing: DevToolsVDI
14:17:35 Processing: DevToolsVDIInc
14:17:35 Processing: DevToolsVDISamples
14:17:35 Processing: DevToolsDbg Int
14:17:35 Selected: DevToolsDbg Int
14:17:35 Processing: DevToolsDbg IntDbg Int Common
14:17:35 Selected: DevToolsDbg IntDbg Int Common
14:17:35 Processing: DevToolsDbg IntEXE
14:17:35 Selected: DevToolsDbg IntEXE
14:17:35 Processing: Samples
14:17:35 Processing: SamplesADO
14:17:35 Processing: SamplesDBLIB
14:17:35 Processing: SamplesDesktop
14:17:35 Processing: SamplesDTS
14:17:35 Processing: SamplesESQLC
14:17:35 Processing: SamplesMisc
14:17:35 Processing: SamplesMSDTC
14:17:35 Processing: SamplesODBC
14:17:35 Processing: SamplesODS
14:17:35 Processing: SamplesOLEAut
14:17:35 Processing: SamplesRepl
14:17:35 Processing: SamplesSilverstoneDB
14:17:35 Processing: SamplesSQLDMO
14:17:35 Processing: SamplesSQLNS
14:17:35 Processing: SamplesUtils
14:17:35 Processing: SamplesXML
14:17:35 Processing: CoreRepl
14:17:35 Selected: CoreRepl
14:17:35 Processing: CoreReplRes1033
14:17:35 Selected: CoreReplRes1033
14:17:35 Processing: CoreReplResIntl
14:17:35 Selected: CoreReplResIntl
14:17:35 Processing: Core
14:17:35 Selected: Core
14:17:35 Processing: CoreRes1033
14:17:35 Selected: CoreRes1033
14:17:35 Processing: CoreResOther
14:17:35 Selected: CoreResOther
14:17:35 Processing: Repostry
14:17:35 Selected: Repostry
14:17:35 Processing: RepostryRepstSys
14:17:35 Selected: RepostryRepstSys
14:17:35 Processing: RepostryRes1033
14:17:35 Selected: RepostryRes1033
14:17:35 Processing: RepostryResIntl
14:17:35 Selected: RepostryResIntl
14:17:35 Processing: CoreMisc
14:17:35 Selected: CoreMisc
14:17:35 Processing: CoreMiscActiveX
14:17:35 Selected: CoreMiscActiveX
14:17:35 Processing: CoreMiscActiveXRes1033
14:17:35 Selected: CoreMiscActiveXRes1033
14:17:35 Processing: CoreMiscActiveXResIntl
14:17:35 Selected: CoreMiscActiveXResIntl
14:17:35 Processing: CoreMiscRes1033
14:17:35 Selected: CoreMiscRes1033
14:17:35 Processing: Monarch
14:17:35 Selected: Monarch
14:17:35 Processing: MonarchMonr1033
14:17:35 Selected: MonarchMonr1033
14:17:35 Processing: MonarchMonrIntl
14:17:35 Selected: MonarchMonrIntl
14:17:35 Processing: Jet
14:17:35 Selected: Jet
14:17:35 Processing: CoreInst
14:17:35 Selected: CoreInst
14:17:35 Processing: CoreCOM
14:17:35 Selected: CoreCOM
14:17:35 Processing: CoreCOMRes1033
14:17:35 Selected: CoreCOMRes1033
14:17:35 Processing: CoreCOMResIntl
14:17:35 Selected: CoreCOMResIntl
14:17:35 Processing: CoreTool
14:17:35 Selected: CoreTool
14:17:35 Processing: CoreToolRes1033
14:17:35 Selected: CoreToolRes1033
14:17:35 Processing: CoreToolResOther
14:17:35 Selected: CoreToolResOther
14:17:35 Processing: DBLibCli
14:17:35 Selected: DBLibCli
14:17:35 Processing: SFExt
14:17:35 Selected: SFExt
14:17:35 Processing: SFExtActiveX
14:17:35 Selected: SFExtActiveX
14:17:35 Processing: SFExtActiveXRes1033
14:17:35 Selected: SFExtActiveXRes1033
14:17:35 Processing: SFExtActiveXResIntl
14:17:35 Selected: SFExtActiveXResIntl
14:17:35 Processing: SFExtRes1033
14:17:35 Selected: SFExtRes1033
14:17:35 Processing: SFExtResIntl
14:17:35 Selected: SFExtResIntl
14:17:35 Processing: Trace
14:17:35 Selected: Trace
14:17:35 Processing: TraceRes1033
14:17:35 Selected: TraceRes1033
14:17:35 Processing: TraceResOther
14:17:35 Selected: TraceResOther
14:17:35 Processing: CnctBinn
14:17:35 Processing: MiscCore
14:17:35 Selected: MiscCore
14:17:35 Processing: MC
14:17:35 Selected: MC
14:17:35 Processing: MCMC1033
14:17:35 Selected: MCMC1033
14:17:35 Processing: MCMCIntl
14:17:35 Selected: MCMCIntl
14:17:35 Processing: MCHelp
14:17:35 Selected: MCHelp
14:17:35 Processing: UI
14:17:35 Processing: UIUIHlp
14:17:35 Processing: UIUI1033
14:17:35 Processing: UIUIIntl
14:17:35 Processing: ClstSys
14:17:35 Processing: SQLMgr
14:17:35 Selected: SQLMgr
14:17:35 Processing: SQLMgrRes1033
14:17:35 Selected: SQLMgrRes1033
14:17:35 Processing: SQLMgrResIntl
14:17:35 Selected: SQLMgrResIntl
14:17:35 Processing: SvrTool
14:17:35 Selected: SvrTool
14:17:35 Processing: SvrToolRes1033
14:17:35 Selected: SvrToolRes1033
14:17:35 Processing: SvrToolResIntl
14:17:35 Selected: SvrToolResIntl
14:17:35 Processing: DTSUI
14:17:35 Selected: DTSUI
14:17:35 Processing: DTSUIRes1033
14:17:35 Selected: DTSUIRes1033
14:17:35 Processing: DTSUIResIntl
14:17:35 Selected: DTSUIResIntl
14:17:35 Processing: ClFTSys
14:17:35 Processing: ClFtdata
14:17:35 Processing: MSOlap
14:17:35 Selected: MSOlap
14:17:35 Processing: MSOlapRes1033
14:17:35 Selected: MSOlapRes1033
14:17:35 Processing: MSOlapResIntl
14:17:35 Selected: MSOlapResIntl
14:17:35 Processing: ATL
14:17:35 Selected: ATL
14:17:35 Processing: ATLwinnt
14:17:35 Selected: ATLwinnt
14:17:35 Processing: ATLwin9x
14:17:35 Selected: ATLwin9x
14:17:35 Processing: MFC42U
14:17:35 Selected: MFC42U
14:17:35 Processing: VC
14:17:35 Selected: VC
14:17:35 Processing: VB
14:17:35 Selected: VB
14:17:35 Processing: OCX1
14:17:35 Processing: SQLAdHlp
14:17:35 Selected: SQLAdHlp
14:17:35 Processing: SQLAdHlpRes1033
14:17:35 Selected: SQLAdHlpRes1033
14:17:35 Processing: SQLAdHlpResOther
14:17:35 Selected: SQLAdHlpResOther
14:17:35 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
14:17:35 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
14:17:35 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
14:17:35 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
14:17:35 End: LogSelectedComponents()
14:17:35 Processing: SQLProg
14:17:35 Processing: SQLProgSQLServr
14:17:35 Processing: SQLProgSQLServrHelp
14:17:35 Processing: SQLProgSQLServrSCMDev
14:17:35 Processing: SQLProgSQLServrSCMDevSCMh
14:17:35 Processing: SQLProgSQLServrSCMDevSCMX86Lb
14:17:35 Processing: SQLProgSQLServrSCMDevSCMALb
14:17:35 Processing: SQLProgSQLServrRs1033
14:17:35 Processing: SQLProgSQLServrRsIntl
14:17:35 Processing: SQLProgSQLServrActiveX
14:17:35 Processing: SQLProgSQLServrSystem
14:17:35 Processing: SQLProgSQLServrWatson
14:17:35 Processing: SQLProgSQLServrWatsonWatson1033
14:17:35 Processing: SQLProgSQLServrWatsonWatsonOther
14:17:35 Processing: SQLProgSQLServrMSXMLSQL
14:17:35 Processing: SQLProgSQLServrMSXMLSQLRes1033
14:17:35 Processing: SQLProgSQLServrMSXMLSQLResIntl
14:17:35 Processing: SQLProgUpgTools
14:17:35 Processing: SQLProgUpgToolsUpgSys
14:17:35 Processing: SQLProgUpgToolsActiveX
14:17:35 Processing: SQLProgUpgToolsRes1033
14:17:35 Processing: SQLProgUpgToolsResOther
14:17:35 Processing: SQLProgUpgToolsResld
14:17:35 Processing: SQLProgReplSupp
14:17:35 Processing: SQLProgReplSuppReplDat
14:17:35 Processing: SQLProgReplSuppRepComm
14:17:35 Processing: SQLProgReplSuppRepNoDk
14:17:35 Processing: SQLProgReplSuppActiveX
14:17:35 Processing: SQLProgInstall
14:17:35 Processing: SQLProgSystem
14:17:35 Processing: SQLProgSvrExt
14:17:35 Processing: SQLProgSvrExtHelp
14:17:35 Processing: SQLProgSvrExtSvrExtRs
14:17:35 Processing: SQLProgSvrExtResIntl
14:17:35 Processing: SQLProgDat
14:17:35 Processing: SQLProgDatSmpl
14:17:35 Processing: SQLProgBaseSys
14:17:35 Processing: SQLProgBaseBinn
14:17:35 Processing: SQLProgMSSearch
14:17:35 Processing: SQLProgMSSearchHelp
14:17:35 Processing: SQLProgMSSearchActiveX
14:17:35 Processing: SQLProgBaseInst
14:17:35 Processing: SQLProgUI
14:17:35 Processing: SQLProgSymbols
14:17:35 Processing: SQLProgSymbolsEXE
14:17:35 Processing: SQLProgSymbolsDLL
14:17:35 Processing: SQLProgPerfmon
14:17:35 Processing: SQLProgPerfmonSystem
14:17:35 Processing: SQLProgRoot
14:17:35 Processing: SQLProgEXE
14:17:35 Processing: SQLProgDLL
14:17:35 Processing: MgtTool
14:17:35 Processing: MgtToolSEM
14:17:35 Processing: MgtToolSEMHTML
14:17:35 Processing: MgtToolSEMMSD98
14:17:35 Processing: MgtToolSEMMSD98SYS
14:17:35 Processing: MgtToolSEMMSD98Res
14:17:35 Processing: MgtToolSEMMSD98Hlp
14:17:35 Processing: MgtToolSEMHelp
14:17:35 Processing: MgtToolSEMRes1033
14:17:35 Processing: MgtToolSEMResIntl
14:17:35 Processing: MgtToolSEMMSD98RsI
14:17:35 Processing: MgtToolSEMActiveX
14:17:35 Processing: MgtToolSEMActiveXRes1033
14:17:35 Processing: MgtToolSEMActiveXResIntl
14:17:35 Processing: MgtToolSEMScripts
14:17:35 Processing: MgtToolSEMOLEDB
14:17:35 Processing: MgtToolSEMOLEDBRes1033
14:17:35 Processing: MgtToolSEMOLEDBResIntl
14:17:35 Processing: MgtToolSEMMSD7
14:17:35 Processing: MgtToolSEMMSD7Res
14:17:35 Processing: MgtToolSEMMSD7RsI
14:17:35 Processing: MgtToolProfiler
14:17:35 Processing: MgtToolProfilerHelp
14:17:35 Processing: MgtToolProfilerRes1033
14:17:35 Processing: MgtToolProfilerResIntl
14:17:35 Processing: MgtToolQryanlz
14:17:35 Processing: MgtToolQryanlzHelp
14:17:35 Processing: MgtToolQryanlzRes1033
14:17:35 Processing: MgtToolQryanlzResIntl
14:17:35 Processing: MgtToolDTCCLi
14:17:35 Processing: MgtToolWzcnflct
14:17:35 Processing: MgtToolWzcnflctWzcnHlp
14:17:35 Processing: MgtToolWzcnflctWzcn1033
14:17:35 Processing: MgtToolWzcnflctWzcnOthr
14:17:35 Processing: MgtToolWzcnflctWzcnCmn
14:17:35 Processing: MgtToolUtilSys
14:17:35 Processing: MgtToolUtilBinn
14:17:35 Processing: Connect
14:17:35 Processing: ConnectConnSys
14:17:35 Processing: Books
14:17:35 Processing: BooksBookso
14:17:35 Processing: BooksBooksoUtils
14:17:35 Processing: DevTools
14:17:35 Processing: DevToolsHeaders and Libraries
14:17:35 Processing: DevToolsHeaders and LibrariesInclude
14:17:35 Processing: DevToolsHeaders and LibrariesLibx86
14:17:35 Processing: DevToolsHeaders and LibrariesLibAlpha
14:17:35 Processing: DevToolsHeaders and LibrariesESQLC
14:17:35 Processing: DevToolsMDAC SDKs
14:17:35 Processing: DevToolsVDI
14:17:35 Processing: DevToolsVDIInc
14:17:35 Processing: DevToolsVDISamples
14:17:35 Processing: DevToolsDbg Int
14:17:35 Processing: DevToolsDbg IntDbg Int Common
14:17:35 Processing: DevToolsDbg IntEXE
14:17:35 Processing: Samples
14:17:35 Processing: SamplesADO
14:17:35 Processing: SamplesDBLIB
14:17:35 Processing: SamplesDesktop
14:17:35 Processing: SamplesDTS
14:17:35 Processing: SamplesESQLC
14:17:35 Processing: SamplesMisc
14:17:35 Processing: SamplesMSDTC
14:17:35 Processing: SamplesODBC
14:17:35 Processing: SamplesODS
14:17:35 Processing: SamplesOLEAut
14:17:35 Processing: SamplesRepl
14:17:35 Processing: SamplesSilverstoneDB
14:17:35 Processing: SamplesSQLDMO
14:17:35 Processing: SamplesSQLNS
14:17:35 Processing: SamplesUtils
14:17:35 Processing: SamplesXML
14:17:35 Processing: CoreRepl
14:17:35 Processing: CoreReplRes1033
14:17:35 Processing: CoreReplResIntl
14:17:35 Processing: Core
14:17:35 Processing: CoreRes1033
14:17:35 Processing: CoreResOther
14:17:35 Processing: Repostry
14:17:35 Processing: RepostryRepstSys
14:17:35 Processing: RepostryRes1033
14:17:35 Processing: RepostryResIntl
14:17:35 Processing: CoreMisc
14:17:35 Processing: CoreMiscActiveX
14:17:35 Processing: CoreMiscActiveXRes1033
14:17:35 Processing: CoreMiscActiveXResIntl
14:17:35 Processing: CoreMiscRes1033
14:17:35 Processing: Monarch
14:17:35 Processing: MonarchMonr1033
14:17:35 Processing: MonarchMonrIntl
14:17:35 Processing: Jet
14:17:35 Processing: CoreInst
14:17:35 Processing: CoreCOM
14:17:35 Processing: CoreCOMRes1033
14:17:35 Processing: CoreCOMResIntl
14:17:35 Processing: CoreTool
14:17:35 Processing: CoreToolRes1033
14:17:35 Processing: CoreToolResOther
14:17:35 Processing: DBLibCli
14:17:35 Processing: SFExt
14:17:35 Processing: SFExtActiveX
14:17:35 Processing: SFExtActiveXRes1033
14:17:35 Processing: SFExtActiveXResIntl
14:17:35 Processing: SFExtRes1033
14:17:35 Processing: SFExtResIntl
14:17:35 Processing: Trace
14:17:35 Processing: TraceRes1033
14:17:35 Processing: TraceResOther
14:17:35 Processing: CnctBinn
14:17:35 Processing: MiscCore
14:17:35 Processing: MC
14:17:35 Processing: MCMC1033
14:17:35 Processing: MCMCIntl
14:17:35 Processing: MCHelp
14:17:35 Processing: UI
14:17:35 Processing: UIUIHlp
14:17:35 Processing: UIUI1033
14:17:35 Processing: UIUIIntl
14:17:35 Processing: ClstSys
14:17:35 Processing: SQLMgr
14:17:35 Processing: SQLMgrRes1033
14:17:35 Processing: SQLMgrResIntl
14:17:35 Processing: SvrTool
14:17:35 Processing: SvrToolRes1033
14:17:35 Processing: SvrToolResIntl
14:17:35 Processing: DTSUI
14:17:35 Processing: DTSUIRes1033
14:17:35 Processing: DTSUIResIntl
14:17:35 Processing: ClFTSys
14:17:35 Processing: ClFtdata
14:17:35 Processing: MSOlap
14:17:35 Processing: MSOlapRes1033
14:17:35 Processing: MSOlapResIntl
14:17:35 Processing: ATL
14:17:35 Processing: ATLwinnt
14:17:35 Processing: ATLwin9x
14:17:35 Processing: MFC42U
14:17:35 Processing: VC
14:17:35 Processing: VB
14:17:35 Processing: OCX1
14:17:35 Processing: SQLAdHlp
14:17:35 Processing: SQLAdHlpRes1033
14:17:35 Processing: SQLAdHlpResOther
14:17:35 SQL program folder: C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAME
14:17:35 SQL data folder: C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAME
14:17:35 Windows system folder: C:WINDOWSsystem32
14:17:35 Prog req: 61137, Data req: 3072, Sys req: 50573
14:17:35 Prog avail: 1573556, Data avail: 1573556, Sys avail: 1573556
14:17:35 Prog req vs. avail, 114782, 1573556
14:17:35 Data req vs. avail, 3072, 1573556
14:17:35 Sys req vs. avail, 53645, 1573556
14:17:35 C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBinscm.exe -Silent 1 -Action 6 -Timeout 5000 -Service SQLAgent$INSTNAME
14:17:35 Process Exit Code: (0)
14:17:35 C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBinscm.exe -Silent 1 -Action 6 -Timeout 5000 -Service MSSQL$INSTNAME
14:17:35 Process Exit Code: (0)
14:17:35 Begin: InstallPkgs(ID_INSTALLMDAC)
14:17:35 Begin Action: Locked Connectivity Files Check
14:17:35 ConnectivityLocked returned: 0
14:17:35 The operation completed successfully.

14:17:35 End Action: Locked Connectivity Files Check
14:17:35 Setup is installing Microsoft Data Access Components (MDAC) ...
14:17:35 D:SQL2KSP42x86Othersqlredis.exe /q:a /C:"setupre.exe MDACQFE=0 WARN=1 -s -SMS"
14:17:35 Unloading library - sqlsut.dll (#U2)
14:17:43 Loading library - sqlsut.dll (#L2)
14:17:43 ExitCode: 0
14:17:43 End: InstallPkgs(ID_INSTALLMDAC)
14:17:43 **** STARTING OPEN OP IN WRITE MODE ****
14:17:43 **** CLOSED OPEN OP IN WRITE MODE ****
14:17:43 Begin: MoveFileData()
14:17:43 Enabled SELFREGISTERBATCH
14:17:43 Enabled CORECOMPONENTHANDLING
14:17:49 Begin Action: MoveFileDataSpecial
14:17:49 End Action: MoveFileDataSpecial
14:17:49 End: MoveFileData()
14:17:49 Begin: ProcessAfterDataMove()
14:17:49 Begin Action : Installing Server Net
14:17:49 Server Instance : INSTNAME
14:17:49 Server Net Will only be installed on server only in Enterprise Editions
14:17:49 End: ProcessAfterDataMove()
14:17:49 Begin: BuildServer()
14:17:49 Begin Action: CreateRegistrySetSQL
14:17:49 End Action: CreateRegistrySetSQL
14:17:49 Begin Action: RegWriteSetupEntry
14:17:49 End Action: RegWriteSetupEntry
14:17:49 *** Unable to get RegisteredOwner to apply to Serial number
14:17:49 Begin Action: CreateSer
14:17:49 End Action: CreateSer
14:17:49 SetFileSecuritySQLAndAdmin for C:WINDOWSsetup.iss returned: 0, 0
14:17:49 SetFileSecuritySQLAndAdmin for C:WINDOWSsqlsp.log returned: 0, 0
14:17:49 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:17:49 SetFileSecuritySQLAndAdmin for C:WINDOWSsqlsp.log returned: 0, 0
14:17:49 SetFileSecuritySQLAndAdmin for C:WINDOWSsqlstp.log returned: 0, 0
14:17:49 SetFileSecPerfAndLogUsers for C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEBinnSQLCTR80.DLL returned: 0, 0
14:17:49 Begin ServPriv (INSTNAME)
14:17:49 End ServPriv()
14:17:50 Upgrading databases
14:17:50 Upgrading databases on instance 'INSTNAME'
14:17:50 C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBinscm.exe -Silent 1 -Action 6 -Service MSSQL$INSTNAME
14:17:50 Process Exit Code: (0)
14:17:50 C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBinscm.exe -Silent 1 -Action 6 -Service MSSQL$INSTNAME
14:17:50 Process Exit Code: (0)
14:17:50 C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBinscm.exe -Silent 1 -Action 1 -Service MSSQL$INSTNAME -StartupOptions -T4022 -T4010 -m
14:18:41 Process Exit Code: (0)
14:18:41 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -b -n -d master -o "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
eplsys.out" -i "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
eplsys.sql" -Usa -P"
14:19:18 Process Exit Code: (0)
14:19:18 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -b -n -d master -o "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
eplcom.out" -i "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
eplcom.sql" -Usa -P"
14:19:35 Process Exit Code: (0)
14:19:35 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -b -n -d master -o "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
epltran.out" -i "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
epltran.sql" -Usa -P"
14:19:57 Process Exit Code: (0)
14:19:57 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -b -n -d master -o "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
eplmerg.out" -i "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
eplmerg.sql" -Usa -P"
14:20:25 Process Exit Code: (0)
14:20:25 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -b -n -d master -o "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
emove_old_msx_accounts.out" -i "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall
emove_old_msx_accounts.sql" -Usa -P"
14:20:25 Process Exit Code: (0)
14:20:25 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -b -n -d master -o "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstallsp4_serv_uni.out" -i "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstallsp4_serv_uni.sql" -Usa -P"
14:20:27 Process Exit Code: (0)
14:20:27 D:SQL2KS~1x86BINNosql.exe -SlpcERVER01INSTNAME -b -n -d master -o "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall80sp4-tools.out" -i "C:Program FilesMicrosoft SQL ServerMSSQL$INSTNAMEinstall80sp4-tools.sql" -Usa -P"
14:20:28 Process Exit Code: (1)
14:20:33 Error running script: 80sp4-tools.sql (1)
14:20:33 C:DOCUME~1ADMINI~1LOCALS~1TempSqlSetupBinscm.exe -Silent 1 -Action 6 -Service MSSQL$INSTNAME
14:21:08 Process Exit Code: (0)
14:21:08 Action CleanUpInstall:
14:21:08 Installation Failed.




I hope for any help, because re-installing is not an option.There are 250 db's on it.



thanks so far.



rb

View 6 Replies View Related

SQL Server 2005 Install Error (Error 29528. Unexpected Error While Installing Performance Counters. )

Jun 12, 2007

I'm currently receiving the following error message whilst attempting to install SQL Server 2005 Standard Edition on Windows Server 2003 (32 Bit):
Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.

This server already has an install of SQL Server 2000 as the default instance. I'm attempting to install a new named instance of SQL Server 2005.

Extract from log:

<Func Name='LaunchFunction'>
Function=Do_sqlPerfmon2
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlPerfmon2
PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
<Func Name='Do_sqlPerfmon2'>
<EndFunc Name='Do_sqlPerfmon2' Return='0' GetLastError='2'>
PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
MSI (s) (4C:FC) [10:20:02:833]: Executing op: ActionStart(Name=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Removing performance counters,)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1281,Source=BinaryData,Target=Rollback_Do_sqlPerfmon2,CustomActionData=100Removing performance counters200000DTSPipelineC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INI)
MSI (s) (4C:FC) [10:20:02:849]: Executing op: ActionStart(Name=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing performance counters,)
MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1025,Source=BinaryData,Target=Do_sqlPerfmon2,CustomActionData=100Installing performance counters200000C:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INIC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.HC:Program FilesMicrosoft SQL Server90DTSBinnDTSPipelinePerf.dllDTSPipeline0DTSPipelinePrfData_OpenPrfData_CollectPrfData_Close)
MSI (s) (4C:94) [10:20:02:864]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI1683.tmp, Entrypoint: Do_sqlPerfmon2
<Func Name='LaunchFunction'>
Function=Do_sqlPerfmon2
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlPerfmon2
PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
<Func Name='Do_sqlPerfmon2'>
<EndFunc Name='Do_sqlPerfmon2' Return='2' GetLastError='2'>
PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
Gathering darwin properties for failure handling.
Error Code: 2
MSI (s) (4C!F0) [10:23:46:381]: Product: Microsoft SQL Server 2005 Integration Services -- Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.

You can ignore this and it will complete the installation, but subsequently trying to patch with SP2 will fail on the same sections - Hotfix.exe crashes whilst attempting to patch Database Services, Integration Services and Client Components (3 separate crashes).

I've removed SQL Server 2005 elements and tried to re-install, but it's not improved the situation.

Any ideas?

View 3 Replies View Related

SQL Server Client Tools

Jan 28, 2006

HiHow network administartor can find , who has AQL server client tools onhis system?Thanks

View 2 Replies View Related

How 2 Install Client Tools For SQl Server

May 31, 2004

In Server Explorer of VS .NET 2003, I tried to generate SQL script of the dbo.Portal (ibs)
but got
"To use this feature, you must install the client tols for SQL Server"

When I searched for Help, I've got
"1.Insert the MS SQL Server 2000 compact disc in your CD-ROM drive"

I installed and use MSDE and cannot recall the use of any CD for installation.

1)
Does it mean that I cannot install client tools from MSDE installation?

If not...

2)
I have installation of MS SQL Server200 Enterprise that cannot be installed on Windows Xp Professional that I use. Can I still install "client tools" from Enterprise Ed. for MSDE

View 2 Replies View Related

SQL Server Client Tools Installation

Jul 23, 2005

I'm trying to install SQL Server 2000 client tools on an XP workstation.MSDE already exists on the workstation. During the install I am neverprompted for a location to install to. I want to install to my D drive. Theinstall defaults to my C drive.Any thoughts?

View 2 Replies View Related

SQL Server 2000 Client Tools

Jul 20, 2005

According to MS Knowledge Base Article 269824, "[SQL Server 2000 ClientTools] ... must be installed ... on any computer on which someone may makedesign changes in an Access project to a SQL Server 2000 database".This is the situation I'm facing. Can I download these Client Tools andinstall them for free, or are they only available on the SQL Server 2000Installation CD?Thanks for any help!

View 1 Replies View Related

Upgrade Client Connectiviity Tools On Client Machines

Jul 23, 2005

Hello,Is it necessary to upgrade the Client Connectivity Tools on all clientmachines after the SQL Server database server is upgraded from Version7.0 to 2000?Thank you in advance!Eddy

View 1 Replies View Related

Urgent SQL Server Client Tools Question

Oct 11, 2007

I have to go back east.. I am going to be working remotely.
We still used SQL Server 2000 at work..
Will I be able to use SQL Server 2005 Express edition to remotely connect to and modify stored procs and tables?
 
what are all my options??

View 1 Replies View Related

Setup SQL Server 2k Client Connectivity Tools

Jul 13, 2004

Anybody please help me !

i was tried to install SQL Server 2k Client tools connectivity to my win 95, i was follow the installation procedure, 1). install common library updates for win 95, and then 2). install the server component (client connectivity tools), the installation is running well till copying "Microsoft Data Access Components - MDAC", i got error message : "Installation of the MDAC package failed (-1)". (so the installation doesn't complete).

please anybody help me, what's happen to my computer ?????????
:confused:


thanks for the help.

Andre.

View 2 Replies View Related

Can't Start Sql Server 2000, Error: Use Sql 2005 Management Tools !!!!

Aug 20, 2006

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"

can you help me ? plz !?

View 1 Replies View Related

Installing SQL Server Management Tools

Dec 10, 2007

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?

View 4 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved