percivalevans
asked on
Cube Deployment Error in Analysis Services MS SQL Server 2005
ISSUE: I cannot deploy my cube I created in an Analysis Services tutorial. See. http://msdn.microsoft.com/en-us/library/ms166576(v=SQL.90).aspx.. When I deploy my cube I get this error,
“Error 1 The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.”
FACTS ABOUT MY SETUP:
1. BI and SQL Sever 2005 is on a local XP computer
2. My instance is MSSQLSERVER (see SQL Server Configuration Manager)
3. My computer name is MARIO-81135DD02
4. When I connect to the SQL Server the server name is “MARIO-81135DD02”
and authentication is “Windows Authentication
MY ATTEMPTS:
1. Change project properties to several names for server
MARIO-81135DD02
MARIO-81135DD02/MSSQLSERVE R
MARIO-81135DD02\MSSQLSERVE R
2. Under Connection Manager I edit the string and test connection with computer name (MARIO-81135DD02) and localhost. No problem
3. Under Connection Manager I used Native OLE DB\SQL Server Native Client 10.0 and Native OLE DB\Microsoft OLE DP Provider for SQL Server. No problem
4. Under Impersonation Information I experimented with all scenarios (Use a specific user name and password to default) All give me the error as stated above
Images are attached
BIsettings.doc
“Error 1 The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.”
FACTS ABOUT MY SETUP:
1. BI and SQL Sever 2005 is on a local XP computer
2. My instance is MSSQLSERVER (see SQL Server Configuration Manager)
3. My computer name is MARIO-81135DD02
4. When I connect to the SQL Server the server name is “MARIO-81135DD02”
and authentication is “Windows Authentication
MY ATTEMPTS:
1. Change project properties to several names for server
MARIO-81135DD02
MARIO-81135DD02/MSSQLSERVE
MARIO-81135DD02\MSSQLSERVE
2. Under Connection Manager I edit the string and test connection with computer name (MARIO-81135DD02) and localhost. No problem
3. Under Connection Manager I used Native OLE DB\SQL Server Native Client 10.0 and Native OLE DB\Microsoft OLE DP Provider for SQL Server. No problem
4. Under Impersonation Information I experimented with all scenarios (Use a specific user name and password to default) All give me the error as stated above
Images are attached
BIsettings.doc
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
your welcome any time
ASKER
1. I wasn’t sure how to check for this other than doing what I did in number 2. I went to SQL management studio and attempted to login to Analysis Services under my computer name "Mario-81135dd02" Please NOTE: all modes of authentication were grayed out. See 2 for that error
2. I did get through. I got this error, "Cannot connect to MARIO-81135dd02" (which is my localhost) Additional information: A connection cannot be made. Ensure that the server is running. (Microsoft.Analysis.AdomdC
3. Yes, cube can be process normally
4. That is the name of the project. It was created by default in the tutorial. I did try changing it to AdventureWorksDW (which is the database I attempting to deploy). Still getting the same error message
Currently searching that error message on google. We are getting close I hope