topic Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string in Report Server

We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

samgreene1 — Fri, 26 Feb 2021 18:15:18 GMT

Hi,

We just applied Jan 2021 update. Co-worker has designed a report using sql server using direct query. When deploying to the server, getting the error: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string correctly.

"An unexpected error occurred
An unexpected error occurred. Please try again later.
Please try again later or contact support. If you contact support, please provide these details.
We couldn't connect to the Analysis Services server. Make sure you've entered the connection string correctly.:
Request ID: 414e3377-166b-8443-a8a7-cf5f539339e1
Time: Fri Feb 26 2021 11:14:38 GMT-0700 (Mountain Standard Time)
Service version: /powerbi/libs"

Switched to using the actual server name instead of a DNS Cname and still getting the same result.

Any advice?

Thanks,

Sam

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

FarhanAhmed — Fri, 26 Feb 2021 04:53:57 GMT

Can you please share the error screenshot where you are getting?

What are the data source user credentials you are using in PBIRS?

Are you able to connect to SSAS from the desktop?

are you able to connect SSAS from PBIRS Machine (try to connect SSAS thru excel in PBIRS Machine.)

There are logs in "E:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles" to see if that helps you.

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

samgreene1 — Fri, 26 Feb 2021 18:46:28 GMT

I've updated my question to include the full error text. We are connecting to SQL Server, not SSAS. Using SQL Login type creds. Many other reports are functioning, but this new one is not. I will try to create a new report as a test. Maybe this user did something odd.

Update: recreated his query using same login and direct query type and it worked. I noticed that in the data source on the report server for my functioning report contains "persist security info=False". That's the only difference I'm seeing, but the data sources are configured similarly in Power BI Desktop.

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

samgreene1 — Fri, 26 Feb 2021 18:44:44 GMT

Here is the log from the server:

ErrorCode=QuerySystemError, Language=en-US, ProviderErrorCode=0xC1070000, ProviderErrorMessage=[2663DD5278984E7565A2F88E29150C3F45B0F0A259F58B6FD892970FE6450AA7], ProviderGenericMessage=[COM error: COM error.], ErrorSource=PowerBI, ErrorSourceOrigin=MsolapWrapper, OnPremErrorCode=, InnerErrorDetails=[Type=MsolapWrapper.MsolapWrapperException, Message=Failure encountered while getting schema];stackTrace: at Microsoft.PowerBI.DataExtension.Msolap.SchemaCommand.GetModelMetadata(String catalogName, String perspectiveName, String supportedVersion)
at Microsoft.PowerBI.ReportingServicesHost.LocalReportProcessingHost.ExecuteSchemaCommand[T](ExploreHostDataSourceInfo dataSourceInfo, IDbConnectionPool connectionPool, IConnectionFactory connectionFactory, IConnectionUserImpersonator connectionUserImpersonator, QueryExecutionOptionsBase queryExecutionOptions, ITelemetryService telemetryService, Func`2 action, String failTelemetryMessage, ServiceErrorStatusCode statusCode, ExploreBaseEvent exploreEvent);message:GetModelMetadata;| RequestID = a1173494-81a9-292f-4566-084d7b279d8d ClientSessionID = d56d49c9-7cc5-b863-0a59-46860d78fa5b
2021-02-26 11:41:45.0192|ERROR|7|PBI.Win.ReportingServicesHostTrace|type:Error;message:library:Throwing Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: , Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: An error occurred while loading the model for the item or data source 'a3b62991-417f-4020-89ab-31aa0c21cc46_1529049499'. Verify that the connection information is correct and that you have permissions to access the data source. ---> Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException: Failed to get CSDL. ---> MsolapWrapper.MsolapWrapperException: Failure encountered while getting schema
at MsolapWrapper.Utils.ThrowErrorIfHrFailed(Int32 hr, String message)
at MsolapWrapper.CDbSchemaRowsetWrapper.ExecuteSchemaRowset(Guid schema, Object[] restrictions, PropertySetCollection propSets)
at MsolapWrapper.SchemaCommand.ExecuteReader(Guid schema, Object[] restrictions)
at MsolapWrapper.SchemaCommand.GetModelMetadata(Object[] restrictions)
at Microsoft.PowerBI.DataExtension.Msolap.SchemaCommand.GetModelMetadata(String catalogName, String perspectiveName, String supportedVersion)
--- End of inner exception stack trace ---
at Microsoft.PowerBI.DataExtension.Msolap.SchemaCommand.GetModelMetadata(String catalogName, String perspectiveName, String supportedVersion)
at Microsoft.PowerBI.ReportingServicesHost.LocalReportProcessingHost.ExecuteSchemaCommand[T](ExploreHostDataSourceInfo dataSourceInfo, IDbConnectionPool connectionPool, IConnectionFactory connectionFactory, IConnectionUserImpersonator connectionUserImpersonator, QueryExecutionOptionsBase queryExecutionOptions, ITelemetryService telemetryService, Func`2 action, String failTelemetryMessage, ServiceErrorStatusCode statusCode, ExploreBaseEvent exploreEvent)
--- End of inner exception stack trace ---;;| RequestID = a1173494-81a9-292f-4566-084d7b279d8d ClientSessionID = d56d49c9-7cc5-b863-0a59-46860d78fa5b
2021-02-26 11:41:45.0192|ERROR|7|Failure in conceptualschema| RequestID = a1173494-81a9-292f-4566-084d7b279d8d ClientSessionID = d56d49c9-7cc5-b863-0a59-46860d78fa5b Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: An error occurred while loading the model for the item or data source 'a3b62991-417f-4020-89ab-31aa0c21cc46_1529049499'. Verify that the connection information is correct and that you have permissions to access the data source. ---> Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException: Failed to get CSDL. ---> MsolapWrapper.MsolapWrapperException: Failure encountered while getting schema
2021-02-26 11:41:45.0192|INFO|7|Sending response. Response code DOMAIN\SGreene 200, Elapsed time 0:00:00.0672904| RequestID = a1173494-81a9-292f-4566-084d7b279d8d ClientSessionID = d56d49c9-7cc5-b863-0a59-46860d78fa5b
2021-02-26 11:41:45.1789|INFO|26|Received request GET /libs/styles/InfoNav-Sprites.png| RequestID = s_5d392620-327d-4381-83d1-464dc8f995ef
2021-02-26 11:41:45.2102|INFO|26|Received request GET /libs/scripts/textboxVisual.js| RequestID = s_d440cbc4-69a6-49a6-a668-565c591efe76
2021-02-26 11:41:45.2102|INFO|26|Received request GET /libs/scripts/cartesianVisuals.js| RequestID = s_00b503db-272c-4055-8a58-9c6dcc94ef33
2021-02-26 11:41:45.3977|INFO|26|Received request POST /api/explore/reports/a3b62991-417f-4020-89ab-31aa0c21cc46/conceptualschema| RequestID = afd1bf7d-7bf5-a989-dc41-a8305dda1eaa ClientSessionID = d56d49c9-7cc5-b863-0a59-46860d78fa5b
2021-02-26 11:41:45.4446|ERROR|28|Failure in conceptualschema| RequestID = afd1bf7d-7bf5-a989-dc41-a8305dda1eaa ClientSessionID = d56d49c9-7cc5-b863-0a59-46860d78fa5b Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: An error occurred while loading the model for the item or data source 'a3b62991-417f-4020-89ab-31aa0c21cc46_1529049499'. Verify that the connection information is correct and that you have permissions to access the data source. ---> Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException: Failed to get CSDL. ---> MsolapWrapper.MsolapWrapperException: Failure encountered while getting schema

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

blynchdata — Sat, 27 Feb 2021 16:17:49 GMT

Could there be an a connection to SSAS in the report even though it is not used in the report?

It's odd that this error is happening at deployment and not when trying to run the report, that's when I'm used to seeing this one. Usually it doesn't try to connect to SSAS at deployment.

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

samgreene1 — Sat, 27 Feb 2021 17:35:34 GMT

I get this same error when deploying a report for the first time, before the data source is updated with credentials, so maybe it is behind the scenes SSAS usage by Power BI with every data source. Just a guess.

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

Icey — Tue, 02 Mar 2021 05:40:34 GMT

Hi samgreene1 ,

Update: recreated his query using same login and direct query type and it worked. I noticed that in the data source on the report server for my functioning report contains "persist security info=False". That's the only difference I'm seeing, but the data sources are configured similarly in Power BI Desktop.

This may be the cause.

For Persist Security Info, valid values are True or False.

When set to True, security information, such as the user identity or password previously specified on the connection string, can be obtained from the connection after the connection is made.

The default value is False. Then security information is discarded after it is used to open the connection, ensuring that an untrusted source does not have access to security-sensitive information.

Best Regards,

Icey

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

samgreene1 — Tue, 02 Mar 2021 18:39:18 GMT

Thanks to everyone for your help. I found the issue yesterday after I created a working report and uploaded to the server. Teammate tried to download to edit and got an error similar to 'could read past end of stream'. That lead to me asking for his desktop version which was October! Once he updated everything was working. 😅

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

Moss_Lost2020 — Mon, 08 May 2023 07:59:34 GMT

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

PedroGonçalves — Mon, 08 May 2023 08:33:27 GMT

Hello, I got the same error I guess. But I do not have the desktop version. I am just an user of the report. How do I fix that? This is the error:
An unexpected error occurred
An unexpected error occurred. Please try again later.
Please try again later or contact support. If you contact support, please provide these details.
We couldn't connect to the Analysis Services server. Make sure you've entered the connection string correctly.:
Request ID: 339dab2f-dafb-a036-5a9c-c5747b6037e9
Time: Mon May 08 2023 10:31:07 GMT+0200 (Central European Summer Time)
Service version: /powerbi/libs

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

IgorKrupitsky — Fri, 27 Oct 2023 13:34:48 GMT

1. make sure report server and ssas server are on the same machine
2. make sure you use machine name and not server alias
3. use ssas http access if all else fails

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

ayaasfour — Tue, 21 Nov 2023 18:34:38 GMT

what to do if they are on different servers?

Re: We couldn't connect to the Analysis Services server. Make sure you've entered the connection string

IgorKrupitsky — Wed, 22 Nov 2023 02:32:07 GMT

use ssas http access

https://learn.microsoft.com/en-us/analysis-services/instances/configure-http-access-to-analysis-services-on-iis-8-0?view=asallproducts-allversions