How can we help you today? How can we help you today?

xp_readerrorlog issues?

Hi,

Anyone had any issues with xp_readerrorlog in 7.1.2.8327 ? I'm seeing several instances as per the image which doesn't look good...xrwbt7ktsbql.png

...and they all originate from SQL Monitor

kill doesn't work , removing that server from the list of monitored ones does nothing and stopping the actual monitoring service (which runs on a different server to that) does nothing either!

Short of rebooting this server in the middle of the day I'm at a loss as to what to do.

Any advice appreciated :smile:
TedMaulUK
0

Comments

5 comments

Sort by
  • Russell D
    Hi Ted, what version of SQL are you using?
    Russell D
    0
  • TedMaulUK
    Hi Russell,

    SQL 2005 on Windows Server 2003R2 64 bit
    TedMaulUK
    0
  • Russell D
    Thanks @TedMaulUK - there is a known issue in SQL 2005/2008, which could explain why these are hanging around. Can you make sure you're patched up according to Microsofts advice here: https://support.microsoft.com/en-us/help/973524/fix-the-execution-of-the-xp-readerrorlog-command-in-sql-server-2005-an and let me know if this resolves things for you?
    Russell D
    0
  • Alex B
    @TedMaulUK

    You'll likely run into another issue after this in that Windows Server 2003 isn't supported by SQL Monitor v7 (and hasn't been since v5). It's apparently worked up until v7.0.8 where we switched over to using more WMI queries instead of remote registry, so you could get away with using v7.0.7 (download here) which also happens to not use xp_readerrorlog).

    Kind regards,
    Alex
    Alex B
    0
  • TedMaulUK
    Thanks guys..

    Have got SP4 going on this week and have downgraded to v6 but for now everything is working as it should, cheers. Will upgrade back to 7.0.7 later on this week.
    TedMaulUK
    0

Add comment

Please sign in to leave a comment.