March 1, 2011 at 11:51 am
Hi,
I have a SQL Server 2005 SP1 installed on a Windows Server 2003 SP1. A few weeks ago, the system administrator tried to install the SP2 for the Windows Server 2003 but it went wrong, so he rolled back it.
Since then, the SQL Server Agent is not starting and show the following error on the SQLAgent.out:
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002]
2011-03-01 15:17:17 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2011-03-01 15:17:17 - ? [098] SQLServerAgent terminated (normally)
I googled for a solution, but none have worked (reapply MDAC 2.8, check register entry, configure a new DSN, etc).
I also tried to install SQL Server 2005 as a Named Instance without removing the Default Instance, but the installation failed with the same error (Data source name not found and no default driver specified).
Does anyone of you guys had a similar problem and was able to resolve it?
Thanks in advance
March 1, 2011 at 5:42 pm
Anyone?
March 1, 2011 at 6:11 pm
From here: http://social.msdn.microsoft.com/Forums/en/sqlgetstarted/thread/73327808-c24d-4b01-be70-840c15c9ff3a
Is this a virtual server? You might need to doublecheck the registry.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
March 1, 2011 at 6:21 pm
Craig Farrell (3/1/2011)
From here: http://social.msdn.microsoft.com/Forums/en/sqlgetstarted/thread/73327808-c24d-4b01-be70-840c15c9ff3aIs this a virtual server? You might need to doublecheck the registry.
Thanks for the reply, but I already tried this and it didn't work either...
March 1, 2011 at 7:18 pm
rafa.aborges (3/1/2011)
Craig Farrell (3/1/2011)
From here: http://social.msdn.microsoft.com/Forums/en/sqlgetstarted/thread/73327808-c24d-4b01-be70-840c15c9ff3aIs this a virtual server? You might need to doublecheck the registry.
Thanks for the reply, but I already tried this and it didn't work either...
Yah, whoops, I missed this line in your post, sorry:
googled for a solution, but none have worked (reapply MDAC 2.8, check register entry, configure a new DSN, etc).
Eyes just kept trucking right over it to the next sentence, no idea why.
Okay, an off the wall question for you:
Is the install for SQL 32bit or 64 bit, and what is the OS? Came across a couple of items in my research that point to that as a possible problem regarding the ODBC. I doubt you have that problem, but it can't hurt to double check.
You mentioned you've already tried re-applying the MDAC, and this really sounds like a standard connection string error. Unfortunately, the best I can offer here is to head to the services and double check a few things. You'll want SQL Server Agent (InstanceName/MSSQLSERVER). Check your Path to executable, see if you've got some strange startup options there. check your Logon, see if it's got something wily. Doublecheck what it thinks it's got dependencies to (should be just SQL Server).
After that... might have a bug or corruption in the executable itself.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
March 1, 2011 at 7:50 pm
Craig Farrell (3/1/2011)
rafa.aborges (3/1/2011)
Craig Farrell (3/1/2011)
From here: http://social.msdn.microsoft.com/Forums/en/sqlgetstarted/thread/73327808-c24d-4b01-be70-840c15c9ff3aIs this a virtual server? You might need to doublecheck the registry.
Thanks for the reply, but I already tried this and it didn't work either...
Yah, whoops, I missed this line in your post, sorry:
googled for a solution, but none have worked (reapply MDAC 2.8, check register entry, configure a new DSN, etc).
Eyes just kept trucking right over it to the next sentence, no idea why.
Okay, an off the wall question for you:
Is the install for SQL 32bit or 64 bit, and what is the OS? Came across a couple of items in my research that point to that as a possible problem regarding the ODBC. I doubt you have that problem, but it can't hurt to double check.
You mentioned you've already tried re-applying the MDAC, and this really sounds like a standard connection string error. Unfortunately, the best I can offer here is to head to the services and double check a few things. You'll want SQL Server Agent (InstanceName/MSSQLSERVER). Check your Path to executable, see if you've got some strange startup options there. check your Logon, see if it's got something wily. Doublecheck what it thinks it's got dependencies to (should be just SQL Server).
After that... might have a bug or corruption in the executable itself.
Hi Craig, thanks again.
I already tried the recommendations you passed, with no success.
I believe it's an ODBC issue. I think some .DLL got corrupted after the SA rolled back the Windows Server 2003 SP2.
Also, if I try to connect through "osql" I got the same error (Data source name not found and no default driver specified).
It's a SQL 32 bits on a Windows Server 2003 SP1.
Another thing that I mentioned before which worries me is that I tried to install the SQL Server again as a Named Instance and I couldn't, because when it tries to startup the SQL Server Agent of the Named Instance, I got the same error.
I don't have any other thing in mind to solve this, if someone does, please, help me on this!
Thanks
March 1, 2011 at 8:55 pm
rafa.aborges (3/1/2011)
Also, if I try to connect through "osql" I got the same error (Data source name not found and no default driver specified).
:crazy: There goes my theory on the Agent. I was wondering if the separate installs were using the same exe.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
March 1, 2011 at 9:56 pm
Craig Farrell (3/1/2011)
rafa.aborges (3/1/2011)
Also, if I try to connect through "osql" I got the same error (Data source name not found and no default driver specified).:crazy: There goes my theory on the Agent. I was wondering if the separate installs were using the same exe.
I really don't know what happened... I guess the SP2 for Windows Server 2003 messed with some ODBC file... I think I don't have any other option than format the server and install the OS and the SQL.
March 4, 2011 at 10:07 am
Hello, before you reformat the server and reload everything all over again, I would run the windows install program and do a repair install, that way if the rollback did mess it up, then the repair should hopefully fix it again. - just a thought
March 4, 2011 at 10:19 am
doug.mcgee (3/4/2011)
Hello, before you reformat the server and reload everything all over again, I would run the windows install program and do a repair install, that way if the rollback did mess it up, then the repair should hopefully fix it again. - just a thought
Hi Doug, thanks for the reply.
I'll use a similiar approach to this. I'll move the databases that are running on this current server and move to another one, then, I'll repair Windows and check if it will work.
Thanks
March 4, 2011 at 10:40 am
Have you attempted to remove the Microsoft SQL Native Client prior to applying the Service Pack 2? There is a good chance that this is corrupt.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply