properblem reading error log after installation

SQL Server performance monitoring and alerting

Moderators: eddie davis, priyasinha, Adam, chriskelly, Chris Lambrou, Chris Spencer

properblem reading error log after installation

Postby laertes » Wed May 02, 2012 9:41 am

Hi,
I installed sql Mon 3.0 this weeken and now i am seeing a lot of the following error:

Error: 18002, Severity: 20, State: 1.
Exception happened when running extended stored procedure 'xp_readerrorlog' in the library 'xpstar90.dll'. SQL Server is terminating process 94. Exception type: Win32 exception; Exception code: 0xc0000005.

Is this an error introduced by sql mon 3 or is it something I need to adress?

regards,
/Lars
laertes
 
Posts: 2
Joined: Wed May 02, 2012 9:36 am

Postby Brian Donahue » Wed May 02, 2012 11:16 am

Hi Lars,

C0000005 is an "access violation", meaning the extended stored procedure is trying to read or write memory that is outside the address space of SQL Server. It means that the SQL Server installation has come unglued. You can try reinstalling or removing/readding the extended stored procedure.
Brian Donahue
 
Posts: 6669
Joined: Mon Aug 23, 2004 10:48 am

Postby laertes » Wed May 02, 2012 11:19 am

Hi, thanks for the reply.

Could you tell me which is the easiest way to reinstall the extended SP?

regards,
/Lars
laertes
 
Posts: 2
Joined: Wed May 02, 2012 9:36 am

Postby Brian Donahue » Wed May 02, 2012 12:01 pm

SQL Server has a procedure "sp_addextendedproc" that you can use. So for starters you can sp_dropextendedproc and then sp_addextendedproc-it back in. As it's a system procedure, you may need to repair the installation though.
Brian Donahue
 
Posts: 6669
Joined: Mon Aug 23, 2004 10:48 am


Return to SQL Monitor 3

Who is online

Users browsing this forum: No registered users and 0 guests