Excel Services Data Refresh Failed. Kerberos.dll bug (Server 2008 pre R2).

I have had several cases where a customer will have Kerberos properly configured but refresh in the browser fails.

In the UI, the error will appear.

"Unable to get the required information about this cube.  The cube might have been reorganized or changed on the server.  The PivotTable was not refreshed."

IMPORTANT: I have also seen the standard “Data Refresh Failed” error: 

There are a variety of places you can look to see if this is indeed an error with the Kerberos.dll:

1. UDL (Universal Data Link)
2. ULS Logs
3. Event Viewer
4. Network Trace

There is one common theme you will notice across all these results, NOT SUPPORTED.

1. Test a UDL to the datasource from the server running Excel Services.

*Since the OS is 64 bit, you will need to call it a certain way (see below):

On the server you are running Excel Calculation Services on please perform the following:
1. Right click on your desktop (or wherever you are having the problem) and create a new text doc.
2. Rename it to .udl (make sure you do NOT have on "hide known extensions") Save > Close > Place this on the Root of C:. Execute the command below from a command line or Start/Run: C:\Windows\syswow64\rundll32.exe "C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll",OpenDSLFile C:\test.udl
3. Double click, choose Microsoft OLE DB Provider for Analysis Services 10.0 on the first tab (Provider).
4. On the 2nd tab (Connection) enter the AS Server name (or AS servername\instance for a named instance) in the Data Source box. Leave Location empty. For the server name enter the shortname/netbios name.
5. On the 2nd tab (Connection) choose "Use Windows NT Integrated security".
6. Now go to the 4th tab (All) and scroll down to highlight SSPI. Click on "Edit Value" and enter Kerberos as the Property Value.
7. Go back to the 2nd tab (Connection) and choose "Test Connection".

If you see the error, "Test connection failed because of an error in initializing provider.  The following system error occurred: The function requested is not supported.", you need to upgrade the kerberos.dll (see KB 969083).


2. ULS logs.

If you see the below error in the ULS Logs, you need to upgrade the kerberos.dll (see KB 969083).

"OLEDBConnection::InitConnection: The following system error occurred:  The function requested is not supported."

3. Event Viewer (turn on Kerberos Event Logging here, reproduce the error in the browser, then look in Event Viewer > Windows Logs > System):

If you see the error "KDC_ERR_ETYPE_NOTSUPP" in the Event Viewer, you need to upgrade the kerberos.dll (see KB 969083).

4. Network Trace.

If you see the error "NT Status: STATUS_NOT_SUPPORTED" in a Network Trace, you need to upgrade the kerberos.dll (see KB 969083).

To resolve all the above errors, apply the Hotfix in the below KB to the machines receiving Kerberos traffic (including the database; SQL & SSAS).

A Kerberos authentication fails together with theerror code 0X80090302 or 0x8009030f on a computer that is running Windows Server 2008 or Windows Vista when the AES algorithm is used


A real easy thing to do is look at the Kerberos.dll in C:\Windows\System32\kerberos.dll > right click > Properties > Details

It needs to be at least 6.0.6002.22138. If it is not, apply the above Hotfix.

Skip to main content