Post reply

Error: 18456, Severity: 14, State: 10

  • May 7, 2009 at 5:33 am

    #155670

    Hi All,

    I am facing this problem with my SQL Server 2005. The application is generating lots of alerts as below :

    Error: 18456, Severity: 14, State: 10

    Login failed for user 'xx' [CLIENT: ??.??.??.??]

    When I check the Activity Monitor, some of the active session is working fine for the user 'XX'. Again the error disappear after sometime and everything seems to be working fine. This issue has popped up since last few days only.

    Remember: This is a production server and I will not be able to restart the server or services.

    Thanks

  • May 7, 2009 at 5:40 am

    #990246

    Hi,

    Check these

    http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

    http://support.microsoft.com/kb/889646

    To resolve this issue, you must add an account to the Database Creators role and to the Security Administrators role in SQL Server. You add the account that the application pool is running as. To do this:

    1. Add the account that the application pool is running as to the Security Administrators role and to the Database Creators role in SQL Server. To do this:

    1. Start SQL Server Enterprise Manager.

    2. Expand Microsoft SQL Servers, expand the server group, expand the appropriate server, and then expand Security.

    3. Right-click Logins, and then click New Login.

    4. Type the account name in the Name box. Use the following format for the account name:

    DomainName\AccountName

    Note If SQL Server is installed on a separate computer and you want to run the application pool as the Network Service account, the computer that is running Windows SharePoint Services must have permissions to access the remote computer that is running SQL Server. On the remote computer that is running SQL Server, add the DomainName\ServerName$ account to the Database Creators role and to the Security Administrators role.

    5. Click the Server Roles tab.

    6. In the Server Role list, click to select the Security Administrators check box, and then click to select the Database Creators check box. Click OK.

    7. Quit SQL Server Enterprise Manager.

    2. On the Configure Administrative Virtual Server page of SharePoint Central Administration, create a new application pool, specify the account as the application pool account, and then click OK. The Application Pool Changed page is displayed.

    3. Restart Microsoft Internet Information Services (IIS). To do this, click Start, click Run, type iisreset in the Open box, and then click OK.

    4. On the Application Pool Changed page, click OK. On the Set Configuration Database Server page of SharePoint Central Administration, specify the configuration database settings.

    [font="Comic Sans MS"]+++BLADE+++[/font]:cool:

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply