Ask a Question related to ASP Database, Design and Development.
-
Wayne #1
Problem returning data with a stored procedure
I have an ASP calling a stored procedure to return a recordset. The stored
procedure quires
another server for part of the data being returned (using linked MS SQL 7
servers). The stored
procedure runs fine from with query analyzer, but I get this when calling
from within the
ASP page:
error 'ASP 0113'
Script timed out
If I comment out the lines in the stored procedure, it runs fine from within
ASP then. So I'm
thinking it must be some type of permission issue. Any ideas??
Thanks
Wayne Guest
-
Help - stored procedure not returning a recordset
I have an ASP page that calls a SQL Server stored proc that should return multiple recordsets, but it appears to be returning something else, or it... -
Stored Procedure not returning values.
There are two problems: 1. SQL Server returns the "x number of records affected" message that you see in Query Analyzer to the client as a... -
Stored Procedure Not Returning
I have a stored procedure that calls another stored procedure. The second stored procedure will run and update the correct data - it just never... -
Stored Procedure not returning the wanted resultset
My stored procedure is not returning the resultset I am expecting. The procedure is: CREATE PROCEDURE hms.getHMStest( @userid int, @userrole... -
Help with Stored Procedure returning recordset
Hi, Try to add set nocount on in the beginning of procedure. "Scott McDaniel" <junk@junk.com> wrote in message... -
John Beschler #2
Re: Problem returning data with a stored procedure
Have you made sure the the user your ASP pages are running
under has an account on the linked SQL server and that it
is able to authenticate to that server.
To test it: create a simple SP on the linked server and a
simple ASP page to call that ASP directly from the linked
server. If this works, I would think that the sp with the
linked query should work.
HTH,
John
The stored>-----Original Message-----
>I don't think it is timing out from the stored procedure.procedure into a VB>procedure
>runs in about 2 to 3 seconds. I can drop the storedI get a timeout>app and it runs fine. The ASP page still doesn't work andbelieve>error.
>
>I'll try increasing the timeout settings though....
>
>"John Beschler" <giles@geewhiz.com> wrote in message
>news:029a01c3681f$b4bc4ca0$a501280a@phx.gbl...>> Why would the message "script Timeout" lead yo toreturn>> it's a permissions issue?
>>
>> In any case, that error means that the web server was
>> waiting for the script (ASP) to finish running andThe>> it's results to the ASP dll. It did not do that in the
>> alloted time so the browser issued that error message.alloted>> quick, but not the best approach, is to extend theis>> time that scripts are allowed to run. The correct fix,(using>> to determine why your stored procedure takes so long to
>> run and then fix that.
>>
>> To extend the timeout for scripts you can either change
>> the setting in the web server or add the ScriptTimeout
>> Property of the Server object to your page.
>>
>> For example:
>> Server.ScriptTimeout = 240
>> set the timeout to 240 seconds.
>>
>> HTH,
>> John
>>
>>
>>
>>>> recordset. The stored>> >-----Original Message-----
>> >I have an ASP calling a stored procedure to return a>> >procedure quires
>> >another server for part of the data being returned>>> linked MS SQL 7>> this when calling>> >servers). The stored
>> >procedure runs fine from with query analyzer, but I get>> runs fine from within>> >from within the
>> >ASP page:
>> >
>> >error 'ASP 0113'
>> >Script timed out
>> >
>> >If I comment out the lines in the stored procedure, it>> ideas??>> >ASP then. So I'm
>> >thinking it must be some type of permission issue. Any>> >
>> >Thanks
>> >
>> >
>> >.
>> >
>
>.
>John Beschler Guest



Reply With Quote

