Re: Connection to SQL Server 2005 lost

Sorry I don't have another answer for you. I have not heard of or seen this particular issue before.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Glenn Handeland" <GlennHandeland@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@xxxxxxxxxxxxxxxx
Thank you for the suggestion.

We have not tried the native client, because the FAQ says:

Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
server?

A. Applications deployed before SQL Server 2005 was released can and should
continue to use MDAC.

Most likely it is a server configuration problem. Our program is used by
many clients, accessing the datebase from different computers/configurations,
and all of them experience this error message when conneting to a given SQL
Server 2005 Server. Some of our clients from other firms also have their own
SQL Server 2005 running, and they have successfully managed to connect to
their database using MDAC and never experience this error message.


"Andrew J. Kelly" wrote:

Have you tried using the SQL Native Client (SNAC) instead to see if that
makes a difference?
http://msdn2.microsoft.com/en-us/data/aa937733.aspx


--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Glenn Handeland" <Glenn Handeland@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@xxxxxxxxxxxxxxxx
> We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
> (Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly > for
> years, but after upgrading to SQL Server 2005, the database connection > is
> sometimes lost during larger operation involving open/close of several
> recordsets. The general error message says:
> “[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist or
> access
> denied". "Simpler" parts of the program involving just a recordset or > two
> always work fine. Any idea of what is going on here?



.

Relevant Pages

  • Re: DataSet.GetChanges() in RowChanged(DataRowAction.Add)
    ... have you considered SQL Express and use ... > I realize now that I didn't describe well how the client application is ... > Framework installed on the client machine, but not any SQL Server). ... > 20 tables in different relations with eachother in the database, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now successfully installed them. ... Access front end to a SQL database, Excel can be a front end, A word mail merge document could access a SQL database via ODBC. ... We are trying to install the client software. ... We understand that a Northwind training database is available for SQL Server. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now ... A word mail merge document could access a SQL database via ... We want to install to gain an understanding. ... Once we've managed to install the SQL Server Client we can start to ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: TDS vs. TCP
    ... I start capturing the network traffic between SQL ... Server and the client. ... I don't see any TDS packets but the communication between SQL ... stand-a-lone server and the client, ...
    (microsoft.public.sqlserver.clustering)
  • Re: DMX Query response time
    ... the prediction is done in client-side. ... In SQL 2005, all predictions are performed in the server. ... >>>> server are remoted to the client and cached into client memory until ...
    (microsoft.public.sqlserver.datamining)
Loading