connecting to online server

Question

Post reply

connecting to online server

blackdevil_heart

SSC Enthusiast

Points: 106
More actions
March 15, 2010 at 6:33 am

#75557

Hi guys,
i just finished a .Net Web application for a client. I've uploaded it to their site. The problem is that the connection string property in the web.config file doesn't seem to work. The current connection string looks like this: "Data Source=Server1.DSNConn1;Database=ServerOne;Trusted_Connection=no;User Id=serverman;Password=*******"
The online server is a SQL Server 7.0. I tried creating a DSN on the Hosting server and replaced it in the web.config file, but it still didn't work. Maybe i should try to use the IP address or server name, but i'm unsure about how to do it.
Pls help. Thanx.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Henrico Bekker One Orange Chip Points: 27652 More actions · Answer 1

try using

initial catalog

, instead of

database

:

Data Source=servername;Initial Catalog=dbname;

or try: http://www.connectionstrings.com

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

Steve Jones - SSC Editor SSC Guru Points: 734434 More actions · Answer 2

Do you have an error?

I would suggest you grab a template from ConnectionStrings.com, as noted above, and use that.

blackdevil_heart SSC Enthusiast Points: 106 More actions · Answer 3

Thanx Guys. I was actually at connectionstrings.com before coming here. I wasn't just sure which one to use. Still confused.

Steve Jones - SSC Editor SSC Guru Points: 734434 More actions · Answer 4

Use this:

Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;

That's a basic, standard one for .NET connections with a user/pwd. If you can use trusted connection, that's great, but this should work. The DSN stuff can work, but it introduces a potential dependency on the particular machine and other setup.