[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

SQL Server 2008 Analysis Services Deployment Connectivity problem

Posted on 2012-09-17
3
Medium Priority
?
602 Views
Last Modified: 2016-02-18
I've created my first Cube based on the ContosoRetailDW.  Builds fine.  When I try to Deploy it I get  "Error      4      The project could not be deployed to the 'WIN-3VTVH3GMKVH\MSSQLSERVER' server because of the following connectivity problems :  The 'MSSQLSERVER' instance was not found on the 'WIN-3VTVH3GMKVH' server..."

I'm running SQL Server 2008 R2 on Windows 2008 with all the latest updates.  All servers are within a single VMware machine in my lab environment (except for the DC on a separate VMware machine).

I've tried everything I could understand from a Google search including:
- verifying that the instance of SQL Server Analysis Services and SQL Server Browser are Started
- trying different variations of the Target Server Property for my SSAS Project.

When I try to connect to the WIN-3VTVH3GMKVH\MSSQLSERVER instance of Analysis Services using Mgt Studio it only gives me the option to connect to WIN-3VTVH3GMKVH which surprises me.  Seems like I should see the MSSQLSERVER instance.

I need some help unraveling this.  Thanks!
0
Comment
Question by:daldenwilliams
  • 2
3 Comments
 
LVL 37

Accepted Solution

by:
ValentinoV earned 1600 total points
ID: 38408506
MSSQLSERVER is the default instance, you don't need to mention it.  So when you connect to WIN-3VTVH3GMKVH, you're actually connecting to WIN-3VTVH3GMKVH\MSSQLSERVER.
0
 

Author Closing Comment

by:daldenwilliams
ID: 38411331
Thanks, Valentino.  This is exactly the type of silly question I have the most trouble solving on my own:  so fundamental that no one else would make the mistake and have to ask about it.  The complex problems are often easier to research.
0
 
LVL 37

Expert Comment

by:ValentinoV
ID: 38412522
Glad I could help :)

I have to say though that what you were trying to do is normal.  It is actually illogical that it refuses to connect while specifying the name of the default instance.  Even though it's the default, it shouldn't mean that you can't specify it, right? Oh well, I guess that's one of the "features" we'll have to live with...
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After restoring a Microsoft SQL Server database (.bak) from backup or attaching .mdf file, you may run into "Error '15023' User or role already exists in the current database" when you use the "User Mapping" SQL Management Studio functionality to al…
SQL Server engine let you use a Windows account or a SQL Server account to connect to a SQL Server instance. This can be configured immediatly during the SQL Server installation or after in the Server Authentication section in the Server properties …
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…

873 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question