Connection Error

[reykentj]

Environment: Op Sys 2003 server; Sql Server 2005 with update; Visual Studio; Multiple VB functions and subroutines as stored procedures.This subroutine needs to use a connection string to enable MARS. It does not have the SQL Attributes. They seem to prohibit byref class instantiations being returned. Dim connectionString As String = _ "server=(local);" & _ "Trusted_Connection=yes;" & _ "database=Frontier_equipment;" & _ "MultipleActiveResultSets=true;" RecordTypeConnection = New SqlConnection() RecordTypeConnection.ConnectionString = connectionString RecordTypeConnection.Open() Error Numr 5 Error Desc 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) rkj

[kubben]

Are you sure your sql server name is correct? Are you sure the sql server allows trusted connection. Can you ping the sql server name from where you are trying to run this app? Is there an instance of a sql server you are trying to connect to? You have to put that into your server name. Sometimes you have to set a port number for sql server instances. Anyway, a few thoughts, I hope that helps. Ben

[reykentj]

I had read that Stored procedures running within the SQL Server could use the local option for server name. Placing the combined servername\sqlservername as the servername worked.!! Thank you.:):) rkj

[Dave Kreskowiak]

Along with what kubben said, your connection string says that it expects the database server to be on the same machine as the one where your code is running. I hope this is true, otherwise you'll have to change your connection string. Does your SQL Server instance have Named Pipes enabled?

Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
     2006, 2007

[reykentj]

The stored procedures are on the same machine as the server. Replacing server(local) with servername\server made the whole thing work.:) rkj

[Dave Kreskowiak]

If it's a stored procedure, you can try "context connection = true" for the connection string to use the connection that the SP is executing under. But, as you can read here[^], this is not always the best idea.

Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
     2006, 2007

[reykentj]

I was using that but I needed the MARS capability.:) rkj