HI, I have been having a weird problem since so long.
Our Production server: SQL server 2000 My Dev box: SQL Server 2005 I registered the production server to my Management Studio and manage it as required. The connection string I have in my web.config file is <add key="WebDBConnectionString" value="server=<ip address>;database=WebDB;uid=userid;pwd=password;"/> as you see I am using the ip address instead of the name of the server in my connection string. This is a SQL SERVER 2000 PRODUCTION SERVER. But often times we keep getting the below 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) ********************************************************************************************************************************* Yes this sounds crazy!!!!! Our production is a SQL Server 2000 and we get this SQL Server 2005 error. We have been getting this since more than a year or may be 2. But as a fix we just restart our production SQL Server service and this error would disappear. We never tried installing a SQL Server 2005 on our production server so there is no possibility of even having an instance of it on it. We also looked in the Add Remove programs there are no traces of SQL 2005 either. Can any guess what may be happening in our case. Thanks in advance, -L
