August 9 2010

Installing SQL Server 2005 on a Windows Server 2008 R2 Cluster fails

I use a maximum of one Google Ad per post to help offset some of my blog hosting costs.


We had an interesting problem on a recent project where SQL Server 2005 wouldn’t install on a Windows 2008 R2 failover cluster.
The cluster validates properly however when installing SQL Server 2005, the install ¬†threw an “User has cancelled the installation” error. ¬†The logs showed that communications to the remote node were failing:

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.

The fix is outlined below:

  1. Make sure the task scheduler service is running on the remote cluster node. If the task scheduler service is a cluster resource, fail that resource over to the remote node.
  2. Open regedit and go to HKLMSystemCurrentControlSetControlLSA and change the “disabledomaincreds” from 1 to 0 on all clusters nodes, then reboot all nodes.


I use a maximum of one Google Ad per post to help offset some of my blog hosting costs.


Category: Windows | LEAVE A COMMENT
May 29 2009

Creating a Windows Server 2003 or 2008 Cluster within Hyper-V using iSCSI shared storage

Shared disk options when trying to create a cluster using virtualized nodes within Microsoft Hyper-V are very limited – in fact, only iSCSI will work! You can no longer use a shared SCSI device as you could with older Microsoft virtualization product or like you can with products from VMWare.

I was happy to find that StarWind offers a free iSCSI Target Server ( – it’s very simple to install and share out storage and best of all it is free – great for test / dev environments.

Gavin McShera has a fantastic step-by-step guide on how to set up a 2008 cluster in a Hyper-V environment over here –>

December 16 2008

Exchange 2003 cluster with Symantec Endpoint Protection (SEP)

After a reasonably painless recent rollout of SEP v11 to our fleet, we’ve come across some issues running it on a Windows 2003 Active-Passive Exchange 2003 cluster. Symptoms: nodes unresponsive, sometimes together, sometimes minutes after the other one – not even blue screened but completely unresponsive, nothing on the console.

Anyway the short of it was that we managed to get a memory dump and learned that system32driverswpsdrvnt.sys had been causing the issues. Doesn’t ring a bell? Well it’s the Sygate Personal Firewall which has now been rolled into Symantec Endpoint Protection, the network threat protection component.

We obviously didn’t want to completely remove AV from our email system if possible, so we modified the installation to only contain the core files plus AV protection (see below)

2 weeks running like this and the problem has not reoccurred.