INF: AlwaysOn – The secondary database doesn’t come automatically when the primary instance of SQL Server goes down

In this blog we would discuss about behavior of AlwaysOn availability group where the secondary database doesn’t come automatically when the primary instance goes down. The secondary database goes into Resolving state. On the failover cluster manager the resource appears in fail state. While doing some research, we found that if we stop SQL Service manually…

2

Can I listen to you Mr. MSDTC?

MSDTC unlike on earlier version of Windows, support multiple instances on Windows 2008. You can create a Clustered MSDTC resource in each Cluster Group. The below link gives you more information understanding MSDTC resources in Windows 2008 Failover Cluster. http://technet.microsoft.com/en-us/library/cc730992(WS.10).aspx   Some Default Facts: 1.       If there are no clustered MSDTC resources, SQL Server will…

1

Unable to see the properties of DTC in the Component Services

After Preparing and Installing SQL Server 2008 Cluster on a Windows 2008 Server Cluster from the “Advanced” option in the Landing Page, we are unable to see the properties of one of the Instances of DTC in the Component Services UI. It appears blank with the message: No properties are available on this object. We…

1

SQL Server 2008 & SQL Server 2008 R2 clustering FAQ’s:

1.       Can I use SQL 2008 slipstreamed installer to install SQL Server 2008 failover cluster? Yes. Launch the setup.exe from command prompt with PCUSource = <path to extracted SP1>. Refer http://blogs.msdn.com/petersad/archive/2009/03/02/sql-server-2008-basic-slipstream-steps.aspx for additional information. You can use merged slipstream installer for SQL 2008 cluster installation.   2.       If I install failover cluster using slipstream, do…


Unable to view Error logs in SQL Server Management Studio on a cluster

While trying to view the SQL Error logs in SQL Server Management Studio or using xp_readerrorlogs it internally executes sp_enumerrorlogs. And sp_enumerrorlogs – tries to execute the below command:          serverproperty(‘ServerName’) – The command was providing the cluster name(CLUS180633) instead of the SQL virtual server name (SQL). – Further examination of the registry revealed the…

3

On a Clustered SQL Server 2005 running on Windows 2003 machine the maintenance plan MIGHT fail with: “The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired)”

On a Clustered SQL Server 2005 running on Windows 2003 machine the maintenance plan fails with below error.  This issue is also seen on a newly created a maintenance plan as well. Executed as user: <Domain>\User. Microsoft (R) SQL Server Execute Package Utility  Version 9.00.4035.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.   …

5

Unable to failover a Named instance of SQL server 2005 in cluster or unable to bring a Named Instance of SQL server 2005 Online

The problem is that we have a Named instance of SQL Server 2005 in a 2 node cluster. While trying to bring the SQL Services online we get these error messages in the Application Event Log.   Application Event Log:  Event Type:       Error Event Source:    MSSQL$SQL2k5 Event Category: (3) Event ID:          19019 Date:                7/17/2009 Time:               …

1

INFORMATIONAL: Understanding and Troubleshooting MSP Error: 29512 SQL Server Setup was unable add user <DomainUsername>, when you try to install SQL Server 2005

Good morning Folks! Today I will take you through a setup issue that many of you might have run into when trying to install SQL Server 2005 (especially on a cluster). I’ve tried to list down all possible solutions to the following errors one faces while installing/patching SQL Server 2005.   Hope you find this…

3

SQL Server 2005 SP2 installation hangs on a 2 Node cluster with the message: "Awaiting first complete passive cluster node"

Environment: SQL Server Enterprise Edition 2005 32 bit on Windows Server 2003 Enterprise SP1 Consider a scenario where you are installing SQL Server 2005 Servce Pack 2 on a clustered environment. Sometimes you will notice that the installation get hung while installing the patch on the passive node, the setup screen will show you following…

1

Unable to create Maintenance Plans or DBMail Fails after service pack/Hotfix is applied on SQL Server 2005 fail over cluster instance running on Windows 2008 cluster

We have seen a couple of cases, wherein we are unable to create maintenance plan or DBMail Fails after applying SP on SQL Server 2005 failover cluster instance running on Windows 2008 Cluster. Resource Database and other system databases may not be updated when SP and other hotfixes are applied to SQL Server 2005 clustered…