Post reply

Connection issue from SSRS to SSAS data source

  • March 15, 2021 at 10:29 pm

    #3858208

    I have a data source defined on our SSRS server and it connects successfully when I am in IE but from Chrome or Edge, it fails.

    I ran Server Profiler on the SSAS server and see that when I Test Connection with IE, my user account logs in but when I do the same in Chrome or Edge, the NTUserName is ANONYMOUS LOGON.

    Everything my searching comes up with says it's a Kerberos issue. Kerberos Configuration Manager reports a status of 'Good'. I have the SPN's set up correctly as it works with IE but in the near future, we will be discontinuing IE and moving to Edge.

    Your help is appreciated.

    Wayne

     

  • March 15, 2021 at 11:13 pm

    #3858231

    see this for edge https://stackoverflow.com/questions/57034199/integrated-windows-authentication-in-microsoft-edge

    and this for chrome https://knowledge.kofax.com/Smart_Process_Applications_-_TotalAgility/Configuration/Configure_Chrome_To_Allow_Windows_Authentication_Without_Prompting

  • March 16, 2021 at 1:13 am

    #3858265

    Excellent! It's now working in the Edge browser. I had the IE settings correct but didn't have the Edge policies set.

    What fixed it for me was this registry setting -

    AuthNegotiateDelegateAllowlist

    Windows Registry Settings

    • Path (Mandatory): SOFTWARE\Policies\Microsoft\Edge

    • Value Name: AuthNegotiateDelegateAllowlist

    • Value Type: REG_SZ

    The reports now connect to the data source with the Edge browser.

    I will look into the Chrome solution tomorrow.

    Thanks for your help. I really appreciate it.

    Wayne

  • March 26, 2021 at 4:56 pm

    #3862478

    For Chrome, I had already done the settings in the supplied URL and it didn't work for me.

    What did work for Chrome was a similar registry setting I had used for Edge.

    [HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome]

    "AuthNegotiateDelegateAllowlist"="server01,server02,"

    Also, if users are accessing the report server with a DNS alias, you will need to add the alias to this registry setting.

    Thanks again for your help.

    Wayne

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply