Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I use SQL Server 2012 and SSAS Tabular Mode (My Instance Name Is MSSQLSERVER2012T)

Then I download AdventureWorks Tabular Model SQL Server 2012 From This link

I open it with Visual Studio 2010 and configure my Instance Name like this picture :

enter image description here

enter image description here

When I deploy my project I have This picture :

enter image description here

But after one minute I get this error :

enter image description here

And when I click on Details Of Error I get this message :

enter image description here

OLE DB or ODBC error: Login timeout expired; HYT00; 
A network-related or instance-specific error has occurred while 
establishing a connection to SQL Server. Server is not found or not accessible. 
Check if instance name is correct and if SQL Server is configured to allow 
remote connections. For more information see SQL Server Books Online.; 08001; 
Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001.

A connection could not be made to the data source with 
the DataSourceID of 'a16b8d9d-3811-4be1-91e7-a9d0a2df4d38', 
Name of 'SqlServer localhost'.

enter image description here


enter image description here

But it not work for me???

In my SSAS one Database was created like this picture :

enter image description here

share|improve this question

migrated from Jan 28 '14 at 11:15

This question came from our site for professional and enthusiast programmers.

1) The error message is talking about Named Pipes, not TCP, and 2) Why are you fiddling with your SQL Server Express's network settings when elsewhere you seem to be talking to the 2012 Developer Edition? – Damien_The_Unbeliever Jan 28 '14 at 7:46
Moreover, the error indicates it attempted to connect to LOCALHOST, not a named instance... (local)\mssqlserver2012t .. as described in your first screenshot – drewlander Jan 28 '14 at 8:01
@Damien_The_Unbeliever : How I Can fix my problem? How I can fix Named Pipes?! what is my problem? – Ardalan Shahgholi Jan 28 '14 at 10:40
@drewlander : After fix my instance name(.\MSSQLServer2012T) , one database was created in my SSAS (see last pic.) – Ardalan Shahgholi Jan 28 '14 at 10:42
@Damien_The_Unbeliever Generally, the "Named Pipes" reference in this error is a red herring. Named Pipes is just the last of the three protocols (Memory, TCP, Named Pipes) that is checked for a match between client and server, so it is always the protocol that is used in the error message. If the OP wants the SQL Server to support TCP (and this is what MS recommends), then they likely need to change the client configuration settings also (the client and server settings are separate, even on the same box). Also, there are 32bit and 64bit versions of each. – RBarryYoung Jan 28 '14 at 16:39

Your named Pipes connections are disabled, try fixing thisIn he SQL Server Configuration Manager

share|improve this answer
Why do I have the feeling that @Damien is right and you both are looking at the wrong instance? Shouldn't that 2012 named instance be used in this process? – Marian Jan 28 '14 at 17:20
I think you are correct. Port number 1433 is also unusual for a named instance. – Twinkles Jan 29 '14 at 8:07

protected by Community Jan 13 '15 at 11:59

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.