SQL - Sql Server 2008 R2 ( Provider Named Pipes Provider, error:40- Could not open a connection to SQL Server)

By -
Today I have installed SQL server 2008 R2 express edition to my local machine but when I tried to login to the server got the below error message.


Fig 0.1


















I did install express edition some years back and was successful at that time and not remembering such issue came up at that time.

I tried below steps but still was not successful.

             - Enabled TCP\IP port
             - Added exception for SQL server and browser in windows firewall
             - double checked the server is running or not

But I was not lucky enough to get into the server.

Ignoring small things in life will cost you more some time as here in this scenario I have forgot to give the server name and the instance together before hitting the login button.

I am able to login to the express edition when I have given the server name as .\SQLEXPRESS.  Catch here is server will not listen if you give it as only dot(.) or [local host].

Comments

  1. RajeshOctober 16, 2013 at 1:55 AM

    Can you let me know how many instance you have in your machine.. Is it installed as Named instance?? This issue usually will come only if you install named instance..Other wise (.) or localhost or Machine IP will do.

    ReplyDelete
  2. Jithesh K BalanOctober 17, 2013 at 11:05 AM

    There is only one instance. Yes you are right, this error comes only if it is named instance and by default SQL express edition installed as Named Instance.

    ReplyDelete
    Replies
    1. RajeshOctober 19, 2013 at 3:27 AM

      Can you check the port number of this instance? Change to 1433 if it is not the same and try with localhost. I'm yet to install express edition and check to see this issue..

      Delete

Post a Comment

Popular posts from this blog

Microsoft BI Implementation - Cube back up and restore using XMLA command

By -
Image
Current BI implementation require to deploy the cube in multiple location to make it available  locally in each location to improve the performance. Cube development happening in one location say X but since the company is having presence in around the world and so business users sits in different locations X, Y and Z. Internet connectivity between X, Y and Z are not good and accessing the cube deployed in X from Y and Z is very slow and it impact the end user productivity. To overcome this issue, cube has to be deployed in Y and Z locally and upload the connection in their local SharePoint as mentioned below.  Fig 1 Now let see how we can automate all these process from taking back up of the cube database to restore it in each location. Follow the below mentioned steps to automate back up and restore of cube database. - select the back up option by right click on the cube database to be backed up and generate the XMLA script after providing necessary proper
Read more

Databricks - incorrect header check

By -
This post I would like to show you how we can fix the problem of " Incorrect header check " received while fetching the data from hive table. Actual message " SparkException: Job aborted due to stage failure: Task 0 in stage 63.0 failed 4 times, most recent failure: Lost task 0.3 in stage 63.0 (TID 3506, 10.1.1.7, executor 28): java.io.IOException: incorrect header check.   at org.apache.hadoop.io.compress.zlib.ZlibDecompressor.inflateBytesDirect(Native Method)     at org.apache.hadoop.io.compress.zlib.ZlibDecompressor.decompress(ZlibDecompressor.java:221)     at org.apache.hadoop.io.compress.DecompressorStream.decompress(DecompressorStream.java:82)     at org.apache.hadoop.io.compress.DecompressorStream.read(DecompressorStream.java:76)     at java.io.InputStream.read(InputStream.java:101) " To better understand the scenario, let me explain how the data got loaded in the hive table. we are storing the data from source systems to RAW layer. H
Read more