Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > dbghelp.dll version 4.0.5 messages in errorlog

dbghelp.dll version 4.0.5 messages in errorlog

Updated March 13, 2017


When monitoring an SQL server with DPA , the SQL server errorlog file gets bloated with messages like 'dbghelp.dll' version '4.0.5'.


  • DPA version 10.2 and later
  • monitoring SQL server 2012 Pre SP1 CU6
  • DPA deadlock feature is enabled


DPA 10.2 added a feature for deadlock logging. This item is not on by default and is using Extended events and then  the sys.fn_xe_file_target_read_file stored procedure to read the extended events. If DPA was configured to also use event_file as the target for extended events. 


Apply the Microsoft patch - FIX: "Using 'dbghelp.dll' version '4.0.5'" error is logged in SQL Server 2012 or SQL Server 2008 R2 when a statement or job executes the sys.fn_xe_file_target_read_file stored procedure on the monitored SQL server.

Or turn off DPA's extended events feature at the same time turning off DPA's deadlocks feature.

Go to options > Administration tab > Advanced options > Db instance options tab > support options check box checked in the upper right. > DEADLOCK_POLL_ENABLED.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified