January 25, 2008 at 7:53 am
Pete,
Murphy's law! I had a 50/50 chance ...
-- will check master database
DBCC CHECKDB ('master')
If the DBCC CHECKDB come back with *any* errors, make sure to post everything that comes back in RED as well as the result counts at the bottom.
"Key"
MCITP: DBA, MCSE, MCTS: SQL 2005, OCP
January 28, 2008 at 10:51 am
Hooray - SORTED!!!!
I delved around in the trace logs and everyone but still no joy. However, today I was looking again in the Enterprise Manager and noticed my database (amongst other dummy ones and Northwind) was the only one marked as "Single User". I googled this to find that that would stop ANYONE accessing the database. Once I reset access to all users, hey presto it all worked again.
I can only suspect that the disk full issue which stopped the transaction log self extending somehow made SQL decide to switch the database into single user mode.
So a big thanks to all those who responded with ideas and hope this solution may help others in future.
Cheers
Pete
January 28, 2008 at 2:31 pm
Pete,
Glad to hear you were able to finally get to the root of the connectivity issue!
Thanks for sharing your notes on the "Fix".
See you around the forums ...
"Key"
MCITP: DBA, MCSE, MCTS: SQL 2005, OCP
January 30, 2009 at 10:59 am
This reply is not an attempt to answer the current issue, but yet to add my own. I inherited this DB and know virtually nothing about how it was set-up originally; just managed to keep it going "as-is" for the last 5 years. It was recently recovered from a server crash and subsequently upgraded to SQL Server 2003.
ISSUE: Error number 3151: ODBC--connection to 'x' failed.
When I perform the "Test Data Source" in MS SQL Server DSN Configuration - I receive a "TESTS COMPLETED SUCCESSFULLY!" Hence I am at a loss as to why I keep getting the 3151 error above.
Any help would be appreciated.
Thanks
April 12, 2010 at 8:52 am
I have a similar problem too.
I am trying to connect to an Oracle (Test) Database via a VB5 Front End and we are getting Run-time error '3151' ODBC Connection to 'x'
Problem is the Test environment is a clone of our Live environment 'y' which is working fine......
Both clients are running on exactly the same server, but the databases are running on a local (Linux) box for DB x but a managed server (presumeably Linux) for DB y
Our DBA is away, we cleverly let our VB5 developer go (before we created the test environment x) and I am merely a tester with limited SQL and no VB5.....
Please help as I don't know how long we can survive without a test environment (or indeed a failover)
February 23, 2011 at 10:03 am
Did you ever resolve this, I am having the same issue.
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply