Connection issues

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

We have an application server which serves as an access point to a
database. Each user connected to the server has their own connection
to the database. Pooling is turned on, but since everyone has a unique
Workstation ID, they share with only themselves.

Lately, we have seen many strange errors come across. It looks a
stored procedure we call is returning null(No, not DBNull, but actual
dotnet null). We can see what the user is feeding as input into the
stored procedure and in any normal test, we get back the proper
information. At any given time that one user is getting this error, 49
other users can make the same call and get back proper information.
The database is Sql Server 2000 SP3a.

Has anyone seen this before? Does anyone know how to fix it/what is
wrong?

Currently, our fix(not very good), is if a user calls up and says they
have a problem, we kill their connection through enterprise manager.
They retry, get a 'General network error.' On the next try, they are
off and running with no problems. This would lead me to believe there
is an issue with the connection. We are using both SqlDataAdapter and
SqlCommands to execute the stored procedure.

Any help on this issue or debugging procedures to find more information
would be greatly appreciated. I have run a profile on the commands
being executed database side, but this doesn't seem to help.

Steve

.

Relevant Pages

  • Re: ADO Connection Timeout
    ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)
  • Complicated Connection Problems bewteen ADP and SQL Server
    ... This database ... expertise for getting the user workstations talking to the SQL Server. ... connection would fail and the adp wouldn't be able to talk to the server. ... might be in my ADO connection string. ...
    (microsoft.public.access.adp.sqlserver)
  • Complicated Connection Problem between ADP and SQL Server
    ... This database ... expertise for getting the user workstations talking to the SQL Server. ... connection would fail and the adp wouldn't be able to talk to the server. ... might be in my ADO connection string. ...
    (microsoft.public.sqlserver.connect)
  • Re: ADO Connection Timeout
    ... so what happens when a connection failure forces one station to revert ... to a local database? ... Further, you *will* have contention issues, Jet does not support record ... to the central server, but you are willing to live with periods where it ...
    (microsoft.public.data.ado)
  • Re: ADO Connection Timeout
    ... When the first test is run, the results are stored in the central database. ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)