You might try asking on a news group related to what ever language you wrote

"Kurt Heunis" <KurtHeunis@discussions.microsoft.com> wrote in message
news:8FEC2813-EE22-4175-9695-A46984F8CCE8@microsoft.com...
> Hi Andrew,
>
> Thanks for your response. Do you perhaps have a URL that I can research to
> help me change my web service?
>
> Kurt
>
> "Andrew J. Kelly" wrote:
>
>> Most Network IO waits are caused by the client (who ever is actually
>> talking
>> to SQL Server and requesting the rows) not being able to handle the rows
>> returned fast enough. In this case it sounds like the web service gets
>> hung
>> in the middle of processing the rows being returned. If you don't have a
>> pool of web services then all the other requests to the service are
>> affected.
>>
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Kurt Heunis" <KurtHeunis@discussions.microsoft.com> wrote in message
>> news:1A480DAB-82E7-40EC-A1A2-7C8E7DE413ED@microsoft.com...
>> > We have a .NET web service running on one of our servers connecting all
>> > our
>> > application users to a SQL Server 2000 database with service pack 4.
>> > Every
>> > now and then we experince a NETWORKIO wait type which then causes all
>> > our
>> > application users to receive a "Object reference not set to an instance
>> > of
>> > an
>> > object" error. The only way to resolve this issue is to kill the
>> > process
>> > ID.
>> > Is there something else we should be looking at?
>>
>>
>>