SQL Server 2005 64bit SP2 Installation Issue On Cluster Servers.
Nov 23, 2007
Hi All,
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.
I have a problem with DTS - ActiveXScripting that it cannot initialize the script engine, I have the backward compatibility stuff installed, even tried a repair but still does not work.
Many thanks for any help you can provide on this problem.
Paul
Error Information below:
Date 17/04/2007 13:07:32 Log Job History (Test ActiveX Script)
Step ID 1 Server GBCONV1A002V03 Job Name Test ActiveX Script Step Name Step 1: Exec TestActiveX script Duration 00:00:01 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message Executed as user: WW004ConSrvSQLAgentA002. ...TSStep_DTSActiveScriptTask_1 DTSRun OnError: DTSStep_DTSActiveScriptTask_1, Error = -2147220487 (800403F9) Error string: ActiveX Scripting was not able to initialize the script execution engine. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 4500 Error Detail Records: Error: -2147220487 (800403F9); Provider Error: 0 (0) Error string: ActiveX Scripting was not able to initialize the script execution engine. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 4500 DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1 Error: -2147220440 (80040428); Provider Error: 0 (0) Error string: Package failed because Step 'DTSStep_DTSActiveScriptTask_1' failed. Error source: Microsoft Data Transformation Services (DTS) Package Help file: ... Process Exit Code 1. The step failed.
We have a 64bit installation of SQL Server (SSIS, SSAS) running and working fine. There is a requirement to install 64bit SSRS on this existing setup. The problem is: While running the SQL Server Setup wizard, the Reporting Services checkbox remains greyed out. In other words, there isnt an option to select SSRS for installation. So the question is: Is it even possible to install 64bit SSRS on an existing 64bit SQL server installation - given that SSRS wasnt installed during the first pass. PS: The SQL Server is SP2 on a Windows Server 2003 configured as an App Server.
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?
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)
Currently we have a single SQL server. It went down and the higher ups were none to happy. Lots of money lost, down time, unhappy customers....the whole nine yards. They want to throw all sorts of money at the problem and want a solution that is high availability and provides load balancing. I think I came up with a solution.
3x Windows 2003 Enterprise Edition servers running SQL 2005 Standard in a cluster all connected to a SAN.
I'm guessing I need to set up Network Load Balancing in order to load balance the SQL database. What we would love to have happen is if one of the servers goes down, everything else just picks up. That coupled with our database that is increasing in size and transactions gets load balanced.
Am I going down the right path? Something else I should look at? Or that I am missing?
Currently we have a single SQL server. It went down and the higher ups were none to happy. Lots of money lost, down time, unhappy customers....the whole nine yards. They want to throw all sorts of money at the problem and want a solution that is high availability and provides load balancing. I think I came up with a solution.
3x Windows 2003 Enterprise Edition servers running SQL 2005 Standard in a cluster all connected to a SAN.
I'm guessing I need to set up Network Load Balancing in order to load balance the SQL database. What we would love to have happen is if one of the servers goes down, everything else just picks up. That coupled with our database that is increasing in size and transactions gets load balanced.
Am I going down the right path? Something else I should look at? Or that I am missing?
Thanks and sorry for posting this in multiple places!
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 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 just installed the 64bit Vista and than wanted to install the 64bit SQL 2005 Std. Server on it.
Note: I downloaded my license from https://licensing.microsoft.com/eLicense/L1033/ProductDetail.Asp?SKU=228-05338.
Installing from SQLSTDSEL.ISO file results in the warning that for the REPORT- Server the .NET version has to be 32bit.
Stopping the installation at this point and try to install from SW CD SQL Svr Standard Edtn 2005 64Bit X64 English #1 x64 MLF.x11-57664 + SW CD SQL Svr Standard Edtn 2005 64Bit X64 English #2 x64 MLF.x11-57665 does not give the above error but on the other hand installs no server at all since somehow the installation routine is not working at all.
Installing now - after at least analysis server and reports server are 64bit and installed - from the first mentioned ISO results in the installation of the DB- Server.... but as a 32bit installation.
Now I wonder what did not work out - so maybe someone here has an idea if and how this problem is solveable.
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)
During the installation of Adding node to a SQL Server failover cluster(On passive node) getting error like.. The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.We  run the below commands but didn’t get any resolution & got the same above error .  1<sup>st</sup> Method…
1. Open console command (Run->CMD with administrator privileges).Â
2. net stop winmgmtÂ
3. Rename folder %windir%System32WbemRepository to other one, for backup purposes (for example _Repository).Â
4. net start winmgmt
2<sup>nd</sup>Â Method..
1. Disable and stop the WMI service.
a) Command : - sc config winmgmt start= disabled
b. Command : - Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â net stop winmgmt
I am learning SQL Server failover cluster installation. My question is regarding the options to install failover cluster instances on the Windows Failover Cluster. I have seen ead there are two options to do so.
From the installation center, installation option-> New SQL Server installation option and afterwards add node to SQL Server failover instance.From Installation Center, Advanced option-> Failover cluster preparation and then Failover cluster completion step.What is the difference between these two options and which option to use in which scenario?
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
We shall be taking a bunch of 7.0 instances and moving/upgrading to a SQL 2000 cluster server. I was thinking of creating new named instances on the 2000 cluster and upgrading each 7.0 server to it's respective named instance. Also thought of using the 2000 copy database wizard; I was told this didn't always work. Anyone hear of problems with this? Thanks
I'd like to install SQL SERVER 2005 Express Edition ,I begin to install it from DVD but during the installation it dosn't ask me about any instance and after installation there isn't SQLExpress service and I can't use sql server .(there are not MSSQL and Binn directory in sql server 2005) but when I install visual studio 2005 and after that I install sql server 2005 it ask me for name of instance and with this way every thing is ok and I use sql server completely.
I 'd like to know the complete installation of sql server 2005 is depend on installation of visual studio 2005 befor it ?if not how can I introduce any instance after installation of sel server 2005 .
This may seem like a completely foolish question, but is there any issue in using the 32bit workstation components (on XP) to connect to the 64bit server-side components? New to SQL2K5 and never had any issues using the 2K workstation/server components together.
I'm having problems installing SP1 on one of our servers.
If I try to install the x64 version of SP1 setup says it can not update my server and I should use x86 version. Trying to install the x86 version results in the message I should use x64 version....
When adding a node to a SQL Server 2012 Standard edition cluster, how I do I identify the location for SQL server shared components and the rest of the SQL Server installation binaries?
When adding a node to a SQL Server 2012 Standard edition cluster all the binaries went to the C: drive default location. We put those files on a different drive when installing the first node. What needs to be done so both nodes have the binaries on the same drives and folders?
I have a Windows 2003 Enterprise x64 edition cluster setup and functioning normally. Now, I am trying to get SQL Server 2000 installed as a failover cluster but am having some difficulty. When installing, I get the message '[sqsrvres] ODBC sqldriverconnect failed' in the event log. The message happens when the installer is trying to bring the SQL Server Service resource online.
I am able to ping the name of the instance successfully. I am able to manually start the 'MSSQL$InstanceName' service. I have turned off the firewall on both machines, but this did not help. I have the DTC Service setup as a resource in the same cluster group.
I also read http://support.microsoft.com/default.aspx?scid=kb;en-us;815431 which seemed promising, but did not reolve the problem.
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
I have implemented a application on SQL Server 2005, this application runs huge queries and some stored procedures. Now that client is shifting on SQL Server 64bit edition, what should i need to worry about. What all changes am i expected to handle.
I would also like to know if there are any other issues to be considered.
Recently, we have migrated our database from 32bit to 64bit. So far the application is working fine.
But I want to confirm that by any tool or automated process.
Is there any way or tool to check that the migrated data is correct and also to check if migrated database objects will work fine in 64 bit environment.
We have an application where part of the database is used for searching products and is very processor intensive due to the number of permutations and calculation that are required. This section of the database is scaled out by using transactional replication so that the €œsearch€? load is removed from central database€™s daily operations.
Each €œsearch€? server can handle around 15,000 search an hour with SQL taking about 3 seconds to return the result in XML (the system has be optimised to squeeze out every last bit of performance). This is in a 32bit environment. One other point, which is probably relevant, is that the Search data only totals 500MB.
With the possibility of upgrading these severs in the near future would we see any performance benefits in going 64bit. I know we won€™t take advantage of increased memory access due to the size of the search data but is there any discernable performance advantage between 32bit v€™s 64 bit processors and SQL Server 2005 64Bit. Or should I stick with SQL Workgroups and 32bit processor and save on the Standard SQL licence?
