There are have 2 nodes.Both on cluster and on a test_domain.Test domain is a active directory domain.
Node_A & node_B has C and D drives.D drive will have programs.
There is one common drive E - where data will go.
Now,I have to install SQL2000 on it.Can anyone tell me in layman's way how to install it.Do I have to have D drive in shared mode?When I give remote connection what should I give here?
Win 2000 clustered was installed by a NT expert and is working fine.
I am assuming drive_D will hold the SQl programs.
I tried one article posted here from Sqlserver preformance side but nothing worked.
Does it matter as both the nodes are on a Active Directory?
I am trying to configure a 2 node SQL cluster. MSCS is configured and is failing over correctly, however when I start the installation of SQL Server, and specify the IP address of the virtual server and hit next, the installation hangs, and stops responding. I have configured MS DTC and verified that it shows up in the cluster administrator. I am not sure what else to do, please help.
I have installed a dual node active passive W2K3 Clusters with SQL 2K. The cluster has RAID10 for data and RAID1 for Quorum and Transaction Logs. How do I put the Transaction logs on the RAID1 disk as at install SQL2K only asks where you would like to put the SQL data ?
I applied sql2k post sp4 fix 2040 and 2162 on active node of the cluster without error, the version number is 8.00.2162. When failover the cluster and double check version number again, it's 8.00.2040. That means fix 2162 didn't push to passive node. So I tried apply fix 2162 on current active node but stopped with KB904660(ENU) setup error: An error in updating your system has occurred. Can't find any log file, and OS is win2k3 enterprise edition with sp1. Anyone got similar issue?
We have a current install of SQL2005 Developer on a Win 2003 Server Enterprise and it works as advertised. It is accessed as Test05
Yesterday a SQL2000 Developer Edition was also installed on the same Server as named instance Test05Test052000.
The 2000 seems to start and run OK and can be connect to by Management studio etc from that same box. However it can not be connect to via the network. Any ideas?
Hi While configuring an active / active cluster, do I need to run the SQL setup on both nodes? The SQL2K setup installs binaries on localdisks of both nodes - hence the question.
The company for which I work did not have a DBA until I started a few weeks ago. Whoever installed SQL2K used the wrong CD so they have been running Personal Edition on their servers. I have installed a new SQL2K standard instance and have restored everything except the jobs and DTS packages. Can the msdb from the Personal edition be restored to the standard instance?
Is it possible to downgrade SQL from Enterprise to Standard Edition, or do you have to remove the previous installation (uninstall) and reinstall. Meaning you would also have to restore all user databases? Thanks.
I'm have been assigned the task of installing SQL Server 2005 as a cluster on a Windows cluster that has already been setup with a sans.
I've done alot of reading the past two days and I still have a few questions which I need answered before I begin.
Our setup- DC - nothing but domain controller S1 - SQL server 1 S2 - SQL server 2
S1 and S2 share the following drives (database) (transaction logs) (F) (G)
Do I install SQL on each of the clusters? If so, do I just follow the instructions the exact same? And am I suppose to power S2 down while I install SQL on S1 and then vice-versa?
1. have 4 drives and all are within the SQL resource group but can see only 1 drive through management studio when doing a backup
2. Is restore only possible through the /backup folder on the default installation path as it is a small drive so can a restore be possible from any other locations
I have two clustered server. (ms sql 2000 server, windows 2003 server) now i need to add one new server to the cluster and take the secondary node off. I have installed SP4 & hotfix in my SQL Server cluster before.
My question is do I still need to install SP4 & hotfix in my new server?
I have YET to have a 100% CLEAN install of SQL 2005 in a clustered environment. SQL 2005 Std. was not so bad, I think I finally managed a 99% clean install (no script errors on patches) on the third try.
SQL 2005 EE keeps erroring off on 2153 patch install. The error logs are no help at all; they simply stop logging activity at about the point that the error occurs.
Process: Install OS Patch OS to SP1 Cluster OS on SAN Configure Cluster Groups (DBC01, DBC02, DBC03) with cluster disks Configure MSDTC (network access, configure cluster resources)
Start SQL Installation Install RTM Binaries on Node 1 for Default Instance Install Workstation and non-cluster components on remaining nodes Install RTM Binaries on Node 2 for Named Instance
Reboot all nodes
Install SP1 for all instances from node 1
Install SP1 for all local services/applications for all other nodes
While attempting to install the 2153 SQL patch/hotfix, the process will either: Hang while waiting for the first passive node for the default instance; or Crash immediately with no error messages in the logs.
This is no nearly detailed enough, I know. I'm missing error messages and more. It's snowing outside and I have to get home. I just think that the installation for this product in a clustered environment is very unstraightforward at best, and at worst is a real liability to an organization since it's practically impossible to get it clean the first time through.
I'm trying to install SQL into a new cluster. The cluster service is up and running fine. I can even fail it from Node 1 to Node 2 with no problem.
However, when I try to install SQL, I get a screen that tells me that SQL is performing required operations on the cluster nodes...this may take a few minutes.
After hanging on that message for a looong time, SQL comes up with a generic message that the install failed and that SQL is cleaning up. Then, nothing. No error message, nothing that I can track down.
Some system information: Node 1. Dell PE2650, 2x 2.8 GHz, 2 GB RAM - Windows 2000 Advanced Server - Dell Perc3/DC RAID/SCSI Controller - Dell Perc3/DI Integrated RAID Controller
Shared Storage. Dell PV220 - Q: Quorum (1 GB) - S: Data (136 GB) - T: Logs (20 GB)
Additional Notes: 1. I am using a checklist from Dell and another from MS. 2. I have also downloaded and read the checklist from sql-server-performance.com. 3. I have ensured that the comclust.exe was run on both nodes prior to starting the SQL installation 4. I am using SQL Enterprise Edition. We used the same CD to install a cluster server two weeks ago.
Questions: 1. Where can I find an installation error log that might point more specifically to where the problem might be? 2. Any thoughts on what the problem might be? 3. Anyone ever experience something similar?
Have SQL 2000 SP4 clustered instance running now. Attempted inplace upgrade to SQL 2K5 standard edition. Boxes are Windows 32 bit Ent Edition, SP2. Install wizard installed pre-req's just fine, and I got past the "components to install" box of the install wizard. When I clicked next, the current 2000 instance (already installed component) was grayed out and I could not select it. Checking the messages in the install wizard, I saw that my "upgrade was blocked". I cancelled out of the install wizard to verify all requirements.
Bounced both boxes, and now when I try to run the install wizard, it tried to install the required support files (ASP.net 2.0, SQL Native Client and what not) and then the install wizard hangs..... and never comes back. I have to kill it from taskmgr. Bounced the boxes and tried again, same thing. Install wizard hangs forever.
Yes, I am running from the active node holding the cluster resources. Yes, SQL 2000 instance is cold. Yes, I've checked add/remove programs and there is nothing to uninstall. Checked event viewer and I see the following errors:
Hanging application setup.exe, version 2005.90.1399.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Fault bucket 238575085.
I've reached out to our TAM, but any help would be appreciated. No matter how many times I try, the install wizard now chokes and never comes back.
When you try to re-apply SP2 for SQL 2005 on node added to cluster it continously fails?
Only way to apply SP2 is to shut down original node(with SP2 allready applied) and then apply SP2 and hotfixes on additional node!
I would like to see some reply from SQL support team for this 'issue'. Is this normal? This bring many issues when you have more than one sql on 2 node cluster....etc
I'm running into issues installing SQL 2005 Enterprise on a Win2003 server. They seem to be related to missing rights. I've done a lot of research and have come up empty. Does anyone know why I'm getting these log entries? Thanks for any help.
Running: OpenPipeAction at: 2006/0/31 11:35:35 Complete: OpenPipeAction at: 2006/0/31 11:35:35, returned false Error: Action "OpenPipeAction" failed during execution.
Error: 0x80070005 TaskScheduler::SetTargetComputer for \SERVER Complete: RunRemoteSetupAction at: 2006/0/31 11:35:35, returned false Error: Action "RunRemoteSetupAction" failed during execution. Error information reported during run: Attempting to determine log files for remote install. Connection to remote computer's scheduler service. Error: 80070005 Access is denied.
Skipped: InstallASAction.11 Waiting for actions from remote setup(s) Breaking wait state and aborting package due to cancel code received: 1602 Remote setup(s) are ready Notify package action is determined: 1602 Error Code: 0x800700e9 (233) Windows Error Text: No process is on the other end of the pipe.
Source File Name: remotemessageliboverlappedpipelistener.cpp Compiler Timestamp: Fri Jul 29 01:13:51 2005 Function Name: sqls::OverlappedPipeListener::writePipe Source Line Number: 294 Notification failed to send.
I am trying to install SQL 2005 in a 2-node Windows 2003 cluster. I set the cluster up through Virtual Server 2005 with 2 virtual nodes and one virtual domain. The nodes can connect to each other as well as the physical machine. When I try to install a fresh copy of SQL 2005 on my cluster, I get an error every time. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:
******************************************* Setup Consistency Check Report for Machine: --SERVERNAME-- ******************************************* 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: Warning Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled 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: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56 ---------------------------------------------------------- Failed to find a cluster group that owned shared disk: J: WinException : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56
I am having a problem installing the first instance in our two node cluster. We're running 64-bit 2003. I'm trying to install the database engine and client tools only, so of course I get the IIS warning for both nodes. This is expected because I don't want Reporting Services. So the install should still work. However, I'm also getting the ASP.net registration message on only one node.
"Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS)."
I suspect that I should be getting the error on both nodes because I don't have IIS installed on either node. But again, I only get a warning for one node. This is probably the cause of my failure because it sees the nodes as being out of sync. I'm not sure how to correct this though when it appears that the nodes are exactly the same. Does anybody have any ideas? Thanks in advance!
yesterday i installed sql2k5 on a activepassive cluster and for some strange reason the mssqlserver service does not want to start up on the node that i installed it on but if i fail it over to the passive node it will start fine. system info below:
I am looking for a best practice or any suugestion on the best way to install an additional Sql 2005 instance in a cluster environment. We have a production environment that is active/active/passive and need to install an additional instance with a little impact to the current production instances as possible. Ant suggestions or articles I can review?
I can't seem to install SQL Server 2005 (x64 version) on an x64 Win2k3 two node cluster.
I get all the way through the configuration and setup fails because it cannot start a task on the remote node. The error message indicates to check the task scheduler log file, which I have and I cannot find any 'errors' in the file.
Google/MSDN/Technet turn up nothing on multiple searches. Has anyone else run into this problem?
My installation account is a local admin on both machines, so is the sql cluster account. For the life of me I cannot figure out what's different for an x64 install vs 32bit....
Try to install sql 2005 x64 on a Win2003r2 x64 two node cluster. All looks fine as far I get to the "cluster node configuration" dialog. My second node is always displayed as "unavailable node" reason "unknown".
- I checked the logfiles but could not find any error. - Installation user & cluster user are both local admins. - Tried with sql 2005 x32 version -> same result.
What do I miss out here? Any help is highly appreciated.
Do I have install sp2 on each node in the cluster or do I just need to install it on the active node and reboot? Do I need to pause the active node? I was looking for some documentation for this and didn't mention anything regarding pausing the active node in the cluster in order to apply the sp2 for sql 2005.
When trying to install SQL 2005 as a failover cluster in a Windows 2003 64 bit SP 2 cluster, I receive the following error when trying to select the installation path after choosing to install as a failover cluster.
_________________________ TITLE: Microsoft SQL Server Setup ------------------------------ The drive specified cannot be used for program location. Program files must be installed on a valid local disk available on all cluster nodes. The valid values are __________________________
There is a knowledge base artical that says this can be from not installing the software with an account with admin permissions on all the servers in the cluster with the 64 bit install, but the account I used is an admin on both servers.
The only thing that I can think is causing the problem is that it is setup to boot from our SAN and it is using one fabric. By default Microsoft Clustering doesnt like this, but we use the newest storeport driver and applied the registry key supplied in KB article 886569 to resolve this. I could not find any documentation showing that this would limit a SQL 2005 Failover Cluster from seeing the shared storage.
I am trying to install a new database onto a SQL 2005 cluster with installshield and am getting an error that I can not find any info on. The error is as follows.
"Cannot use program file ... for cluster server. Only 4 metafiles on which the cluster resources of the server has a dependency can be used."
I will confess to knowing very little about clustering so any help would be greatly appreciated.
Hello all: looking for some general advice on proper approach. looking to move databases off of a clustered instance to a new (non-clustered) server. Got several issues i'd like some advice on.
1. This is an OLTP instance that's been around for a while & it's pretty well encrusted with apps & processes that attach to it. Therefore it would be a very good thing if we didn't need to change the connection information in several hundred places after the move. I've tested one approach to this that seems to work: moved the instance to a server which has the same name as the cluster resource associated with the clustered instance and an instance that has the same name as the clustered instance. For example: cluster install is aiproddbproduction, moved it to a box called aiproddb with a named instance called "production". There's a bunch of tedious network stuff that has to be done to make this work (binding an IP address to the MAC address of the new box and some murky DHCP reservation fiddling), but after the network crew got done cursing me it did finally work. Does this seem like a reasonable approach?
2. What's the best way to transfer security info to the new instance? I used the transfer Logins DTS widget but had some problems with it not being able to find some groups in AD.
3. what's the best way to transfer DTS packages?
4. is it necessary for the new instance to be at the same patch level as the old instance? the old clustered instance is still at SP3 and i threw the latest SP4 on the new location. good/bad/indifferent?
5. i was planning on taking a full backup & restoring it to the new machine. Is there a better way? Is the wizard for copying databases a good thing?
Those are these issues i'm aware of and have given some thought to. There are probably things about this i haven't considered and would appreciate some word on.
We have 5 instances on our clients old machine with SQL 2005, now they want us to move on cluster environment with SQL 2012.
Once I have installed and configured SQL cluster with single instance, but how to install SQL Cluster environment for Multiple instances.
Should I install all the instances first and than have to configure cluster ? OR Is there any way that first I will install cluster and than we can add the instances ?
Hi we have a two node windows 2003 x64 cluster, each running a SQL 2005 instance. I've added a new node to the cluster and am now trying to set up a new instance of SQL 2005 on the new node (node c). During the install i am getting a failure just after the stage where you choose the features to install. I'm selecting SQL database engine with Failover Cluster. When i click next i get a message which states:
"The drive specified cannot be used for program location. Program Files must be installed on a valid local disk available on all cluster nodes. The valid values are"
I've read a number of articles about possible causes for this and i've checked all the suggested causes but none of these have made a difference. The cluster disk resource is healthy and can be failed between all nodes in the cluster. No errors are generated. I am using an account which has domain admin rights and I can access all admin shares on all nodes. Some of the articles i have referenced are here:
http://support.microsoft.com/kb/907261
http://support.microsoft.com/?kbid=913815
http://blogs.technet.com/mbaher/archive/2007/03/23/clustering-sql-2005-and-administrative-shares.aspx I've tried uninstalling all components etc but still i can't get it to work. The next step is rebuilding the server completely so does anyone have any suggestions?
I have a Cluster environment that has SQL 2000 Enterprise installed. I would like to install SQL 2005 Enterprise as well. What should I watch out for. Do I need to specify a named instance for the 05 install, setup is giving me the option and does see the 2000 instance? Is there a document that walks through this installation?
