This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Extended event errors

DPA is causing issues on my clustered MS SQL DB production server. Is there a way to tell what monitors are using extended events? This is a MS SQL 2008 instance. Info from the technician:

I see “dbghelp.dll' version '4.0.5' ” error again in SQL error log

Here my findings, dbghelp appears when extended event is called and is an issue that has been resolved based on Microsoft’s information: 

-SQL server 2008 R2 SP2 (current SQL server is 2008 (SP4)  not R2)

http://support.microsoft.com/kb/2938478/en-us

-SQL server 2012 SP1

http://support.microsoft.com/kb/2874879/en-us

I see an application is running and triggering this error on SQL log, I guess is a third party app and If you consider we can engage support from them trying to avoid they uses extended events features.

image1.jpg

Login: WKFSMon

Program Name: IgniteMonitor

image2.jpg

DECLARE @XMLData xml

SELECT TOP 1 @XMLData = CAST(target_data AS xml) FROM sys.dm_xe_session_targets st JOIN sys.dm_xe_sessions s ON s.address = st.event_session_address

WHERE name = 'system_health'

SELECT count(1) FROM @XMLData.nodes('//event[@name="xml_deadlock_report"]') AS X (Col)

WHERE col.value('(data/value)[1]', 'VARCHAR(MAX)') LIKE '<deadlock%' AND DATEDIFF(MINUTE, col.value('(./@timestamp)', 'DATETIME'), GETDATE()) < 10.0

We can confirm that due each time this sentence is executed dbhelp error is logged.

Extended events information:

https://technet.microsoft.com/en-us/library/bb630354(v=sql.100).aspx

DDL DM views and functions:

https://technet.microsoft.com/en-us/library/bb630317(v=sql.100).aspx

Options can be chosen:

-Pause application that is triggering this issue.

-enable trace flag -T3656  (Enabled resolve of all callstacks in extended events)

-engage Third party provider and ask to avoid  use of extended events or if they have a solution on their side.

-engage Microsoft personnel an verify if they have a solution for this SQL server and windows version.

-Upgrade SQL server version to SQL Server 2008 R2 SP2 (http://support.microsoft.com/kb/2938478/en-us) it can take many time.

Currently I see another error on SQL log that are being executed from the same login and application:

CImageHelper::Init () Failed load of dbghelp.dll - A dynamic link library (DLL) initialization routine failed.

CImageHelper::Init () Version-specific dbghelp.dll is not used