Forum Discussion

LeenBem's avatar
LeenBem
Frequent Visitor
8 months ago
Solved

COM error: Microsoft.AnalysisServices.AzureClient, An error occured while sending the request...

Hello,

we have some users that get this error all of a sudden in Excel when they try to connect to PBI Semantic Models to build Excel pivot tables:

COM error: Microsoft.AnalysisServices.AzureClient, An error occured while sending the request...

- It worked before for them for months. We signed out and logged in again without any succes.

- They have the correct build-persmissions to the models.

- It is an issue on all models, so not related to any issues in the model.

- The version of Excel they use is 2509. Some other users work with the same version and no issues. 

 

Any ideas how I can get more details on this error and/or what can be the cause of this?

Thanks,

Leen

Need Help
  • LeenBem's avatar
    LeenBem
    8 months ago

    We found out the issue was related to missing TLS 1.2 and TLS 1.3 registry keys after Windows 10 to Windows 11 upgrade.

    Performed the steps below to solve:
    • Download the file 'Registry_TLS12_13_Win10_to_Win11.reg' 
    • Copy the downloaded file to a folder on the computer of the end user (e.g. C:\Temp)
    • Open a Command Prompt as Administrator
    • Navigate to the folder in which the registry file is saved by using the command below:
    Cd LocationOfFile
         e.g. cd c:\Temp
    • Type the following command and press the Enter button of the keyboard
       Registry_TLS12_13_Win10_to_Win11.reg
      Handy to know, you can start typing Registry and then press the Tab button of the keyboard so that the name is autocompleted
    • Wait until the command has successfully ran
    • Restart the computer
    • Check if the issue still occurs or not

7 Replies

  • v-kpoloju-msft's avatar
    v-kpoloju-msft
    Community Support
    8 months ago

    Hi LeenBem,

    Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to GeraldGEmerick, for those inputs on this thread. 

    Has your issue been resolved? If the response provided by the community member GeraldGEmerick, addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

    Or have you rasied a support ticket suggested by the GeraldGEmerick.

    Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.

    Thank you for using the Microsoft Community Forum.

    • v-kpoloju-msft's avatar
      v-kpoloju-msft
      Community Support
      8 months ago

      Hi LeenBem,

      Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

      Thank you.

  • LeenBem's avatar
    LeenBem
    Frequent Visitor
    8 months ago

     Hi GeraldGEmerick , thanks for your feedback.

    Unfortunately, there is no known issue about this and so I still not found a solution. We believe it might be linked to some Windows Updates that are pushed automatically in our organisation, so are investigation that.
    Kind regards,

    Leen

  • v-kpoloju-msft's avatar
    v-kpoloju-msft
    Community Support
    8 months ago

    Hi LeenBem,

    Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to GeraldGEmerick, for his inputs on this thread.

    This specific error “COM error: Microsoft.AnalysisServices.AzureClient, An error occurred while sending the request” generally means Excel cannot reach the Power BI XMLA endpoint. Since permissions and datasets look fine, the issue is likely local to the affected machines (authentication cache, network restrictions, or TLS inspection). Please try clearing Excel auth cache, ensuring required endpoints are allowed, updating Excel, and testing via Excel Online.

    Refer this link: https://learn.microsoft.com/en-gb/power-bi/collaborate-share/service-analyze-in-excel 

    Hope this clears it up. Let us know if you have any doubts regarding this. We will be happy to help.

    Thank you for using the Microsoft Fabric Community Forum.

  • LeenBem's avatar
    LeenBem
    Frequent Visitor
    8 months ago

    We found out the issue was related to missing TLS 1.2 and TLS 1.3 registry keys after Windows 10 to Windows 11 upgrade.

    Performed the steps below to solve:
    • Download the file 'Registry_TLS12_13_Win10_to_Win11.reg' 
    • Copy the downloaded file to a folder on the computer of the end user (e.g. C:\Temp)
    • Open a Command Prompt as Administrator
    • Navigate to the folder in which the registry file is saved by using the command below:
    Cd LocationOfFile
         e.g. cd c:\Temp
    • Type the following command and press the Enter button of the keyboard
       Registry_TLS12_13_Win10_to_Win11.reg
      Handy to know, you can start typing Registry and then press the Tab button of the keyboard so that the name is autocompleted
    • Wait until the command has successfully ran
    • Restart the computer
    • Check if the issue still occurs or not
    • LeenBem's avatar
      LeenBem
      Frequent Visitor
      8 months ago
      Content of file: Registry_TLS12_13_Win10_to_Win11.reg

      Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client]
"Enabled"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Server]
"Enabled"=dword:00000000