Re: Weird Stored Procedure Problem - stopping without any errormessage

Just a shot in the dark, but could the stored procedure be timing out? How
long does it take before the procedure stops running?


"Christian Peterek" <spam_den_chris@xxxxxx> wrote in message
news:du1ehb$9s2$1@xxxxxxxxxxxxxxxxxxxx
Hi NG,

Currently I am encountering a weird problem, which even the big google
could not fix.

I've got a stored procedure(SP), that calls two other stored procedures.
SP1 (which i call from the classic asp) calls first the SP2 and then the
SP3.
But for some reason, the SP3 just aborts it's work somewhere in a cursor
loop, which makes SP1 stop, too. No SP throws any error message.

The weird thing is, that if I call the SP1 from the MS Query Analyzer
(with the same Parameters as from the ASP script), it works as it
should. I scrolled through the Messages window, and there is no error
message, too. So I assume, that the SPs are correct.

I added a "debug print" to the SP1 and SP3, that just inserted lines
into a table. I added these lines to the both while loops in the SP3 and
every time I ran it from asp, the loops stopped at another position
(somewhere close to each other but still it was always another
position-count that was "printed" to the table), but the parameters, and
the work the SP had to perform did not change.

As I multiplied the debug print ( had the SP3 to write 6 times per loop
to the log table) the SP3 aborted even earlier, when called from asp.
But not from the Query Analyzer.

*I even tried different ways to use the ADODB.Connection object, but the
effect was always the same.
*I can rule out that the problem is connected to authentication
difficulties or something like that.
*I tried to call the SP1 with and without the transactions.
*I'm sure that the SPs are all working and correct, throwing no errors.
*Running the SP1 from the Query Analyzer takes about 1 second. So its
not a Timeout problem.
*Calling SP3 from ASP alone works.

So are the questions:
* Is there any Query / Statement limit?
* Can I do anything to solve the problem?
* Any other Ideas?

Thanks for your help,

Chris


X-POST:microsoft.public.sqlserver.programming
X-POST:microsoft.public.scripting.vbscript
X-POST:microsoft.public.inetserver.asp.db
FOLLOWUP-TO:microsoft.public.inetserver.asp.db


.

Relevant Pages

  • PROBLEM SOLVED - Weird Stored Procedure Problem - stopping without any errormessage
    ... But for some reason, the SP3 just aborts it's work somewhere in a cursor loop, which makes SP1 stop, too. ... The weird thing is, that if I call the SP1 from the MS Query Analyzer (with the same Parameters as from the ASP script), it works as it should. ...
    (microsoft.public.inetserver.asp.db)
  • SOLVED Weird Stored Procedure Problem - stopping without any errormessage
    ... But for some reason, the SP3 just aborts it's work somewhere in a cursor loop, which makes SP1 stop, too. ... The weird thing is, that if I call the SP1 from the MS Query Analyzer (with the same Parameters as from the ASP script), it works as it should. ...
    (microsoft.public.inetserver.asp.db)
  • Re: Weird Stored Procedure Problem - stopping without any errormessage
    ... Run SQL Server Profiler and see what is going on while you call the SP1 ... the SP3 just aborts it's work somewhere in a cursor ... that if I call the SP1 from the MS Query Analyzer ... (with the same Parameters as from the ASP script), ...
    (microsoft.public.inetserver.asp.db)
  • Re: XP Pro (Gold?) and SP3
    ... The semantics is that it is possible to install sp3 on a system with sp1 or sp2; ... Windows XP SP3 will be available through Windows Update and the Microsoft ...
    (microsoft.public.windowsxp.general)
  • Re: Share point Services ASP.NET error
    ... That must have been a change in functionality that SP3 provides that I missed. ... generally everything is under ASP 1.1. ... pools, so two versions of the framework do not try and load in one ... all our SharePoint portals into their own pools; ...
    (microsoft.public.sharepoint.portalserver)
Loading