Strange problem that I've been chasing all day:
- Windows 2012 R2 Standard Edition
- SQL Server 2012 SP1 CU8 Enterprise Edition
Relational DB and SSAS are installed on the same server.
OLAP database has connection string to local SQL database.
- SQLNCLI11.1
- Windows Auth
- Initial Catalog is specified in the connection string
- Test Connection succeeds in SSMS
- Impersonation info is set to impersonate a specific user - users exists, password is correct, has necessary rights
Processing the OLAP database results in the usual flurry of error messages and events in the Windows Application event log with the key phrase "Client unable to establish connection; 08001; Encryption not supported on the client.; 08001."
There's a lot of FUD and hearsay on the internet about this error, most "solutions" recommend changing the connection string to use a different provider. I've tried the SqlClient managed provider, the SQL Native Client, the "Microsoft OLE DB for Sql Server" provider and all fail similarly when processing the cube, and all succeed when testing the connection interactively.
The one thing that DID make a difference? I changed the service identity for SSAS from NT Service\MSOLAPServer (or whatever the default virtual account is) to a specific domain user and magically all problems went away. Keep in mind, the data source is set up to impersonate, not use the service identity, so why changing this made any difference is a mystery.
Any ideas? I'd like to get to the bottom of this because it's come up several times on several different systems and it's always a research project to find a configuration that actually works.
-cd Mark the best replies as answers!