"Ben Nevarez" <BenNevarez@discussions.microsoft.com> wrote in message
news:92C417B2-2A62-4E11-B0E9-688CBF8ABA4F@microsoft.com...
>
> I would check that the password in the connection string is correct.
>
> But more important, I would not use the sa account from an application.
>
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
>
> "UJ" wrote:
>
>> I have a web site on a clustered server. One server is hosting the
>> website.
>> Occasionally we get the following error message:
>>
>> Login failed for user 'sa'.
>> 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
>> 'sa'.
>>
>> Source Error:
>>
>>
>> An unhandled exception was generated during the execution of the
>> current web request. Information regarding the origin and location of the
>> exception can be identified using the exception stack trace below.
>>
>>
>> Stack Trace:
>>
>>
>> [SqlException: Login failed for user 'sa'.]
>> System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
>> isInTransaction) +474
>>
>> System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString
>> options, Boolean& isInTransaction) +372
>> System.Data.SqlClient.SqlConnection.Open() +384
>> Marlin.Utility.Login(String aUserName, String aPassword, Page Page) in
>> c:\inetpub\wwwroot\marlin\utility.cs:419
>> Marlin.login.btnSubmit_Click(Object Source, EventArgs e) in
>> c:\inetpub\wwwroot\marlin\login.aspx.cs:80
>> System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
>>
>> System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
>> eventArgument) +57
>> System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
>> sourceControl, String eventArgument) +18
>> System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
>> +33
>> System.Web.UI.Page.ProcessRequestMain() +1292
>>
>>
>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>> Version Information: Microsoft .NET Framework Version:1.1.4322.2300;
>> ASP.NET
>> Version:1.1.4322.2300
>>
>>
>>
>> Why does SA suddenly stop working? The only way to make it work is to
>> restart IIS.
>>
>>
>>

"UJ" <fred@nowhere.com> wrote in message
news:etzNLJKPGHA.3576@TK2MSFTNGP15.phx.gbl...
> This works fine and then suddenly stops working. No one has changed the
> password or the file.
>
> The only way to get it to work is to restart IIS and SQL.
>
> J.
>
> "Ben Nevarez" <BenNevarez@discussions.microsoft.com> wrote in message
> news:92C417B2-2A62-4E11-B0E9-688CBF8ABA4F@microsoft.com...
>>
>> I would check that the password in the connection string is correct.
>>
>> But more important, I would not use the sa account from an application.
>>
>> Ben Nevarez, MCDBA, OCP
>> Database Administrator
>>
>>
>> "UJ" wrote:
>>
>>> I have a web site on a clustered server. One server is hosting the
>>> website.
>>> Occasionally we get the following error message:
>>>
>>> Login failed for user 'sa'.
>>> 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
>>> 'sa'.
>>>
>>> Source Error:
>>>
>>>
>>> An unhandled exception was generated during the execution of the
>>> current web request. Information regarding the origin and location of
>>> the
>>> exception can be identified using the exception stack trace below.
>>>
>>>
>>> Stack Trace:
>>>
>>>
>>> [SqlException: Login failed for user 'sa'.]
>>> System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
>>> isInTransaction) +474
>>>
>>> System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString
>>> options, Boolean& isInTransaction) +372
>>> System.Data.SqlClient.SqlConnection.Open() +384
>>> Marlin.Utility.Login(String aUserName, String aPassword, Page Page)
>>> in
>>> c:\inetpub\wwwroot\marlin\utility.cs:419
>>> Marlin.login.btnSubmit_Click(Object Source, EventArgs e) in
>>> c:\inetpub\wwwroot\marlin\login.aspx.cs:80
>>> System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
>>>
>>> System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
>>> eventArgument) +57
>>> System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
>>> sourceControl, String eventArgument) +18
>>> System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
>>> +33
>>> System.Web.UI.Page.ProcessRequestMain() +1292
>>>
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------------------
>>>
>>> Version Information: Microsoft .NET Framework Version:1.1.4322.2300;
>>> ASP.NET
>>> Version:1.1.4322.2300
>>>
>>>
>>>
>>> Why does SA suddenly stop working? The only way to make it work is to
>>> restart IIS.
>>>
>>>
>>>
>
>