Re: Strange Invalid Connection Error

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Keith Kratochvil (sqlguy.back2u_at_comcast.net)
Date: 03/10/04 

Date: Wed, 10 Mar 2004 07:59:56 -0600

You are correct, that is an error from Named Pipes. Good idea having them switch to TCP/IP.

Have you tried using the MDAC Component Checker to determine which version of ADO (ODBC) is loaded on the machines?
http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&DisplayLang=en

How does the MDAC version that they are running compare the the MDAC version on your system? 

-- 
Keith
"Neil Penn" <neil.penn@btinternet.com> wrote in message news:eYEGvhoBEHA.2768@tk2msftngp13.phx.gbl...
> SQL Server 2000
> Windows 2000
> 
> I would really appreciate it if someone could explain a strange error that
> appeared on a customer PC.
> 
> We have an application that loads data from an Access database into a SQL
> Server database.
> To start the application you have to "sign in" to the SQL Server database
> from the application.
> 
> The application has been working fine on lots of PCs, but a customer
> reported that with one particular install when they went to start the
> process for loading the data they got the following errors:
> 
> 2147418113 DBNMPNTW Invalid Connection
> 2147467259 Connection Failure
> 
> Now in order to logon to the application it is necessary to connect to the
> SQL Server database and the code for loading the data uses the same
> connection - so why was there suddenly this error?
> 
> Also they have a second application using the connection with no problems.
> 
> Once they installed the application on a second PC it worked fine.
> 
> I would really like to know why they had the problem with the application.
> Here are some more things to know:
> 
> 1. The application that had the problems uses ADO. The user logs on by
> specifying an ODBC connection, however the application actually turns this
> into a native OLEDB SQL Server connection.
> 
> 2. The second application that was running fine just uses ODBC - no ADO.
> 
> 3. They had tried restarting the PC, and re-running the application. The
> error occurred consistently.
> 
> 4. I know the first error is a named pipes error. I asked them to change the
> ODBC settings to TCP/IP but they still said they got an error. Unfortunately
> I do not yet have this second error.
> 
>

Relevant Pages

  • Re: Help Please Wit Error
    ... Occasionally I receive the error you are mentioning when the SQL Server ... I have had to completely remove the MDAC and re-install it as well ... see an example of the connection string you are using. ... Please install Microsoft Data Access Components ...
    (microsoft.public.dotnet.csharp.general)
  • Re: Any help here???
    ... System.Data.OleDb - connection to other Access Databases ... troubleshoot SQL Server connectivity issues - you should investigate the MDAC ... >>> could think of off hand for installing MDAC is for any old COM ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Help Please Wit Error
    ... > extracted from MDAC 2.8 RTF. ... >> Occasionally I receive the error you are mentioning when the SQL Server ... >> see an example of the connection string you are using. ... Please install Microsoft Data Access Components ...
    (microsoft.public.dotnet.csharp.general)
  • Re: Any help here???
    ... System.Data.OleDb - connection to other Access Databases ... troubleshoot SQL Server connectivity issues - you should investigate the MDAC ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Strange Invalid Connection Error
    ... > To start the application you have to "sign in" to the SQL Server database ... > 2147418113 DBNMPNTW Invalid Connection ... The second application that was running fine just uses ODBC - no ADO. ...
    (microsoft.public.sqlserver.programming)