"Baz" <B**@discussions.microsoft.com> wrote in message
news:91C7FC5F-C9DC-45F8-ABDC-4C4E7EC22A3A@microsoft.com...
>
> After restarting my SQl Server instance my ASP.net applicaions running on
> Windows 2000 are unable to connect to the SQL Server. My asp appplications
> are still able to connect
>
> The connection string I am using is
> user id=sa;pwd=????;data source=????;persist security info=False;initial
> catalog=DBNAme
>
> My clients running on Windows 2003 Server are still able to connect after
> the restart.
>
> I have tried the following:
>
> Restarted the 2000 Machine hosting the client with no resolution
>
> Changed the "data source" parameter to use the ip of the database server
> rather than the DNS name with no resolution.
>
> Added an entry in the ODBC Data Source Administrator for the server on the
> 2000 Machine with no resolution
>
>
> I am able to ping the Database server and access it from Query Analyser
> from
> the 2000 servers.
>
> I was wondering if anyone has come across a similiar problem or if anyone
> has any pointers as to what other changes to try??
>
> Thanks,
> BArry
>
>

"Sahil Malik [MVP]" wrote:

> Barry,
>
> By restarting the SQL Server you effectively corrupt the connection pool on
> the client machine. In .NET 1.1 you will have to restart the app
> server/client machine too, in .NET 2.0 you can clear the connection pool.
>
> The asp applications are able to connect because they donot have a
> connection pool underneath like asp.net apps do.
>
> - Sahil Malik [MVP]
> Upcoming ADO.NET 2.0 book - http://tinyurl.com/9bync
> ----------------------------------------------------------------------------
>
> "Baz" <B**@discussions.microsoft.com> wrote in message
> news:91C7FC5F-C9DC-45F8-ABDC-4C4E7EC22A3A@microsoft.com...
> >
> > After restarting my SQl Server instance my ASP.net applicaions running on
> > Windows 2000 are unable to connect to the SQL Server. My asp appplications
> > are still able to connect
> >
> > The connection string I am using is
> > user id=sa;pwd=????;data source=????;persist security info=False;initial
> > catalog=DBNAme
> >
> > My clients running on Windows 2003 Server are still able to connect after
> > the restart.
> >
> > I have tried the following:
> >
> > Restarted the 2000 Machine hosting the client with no resolution
> >
> > Changed the "data source" parameter to use the ip of the database server
> > rather than the DNS name with no resolution.
> >
> > Added an entry in the ODBC Data Source Administrator for the server on the
> > 2000 Machine with no resolution
> >
> >
> > I am able to ping the Database server and access it from Query Analyser
> > from
> > the 2000 servers.
> >
> > I was wondering if anyone has come across a similiar problem or if anyone
> > has any pointers as to what other changes to try??
> >
> > Thanks,
> > BArry
> >
> >
>
>
>

"Baz" <B**@discussions.microsoft.com> wrote in message
news:4B06B480-8448-4CBF-A659-218862BF8C13@microsoft.com...
> Sahil,
>
> I tried restarting the Windoows 2000 Application Server hosting the .Net
> 1.1
> applications and it do not resolve the issue.
>
> It was resolved by restarting the SQL Server again and the .Net 1.1
> Applications hosted on windows 2000 could then connect to the database. It
> is
> 'strange' that the 1.1 applications hosted on 2003 Server did not lose
> connection to the database server.
>
> Are you aware of any issue whereby .Net 1.1 appliactions hosted on Windows
> 2000 server do not pick up restarts of sql server?
>
> Barry
>
> "Sahil Malik [MVP]" wrote:
>
>> Barry,
>>
>> By restarting the SQL Server you effectively corrupt the connection pool
>> on
>> the client machine. In .NET 1.1 you will have to restart the app
>> server/client machine too, in .NET 2.0 you can clear the connection pool.
>>
>> The asp applications are able to connect because they donot have a
>> connection pool underneath like asp.net apps do.
>>
>> - Sahil Malik [MVP]
>> Upcoming ADO.NET 2.0 book - http://tinyurl.com/9bync
>> ----------------------------------------------------------------------------
>>
>> "Baz" <B**@discussions.microsoft.com> wrote in message
>> news:91C7FC5F-C9DC-45F8-ABDC-4C4E7EC22A3A@microsoft.com...
>> >
>> > After restarting my SQl Server instance my ASP.net applicaions running
>> > on
>> > Windows 2000 are unable to connect to the SQL Server. My asp
>> > appplications
>> > are still able to connect
>> >
>> > The connection string I am using is
>> > user id=sa;pwd=????;data source=????;persist security
>> > info=False;initial
>> > catalog=DBNAme
>> >
>> > My clients running on Windows 2003 Server are still able to connect
>> > after
>> > the restart.
>> >
>> > I have tried the following:
>> >
>> > Restarted the 2000 Machine hosting the client with no resolution
>> >
>> > Changed the "data source" parameter to use the ip of the database
>> > server
>> > rather than the DNS name with no resolution.
>> >
>> > Added an entry in the ODBC Data Source Administrator for the server on
>> > the
>> > 2000 Machine with no resolution
>> >
>> >
>> > I am able to ping the Database server and access it from Query Analyser
>> > from
>> > the 2000 servers.
>> >
>> > I was wondering if anyone has come across a similiar problem or if
>> > anyone
>> > has any pointers as to what other changes to try??
>> >
>> > Thanks,
>> > BArry
>> >
>> >
>>
>>
>>