Post reply

Is this Memory issue

  • October 28, 2009 at 2:57 pm

    #212723

    Hi,

    We have upgraded SQL Server 2000 standard edition x86 with SP4 to SQL Server 2005 developer edition x86 using in-place upgrade. We have 2 GB RAM. Max & Min memory are set to default values and AWE is NOT enabled.

    After the upgrade, I'm seeing the below messages in the error log frequently:

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

    2009-10-24 13:56:23.69 Server SQL Server performance object 'SQLServer:Buffer Node' not found in registry. SQL Server performance counters are disabled.

    2009-10-24 13:56:23.73 Server Error: 3409, Severity: 16, State: 1.

    2009-10-24 13:56:23.73 Server 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.

    2009-10-24 13:56:23.76 Server Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.

    please advice me to get rid of the above

    thank you

  • October 28, 2009 at 3:09 pm

    #1072105

    Looks to me like there may have been a problem during the in-place upgrade. Not really sure where or what you need to look into as all my upgrades were fresh installs.

  • October 28, 2009 at 3:26 pm

    #1072119

    Looks to me like there may have been a problem during the in-place upgrade. Not really sure where or what you need to look into as all my upgrades were fresh installs.

    Thank you,

    But the in-place upgrade was successful with NO errors. Can I reinstall only the sqlctr.ini, and will it fix the issue?

    thanks

  • October 28, 2009 at 3:44 pm

    #1072135

    gmamata7 (10/28/2009)

    Looks to me like there may have been a problem during the in-place upgrade. Not really sure where or what you need to look into as all my upgrades were fresh installs.

    Thank you,

    But the in-place upgrade was successful with NO errors. Can I reinstall only the sqlctr.ini, and will it fix the issue?

    thanks

    No errors that were reported. I have seen things like that occur.

    You can try it, not sure. I'd hope someone else might have more to say.

Viewing 4 posts - 1 through 3 (of 3 total)

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