OLE DB or ODBC error: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied

Question

Hi,
I have one client and one server.  In both hosts I created an OS-user named User1.
The user have been given various role under the prefix SQLServer2005.
The default instance of SQL Server and instance (background-process) of
Analysis Service are also run under User1.
I connected via Management Studio to Analysis Service directly in the
server.  I set the permission to access Analysis Service to Everyone. 
This means everyone should be able to use Analysis Service.  I have set
ODBC data source to the server.  Testing was successful.
I created a project to create a cube.  The tables are fairly small (total 300 MB, biggest one 290).
On project setting (created at client) I set the server host as
deployment target. I managed to deploy project when all I have are Data
Source and Data Source Views.
But on deployment I always failed.   The errors remain the same, begins with
OLE DB error: OLE DB or ODBC error: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.; 08001.
I have tried 4 combinations of Impersonation :
(A) Use a specific username and password
  * in which I supply User1 and the password of User1
(B) Use the service account
(C) Use the credentials of the current user
(D) Default
Why is this? The server does certainly exist.  I think the error message is wrong.
I have seen 3 posting that seems related.  One of them say the solution is giving the right impersonation, but gave no detail.  About the privilege, User1 are granted the role of
SQLServer2005MSOLAP.  What is the solution?
Thank you,
Bernaridho

Answer 1

I just had this problem and solved it by creating an alias in SQL Server Configuration Manager, as below:
Scenario: My SQL server is accessible from the internet under my.domain.com, and from itself at ServerName. But the local network can't see itself through the router at my.domain.com, so the deployed project is unable to process the cube, since that would
require Analysis Services to be able to see the SQL Server at my.domain.com, which it can't do.
So I changed the server in my project from my.domain.com to ServerName, and I created a local alias to ServerName in SQL Server Configuration Manager, under SQL Native Client 11.0 Configuration, Aliases. In my case, I pointed it to localhost port 1333, and
used SSH -L 1333:my.domain.com:1433, but I could have pointed the alias directly to the server, just as well. (Verifying... yes, that worked too, so you can forget SSH if you have no interest in it.)