Re: network error

Tech-Archive recommends: Fix windows errors by optimizing your registry



The database must be split with the front-end running on a workstation and
the back-end properly connected with ODBC to the back-end (SQL-Server). Make
sure that you have enough record locks and that your connection is good.
Occasionally, if a NIC card is beginning to fail, you will notice that it
will begin dropping packets after initially working fine. You may want to
set up a perfmon.exe trace to watch and record the network traffic.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

"Frank" <fhsmith7@xxxxxxxxxxxxx> wrote in message
news:_o3ah.16636$K9.6907@xxxxxxxxxxxxxxxxxxxxxxxxx
I have an application consisting of an Access 2002 database serving as the
front end, and a Microsoft SQL Server database holding the tables, as the
back end (SQL Server 2000, I believe). The application reads text files
out of a PC folder, processes the data, and posts the information to tables
in the SQL Server database.

The application runs fine for the fist x records, where x can be 100 to
several thousand, and then stops with the following error message:

Error: -2147467259 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL
Server does not exist or access denied.

This error only seems to happen when the application is running on a
network. We are using Windows NT Authentication for the network login ID
in the ODBC connection.

A search of the Microsoft Knoweldge Base found a couple of articles that
mentioned the error, but the conditions that Microsoft says are leading to
the error, don't seem to apply in our situation.

Any ideas?



.



Relevant Pages

  • Re: Strange Problems with ODBC connection to SQL Server
    ... When accessing Jet data, use DAO. ... This way you are not exposing connection information in clear ... >accesses an SQL Server 2000 repository via ODBC data source. ...
    (microsoft.public.data.odbc)
  • Re: Access and processor usage
    ... and you are using an ODBC connection, that would be your bottle neck. ... bottleneck - need to step up to Sql Server. ...
    (comp.databases.ms-access)
  • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()) er
    ... I understand that you encountered the ODBC error message on your ecommerce ... TCP/IP protocol to your SQL Server instance by calling conn.Open, ... SQL Server instance and see if there is a connection reset when this issue ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.connect)
  • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()
    ... remote connection. ... should I just check named pipes only or both TCP/IP and ... I understand that you encountered the ODBC error message on your ecommerce ... TCP/IP protocol to your SQL Server instance by calling conn.Open, ...
    (microsoft.public.sqlserver.connect)
  • Re: Using SQL Server Express on Shared PC
    ... you don't need to install SSMS or VS on the client system. ... using ODBC you're making the job of getting connected more difficult. ... ODBC requires either a REGISTERED DSN, a file-based DSN or a "DSN-less" connection. ... You also need to configure the Network-shared SQL Server service to permit access by whatever credentials you have chosen. ...
    (microsoft.public.sqlserver.connect)