SQL Server Enterprise 2005 Cluster Installation. Error: The Specified Module Could Not Be Found.
May 29, 2007
Hi Everyone,
I have problem when installing SQL 2005 Enterprise to my Windows 2003 R2 cluster. I install the SQL instance on the first node in my cluster, it analyses the cluster and comes up with no errors or warnings, i answer all the installation questions and proceed with the installation. When installing the SQL engine I see the status changing as the instance is started and then stopped again etc, finally the status changes to "removing backup files" when it get an error that reports:
"The setup has encountered an unexpected error while Completing Commit. The error is: The specified module could not be found."
Unfortunately there isnt any more information to go on. Any help would be appreciated.
When the setup program tries to start the database service (the last step of installation), it indicates an error 29503.
The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (17058)
I receive the below mentioned error message each time I try to install SP2 on SQL 2005 64 Bit Cluster: Using PrevRegRootPath: SoftwareMicrosoftMicrosoft SQL ServerMSSQL.2 GetServiceUserGroup failed for PLMCWSM01, 5 Error Code: 0x800706fd (1789) Windows Error Text: The trust relationship between this workstation and the primary domain failed. Source File Name: sqlcasqlcax.cpp Compiler Timestamp: Fri Feb 9 22:35:02 2007 Function Name: SetInstanceProperty Source Line Number: 1223
MSI (s) (78!08) [01:05:21:864]: Transforming table Error. MSI (s) (78!08) [01:05:21:989]: Transforming table Error.
MSI (s) (78!08) [01:05:21:989]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (78!08) [01:05:21:989]: Product: Microsoft SQL Server 2005 (64-bit) -- Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation. Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
I am trying to install SQL 2005 in a 2-node Windows 2003 cluster. I have tried both upgrade and fresh installation, but got same error. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:
I am installing SQL 2005 on a 2-node cluster running on Windows 2003 R1. When I try to install SQL 2005 on my cluster, I get an installation error. The error stops the installation while checking system configuration after installing prerequisites. The log file includes the following message
could not find file datastoresqldiscoverycollector.cppp Failed to start discovery on machince :Node2
This happens when I run the steup from Node1 .When I run the installation on Node I get the same error with the machine name as Node1 .
I tried Enabling Netbios over TCPIP for the heartbeat network however with no results
Can somebody please provide the next steps .A step by step approach will be greatly appreciated .
I am installing SQL 2005 on a 2-node cluster running on Windows 2003 R2. When I try to install SQL 2005 on my cluster, I get an installation error. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:
C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2007/9/12 16:6:42 Complete: LoadResourcesAction at: 2007/9/12 16:6:42, returned true Running: ParseBootstrapOptionsAction at: 2007/9/12 16:6:42 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2007/9/12 16:6:42, returned true Running: ValidateWinNTAction at: 2007/9/12 16:6:42 Complete: ValidateWinNTAction at: 2007/9/12 16:6:42, returned true Running: ValidateMinOSAction at: 2007/9/12 16:6:42 Complete: ValidateMinOSAction at: 2007/9/12 16:6:42, returned true Running: PerformSCCAction at: 2007/9/12 16:6:42 Complete: PerformSCCAction at: 2007/9/12 16:6:42, returned true Running: ActivateLoggingAction at: 2007/9/12 16:6:42 Complete: ActivateLoggingAction at: 2007/9/12 16:6:42, returned true Running: DetectPatchedBootstrapAction at: 2007/9/12 16:6:42 Complete: DetectPatchedBootstrapAction at: 2007/9/12 16:6:42, returned true Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__3608" returned false. Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions: Condition "Setup is running locally." returned true. Running: PerformDotNetCheck2 at: 2007/9/12 16:6:42 Complete: PerformDotNetCheck2 at: 2007/9/12 16:6:42, returned true Running: InvokeSqlSetupDllAction at: 2007/9/12 16:6:42 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.1399.0 <Func Name='DwLaunchMsiExec'> Examining 'sqlspars' globals to initialize 'SetupStateScope' Opening 'MachineConfigScope' for [OAKLRRDSDBA] Trying to find Product Code from command line or passed transform If possible, determine install id and type Trying to find Instance Name from command line. No Instance Name provided on the command line If possible, determine action Machine = OAKLRRDSDBA, Article = WMIServiceWin32OSWorking, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = WMIServiceReadRegWorking, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = WMIServiceCIMDataWorking, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = XMLDomDocument, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = Processor, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = PhysicalMemory, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = DiskFreeSpace, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = OSVersion, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = OSServicePack, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = OSType, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = iisDep, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = AdminShare, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = PendingReboot, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = PerfMon, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = IEVersion, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = DriveWriteAccess, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = COMPlus, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = ASPNETVersionRegistration, Result = 0 (0x0) Machine = OAKLRRDSDBA, Article = MDAC25Version, Result = 0 (0x0) ******************************************* Setup Consistency Check Report for Machine: OAKLRRDSDBA ******************************************* Article: WMI Service Requirement, Result: CheckPassed Article: MSXML Requirement, Result: CheckPassed Article: Operating System Minimum Level Requirement, Result: CheckPassed Article: Operating System Service Pack Level Requirement, Result: CheckPassed Article: SQL Compatibility With Operating System, Result: CheckPassed Article: Minimum Hardware Requirement, Result: CheckPassed Article: IIS Feature Requirement, Result: CheckPassed Article: Pending Reboot Requirement, Result: CheckPassed Article: Performance Monitor Counter Requirement, Result: CheckPassed Article: Default Installation Path Permission Requirement, Result: CheckPassed Article: Internet Explorer Requirement, Result: CheckPassed Article: Check COM+ Catalogue, Result: CheckPassed Article: ASP.Net Registration Requirement, Result: CheckPassed Article: Minimum MDAC Version Requirement, Result: CheckPassed <Func Name='PerformDetections'> 1 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run: Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache Source File Name: datastoreclusterinfocollector.cpp Compiler Timestamp: Fri Sep 16 13:20:12 2005 Function Name: ClusterInfoCollector::collectClusterVSInfo Source Line Number: 883 ---------------------------------------------------------- Failed to detect VS info due to datastore exception. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "InstallIds" {"MachineConfiguration", "", "OAKLRRDSDBB"} in cache Source File Name: datastoresqldiscoverycollector.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SqlDiscoveryCollector::collectProperty Source Line Number: 132 ---------------------------------------------------------- Failed to open discovery on machine: OAKLRRDSDBB WinException : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastoresqldiscoverycollector.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SqlDiscoveryCollector::collectProperty Source Line Number: 132
A few months ago, I was trying to install SQL Server 2005 SP2 on a cluster (Active-Active), the Cluster has 3 instances, 2 lives in one node and the other one in the other node. When I try to make the deployment an error message appear, I do not have the error right now but it€™s something like €œCould not connect to the passive node, installation failed€?. The worst part of the error was all instances shut down and I couldn€™t bring on line and I have to reinstall all instances. I need to install SP2 but I€™m a little afraid fail again. Do you know the best way to deploy the SP2 on a cluster? Maybe move all instances in one node before install SP2? Can you help me with your comments. Do you think I have problems with the windows cluster?
when I click on the lookups tab with SQL Server 2005 Legacy DTS I get the following error.
The specified module could not be found. (ERROR_MOD_NOT_FOUND) Some modules the query builder depends on could not be found. The query builder designer will not be functional.
I tried to change / add password in SQL Server Compact Edition 2005 (in Mobile 5.0) via SQL Server Management Studio. As a result I got an error: "The specified module could not be found." I wonder why and how can I change the (blank) password to a new one?
when i trying to make run the sql server in the sql server configuration I recieve this message the specific module could not be found [08007007e]. I wnat to know how to solve it
My laptop has VS 2005 installed. I am trying to install MS SQL Server 2000 Enterprise Edition, when i run "install database components", it gave error: "MS SQL Server 2000 Enterprise Edition component is not supported on this operating system. Only client components will be available for installation". then when i click on "ok", then "next", when i click on "next" on the "computer name" page, it gave another error: "A previous program installation created pending file operations on the installation moachine. You must restart the computer before running setup". I restarted my laptop following the instruction, but same thing happened when i run the installation. Plz help
We have been experiencing issues with SQL Server 2005 SP2 upgrade on cluster servers. After running the setup, it gives failure message for Database services.
Installing SP2 on 64bit cluster server we get error regarding "passive node not patched properly or run the setup from passive node". However, select serverproperty(€˜productlevel€™) returns the output as "SP2". On more digging we found from SQL Server Error log, that the resourcedb of that server is of level 9.0.0.3199
€œThe resource database build version is 9.00.1399. This is an informational message only. No user action is required.€?
However if we do the SQL Server 2005 SP2 upgrade on standalone machines with the same software repository, it upgrades successfully and also resourcedb upgraded to 3042 version. So if we look at the errorlog of a standalone machine it gives following message.
"The resource database build version is 9.00.3042. This is an informational message only. No user action is required."
I again reiterate that, this is the issue we have faced on 64bit SQL Server 2005 SP2 upgrade only on cluster SQL Servers, however on standalone machine it works fine and 32bit SP2 installation works fine.
Due to a SQL 2014 cluster installation failure related to security while setting up the primary node, I had to remove the node and any related installation programs from the node and redo the installation again. However I am unable to use the machine name as the SQL network name during the instance configuration, I get the following:
Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException: The SQL Server failover cluster instance name "MachineName" already exists as a server on the network. Specify a different failover cluster instance name.I am still getting the same name since the node name "MachineName" is listed under the cluster name. I have used machine name as SQL network name without an issue. I do not have any existing SQL machine name in network using same machinename which I want to use for this installation.
I am attempting to install SQL Server 2005 Enterprise Edition. The install stalls permanently, the SQL Server's memeory usage and CPU usage plummets to nothing and the SQL Server 2005 Setup Dialogue's status stops at "Validating Database Password." This occurs on the SQL Server Database Services portion of the install. The last line in the SQL Server Setup.log says "<Func Name = 'SAPaswwordPolicyCheck'>
I have verified that the sa password that I am entering when prompted for it in the install setup is valid with respect to SQL Server and Windows Server 2003 SP 1 (13 chars, at least one symbol, at least one upper and at least one lower). What else could be causing this problem? Any ideas or stabs would be greatly appreciated.
Currently running Vista Home Premium 64 and Visual Studio 2008 Trial.
1. Create Win form app. 2. Add new data source... 3. New connection - SQL Server Compact 3.5 - Northwind.sdf 4. Highlight Products and Suppliers. 5. Drag both onto Win form 6. Run with debug 7. Error message "Unable to load DLL 'sqlceme35.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"
some blogs advice change dir in SQL Server Compact 3.5 in regedit but regedit doesn't even have SQL Server Compact 3.5; only SQL ServerSQLExpress.
reinstall SQL Server Compact 3.5 and problem still exists.
I noticed in installing a SQL2005 failover cluster instance,that it is not necessary to install on both servers. Installing on the primary node automagically installs to the secondary node. Does this constitute a COMPLETE install? It all seems to work. BUT this process does not intall client pieces (SSMS, for instance) on the secondary node. If you want that stuff there, do you then go to that box and just do a client install?
I have a problem with the sql 2005 installation in a W2003 R2 cluster. I launch the setup of one node, and I do all the steps of the installation without problems, the copy of data start well, the process request me about the second Cd .. and in this point of the setup ... appears an error. The message is something like :"Remote copy process failed". And the setup finish.
Does anyone experience an slow installation process of SQL 2005 on a MS Cluster enviroment ? I checked the scheduler on node2 and the status is running and no more information on the logs other than the starting time which it was 17 hours ago. Thanks in advance
From the MS cluster I'm able to see both node, do switching etc with not problem. When I install the SQL 2005 on node one and try to add server2 it is showing the server2 in the list of unavailable nodes with the status UNKNOWN. I went over the cluster and SQL installation step by step, but still not clue Any help is appreciate it
I am trying to install Sqlserver SP2 for 64bit with Microsoft Cluster. It failed with Database Services and Client services tool. I am running this installation from the Active Node only. Appreciate any help to fix this.
Following is the error I am seeing.
Product : Database Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : NA Log File : Error Description : This installation must be run from the active node. You are running it from a passive node. To proceed, cancel the installation and run it again from the active node.
Product : Client Components Product Version (Previous): 1399 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 Files (x86)Microsoft 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: 0x8004D01B)
Issue when building a FCI where after the step of specifying what drives the data, logs, tempdb go, the installer errors with this message:
Exit message: The volume that contains SQL Server data directory D:SQL_DataMSSQL11.MSSQLSERVERMSSQLDATA does not belong to the cluster group.
We are running Windows Server 2012 R2 and SQL Server 2012 Enterprise with Veritas Storage Foundation for Windows 6.1. I've confirmed that the disk group exists and is mounted in Windows and presented as available storage. Symantec has an article detailing this same circumstance but the Microsoft KB article that they refer to only has hotfixes for Windows Server 2012, not R2.
Current set-up: three node cluster running Windows Server 2003 Enterprise Edition SP2 with two instances of SQL Server 2005 Standard Edition SP2.
Virtual node 1: Standard Edition, default instance, Database Engine only
Virtual node 2: Standard Edition, named instance, Database Engine, Analysis Services and Integration Services
Physical node A: Prefered node for virtual node 1
Physical node B: Failover node for both virtual node 1 and 2 (thus having two installations of Standard Edition)
Physical node C: Prefered node for virtual node 2
We started off with this set-up because there was no need for Enterprise features, and SQL 2005 supports failover clustering with two nodes in Standard Edition. Saved a bundle of cash, so everybody's happy. Now we need to run a solution on virtual node 2 that requires Enterprise features in Analysis and Integration Services, so an edition upgrade is required on virtual node 2. I have done some research and found several edition upgrade examples, but none that match the above scenario. We are running production on these machines, so I can't risk experimenting with command line options, I have to be right the first time.
Is it possible to mix two editions of SQL Server 2005 in one cluster? Can I upgrade virtual node 2 to Enterprise but leave virtual node 1 at Standard? What procedure do I have to follow to upgrade all three components of virtual node 2 to Enterprise Edition on both physical node B and C?
Hi,I need help. I transferred my database from one server to another byusing attach detach process.I created all the jobs which existed in theold server in the new server. Everything looked fine but a couple ofjobs is a giving me some problems. When I try to edit the job step Icould see that the database dropdown list doesn't contain the databasename(which I transferred from the old server)Does anyone have any idea about it.ThanksArun
I'm Getting "Report Server WMI Provider error: Not Found" when trying to Grant Database Access while configuring the Reporting Sevices Integration. Logging in fine to the DB. Tried all the WMI troublshooting and can't find any issues there. Any tips?
Bootstrapsetup.exe === MSI (c) (88:78) [10:24:26:828]: Resetting cached policy values MSI (c) (88:78) [10:24:26:828]: Machine policy value 'Debug' is 0 MSI (c) (88:78) [10:24:26:828]: ******* RunEngine: ******* Product: F:ServersSetupSqlRun_SQL.msi ******* Action: ******* CommandLine: ********** MSI (c) (88:78) [10:24:26:828]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (88:78) [10:24:26:828]: Grabbed execution mutex. MSI (c) (88:78) [10:24:26:828]: Cloaking enabled. MSI (c) (88:78) [10:24:26:828]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (88:78) [10:24:26:828]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (7C:94) [10:24:26:843]: Grabbed execution mutex. MSI (s) (7C:54) [10:24:26:843]: Resetting cached policy values MSI (s) (7C:54) [10:24:26:843]: Machine policy value 'Debug' is 0 MSI (s) (7C:54) [10:24:26:843]: ******* RunEngine: ******* Product: F:ServersSetupSqlRun_SQL.msi ******* Action: ******* CommandLine: ********** MSI (s) (7C:54) [10:24:26:843]: Note: 1: 2203 2: F:ServersSetupSqlRun_SQL.msi 3: -2147287010 MSI (s) (7C:54) [10:24:26:843]: MainEngineThread is returning 1620 MSI (c) (88:78) [10:24:26:843]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (88:78) [10:24:26:843]: MainEngineThread is returning 1620 === Verbose logging stopped: 3/27/2008 10:24:26 ===
SUMMARY.txt (C:Program FilesMicrosoft SQL Server90Setup BootstrapLOG) has follwing contents...
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Thu Mar 27 09:57:45 2008
Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_5.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_5.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server VSS Writer Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_5.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_6.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Visual Studio 2005 Premier Partner Edition - ENU Product Version : 8.0.50727.42 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_PPESku_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_6.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Books Online (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BOL_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_6.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_5.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Integration Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_DTS.log -------------------------------------------------------------------------------- Machine : ADITYA Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLXML4_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLXML4_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Analysis Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_AS.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Notification Services Product Version : 9.00.1399.06 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_NS.log Error Number : 1602 --------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
