M
matt.delvecchio
i saw a similar post from last year, but i didnt see any clear
solution. the error message:
"A connection was successfully established with the server, but then an
error occurred during the login process. (provider: TCP Provider,
error: 0 - The specified network name is no longer available.)
Exception Details: System.Data.SqlClient.SqlException: A connection was
successfully established with the server, but then an error occurred
during the login process. (provider: TCP Provider, error: 0 - The
specified network name is no longer available.)"
....it would appear to have something to do w/ SQL Server connectivity.
when i get it, i get it repeatedly. however, if i go to a non-db page,
then page to a db-page, it's cleared up.
i am running ASP.NET 2.0, on a commerical hosting environment
(www.datapacket.net), w/ a SQL 2000 server. no problems in dev, usually
works in this prod env.
any ideas what would cause this strangeness?
thanks,
matt
solution. the error message:
"A connection was successfully established with the server, but then an
error occurred during the login process. (provider: TCP Provider,
error: 0 - The specified network name is no longer available.)
Exception Details: System.Data.SqlClient.SqlException: A connection was
successfully established with the server, but then an error occurred
during the login process. (provider: TCP Provider, error: 0 - The
specified network name is no longer available.)"
....it would appear to have something to do w/ SQL Server connectivity.
when i get it, i get it repeatedly. however, if i go to a non-db page,
then page to a db-page, it's cleared up.
i am running ASP.NET 2.0, on a commerical hosting environment
(www.datapacket.net), w/ a SQL 2000 server. no problems in dev, usually
works in this prod env.
any ideas what would cause this strangeness?
thanks,
matt