Posted by AlterEgo on 02/23/07 00:07

central_scrutinizer,

Does the ASP page hang, timeout or just return with no results? If it hangs
or times out, this may be happening:

1. The command is executed from the ASP page.
2. SQL Server needs to allocate more disk space (data or log) and performs
an autogrow of a large amount of disk space. This could take an extended
period of time.
3. The user cancels the ASP page or the page times out.
4. SQL Server cancels the transaction and also cancels the need for
additional disk space.
5. If steps 1-4 are repeated, you get the same result.
6. A user runs the stored procedure in QA allowing it to finish.
7. SQL Server allocates the addional space.
8. The ASP page now runs fine because the space has been allocated (until
the next time the database needs to allocate more space).

-- Bill

1. We would run the stored
"central_scrutinizer" <cbellur@hotmail.com> wrote in message
news:1172185833.914945.318670@m58g2000cwm.googlegroups.com...
>I have an ASP that has been working fine for several months, but it
> suddenly broke. I wonder if windows update has installed some security
> patch that is causing it.
>
> The problem is that I am calling a stored procedure via an ASP
> (classic, not .NET) , but nothing happens. The procedure doesn't work,
> and I don't get any error messages.
>
> I've tried dropping and re-creating the user and permissions, to no
> avail. If it was a permissions problem, there would be an error
> message. I trace the calls in Profiler, and it has no complaints. The
> database is getting the stored proc call.
>
> I finally got it to work again, but this is not a viable solution for
> our production environment:
>
> 1. response.write the SQL call to the stored procedure from the ASP
> and copy the text to the clipboard.
> 2. log in to QueryAnalyzer using the same user as used by the ASP.
> 3. paste and run the SQL call to the stored proc in query analyzer.
>
> After I have done this, it not only works in Query Analyzer, but then
> the ASP works too. It continues to work, even after I reboot the
> machine. This is truly bizzare and has us stumped. My hunch is that
> windows update installed something that has created this issue, but I
> have not been able to track it down.
>

[Back to original message]