SQL Server 2019 Error and Usage Reporting App Won't Start

Question

I've just done 3 SQL Server 2019 (plus CU13) installs and the Error and Usage Reporting App won't start on any of them. Just flashes up a blank screen. I see someone else posted last year about the same issue. Is it not a valid app anymore then?

Answer 1

Hi Saransvan-0628,
Thanks for your reply.

Could you please check if there are any error message in application log event viewer?
I find the SQL Server 2019 Error and Usage Reporting application in my windows server 2016 VM cannot start either.
And there is an error message in the application log:

After some research, I find a solution works for me:

Go to C:\Program Files\Microsoft SQL Server\150\Shared, rename the file SqlWtsn.exe.config to SqlWtsn.exe.config.OLD.  

Then I can start SQL Server 2019 Error and Usage Reporting.

I’m not sure if it is a known issue.
You can submit it to the Microsoft feedback at this link https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0 Your feedback enables Microsoft to offer the best software and deliver superior services. Appreciate for your understanding.

Best Regards,
Amelia

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

I see this when I start the application:

The command-line window in the back is part of it.

Once I press OK, it goes away. But I guess the purpose is only to set preferences, so there is little point to keep it running.

Answer 3

Hi Saransvan-0628,

By default, Microsoft SQL Server collects information about how its customers are using the application. Specifically, SQL Server collects information about the installation experience, usage, and performance. This information helps Microsoft improve the product to better meet customer needs.The Error and Usage Reporting application lets each SQL Server instance configure its own Usage Reports setting.
And the Error and Usage Reporting application is not included in the SQL Server Reporting Services 2017 and later setup. The only mechanism available to configure sending information to Microsoft is by setting registry subkeys on the server.

Please refer to this doc for more details.

Best Regards,
Amelia

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

Thanks ErlandSommarskog and AmeliaGu-msft. As advised by both of you I have reported this as a potential bug on the link you posted.

Answer 5

The renaming of the .config file does work, but I wanted to dig in a little more as to the 'why'. I started editing the .config file and got it working when I removed this line <supportedRuntime version="v2.0.50727"/>. Adding it back in broke it. This line refers to the .NET 3.5/3.0/2.0 suite, so I removed that using Server Manager and then the tool ran fine. Reinstalling .NET 3.5 broke it again. So apparently SQL Server 2019's Error and Usage Reporting App is not compatible with the older .NET 2.0/3.0/3.5 package being installed.

SQL Server itself seems to run fine with it installed, however, so if you require the older .NET, you're better off just removing that line from the config or renaming/removing it altogether.