Forum Discussion
Connection issues to Azure Analysis Services in Excel - The connection string includes explicit user
Starting yesterday, many people in our organization are receiving this error when trying to refresh the Azure Analysis Services model in Excel.
Internal error: An unexpected error occurred (file 'Error.cpp', line 215, function 'err::BaseError::
We use Okta SSO to connect. We've never had this issue. definitely seems like a bug in Excel? or something changed in azure.
Note, initially we were receiving this error:
Errors in the OLE DB provider. The connection string includes explicit user identity and additional authentication options, such as 'Interactive Login' or 'Identity Mode', which is not supported. Either remove the user identity or omit the additional authentication options.
We removed User ID from the connection definition but then started receiving the other error.
example connection
Provider=MSOLAP.8;Persist Security Info=True;Initial Catalog=abc;Data Source=asazure://southcentralus.asazure.windows.net/xyz;MDX Compatibility=1;Safety Options=2;
Microsoft® Excel® for Microsoft 365 MSO (Version 2605 Build 16.0.20026.20168) 64-bit
3 Replies
- Shai_Karmani
Super User
Yeah, this is the new Excel build, not Azure. Version 2605 (Build 20026.20168) rolled out June 9, which lines up perfectly with this breaking org-wide.
What's happening: your first error came from User ID plus an interactive auth hint that the new MSOLAP rejects. You stripped User ID, so now it falls through to the silent token refresh, which fails and throws that ugly generic Error.cpp error instead.
Stuff you can try, in order:
Clear cached creds. Windows Credential Manager, delete anything with asazure or Office/AAD in it, reopen Excel, let it prompt you fresh. Fixes it per-user most of the time.
Switch the connection path. Use Data > Get Data > Azure > Azure Analysis Services database instead of the SQL Analysis Services connector. It handles token caching differently and often dodges the whole problem.
Check every connection in the workbook for leftover Integrated Security=SSPI or any Identity Mode / Interactive Login. Your posted string is clean but check the others.
Roll one machine back to the prior Office build to confirm. If refresh works there, you've proven it's the 2605 regression and you've got a stopgap.
Rolling one box back is your cleanest proof before escalating.If this helped, a thumbs up and accepting the solution would be appreciated.
Best,
Shai Karmanithere is no Azure Analysis Services in Get Data -> Azure.
