No Answers In MSDE Group, Trying Here DB Access From Server Explorer

[pvdg42]

Not sure if this is a MSDE or Visual Studio issue, but here goes:

I have MSDE and SQL Server GUI tools installed (GUI from Developer Edition)
to support database app development with Visual Studio .NET 2003 (VS 2003).
I have the sample databases installed (pubs, North, etc.) via an executable
file ConfigSamples.exe which includes TO-SQL scripts to create the sample
databases then populate the tables with data.
Because ConfigSamples.exe is not "a known archive type" I cannot get inside
to see the TO-SQL scripts to discover how these databases are made to not
demand user authentication in VS 2003 Server Explorer.
From VS 2003, I can see my MSDE instance and the databases, and access them
via Server Explorer or from .NET apps I develop/evaluate. So far, so good.

Now the issue:
I need to create new databases in conjunction with various projects, and
have done so successfully using the SQL Server GUI tools, and from TO-SQL
scripts. When I create the new database, Enterprise Manager and Query
Analyzer allow me access to do whatever I want with the database.
Not so in VS 2003 Server Explorer! the new database does show up in the list
of databases under the MSDE instance, but when I try to expand the new
database node, up pops a dialog asking for a Username and Password, or
offering me the choice of using Win NT Authentication. No answer I provide
to this dialog gives me access to the database. Choosing NT Authentication
gets me another dialog with *no message text* and only an OK button to
click, and trying any ID/password combination gets me a message indicating
it's not acceptable.

I should say that I'm running using full administrative privileges.

So the question is: how can I create a database like the sample databases
that can be accessed in Server Explorer? Is there a way to turn off the
security check?

Disclaimer: I'm not a SQL Server jock (obviously) and am using the software
and databases to teach college classes and evaluate student projects, so try
to keep it fairly simple?

Thanks in advance for any insights.

 

[Kevin Yu [MSFT]]

Hi,

To test if the username and password is valid, please create a .udl file,
double click it and a DataLink Properties dialog box will be shown. You can
use the Test Connection button to check if the connection is valid.

If the username and password are valid, please start a trace with SQL
profiler,since you have SQL server GUI tools installed. Please check if the
Server Explorer is connecting to the SQL server using the correct
credential.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

 

[pvdg42]

Hi,

To test if the username and password is valid, please create a .udl file,
double click it and a DataLink Properties dialog box will be shown. You
can
use the Test Connection button to check if the connection is valid.

If the username and password are valid, please start a trace with SQL
profiler,since you have SQL server GUI tools installed. Please check if
the
Server Explorer is connecting to the SQL server using the correct
credential.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Perhaps I was not clear in my original post.
There is no problem connecting from Server Explorer to the sample databases
such as pubs or Northwind. No username or password is required. It is *only*
when I create a new database that access issues arise. I don't want to have
to deal with usernames and passwords. I want the new databases I create to
be accessible from Server Explorer the same way the samples are.
Please explain what is a UDL file. As I said in my original post, I'm not
SQL Server savvy.
I've checked my hard drive, and there are no files on it with the extension
..udl, yet all the supplied sample databases are accessible.

 

[Kevin Yu [MSFT]]

Hi,

Sorry for my misunderstanding, now I understand that you're connecting to
the SQL Server Express using the windows integrated authentication. Am I
right?

If so, after you create the new database, can you still access the original
demo databases? Or you cannot access all the databases?

To test this, you can create an .UDL file. Here are the steps:

1. Create an Text file on the desktop.
2. Rename the extension to .udl.
3. Double click that .udl file and a Data Link Properties dialog box will
be displayed.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

 

[pvdg42]

Hi,

Sorry for my misunderstanding, now I understand that you're connecting to
the SQL Server Express using the windows integrated authentication. Am I
right?

If so, after you create the new database, can you still access the
original
demo databases? Or you cannot access all the databases?

To test this, you can create an .UDL file. Here are the steps:

1. Create an Text file on the desktop.
2. Rename the extension to .udl.
3. Double click that .udl file and a Data Link Properties dialog box will
be displayed.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Yes, I'm using Windows Integrated Authentication.
After creating a new database, I'm still able to access the other databases
without difficulty. It's only the newly created databases that raise the
access dialogs cited in my original message.
I performed the .udl test you outlined, and there's no problem connecting to
pubs,Northwind or to the new database (MyTFineAutos).
The problem arises when I try to access that new database through Visual
Studio .NET 2003 Server Explorer. When I attempt to expand the node for
MyTFineAutos in Server Explorer, I get the SQL Server Login dialog. If I
select "Use Windows NT Integrated Security", I get a second dialog with
"Microsoft Development Environment" in the title bar, **no text in the
message area** and only an OK button. Clicking the OK button just sends me
back to the SQL Server Login dialog.
How can I access the databases I create from Visual Studio .NET 2003 Server
Explorer?

 

[Kevin Yu [MSFT]]

Hi,

The dialog box with no title and no content makes me think that there might
be some corruption in the VS.NET IDE. Would you try to re-install the
VS.NET 2005? Since we cannot remove and install the server explorer
seperately, it seems that the only workaround is to re-install vs.net 2005.
Also, please download and install MDAC 2.8 sp1 from the following link. I'm
sorry for the inconvenience.

http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-
a9e0-3a1afbd5922e&DisplayLang=en

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

 

[pvdg42]

Hi,

The dialog box with no title and no content makes me think that there
might
be some corruption in the VS.NET IDE. Would you try to re-install the
VS.NET 2005? Since we cannot remove and install the server explorer
seperately, it seems that the only workaround is to re-install vs.net
2005.
Also, please download and install MDAC 2.8 sp1 from the following link.
I'm
sorry for the inconvenience.

http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-
a9e0-3a1afbd5922e&DisplayLang=en

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

This problem is with Visual Studio .NET 2003, not Visual Studio 2005. It
occurs on PC's at my home, in my office and in our classrooms and labs at
the college where I teach. However, I will reinstall Visual Studio .NET 2003
on one of my home PC's and install the MDAC you cite. then report back when
I've finished. Please understand that I will not have time to complete these
procedures until tomorrow at the earliest.
Thanks for trying to help.

 

[Kevin Yu [MSFT]]

Hi,

Thanks for trying. If that still occurs on the machine you have tried,
please let me know and we'll try other ways for troubleshooting.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

 

[pvdg42]

Hi,

Thanks for trying. If that still occurs on the machine you have tried,
please let me know and we'll try other ways for troubleshooting.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

I've seen a light at the end of the tunnel
Although reinstalling VS .NET 2003 had no effect, I stumbled across a
technique that gave me access to the database through Server Explorer.
I created a new connection to the problem database by right-clicking the
connections node. Once I created a connection manually, the previously
mentioned SQL Server dialogs no longer appeared and I'm able to develop
using the previously inaccessible database.
Case closed as far as I'm concerned. Thanks for helping.

 

[Kevin Yu [MSFT]]

You're welcome. It was nice to hear that you have had the problem resolved.
Thanks for sharing your experience with all the people here. If you have
any questions, please feel free to post them in the community.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."