Same web appl, conn str, 2 web svrs, 1 connects other doesn't why?

[BenRosa]

Greetings:

 

I've an asp.net appl published to two different web svrs that use the web-config to establish a db connection. Problem is, one appl connects and the other doesn't.

 

About the one that doesn't, there are other appls on that web svr that do connect to the same db svr w/o issue. Also, this web svr is 64bit (not sure if that's a factor). I've noticed on the conn str of the working db connection (the other appls) they use a "driver" attribute in the conn str. I did attempt to use that same driver attribute in my conn str, but no joy. BTW, the other appls that connect don't use a web-cofig, but rather, an include file for db conn str.

 

Finally, the actual error msg I get is:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

 

Thanks in advance for any and all guidance & advice.

Ed in Tampa

[PlausiblyDamp]

If you just copy the connection string from a working application into this application does that fix the problem?

[BenRosa]

Greetings:

 

Ok, I'll expose my oversight so as others can benefit (the reason for this site right?). In the virtual directory on the failing web svr, the folder designated (holding the appl files) was pointed at the wrong place. It was that simple.

 

Ed in Tampa