Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...
SQL Server Forum / Other Technologies / Clustering / October 2006

Tip: Looking for answers? Try searching our database.

SQl Server fails to start on 1 node

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
itchyrash@gmail.com - 31 Oct 2006 01:22 GMT
Install worked fine, installed sp4 but when I go to fail from one node
to the other it fails to start on the second node. All shared storage,
IP's failover correctly, node service accounts are the same, second
node can connect to the instance by name when it is started on the
other instance. If I take the SQL Server resources offline, move the
group to the second node and start the service through the service
applet it starts without a problem? When it starts on the second node
there are no errors in the sql errorlog but appears that cluster
service stops it because it cannot access the instance?? See errors
from cluster log below

0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:36.275 ERR  SQL Server <SQL
Server>: [sqsrvres] OnlineThread: Error connecting to SQL Server.
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate = IM002; native
error = 0; message = [Microsoft][ODBC Driver Manager] Data source name
not found and no default driver specified
0000137c.00001174::2006/10/30-23:28:38.275 ERR  SQL Server <SQL
Server>: [sqsrvres] OnlineThread: Error connecting to SQL Server.
Reply to this Message
itchyrash@gmail.com - 31 Oct 2006 04:51 GMT
Actually got a work around for this by adding an alias for (local)
which points to the virtual server name, not sure I am happy having it
setup like this or why it is required, may apply sp4 again and see if
that removes the need for this, something is not right
Reply to this Message
Kevin3NF - 31 Oct 2006 15:19 GMT
Are the binaries on the second node updated?  meannig did the SP4 install
"take"?

Check the c:\windows\sqlsp#.log file that corresponds to the second node's
part of the sp install for error messages

What you have is the cluster service failing to connect to the SQL Server
(which is worked around by the alias)

Signature

Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com

> Actually got a work around for this by adding an alias for (local)
> which points to the virtual server name, not sure I am happy having it
> setup like this or why it is required, may apply sp4 again and see if
> that removes the need for this, something is not right
Reply to this Message
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.