Googling the Error number can often lead to the answer. Msg 50000 is a
custom error message meaning it is likely coming from a RAISERROR statement
inside the procedure.
If that doesn't lead to a solution, my troubleshooting escalation scheme is
usually:
1. Re-compile the procedure (ALTER PROCEDURE dl_CARDEX_GetUsageHistory...)
2. Dump the procedure cache (DBCC FREEPROCCACHE)
3. Restart SQL Server services
4. Reboot server
5. Reinstall OS and SS with service packs
6. Change careers ;-)
My guess is problem will be solved before #3 is necessary. If not (and
before proceding beyond #4) let us know if this always happened or just
started happening (after what changed), etc.
[quoted text, click to view] "Tom" <tdietz@gmail.com> wrote in message
news:1166111143.308970.130810@j72g2000cwa.googlegroups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
>
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
>
> dl_CARDEX_GetUsageHistory is the name of my sproc.
>
> I spliced out the select statement and it runs fine in Query Analyzer.
>
> I googled for 'ObsoletedSprocException' and couldn't find a single
> reference to it!
>
> It's coming right from SQL Server as I get this message directly from
> Query Analyzer when executing the sproc.
>
> Any ideas? Very odd that no one has posted anything about this
> exception before.
>
> Thanks,
>