Forum Discussion
Error Refreshing has a code but not detail
Hi
Recently experienced issue with a refresh that doesnt give me the actual issue has anyone had this.
I have tried the various options like matching permissions to organisational etc but to no avail
Underlying error code: -2147467259
Underlying error message: Invalid binary encoding.
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.Detail: ••••••••••••
Microsoft.Data.Mashup.ValueError.Reason: Expression.Error
Cluster URI: WABI-NORTH-EUROPE-H-PRIMARY-redirect.analysis.windows.net
Thanks
Danny
Hi, DannyG1980
There are other people who have encountered the same situation as you and the same error reported.
You can refer to the following methods to solve the problem.
1. Install the latest version of the gateway.
2. Download and install the latest version of Power BI Desktop
3. The effective username in the username mapping for Analysis Services source was set to a personal account. So when we deactivated the personal account, the effective username used in the mapping was no longer valid and the gateway connection was refused.
Then we created a dedicated user for the gateway in the AD and used this account as the effective username in the user name mapping.
This username mapping and choosing and effective username is only necessary for connecting to Analysis Services (cubes). You can read more here: https://docs.microsoft.com/en-us/power-bi/connect-data/service-gateway-enterprise-manage-ssas#map-user-names-for-analysis-services-data-sources
4. Clearing all data source permissions (File-->Options and Settings --> Data Source Settings --> clear each data source permission).
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
2 Replies
Hi, DannyG1980
There are other people who have encountered the same situation as you and the same error reported.
You can refer to the following methods to solve the problem.
1. Install the latest version of the gateway.
2. Download and install the latest version of Power BI Desktop
3. The effective username in the username mapping for Analysis Services source was set to a personal account. So when we deactivated the personal account, the effective username used in the mapping was no longer valid and the gateway connection was refused.
Then we created a dedicated user for the gateway in the AD and used this account as the effective username in the user name mapping.
This username mapping and choosing and effective username is only necessary for connecting to Analysis Services (cubes). You can read more here: https://docs.microsoft.com/en-us/power-bi/connect-data/service-gateway-enterprise-manage-ssas#map-user-names-for-analysis-services-data-sources
4. Clearing all data source permissions (File-->Options and Settings --> Data Source Settings --> clear each data source permission).
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you v-zhangti while this resolved part of the issue some of this was with the RestAPI coding as well
