Extended Event dpa_deadlock_capture: The system cannot find the path specified.

We have been using SolarWinds DPA for quite a while. One of our monitored database instances had been on SQL 2017. When we Enabled Deadlock Collection, an Extended Events session named dpa_deadlock_capture was created. It had an event_file target for saving event data to *.xel files, which were created in this path:

D:\MSSQL14.MSSQLSERVER\MSSQL\Log

We eventually migrated the monitored instance to SQL 2022. *.xel files are now created in this path:

D:\MSSQL16.MSSQLSERVER\MSSQL\Log

However, DPA is looking in the old path and can't find them. There is an error similar to this occurring every five minutes:

The operating system returned error 3(The system cannot find the path specified.) while reading from the file 'D:\MSSQL14.MSSQLSERVER\MSSQL\Log\dpa_deadlock_capture_0_133290808013660000.xel'.

Question: how can I reconfigure DPA to "look" in the correct path?

Find more posts tagged with

extended events

Deadlocks

Accepted answers

All comments

DMasonMavis

PS. We are on version DPA 2024.2.0.503

DMasonMavis

UPDATE

Here are some things I tried that did not work:

I found the *.xel "path" in table dbo.CONDPRM in the [Ignite_Administrator] database, updated it to the correct path with the most recent *.xel file, and restarted DPA. (Change was reverted and DPA was restarted.)
(In SSMS) Created a copy of Extended Events Session dpa_deadlock_capture named dpa_deadlock_capture2, (in SolarWinds DPA/Advanced Options) reset the value of DEADLOCK_POLL_SQL_SERVER_SESSION_NAME to dpa_deadlock_capture2, and restarted DPA. (Reverted DEADLOCK_POLL_SQL_SERVER_SESSION_NAME to dpa_deadlock_capture, and restarted DPA.)

And here is what did finally work:

In SolarWinds DPA/Advanced Options, changed DEADLOCK_POLL_SQL_SERVER_PREFERRED_TARGET from event_file to ring_buffer, and restarted DPA.

I'm not sure why the event_file stopped working, or why I couldn't get it to work again. But as I like to say, "Some mysteries aren't worth solving."