Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!
|||thanks for posting this! was having the same problems but now it worked in a few seconds!
|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.
|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!|||thanks for posting this! was having the same problems but now it worked in a few seconds!|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!
|||thanks for posting this! was having the same problems but now it worked in a few seconds!
|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.
|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

|||Scripting as new Table with insert data isn't supported in SQL Server. I found a C# program that does this; http://www.eggheadcafe.com/articles/20040913.asp

Just needed the server name. Worked beautifully.

Thank you Thank you.

Fred

sql

Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!|||thanks for posting this! was having the same problems but now it worked in a few seconds!|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

Establishing connection to SQL 2005 Server Express

Using localhost (127.0.0.1) an error occurred while establishing a connection to SQL Server 2005.

Error message - An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider)

Error Number: 10061
Event Source: MSSQLServer

Message text: Cannot connect to 127.0.0.1.

Any ideas?

I have just tried this idea and it worked ! ! !

- Removed SQL Native Client through Add or Remove programmes

- Reinstalled SQLServer 2005 Express

- Used .\sqlexpress as server name

- Clicked Connect

and I got connected to the server ! ! !

Thanks.

|||I was having trouble connecting to the sql server from visual studio.
Then I realized that "server name" actually means "sql server name".
I'll consider it a bug.

The drop down list contains server names, such as the name of my local computer as well as other servers on my LAN. Since the list contains server names, and the label says server name, you'd think they mean server name.... but they don't; they mean sql server name.

It's easiest to use ".\" as the server name for localhost, and "sqlexpress" as the name of the sql server instance. So for server name, enter ".\sqlexpress".

By the way, visual studio 2005 is great. What's gotten into microsoft? Ever since windows xp, they seem to be getting their act together... taking time to make things right (e.g. delaying vista, adding visual queues for docking so you don't have to guess where things are gonna land when you drop them). Good job!
|||thanks for posting this! was having the same problems but now it worked in a few seconds!
|||Thank you! Thank You! This is most helpfull. I won't say how much time I spent trying to reconnect to my server after upgrading SQL Express to SP2.

Great formum. Hopefully I'll know enough to give back some day.
|||

Another greatful user of your post. Allow me to add that my database name ended up being msdb

I had been trying to use Northwind

Error: Server Error in '/ReportServer' Application.

I get the following error when going to http://localhost/reportserver, I did try what it recommended but it did't work.

Error:

Failed to access IIS metabase.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase.
The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC). For information on modifying metabase permissions, please see http://support.microsoft.com/?kbid=267904.
Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HostingEnvironmentException: Failed to access IIS metabase.] System.Web.Configuration.MetabaseServerConfig.MapPathCaching(String siteID, VirtualPath path) +3492186 System.Web.Configuration.MetabaseServerConfig.System.Web.Configuration.IConfigMapPath.MapPath(String siteID, VirtualPath vpath) +9 System.Web.Hosting.HostingEnvironment.MapPathActual(VirtualPath virtualPath, Boolean permitNull) +163 System.Web.CachedPathData.GetConfigPathData(String configPath) +382 System.Web.CachedPathData.GetConfigPathData(String configPath) +243 System.Web.CachedPathData.GetApplicationPathData() +68 System.Web.CachedPathData.GetVirtualPathData(VirtualPath virtualPath, Boolean permitPathsOutsideApp) +3385695 System.Web.Configuration.RuntimeConfig.GetLKGRuntimeConfig(VirtualPath path) +189

---

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42Can you access other asp.net applications on the same website, and running under the same app pool (if you are on IIS6) or the ASP.NET process account (if you are on IIS5.1)?|||

Not sure. I am trying to set up the report server so that I can start creating SSRS and report builder stuff off a 1 box before I create live on the server using the backend DB tables of our internal tools.

I am on communicator if you can chat for a few...this has had me going crazy for a few days.

Also ASPNET_REGIIS.exe is not recognized.