July 17, 2009 at 11:57 am
We recently setup a new SQL Server cluster that is going to be running SQL Server 2005 and SQL Server 2008. This is our Development cluster.
We already have 2 production SQL clusters running 4 instances of SQL 2005 each. This is the first time I've seen this, so I need some help as I'm not really finding anything via Google either.
We went through and installed SQL Server 2005 with SP2 on both nodes of the cluster and the installs completed successfully. Whenever we try to move the SQL Server Resource group to the passive node, all resources except for the SQL Server and SQL Server Agent come online. The 2 disk drives, SQL network name & IP address and full text resources come online just fine. The SQL Server resource tries to come online, but after a few attempts, just goes to a Failed state.
I have tried the following:
1. Evicting the passive node from the Windows Cluster and readding it (this fixed an issue with our PROD cluster once - kinda strange)
2. Repairing the installation of SQL on the passive node
3. Verifying all the NIC \ Hardware drivers between the 2 nodes and updating them
4. Ran Shavlik and ensured all the latest patches were installed on both nodes.
5. Completely uninstalled \ reinstalled SQL Server 2005 and no luck
The errors that we are seeing in the Event Log are as shown below. If you have seen this, know of a KB I could follow or have some things to try, please let me know.
Event Type:Error
Event Source:MSSQL$DEVSQL2005
Event Category:(3)
Event ID:19019
Date:7/17/2009
Time:1:46:25 PM
User:N/A
Computer:DEVSQLC1N2
Description:
[sqsrvres] ODBC sqldriverconnect failed
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4b 4a 00 40 01 00 00 00 KJ.@....
0008: 0b 00 00 00 44 00 45 00 ....D.E.
0010: 56 00 53 00 51 00 4c 00 V.S.Q.L.
0018: 32 00 30 00 30 00 35 00 2.0.0.5.
0020: 00 00 00 00 00 00 ......
Event Type:Error
Event Source:MSSQL$DEVSQL2005
Event Category:(3)
Event ID:19019
Date:7/17/2009
Time:1:46:25 PM
User:N/A
Computer:DEVSQLC1N2
Description:
[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0; message = [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4b 4a 00 40 01 00 00 00 KJ.@....
0008: 0b 00 00 00 44 00 45 00 ....D.E.
0010: 56 00 53 00 51 00 4c 00 V.S.Q.L.
0018: 32 00 30 00 30 00 35 00 2.0.0.5.
0020: 00 00 00 00 00 00 ......
July 21, 2009 at 10:53 am
We have resolved this issue after reviewing the Cluster log.
We found that when we had installed and then uninstalled SQL 2008 from the second node, it corrupted the ODBC drivers used to connect to SQL Server. We re-installed the SQL 2008 client components and then the drivers were repaired and failover worked successfully.
Just wanted to post this fix in case anyone runs into this issue.
January 7, 2010 at 11:24 am
Hi Brain,
I exactly got the same issue. In dev environment, we have 2 node Active/Active cluster setup with SQL Server 2005
On Node1: We have 2 SQL Server 2005 instances
VS1\Ins1
VS2\ins2
On Node 2:We have 2 SQL Server 2005 instances
VS3\Ins3
VS4\ins4
I tried to upgrade Ins1 to SQL Server 2008. The installation went well but SQL resource group(SQL Servvice & SQLAgent did not come online). So I have Uninstalled all 4 instances from both nodes. Now I'm trying to install SQL Server 2005 and getting the same error that you got. Now I again uninstalled SQL Server 2005 and rebooted both the nodes and installed SQL Server 2005 again but the same error
please advice me what steps I need to do now?
thanks
January 7, 2010 at 12:20 pm
If you are getting those errors now after uninstalling SQL Server 2008 and doing just fresh installs of SQL Server 2005, I would try installing the SQL Server 2008 Client Tools Connectivity option within SQL 2008 setup on both nodes of the cluster and see if the Resources come back online.
That was essentially the component that got corrupted and was causing the issues I was having. Let me know if that helps.
January 7, 2010 at 12:26 pm
thanks Brain,
I just tried installing SQL Server 2008 client tools only on Node1 and then the resource is came online!!
Now I do Not want SQL Server 2008 components at all on Node and I want to uninstall the SQL Server 2005 & SQL server 2008 client components and then reinstall SQL Server 2005.
I will try that and come back here to post the results
One more question: When we install SQL Server 2008 client components,then it remove the SQL Server 2005 client tools?
In my case it's not. I'm able to see both SQL Server 2005 client tools & SQL Server 2008 Client tools. Is this normal behavior?
thanks again
January 7, 2010 at 12:30 pm
Great news and thanks for posting!
What I found is that the SQL 2008 Components just install some updated DLL's. When SQL 2008 is pulled off the boxes, the updated dll's exist and are not overwritten when you do the SQL 2005 install, which causes the 2005 components to fail.
One thought might be to uninstall \ reinstall the SQL 2008 Client components and try and run something like Filemon to see what files are updated during the install. Just a thought as that might help nail down which files just need to be copied from a working SQL 2005 install. Just some food for thought.
January 7, 2010 at 5:42 pm
Hi,
I have uninstalled all SQL Server 2005 instances, cliet tolls & SQL Server 2008 client tools again and rebooted the both the nodes and started the fresh SQL Server 2005 installation. But still same problem.
See the screenshot2. After that screen, while installing fresh SQL Server 2005 installation, I have clicked OK and the installation completed successfully. But SQL resource (SQL Service & Agent) not coming online. Any body has the fix for this?
Is there a way to update the dlls or drives (that SQL Server 2008 client tools updating ) manually, before starting the SQL Server 2005 installation so that the installation go smooth with this ODBC error '[sqsrvres] ODBC sqldriverconnect failed'
I'm stuck here. Any advice will be appreciated
One more thing I have noticed that, while installing SQL Server 2005, In Service account page of the wizard, under Start the Services at end of the setup
all the sql services are grayed out. I'm assuming that if these services are NOT grayed out, the installation will not have any problems. Is something to do here? plz see the screen shot
thanks
January 8, 2010 at 12:09 am
Hi,
I went to through the below link which address the same issue
So after Uninstalling all the 4 SQL Server instances, I can still the below keys in registry location HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server
100
INS2
RefCount.
Can I delete these 3 folders and reinstall SQL Server 2005? Is that makes sense?
thanks
January 8, 2010 at 6:36 am
At this point, if you are not going to install the SQL 2008 Client tools, then I would either open an incident with Microsoft or see if you can find any articles on forcing an install of SQL Server 2005 Client Components. I briefly searched last night on this and didn't have much luck.
If you go the route of deleting those reg keys, be sure to back them up in case you have unexpected results, you can readd them to the registry. Good luck!
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply