SQL Server Error Messages

  • JB-117464

    Ten Centuries

    Points: 1279

    I am getting 2 error messages (straight after each other) at boot time (immediately after the number of CPUs are announced in sql server logs) but cant find anything about them in BOL/google/msdn. can someone explain why I am getting these 2 messages and what i should do about them? I am using SQL Server 2005 SP1 on windows 2000 server SP4

    Error: 8313, Severity: 16, State: 1.

    Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.

    Error: 3409, Severity: 16, State: 1.

    Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.

  • This was removed by the editor as SPAM

  • K. Brian Kelley

    SSC Guru

    Points: 114465

    Have you tried reloading the counters?

    1) Stop SQL Server

    2) Open a command prompt and navigate to the BINN directory for that SQL Server

    3) Execute lodctr sqlctr.ini

    K. Brian Kelley
    @kbriankelley

  • JB-117464

    Ten Centuries

    Points: 1279

    yeah i did do. i have looked at the  http://support.microsoft.com/?id=812915 and it appears to be my scenario except i am running sql 2005 SP1. i have tried unloading the counters with unlodctr first and lodctr after but to no avail. This is a clean install of windows and sql 2005

  • K. Brian Kelley

    SSC Guru

    Points: 114465

    And I'm guessing a restart didn't fix it. You may want to call Microsoft Support and inquire if you need to unregister/register sqlctr90.dll (usually located in C:\Windows\System32). I know this had to be done for sqlctr80.dll for SQL Server 2000 every once in a while, but I haven't seen a KB article suggesting this path for SQL Server 2005.

    K. Brian Kelley
    @kbriankelley

  • Sam Sheikh

    Mr or Mrs. 500

    Points: 568

    I realise this question was posted was some time ago, but I had the same issue recently, starting up MSSQL 2005 SP2. Basically my problem was that the MSSQL service system account did not have the correct privileges assigned to it. Once admin rights were administered, MSSQL started correctly. Hope this helps someone.

    Sam

  • brian_snyder

    SSC Rookie

    Points: 29

    You da man!! I followed this trail to the end to a pot of gold!! Thanks!!!! You saved my day!!!!!!!!!!!!!!

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

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