MSDE and Sql Server Connection String

  • Thread starter Thread starter Greg Robinson
  • Start date Start date
G

Greg Robinson

Our app's connection string at most (currently all) client sites points to
Sql Server 7 or 2000 on a seperate machine.

We have one small client who is running MSDE. We tried to bring them up
today.

I cannot get a connection to the MSDE. I keep getting

"System.Data.SqlClient.SqlException: SQL Server does not exist or access
denied."

I removed user id and password and set Integrated Security to True in the
connection string.

Our existing FoxPro app has no problems seeing and using MSDE, the .Net
Client cannot. The MSDE is running on the same machine as the .NET client
and the existing FoxPro application.

The FoxPro app uses an ODBC connection which works. I googled this and I am
not coming up with anything.

Any suggestions?
 
Greg:

The following KB article lists some of the potential causes of this error
message. It may be a good reference point.

http://support.microsoft.com/default.aspx?scid=kb;en-us;328306

--
David Lloyd
MCSD .NET
http://LemingtonConsulting.com

This response is supplied "as is" without any representations or warranties.


Our app's connection string at most (currently all) client sites points to
Sql Server 7 or 2000 on a seperate machine.

We have one small client who is running MSDE. We tried to bring them up
today.

I cannot get a connection to the MSDE. I keep getting

"System.Data.SqlClient.SqlException: SQL Server does not exist or access
denied."

I removed user id and password and set Integrated Security to True in the
connection string.

Our existing FoxPro app has no problems seeing and using MSDE, the .Net
Client cannot. The MSDE is running on the same machine as the .NET client
and the existing FoxPro application.

The FoxPro app uses an ODBC connection which works. I googled this and I am
not coming up with anything.

Any suggestions?
 
Hi Greg,

Don't have much experience with msde but you may want to go to
www.connectionstrings.com and try several of the odbc and oledb connection
strings. The syntax may be the problem and the sqlclient may not connect to
msde, but I'm not sure about this.

HTH,

Bernie Yaeger
 
Since SP3 and XP SP2 have come on the scene, it's gotten tougher to log on
to all SQL Server databases--especially those hosted on XP. Make sure your
XP firewall allows ports TCP port 1433 and UDP port 1434. Make sure your
MSDE is configured for mixed mode security if you plan to log on with SQL
Server credentials. Make sure you have granted rights to the Windows login
account you plan to use--that account needs rights to the default database.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
Back
Top