got to the bottom of the problems this morning...

disabling SQL reporting Services on node1 has now allowed it to accept SQL in the event of a failover. Really not...

got to the bottom of the problems this morning...

disabling SQL reporting Services on node1 has now allowed it to accept SQL in the event of a failover. Really not...

thanks for the help.

The main problem here we had was not enough time to test the system before they needed it to go live! We had 4 weeks, then...

Quick update...

I have installed reporting services onto a stand alone server and clustered the reporting database.

This now works fine

I just hope that I can remove reporting services from node1 in...

thanks for that, I need to get a better understanding of how it works and how they have installed it as I'm sure the DB has not been clustered.

Originally...

the cluster was tested for a long period of time both before and after SQL was installed.

It was a fresh build of 2 servers, with fresh install of SQL, no...

on further investigation it appears that SQL reporting services has been installed on one node (the one that will not run SQL)

I will stop the service and see if this...

ps - to add to this, the instance is now only connectable by it's name, not it's IP address, from clients.

Thanks