HELP! Err whn changing Stored Proc used

We had to make a change to a stored procedure and wanted to test out the
change. So made a test version of the sp (all done correctly and verified by
dba). I changed the name of the stored proc used in my report to be the test
version. I could run the sp fine from the data tab and it picked up the
change and displayed the correct results. When I wanted to run it from the
Preview tab ... different story. I tried EVERYTHING and couldnt get it to
not throw an error (SQL0444N Routine "*S_UPTIME" (specification name
"SQL050707202207020") is implemented with code in library or path"
...RES_UPTIME", function "DANTEST.SP_RPT_RES_UPTIME" which cannot be
accessed. Reason code: "4". SQLSTATE=42724. Permissions on the sp are
correct, grant was run, everything is correct from DBA standpoint. IN FACT
... if I create a NEW report and use that stored proc then I dont get an
error. SO ... where to look for the problem. I need to use the new stored
procedure in an existing report and I CANNOT REWRITE that just to use a new
stored procedure. Something is being remembered in the project I need to
make the change in and I dont know where to look. Thanks for any help.I had an issue similar to this and it seems to be that even though you can
run the dataset on the data tab after changing the stored procedure using
the ! it doesn't update the field list. If you look in the config for the
dataset after running it you still see the field list from the old SP, I
tried using the refresh fields button, rerunning the new SP several times
but the field list wouldn't update.
As a work around I just nuked the dataset and recreated a new one with the
same name and the new SP and then the new field list was available.
Hope this helps.
Peace,
Dan
"MJ Taft" <MJTaft@.discussions.microsoft.com> wrote in message
news:63BCFB5C-8196-4622-8D3F-5A336CE07A96@.microsoft.com...
> We had to make a change to a stored procedure and wanted to test out the
> change. So made a test version of the sp (all done correctly and verified
> by
> dba). I changed the name of the stored proc used in my report to be the
> test
> version. I could run the sp fine from the data tab and it picked up the
> change and displayed the correct results. When I wanted to run it from
> the
> Preview tab ... different story. I tried EVERYTHING and couldnt get it to
> not throw an error (SQL0444N Routine "*S_UPTIME" (specification name
> "SQL050707202207020") is implemented with code in library or path"
> ...RES_UPTIME", function "DANTEST.SP_RPT_RES_UPTIME" which cannot be
> accessed. Reason code: "4". SQLSTATE=42724. Permissions on the sp are
> correct, grant was run, everything is correct from DBA standpoint. IN
> FACT
> ... if I create a NEW report and use that stored proc then I dont get an
> error. SO ... where to look for the problem. I need to use the new
> stored
> procedure in an existing report and I CANNOT REWRITE that just to use a
> new
> stored procedure. Something is being remembered in the project I need to
> make the change in and I dont know where to look. Thanks for any help.|||Dan,
I have had that issue before and dealt with it as you mention here. This
issue is different. It doesnt have to do with the fields list as the fields
as there - that isnt the problem. I dont understand the different behavior
between running the stored proc using the ! and running the report against it
using the preview. The report didnt change from before ...just the stored
proc ... shouldnt be such a problem!
"Dan Christjohn" wrote:
> I had an issue similar to this and it seems to be that even though you can
> run the dataset on the data tab after changing the stored procedure using
> the ! it doesn't update the field list. If you look in the config for the
> dataset after running it you still see the field list from the old SP, I
> tried using the refresh fields button, rerunning the new SP several times
> but the field list wouldn't update.
> As a work around I just nuked the dataset and recreated a new one with the
> same name and the new SP and then the new field list was available.
> Hope this helps.
> Peace,
> Dan
> "MJ Taft" <MJTaft@.discussions.microsoft.com> wrote in message
> news:63BCFB5C-8196-4622-8D3F-5A336CE07A96@.microsoft.com...
> > We had to make a change to a stored procedure and wanted to test out the
> > change. So made a test version of the sp (all done correctly and verified
> > by
> > dba). I changed the name of the stored proc used in my report to be the
> > test
> > version. I could run the sp fine from the data tab and it picked up the
> > change and displayed the correct results. When I wanted to run it from
> > the
> > Preview tab ... different story. I tried EVERYTHING and couldnt get it to
> > not throw an error (SQL0444N Routine "*S_UPTIME" (specification name
> > "SQL050707202207020") is implemented with code in library or path"
> > ...RES_UPTIME", function "DANTEST.SP_RPT_RES_UPTIME" which cannot be
> > accessed. Reason code: "4". SQLSTATE=42724. Permissions on the sp are
> > correct, grant was run, everything is correct from DBA standpoint. IN
> > FACT
> > ... if I create a NEW report and use that stored proc then I dont get an
> > error. SO ... where to look for the problem. I need to use the new
> > stored
> > procedure in an existing report and I CANNOT REWRITE that just to use a
> > new
> > stored procedure. Something is being remembered in the project I need to
> > make the change in and I dont know where to look. Thanks for any help.
>
>