0

Unavailable Data Sources

Data sources can be unavailable for several reasons. Here are the most common issues that can cause this:

  • The tabular server has a faulty/corrupt model.
  • The client browser is not configured correctly.
    To fix this, please check this article
  • SPNs and Delegation are not configured correctly.
    This is likely to happen when Windows Authentication is used or when Pyramid is set up as a multi server install.
    The Kerberos Diagnostic tool can assist in troubleshooting this. 
    To find out how to use the Kerberos Diagnostic tool, please refer to this article.
    If the Kerberos Diagnostic tool indicates a Kerberos problem, you can fix it with the help of the bellow guide.
    • In case the Kerberos front-end diagnostic tool shows a missing SPN, you will need to add it. To do this, first check which identity is used for the bio5 app pool. Then start CMD with elevated permissions.

      In case the app pool is running with any of the built in accounts ,type this in CMD:
      “setspn –s HTTP/website_address IIS_SERVER_HOSTNAME$”
      For example:
      “setspn –s HTTP/pyramid.com WEB$”
      If the app pool is running with a Custom account, do this:
      “setspn –s HTTP/website_address DOMAIN\AD_USER_NAME”
      For example:
      “setspn –s HTTP/pyramid.com DEV\administrator”

    • If the Kerberos back-end diagnostic tool shows a missing SPN under the Backend Server section, check which user is running the SSAS service and open CMD with elevated permission.
      In case the SSAS service is running with Local System Account or a NT User, type this in CMD:
      “setspn -s MSOLAPSVC.3/SSAS_NETBIOS_NAME DOMAIN\SSAS_NETBIOS_NAME$”
      For example:
      “setspn -s MSOLAPSVC.3/analysis1 corp\analysis1$”
      And then, this:
      “setspn -s MSOLAPSVC.3/SSAS_FQDN  SSAS_NETBIOS_NAME $”
      For example:
      “setspn –s MSOLAPSVC.3/analysis1.corp.local analysis1$”

      In case the SSAS service is running with an AD user credentials, type this:
      “setspn -s MSOLAPSVC.3/SSAS_NETBIOS_NAME DOMAIN\AD_USER_NAME”
      And then, this:
      “setspn -s MSOLAPSVC.3/SSAS_FQDN DOMAIN\AD_USER_NAME”

      Please note: if the cube is not on the default instance, then you will need to add the instance name after the analysis server name.
      For example: 
      “setspn -s MSOLAPSVC.3/data1:tabular data1$”
      And 
      “setspn -s MSOLAPSVC.3/data1.dev.pyramid.local:tabular data1$”

Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 3 yrs agoLast active
  • 1172Views
  • 1 Following