Error with data collector step using DCEXEC.EXE

Question

Hi all,

I'm using in some query with the Data Collector feature.
In my DEV host I got 3 instances:

• DEFAULT (sql 2019) where there is "MDW" repo DB
• localhost/ALEN (sql 2019)
• localhost/ALEN2022 (sql 2022)

There seems to be a strange error when executing the calls for "Data Collector" on SQL Server 2022.

I have just updated the instance with the latest CU to see if it would fix the issue, but nothing changed.

On the other two instances, simply running from prompt.\dcexec, it returns a message about missing parameters, while on ALEN2022, there is no way to get it to work.

Below the error:
DCEXEC.EXE - Unable to Find Entry Point

Unable to find the entry point ?SQLToolsDiag_TraceMsg@@YAXPEB_WKPEA_WZZ procedure in the dynamic link library C:\Program Files\Microsoft SQL Server\MSSQL16.ALEN2022\MSSQL\Binn\DCEXEC.EXE.

No one error message from SQL SERVER AGENT step (difficult to debug at first glance).

It seems to me something related to the windows sys.
I don't know what to do after a CU update?

Run as "Data collector" is ad-hoc proxy user with right permission that I use on my third named DEV instance (localhost/ALEN) and all go right.

On my 3th DEV instance (2019) job run successful... only in 2022 not!

Do you have some ideas?

ALEN

Answer 1

I Found a quick and dirty solution.
As you can see I've insert a FULL path to the dcexec of SQL SERER 2019 default instance

"C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\dcexec" -c -s 1 -i "$(ESCAPE_DQUOTE(MACH))$(ESCAPE_DQUOTE(INST))" -m 1

and now job ran successful

Answer 2

I tried this on a few machines. On machines where I run SQL 2022 as a named instances, I get the same error messages as you. On machines where SQL 2022 runs as a default instance, I get a "normal" error message:

dcexec: Missing runtime execution mode. Enter '-?' for help. dcexec: Missing set ID. Enter '-?' for help.

I also tested with a named instance running SQL 2019. There it works.

If you need DCEXEC running on a named instance, I would suggest that you open a support case and press for a fix.

My impression is that the Data Collector is not widely used. And probably for good reasons.

Answer 3

Hi @Alen Cappelletti,

I'd like to suggest you may open a ticket to Microsoft support and the engineers will help to resolve the issue.

Services Hub (microsoft.com)

Regards，

Zoe Hui

---

If the answer is helpful, please click "Accept Answer" and upvote it.