REWARD: Fix our SQL Server connection for $150 (CAPA)

From: Rob Cote (rgcote@alum.mit.edu)
Date: 09/06/02


From: "Rob Cote" <rgcote@alum.mit.edu>
Date: Fri, 06 Sep 2002 16:37:45 GMT


We have wrestled with this problem long enough. If you are an expert at
connecting to SQL Server 2000 from an ASP.NET application, then I will pay
you $150 to make this work for our application. We will give you access to
our server machine via a VPN and allow you to debug it. If it takes you 5
minutes, you made great money. If it takes an hour, you've still made good
money.

We are very anxious to get this resolved. Please contact me by phone or
email ASAP (see info at the end of the message).

Here's the problem: We can connect to SQL Server 2000 just fine in our
development set up. We cannot do so in our production set up provided by the
client.

Here's a summary of the environments:

Development environment:
    Workstation is running Visual Studio .NET and Windows 2000 Professional
    Server is running SQL Server 2000 and Windows 2000 Server
    These two machines are connected on a simple LAN

Production environment:
    Single machine is running Visual Studio .NET, SQL Server 2000 and
Windows 2000 Server

The code below shows the connection string we are using for the development
environment and the connection string we are using for the production
environment. In the production environment, the connection will not work. It
gives back some generic error about the connection failing.

Here's what we are doing:

'***************************************************************************
*****
Imports System.Data
Imports System.Data.SqlClient

Public Class CAPADatabase

    ' DEVELOPMENT DESKTOP USE
    'Dim strDBConnectString As String = "server=CONSULTING\CONSULTING_SQL;"
& _
    ' "database=CAPASQL;" & _
    ' "user ID=DB_USER;" & _
    ' "pwd=db_user;"

    ' LIVE SYSTEM USE
    Dim strDBConnectString As String = "server=MCDMSPADMIN01\MCDMSPADMIN01;"
& _
                                       "database=CAPASQL;" & _
                                       "user ID=DB_USER;" & _
                                       "pwd=db_user;"

    Dim dbConnection As New SqlConnection(strDBConnectString)

    Public Sub Open()
        dbConnection.Open()
    End Sub

    Public Sub Close()
        dbConnection.Close()
    End Sub

End Class
'***************************************************************************
*****

- Rob Cote
  Director, Consulting Services
  Hands On Technology Transfer, Inc.
  (781) 272-4757
  robc@traininghott.com



Relevant Pages

  • Re: Third party access to SQL
    ... on in a controlled environment by my company. ... then why would the third party request sysadmin ... access to the production environment? ... SQL Server MVP ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Resets
    ... When we turn on connection pooling, it loads up pretty fast to throw the ... I tend to believe it has something to do with the connection pooling. ... Have you had a look at the SQL Server ... Have you tested the development environment with MaxUserPort=64534, ...
    (microsoft.public.sqlserver.connect)
  • Re: Error "SQL Server does not allow remote connections"
    ... The application could not connect to the sql server db. ... network is blocking the connection. ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 ... integratedSecurity, SqlConnection owningObject) +737554 ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Connection from remote computer to network SQL Server
    ... There is no firewall on the W2K machine acting as the SQL server. ... I tried making the SQL machine a "trusted" on the router. ... connection works. ... To find the IP address of your computer inside the network, ...
    (microsoft.public.access.adp.sqlserver)
  • ADO.net Orcas Samples Install Problem
    ... An error has occurred while establishing a connection to the server. ... When connecting to SQL Server 2005, this failure may be caused by the ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, ... or am I better off with a full SQL Server install. ...
    (microsoft.public.dotnet.framework.adonet)