Analysis Service error: Either the user, Domain\User, does not have access to the Database Name database, or the database does not exist.

As it seems the error text on the subject looks familiar when you have installed SQL Server or working with SQL Server databases. How about getting the error on Analysis Services databases (OLAP) within your BI Platform. So in the case of handling the Business Intelligence platform you must be aware of necessary data providers that are required in order to connect the end user application to backed database platform. If not various various exceptions can appear, including:

• "The specified module could not be found."
• "The handle is invalid."
• "The parameter is incorrect."
• "Errors in the metadata manager."
• "A connection cannot be made. Ensure that the server is running."
• "An unexpected internal error has occurred."

I was able to produce the text of these errors based on the occurrences within my platform, it is obvious that the text may be different if there is an issue of security and not with the data providers you use, in such cases the exceptions includes::

• "Unspecified error."
• "Either the user, Domain\User, does not have access to the Database Name database, or the database does not exist."
• "An existing connection was forcibly closed by the remote host."

So how it is possible to find or obtain the 'right' data provider or avoid such type of common errors, I feel it is worth covering from SQL Server 2000 version onwards where the Analysis Services has obtained much of importance for managing data warehouse based applications. There are various ways to resolve them provided you have identified the required  information.

Within SQL Server 2000 version OLE DB drivers usage has been obvious to connect to other data sources such as excel, oracle etc. in order to install the SQL Server Pivot table series look at this this link. But there is a difference when it comes to SQL Server 2005 Analysis Services, usage of ADOMD.NET (.net based services) has been introduced with Visual Studio versions and to download such drivers refer to this link, or for older versions of Visual Studio download ADOMD.NET 8.0 along with the hotfix here. Its worth referring the use the OLE DB (COM) Provider for Analysis Services 2005 with an additional pre-requisite of Core XML Services installation.

When you have the database and provider to connect the end-user API you need a connection string that will identify the language compatibility between these layers. IN such cases for both ADOMD and ADOMD.NET, the connection string parameters are listed here in the MSDN Library. If in case your Analysis Services database is on seperate machine and the application generates calls from the web server, so the usage of  Windows domain account is common when running OLAP Services. This account can then be granted access in Analysis Services. In ASP.NET, you can use impersonation to change the identity of the ASP.NET process, or in IIS6 or above change the identity of the application pool used for the web site. To secure such connections you can adopt the HTTP access to Analysis Services. This is more complicated than using Windows domains but lets you extend access outside of your local intranet. To end up the subject of connectivity issues I suggest the 2 articles on Microsoft about Configuring HTTP Access to SQL Server 2005 Analysis Services on Microsoft Windows XP & Configuring HTTP Access to SQL Server 2005 Analysis Services on Microsoft Windows Server 2003 type of configuration.