Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric certified for FREE! Don't miss your chance! Learn more
Hello,
I have rpeviously been running trace analysis with no issues on a specific report in the same workspace.
I have since made updates, removed the reprot from the workspace and re published it.
However now, when attempting to connect via SQL Server Profiler, i get this error
Any ideas?
Solved! Go to Solution.
Hi,
It turns out that i added a space accidenally at the end of the report name - for some reason it did not like this!
removed it and it worked fine 🙂
Have you solved your problem? If so, can you share your solution here and mark the correct answer as a standard answer to help other members find it faster? Thank you very much for your kind cooperation!
Thanks for the reply from @lbendlin.
Best Regards
Zhengdong Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi,
It turns out that i added a space accidenally at the end of the report name - for some reason it did not like this!
removed it and it worked fine 🙂
Did you change the Semantic Model name as well?
No matter what workspace i deploy it too, i cannot use it in SQL Server Profiler, really not sure whats blocking it all of a sudden
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .
it automatically uplaoded with the new semantic model - with the same name
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 41 | |
| 41 | |
| 28 | |
| 25 | |
| 22 |