Comments on: Enable Remote Connection on SQL Server 2008 Express

By: terirog

terirog — Thu, 25 Feb 2010 22:53:15 +0000

Thanks! Clear and very helpful.

By: PBC

PBC — Wed, 24 Feb 2010 19:29:11 +0000

Very good explanation. I am still in need of help. At Step 4, the following error message appears:

“The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.”

Any advice?

Thanks …

By: Sinbad1

Sinbad1 — Tue, 23 Feb 2010 03:40:50 +0000

I can’t thank you enough !
Excellent walkthrough .

By: JVillamil

JVillamil — Thu, 18 Feb 2010 18:41:52 +0000

mhmhmh, you should configurate the IIS to run the ReportServer to the port 80

By: dilip

dilip — Thu, 18 Feb 2010 08:12:12 +0000

http://localhost:8080/reportserver but i want to use only http://localhost/reportserver but it not connect because port number require but how can connect without port number.

By: linglom

linglom — Thu, 11 Feb 2010 03:34:43 +0000

Hi, Gautam Could you share what registry that you changed? About your problem (error code 18456), you should look into the SQL Server's log which is located in Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG and ERRORLOG.n files. You will see more details on the error message. The example error message should looks similar to this: 2006-02-27 00:02:00.34 Logon Error: 18456, Severity: 14, State: 8 You see that there is state number which tell the detail of the error message. Here are some common error states and their descriptions: 2, 5 -> Invalid userid 6 -> Attempt to use a Windows login name with SQL Authentication 7 -> Login disabled and password mismatch 8 -> Password mismatch 9 -> Invalid password 11,12 -> Valid login but server access failure 13 -> SQL Server service paused 18 -> Change password required Reference: Understanding "login failed" (Error 18456) error messages in SQL Server 2005

Hi, Daniel Check your SQL Server's name to see if it is correctly. This wizard always generates the server name as [MachineName]. But if you are using SQL Server express, it should be [MachineName]\SQLEXPRESS.

By: Gautam

Gautam — Mon, 08 Feb 2010 16:09:00 +0000

Hi Mr. JVillamil & all, The connection error of sql server authentication is solved by making a change in the registry.By default the windows server 2008 R2 having registry setting for the windows authentication by changing the value of registry key I could solve the problem.

By: Discount Code

Discount Code — Mon, 08 Feb 2010 15:47:27 +0000

Thanks a lot.. It was exactly what I was looking for. Much appreciated..

By: JVillamil

JVillamil — Mon, 08 Feb 2010 06:51:27 +0000

Daniel: why no connect by TCP / IP ???

By: Daniel

Daniel — Sun, 07 Feb 2010 13:34:51 +0000

This was really helpful but unfortunately I still can’t get a connection. I’m trying to use the “ASP.net SQL Server Setup Wizard”. Every time I try to get a list of the databases in SQL Server I get the remote connections error:

“Failed to query a list of database names from the SQL server. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verifty that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)”.