dd

dauris — Thu, 12 Sep 2024 19:46:37 GMT

Se produjo un error inesperado Hubo un error inesperado. Pruebe otra vez más tarde. Vuelva a intentarlo más tarde o póngase en contacto con el soporte técnico. Proporcione estos detalles si se pone en contacto con ellos. No se pudo establecer una conexión con el servidor de Analysis Services. Asegúrese de que la cadena de conexión que ha escrito es correcta. Identificador de la solicitud2384957a-ee9a-ebdd-deda-b4a53d200685 HoraJue 12 de septiembre de 2024 15:25:25 GMT-0400 (hora estándar del Atlántico) Versión del servicio/powerbi/libs Copia

Re: dd

Anonymous — Fri, 13 Sep 2024 05:48:35 GMT

Hi,@dauris .I am glad to help you.

Based on your error message, it seems that there is an error in the connection string of your report data source.
Can you please tell me if you are experiencing this problem while managing pbix report files on Power BI service or on your local report server, and can you provide more detailed information such as the connection mode of the report (import /Direct Query/Live connections) as well as the data source and the data source credentials used? This will help you to quickly locate the problem.
1. If you are experiencing this problem with Power BI service, please check if your connection string is correct.
Check whether your data source credentials are correct (generally in the gateway connection part involves data source credentials validation information, please check in time to make sure that the validation credentials provided can normally access the data source)
2. If you encounter this problem on the report server, please also check if the following connection strings are incorrect
Reconfigure valid access credentials
In report server

URL:
Solución al error "No se pudo establecer una conexión con el servidor de Analysis Services" Power BI | Ejercicios de excel (jsequeiros.com)

3. If the connection mode of your report is Direct Query, you need to note that the report server is a local server, so the security requirements are very high, and users need to provide their own encryption certificate to ensure that the data is legal and safe, and will not bring security problems to the server. You need to provide an encryption certificate for the data source to allow the server to trust the data source connected in Direct Query connection mode.

If you don't want to provide an encryption certificate, you can also try adding a system environment variable to the System Advanced Variables on the computer where your report server is located to allow the report server to trust the domain data source.
Here are my tests

In general, if you don't configure an encryption certificate, pbix reports in Direct Query connection mode will open with the following error (the error message is the same as the one you provided)

At this point you just need to add the system environment variable to your local environment
Open the control panel with win+R

sysdm.cpl

PBI_SQL_TRUSTED_SERVERS domain name（Not distinguishing capitals from lower case letters）

like this:

Restart your report server management and start the server.
Clear your browser's cache to avoid interference from the cache.

At this point, the report server will no longer report errors when the original Direct Query connection mode is opened again.

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

topic Re: dd in Report Server

dd

Re: dd