SEO

Hi,

I'm currently experiencing a problem with ASP.NET 2.0 and SQL Server
2000.

I have a web application and a windows service (on the same machine),
both which need to connect to a SQL Server box. The service
application works, but the web application get the error "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: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server) "

The Web application doesn't have the connection string in the
web.config, but get's it from the windows service via a remoting
request, therefore both are trying to connect to the same database
with the same settings. The SQL 2000 machine is on a different box.

On an install where everything is local (i.e. database as well), all
apps work fine, no matter if it's SQL 2005, SQL Express or MSDE. It
only appears to be the website within IIS and the SQL box is remote.
The connection string passes in user name, server & database, but
password is blank. The instance isn't named.

If I run the website from a development machine within VS2005, the
connectivity is fine. Remote connections are enabled. TCP/IP & Named
pipes are enabled.

Does anyone have any ideas? I've seen some articles regarding
overriding the machine.config to set the provider, but I can't have
the connection string within the web.config.

Regards

Bobby