Spanking brand-new installations of:
- Visual Studio 2022 Community (VS)
- SQL Server 2019 Dev (SQL)
- SQL Server Management Studio v18.10 (SSMS)
There are no other Visual Studio or SQL Server instances or installations.
I can look at my local SQL instance using SSMS but not SQL Server Profiler. I am using Server Name "." and Windows Authentication in both cases. Profiler is being launched both in SSMS and directly launched (in administrative mode or not), with the same results:
SQL-related services are in these states (enabling SQL Server Browser has no effect):
"Trust server certificate" does not help. I suspect the provider is extremely sloppy about the root cause of this response.
(Same system environment as https://stackoverflow.com/posts/70805318/)
localhostas the server name?