Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
M2RTY
Starting Member
1 Post |
Posted - 2010-01-15 : 09:30:09
|
| sorry if this is in the wrong section...please move if required...I built a WS 2008 failover cluster on 2 HP blades and have one instance of SQL 2008 running on it. It has ran fine for weeks, but then something odd has started.Node 1 has been active for a few months, then we failed it over to node 2 for a while.On switching back to node 1, SQL will not start. I get the following group of errors in the cluster log:checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Server Native Client 10.0]Login timeout expired [sqsrvres] ODBC sqldriverconnect failed [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 274d; message = [Microsoft][SQL Server Native Client 10.0]TCP Provider: No connection could be made because the target machine actively refused it. Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 274d; message = [Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.It's hard to get downtime on the system as its used a lot, so when I do get a few hours window I need to make sure I can get it working again. Any ideas would be greatly appreciated!ThanksMartynMartyn |
|
|
|
|
|