April 10, 2007 at 1:31 pm
Hello everyone,
Weird problem that we have encountered by installing a new SQL Server 2000 running on Windows Server 2003.
A little history of our configuration: previous machine was NT 4.0 SP6 with SQL Server 2000 SP3a installed. We developed, tested and distributed our Access .ADP 3 years ago with no connection problems of any kind since that time.
Our hardware maintenance has run out on some old Compaq ProLiant servers and we have replaced the SQL box with a new Dell 2900 PowerEdge server running Windows 2003 Server Standard. As of late, we are having random disconnects on the client side with Access putting up a "Connection Failure" dialog box even when the user is actively entering records into the system. Have any of you ever encountered this situation? We have disabled all TCP offloading engine technology on the machine thinking this was causing a problem with SQL Server as well as changing network cards to a whole different brand. We've pretty much ruled out the physical network at this point because we have changed cables and moved to another port on a different switch to no avail.
Is there some timeout setting or connection pooling setting that I am unaware of at the SQL Server level that has a problem interacting with Windows Server 2003? If so, was this not available in NT 4.0? I have checked and double checked all of the server settings between the old machine and the new and they are identical.
There are no errors in any of the SQL or Windows log files on either the client or the server when a user is disconnected. HELP!
Thanks for any insight Pat and Jim
April 11, 2007 at 7:58 am
My only connection issues with ADP's was this issue http://support.microsoft.com/kb/843248/en-us .
April 12, 2007 at 8:42 am
Hi
My name is Frank and I am getting the same scenario (almost exactly) but I am using access 2002 front and sql server 2005 express back end. That incident actually happened to me while I was entering data in a virtually empty database and the front end app and sql server were on the same machine- It is also happening to client users. Its seems that at random, you will be entering data and then all of a sudden the connection dies- I to have rule out any connection pooling configs. I did read that the connection pooling may be stressed and the pool of connections are 'Leaking'. This might be due to a bad cable or connection, but thats all I have found out.
Any info would be greatly appreciated.
Thanks
Frank
April 12, 2007 at 2:51 pm
I have had unexplained problems with an MS Access 2002 that were fixed by upgrading the database to Access 2003. If that is an option, I would recommend that.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply