Hey, Some of the users are able to access AAS via excel and some of us are getting the below error: Can anyone help us identify what the error is about and what is the resolution for it? Note: The users unable to access via excel are able to connect the cube via Power BI

Hello @Nandan Hegde , Thanks for the question and using MS Q&A platform. Since few users are able to connect to AAS and few aren't, I suspect either it could be a permissions issue, or it could be related to installing client libraries. If you have already verified the permissions and they have relevant permissions, then could you please make sure that the users have installed all three latest AAS client libraries as described in this document: Analysis Services client libraries | Microsoft Learn Let us know how it goes. Thanks

Excel connectivity Issue for AAS

Accepted answer

KranthiPakala-MSFT 46,512 Reputation points Microsoft Employee

2022-11-11T02:46:47.677+00:00

Hello @Nandan Hegde ,

Thanks for the question and using MS Q&A platform.

Since few users are able to connect to AAS and few aren't, I suspect either it could be a permissions issue, or it could be related to installing client libraries. If you have already verified the permissions and they have relevant permissions, then could you please make sure that the users have installed all three latest AAS client libraries as described in this document: Analysis Services client libraries | Microsoft Learn

Let us know how it goes.

Thanks
Please sign in to rate this answer.
Nandan Hegde 32,416 Reputation points MVP

2022-11-11T03:23:34.353+00:00

Hey @KranthiPakala-MSFT
Thank you for your reply!!

The thing is everyone were able to access the cube via excel till last week, Its just since 2 days back that the above issue has started occurring. So do you still think it might be related to the libraries issues ? where there any recent updates in libraries

KranthiPakala-MSFT 46,512 Reputation points Microsoft Employee

2022-11-11T03:41:42.687+00:00

Hello @Nandan Hegde ,

That's strange. I'm not 100% sure about the latest update. But there is a possibility that the client library versions could be old or not the latest. As an additional verification, I would recommend verifying the installed library versions as mentioned in the above document. In addition, I would also recommend doing a manual update of libraries to see if that helps to resolve the issue:

Nandan Hegde 32,416 Reputation points MVP

2022-11-11T05:02:08.937+00:00

@KranthiPakala-MSFT : Thank you for your inputs but still the same issue

KranthiPakala-MSFT 46,512 Reputation points Microsoft Employee

2022-11-11T06:18:43.803+00:00

Thanks for verifying @Nandan Hegde . Looks like this issue requires deeper investigation, hence would recommend filing a support ticket to figure our the root cause and possible solution. Please do share the SR# once it is filed so that we can track it internally.

KranthiPakala-MSFT 46,512 Reputation points Microsoft Employee

2022-11-14T23:27:40.75+00:00

Hi @Nandan Hegde , wanted to check if you have got a chance to file a support ticket for the above issue? If so, could you, please share the SR# for tracking it. In case if you have already found a solution, please feel free to share it here as it would be helpful for others reading the thread.

Thank you

Nandan Hegde 32,416 Reputation points MVP

2022-11-16T03:31:15.937+00:00

MS # 2211100030002488
this is the tkt number

Thanks

KranthiPakala-MSFT 46,512 Reputation points Microsoft Employee

2022-11-23T02:27:48.307+00:00

Hi @Nandan Hegde ,

From the support ticket provided, below are the observations and possible workaround:

It has been observed that at the network layer, the http headers are being forwarded differently which is causing these failures. These http headers are being dropped because AAS forwarding logic does a case sensitive match for headers and these headers have turned camel-cased recently whereas previously all headers were lowercase.

It is suspected that your Organization’s Proxy Server(as this issue is not happening for other customers) is impacting and transforming these headers into camel-case, due to some recent changes being pushed at your network level.

There is a workaround being planned to make all of the header hashsets use string in-sensitive comparison. But for the fix to be deployed and reflect across all Tenants would happen by 2nd week of December at the latest, though this timeline is subjected to change and is tentative as of now.

Meanwhile, product team suggests to please check internally with your network/infrastructure Team of your Organization and explain the cause of the issue (http headers turning camel-cased) to check if this can be mitigated at your network level until the fix is applied by product team.

Hope this info helps.

Thank you

Nandan Hegde 32,416 Reputation points MVP

2022-11-23T03:33:10.273+00:00

Thank you Kranthi for this input but thats the thing :)
If a common change has been made in our network layer, why is it that the issue is not occurring for all employees and just for select few?
How to we bifurcate which employees are vulnerable for this issue and who are not?

KranthiPakala-MSFT 46,512 Reputation points Microsoft Employee

2022-11-24T03:37:05.88+00:00

Hello @Nandan Hegde ,

That's great question. In order to get answers to them, we may have to know what recent changes have been performed by your networking team.
Since you have already filed a support ticket, could you please help provide more details about the recent changes by your networking team to the support engineer who is working on this ticket, so that they can troubleshoot deeper and get better understanding of what exactly is the root cause.

Nandan Hegde 32,416 Reputation points MVP

2022-12-09T11:18:48.81+00:00

Update.
The issue is fixed by MSFT in NE region
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Excel connectivity Issue for AAS

0 additional answers

Your answer