Re: connect to SQL 2005 fails

"Landon Kelsey" <landonmkelsey@xxxxxxxxxxx> wrote in message
news:AC0C18EB-405E-4C5E-8148-FBAA18C12A46@xxxxxxxxxxxxxxxx
I can connect easily using C# & ADO.NET on standalone programs.

I am trying to connect from a web site program under .NET 1.1 VS 7 and
always get

Login failed for user 'LANDON\ASPNET'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about
the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Login failed for
user
'LANDON\ASPNET'.

Source Error:


Line 46: private void Page_Load(object sender, System.EventArgs e)
Line 47: {
Line 48: sqlConnection1.Open();
Line 49: ds = new DataSet();
Line 50: daAttendees = new SqlDataAdapter(


Source File: c:\inetpub\wwwroot\pcswebapp2\webform1.aspx.cs Line: 48

having signed in under IE6 using:
http://localhost/PCSWebApp2/WebForm1.aspx
I've tried everything to fix the problem;






"Jeff in Alaska" wrote:

SQL Server successfully restarted. The SQLFT*.LOG and ERRORLOG files
both
indicate a successful restart. On the SQL Server Confiruation Manager
tool
"Shared Memory", "Named Pipes" and "TCP/IP" are all enabled. "TCP/IP" is
enabled to listen on all IP Addresses. The machine only has one IP that
it
is listening to. The protocol order is Shared Memory, TCP/IP, and Named
Pipes.

When looking at the Process view and the "System Services" view, both
indicate SQL Server is up and operational. the only SQL related tool
that
isn't operational is SQL Server Agent and it is failing due to same
problems
that cause other apps trying to connect to the SQL Server to fail.

Jeff

"Roger Wolter[MSFT]" wrote:

Sounds like the SQL Server service didn't restart after the reboot.
Check
the log at:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG
to see if there is a problem with SQL restarting. If that doesn't
work, try
using the SQL Server Configuration Manager tool to enable the TCP/IP
protocol on the client and server to see if the problem is isolated to
named
pipes.

--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Jeff in Alaska" <Jeff in Alaska@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:577AE98A-4170-4C15-859B-1FAA0D89A658@xxxxxxxxxxxxxxxx
We have a test SQL 2005 (Developer Edition) machine on Windows2003
SP1
Standard Edition. After the reboot to install MS patches Tuesday AM,
it
quit
accepting any SQL Connections. Prior to the reboot it was accepting
connections and working as we expected it to. I've worked with the
Surface
Area configuration tool to make sure it allows connections. We've
backed
out
the patches. After doing this, we've rebooted the box. Yet, we
still are
unable to connect.

The primary error message we are seeing is "A connection was
successfully
established with the server, but then an error occurred during the
pre-login
handshake. (provider: Shared Memory Provider, error: 0 - No process
is on
the
other end of the pipe.) (type SqlException)"

I am also seeing "A connection was successfully established with the
server,
but then an error occurred during the pre-login handshake. (provider:
Shared
Memory Provider, error: 0 - No process is on the other end of the
pipe.)
(Microsoft SQL Server, Error: 233)"

In addition to SQL2005, we have TFS, Windows SharePointServices, and
Reporting Services running on the machine. They are all experiencing
variations on the same message and unable to connect.

Thanks for the assistance.

Jeff





Is there any reason you've hijacked several other OP's posts instead of
posting your own message?

--

Star Fleet Admiral Q @ your service!
Google is your friend!
http://www.google.com



.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... connections need to be returned to the pool to be ... Enterprise version of SQL Server 2000. ... server user login to be sure that it is not mixed with other running clients). ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... communication between ODBC (OLEDB and Native Client, ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL server connection problem
    ... I've tried to change the user connections to 0, ... "SQL server connection time out. ... The following message appears when restart the server and before login ... I receive Error message: “A connection could not be established to ...
    (microsoft.public.sqlserver.clients)
Loading