W2K SP4 / SQL, FAST ASP/SQL APP NOW ONLY WORKS ON SMALL AMOUNTS OF RETURN DATA.

[Grosch]

Good Evening All.

I upgraded to SP4. Immediately I noticed that my ASP
sql 2000 database application was only returning small
amounts of data. Larger amounts of data (50 records)
would time out.

I removed SP4 and went back to SP3. Still issues.
I re-applied SP3, still issues.
I updated to MDAC 2.8, still issues.
I reloaded the security database, still issues.

The bummer is that it is not broken, no errors are being
logged. Checked system, applications, sql, web logs...
Nothing. Page just times out. I view the source of the
page as it is being generated and it is ok, the process
just does not complete.

The processing time is not excessive.

Any help would be greately appreciated.

Thanks in advance.
Grosch

[Ken Schaefer]

What is "timing out"?

The ASP script -or- the SQL Server command?

Cheers
Ken

"Grosch" <grosch@javatown.com> wrote in message
news:05da01c380b5$bb632a20$a301280a@phx.gbl...
:
: Good Evening All.
:
: I upgraded to SP4. Immediately I noticed that my ASP
: sql 2000 database application was only returning small
: amounts of data. Larger amounts of data (50 records)
: would time out.
:
: I removed SP4 and went back to SP3. Still issues.
: I re-applied SP3, still issues.
: I updated to MDAC 2.8, still issues.
: I reloaded the security database, still issues.
:
: The bummer is that it is not broken, no errors are being
: logged. Checked system, applications, sql, web logs...
: Nothing. Page just times out. I view the source of the
: page as it is being generated and it is ok, the process
: just does not complete.
:
: The processing time is not excessive.
:
: Any help would be greately appreciated.
:
: Thanks in advance.
: Grosch

[Grosch]

Thanks for a rapid response.
Looks like the ASP script. If I look at the source
I see the partially completed output.

Please note that this was working 100% before the SP4
patch was installed and is still working 100% on the local
machine. I am only having problems with external internet
access. My local connection is broadband. I am able to
access other internet sites with out any problems.

>-----Original Message-----
>What is "timing out"?
>
>The ASP script -or- the SQL Server command?
>
>Cheers
>Ken
>
>"Grosch" <grosch@javatown.com> wrote in message
>news:05da01c380b5$bb632a20$a301280a@phx.gbl...
>:
>: Good Evening All.
>:
>: I upgraded to SP4. Immediately I noticed that my ASP
>: sql 2000 database application was only returning small
>: amounts of data. Larger amounts of data (50 records)
>: would time out.
>:
>: I removed SP4 and went back to SP3. Still issues.
>: I re-applied SP3, still issues.
>: I updated to MDAC 2.8, still issues.
>: I reloaded the security database, still issues.
>:
>: The bummer is that it is not broken, no errors are being
>: logged. Checked system, applications, sql, web logs...
>: Nothing. Page just times out. I view the source of the
>: page as it is being generated and it is ok, the process
>: just does not complete.
>:
>: The processing time is not excessive.
>:
>: Any help would be greately appreciated.
>:
>: Thanks in advance.
>: Grosch
>
>
>.
>

[Bob Barrows]

No, that's not how you determine where the timeout is occurring. You need to
look at the error message.

Bob Barrows

Grosch wrote:

> Thanks for a rapid response.
> Looks like the ASP script. If I look at the source
> I see the partially completed output.
>
> Please note that this was working 100% before the SP4
> patch was installed and is still working 100% on the local
> machine. I am only having problems with external internet
> access. My local connection is broadband. I am able to
> access other internet sites with out any problems.
>

>> -----Original Message-----
>> What is "timing out"?
>>
>> The ASP script -or- the SQL Server command?
>>
>> Cheers
>> Ken
>>
>> "Grosch" <grosch@javatown.com> wrote in message
>> news:05da01c380b5$bb632a20$a301280a@phx.gbl...

>>>
>>> Good Evening All.
>>>
>>> I upgraded to SP4. Immediately I noticed that my ASP
>>> sql 2000 database application was only returning small
>>> amounts of data. Larger amounts of data (50 records)
>>> would time out.
>>>
>>> I removed SP4 and went back to SP3. Still issues.
>>> I re-applied SP3, still issues.
>>> I updated to MDAC 2.8, still issues.
>>> I reloaded the security database, still issues.
>>>
>>> The bummer is that it is not broken, no errors are being
>>> logged. Checked system, applications, sql, web logs...
>>> Nothing. Page just times out. I view the source of the
>>> page as it is being generated and it is ok, the process
>>> just does not complete.
>>>
>>> The processing time is not excessive.
>>>
>>> Any help would be greately appreciated.
>>>
>>> Thanks in advance.
>>> Grosch

>>
>>
>> .

[Grosch]

There is is no error.
Not in the server logs, Not in the SQL ser ver logs
Not in the windows 2000 Application and System logs.

The time out is like a webpage time out where dns is bad.
In my case DNS works the database works on short querries.
It appears that on larger quierries > 20 rows the thing
hangs up.

>-----Original Message-----
>No, that's not how you determine where the timeout is

occurring. You need to

>look at the error message.
>
>Bob Barrows
>
>Grosch wrote:

>> Thanks for a rapid response.
>> Looks like the ASP script. If I look at the source
>> I see the partially completed output.
>>
>> Please note that this was working 100% before the SP4
>> patch was installed and is still working 100% on the

local

>> machine. I am only having problems with external

internet

>> access. My local connection is broadband. I am able to
>> access other internet sites with out any problems.
>>

>>> -----Original Message-----
>>> What is "timing out"?
>>>
>>> The ASP script -or- the SQL Server command?
>>>
>>> Cheers
>>> Ken
>>>
>>> "Grosch" <grosch@javatown.com> wrote in message
>>> news:05da01c380b5$bb632a20$a301280a@phx.gbl...
>>>>
>>>> Good Evening All.
>>>>
>>>> I upgraded to SP4. Immediately I noticed that my ASP
>>>> sql 2000 database application was only returning small
>>>> amounts of data. Larger amounts of data (50 records)
>>>> would time out.
>>>>
>>>> I removed SP4 and went back to SP3. Still issues.
>>>> I re-applied SP3, still issues.
>>>> I updated to MDAC 2.8, still issues.
>>>> I reloaded the security database, still issues.
>>>>
>>>> The bummer is that it is not broken, no errors are

being

>>>> logged. Checked system, applications, sql, web

logs...

>>>> Nothing. Page just times out. I view the source of

the

>>>> page as it is being generated and it is ok, the

process

>>>> just does not complete.
>>>>
>>>> The processing time is not excessive.
>>>>
>>>> Any help would be greately appreciated.
>>>>
>>>> Thanks in advance.
>>>> Grosch
>>>
>>>
>>> .

>
>
>.
>

[Bob Barrows]

Oh, you're not letting it go until it times out.

You really need to do some debugging to determine where the hangup is
occurring. Put some response.write's at various points in the server-side
code so you get some reporting about what is actually happening (you will
probably have to turn the Buffer off if you have it on). You need to
determine which line of code is causing the hangup (if it is a single line
of code, that is).

If it turns out that the query is taking that long, then you need to debug
and optimize the query, using Query Analyzer. You can get some help with
this over at m.p.sqlserver.programming.

HTH,
Bob Barrows

Grosch wrote:

> There is is no error.
> Not in the server logs, Not in the SQL ser ver logs
> Not in the windows 2000 Application and System logs.
>
> The time out is like a webpage time out where dns is bad.
> In my case DNS works the database works on short querries.
> It appears that on larger quierries > 20 rows the thing
> hangs up.
>

>> -----Original Message-----
>> No, that's not how you determine where the timeout is occurring. You
>> need to look at the error message.
>>
>> Bob Barrows
>>
>> Grosch wrote:

>>> Thanks for a rapid response.
>>> Looks like the ASP script. If I look at the source
>>> I see the partially completed output.
>>>
>>> Please note that this was working 100% before the SP4
>>> patch was installed and is still working 100% on the local
>>> machine. I am only having problems with external internet
>>> access. My local connection is broadband. I am able to
>>> access other internet sites with out any problems.
>>>
>>>> -----Original Message-----
>>>> What is "timing out"?
>>>>
>>>> The ASP script -or- the SQL Server command?
>>>>
>>>> Cheers
>>>> Ken
>>>>
>>>> "Grosch" <grosch@javatown.com> wrote in message
>>>> news:05da01c380b5$bb632a20$a301280a@phx.gbl...
>>>>>
>>>>> Good Evening All.
>>>>>
>>>>> I upgraded to SP4. Immediately I noticed that my ASP
>>>>> sql 2000 database application was only returning small
>>>>> amounts of data. Larger amounts of data (50 records)
>>>>> would time out.
>>>>>
>>>>> I removed SP4 and went back to SP3. Still issues.
>>>>> I re-applied SP3, still issues.
>>>>> I updated to MDAC 2.8, still issues.
>>>>> I reloaded the security database, still issues.
>>>>>
>>>>> The bummer is that it is not broken, no errors are being
>>>>> logged. Checked system, applications, sql, web logs...
>>>>> Nothing. Page just times out. I view the source of the
>>>>> page as it is being generated and it is ok, the process
>>>>> just does not complete.
>>>>>
>>>>> The processing time is not excessive.
>>>>>
>>>>> Any help would be greately appreciated.
>>>>>
>>>>> Thanks in advance.
>>>>> Grosch
>>>>
>>>>
>>>> .

>>
>>
>> .

[. Grosch]

Ouch. 3.5 hours on hold for MS support to find it was my local
development machine with SP4. The removal on the production server was
ok. I was so close to the problem that I didn't realize every thing
worked on the production server via PC-Any where.

Thanks to all for your input. It was the dreaded SQL/SP4 server problem
just on the client machine.



*** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
Don't just participate in USENET...get rewarded for it!