Server Explorer failling to log in to (local) DB

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

kevin - 22 Jul 2005 21:06 GMT

using VS.NET 2003
server explorer gives me "Cannot connect to database MyDB" error when I
expand the Server node representing my local machine.

The problem is that the DB it is trying to login to has been deleted. How
do I change the default DB that VS.NET is looking for. Creating a new DB in
Enterprise Manager with the name MyDB is a workaround for now but not a
solution.

What about developers who only have MSDE?

Reply to this Message

patrick - 23 Jul 2005 01:08 GMT

Why not change the login to a database that does exist? I am not sure whether
MSDE has any databases installed automatically or not, but I presume it has
the same ones that ship with the full thing. I don't have much experience
installing SQL server database apps on other machines, yet, sorry.

> using VS.NET 2003
> server explorer gives me "Cannot connect to database MyDB" error when I
[quoted text clipped - 6 lines]
>
> What about developers who only have MSDE?

Reply to this Message

kevin - 09 Aug 2005 14:41 GMT

Patrick,

Yeah... I... um...tried...that :)

The problem is the VS seems to remember the first database that I made a
connection and continues to try and find that database.

> Why not change the login to a database that does exist? I am not sure whether
> MSDE has any databases installed automatically or not, but I presume it has
[quoted text clipped - 11 lines]
> >
> > What about developers who only have MSDE?

Reply to this Message

Cameron Slade [MSFT] - 09 Aug 2005 23:42 GMT

Hi Kevin,

Your problem doesn't ring a bell. Server Explorer shouldn't be persisting data about what database it was last connected to. When ever I try to expand the MSDE Node on the local machine
the Server Explored doesn't navigate past the server leaf. Maybe I am missing something so if you could provide more detail about how you are navigating to MSDE via SE that would be
helpful.

<My Machine>
|_ SQL Servers
|_<My Machine>

If we are storing the DB name it is probably in the registry. Try searching the registry for the DB Name and see if it comes up. Let me know what you find.

Cameron Slade
Test Manager Visual Studio Data
--------------------

>Thread-Topic: Server Explorer failling to log in to (local) DB
>thread-index: AcWc5/uMWQWDLeljQNqzN/TB7UTJDg==
[quoted text clipped - 42 lines]
>> >
>> > What about developers who only have MSDE?

Cameron Slade
Microsoft VSData Team
http://blogs.msdn.com/vsdata

Signature

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

Reply to this Message

kevin - 10 Aug 2005 18:16 GMT

Cameron thanks for your time,

The series of steps that I took

1. Create database DB1

2. From VS.NET Server Explorer create a dataconnecton to DB1

3. Realize that I mispelled the name of DB1: DROP DB1 and try again

4. RETURN TO VS.NET, REFRESH SERVER EXPLORER AND EXPAND Servers - MyMachine
-Sql Servers -MyMachine

At this point I get a SQL SERVER Login dialog box and regardless of the
password/login combination or Integrated Windows Security, the following
message box opens

Title: Microsoft Development Environment
Text: Cannot open database requested in login 'DB1'. Login fails.

"Obviously, you ninny," you say, "You still have a connection defined for a
non-existant database!"

5. Delete the Data Connection for DB1 and try and expand the Servers tree
again. Same error.
6. Close and reopen VS.Net...same error.

My solution was to create a DB named db1 (no tables)

> Hi Kevin,
>
[quoted text clipped - 61 lines]
> Microsoft VSData Team
> http://blogs.msdn.com/vsdata

Reply to this Message

kevin - 10 Aug 2005 18:20 GMT

Cameron,

I forgot one thing.

The Sql Server Login box has DB1 in the Database field.

Thanks Kevin

Reply to this Message

kevin - 10 Aug 2005 18:27 GMT

I may stand corrected!

I don't think that I ever actually deleted The DB1 Data Connection (step 6
in my response).

I just did that and after restarting VS.NET, problem solved.

I also found no referance to DB1 in the registry.

Cameron, your good!

Reply to this Message

Server Explorer failling to log in to (local) DB

Free Magazines