Post reply

Could not find stored procedure. SQL Server error 2812

  • September 24, 2010 at 12:37 pm

    #238776

    I am able to run the stored procedure in management studio.

    when i create a dataset in BIDS, the metadata came up, but when i execute the stored procedure in a dataset, its giving me the following error.

    "Could not find stored procedure. SQL Server error 2812"

    Thanks for your help guys.

    Satish

  • September 24, 2010 at 1:53 pm

    #1227214

    Make sure the user you are using to connect to the database has permissions to that stored procedure. Also, depending on the version of SQL you are using make sure that you're using the correct owner/schema to call the stored procedure if it's needed.

    I.E. in 2000 and the owner is not DBO or the user callign the procedure you must specify the owner Exec owninguser.myprocedure

    in 2005+ make sure you are specifying the schema if it's not in the default schema of the user attempting to execute the procedure.

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • September 24, 2010 at 1:59 pm

    #1227219

    All the permissions are good.Thanks for the reply.

    I found the soultion. Its really crazy, I do not know why and how but it worked.

    I droped the procedure and recreated and it worked like that.

    Thanks

    Satish

  • September 24, 2010 at 2:03 pm

    #1227223

    Were you the one that originally created the procedure? IF not, and this is a SQL 2000 instance, you were not the owner, therefor you would have needed to specify the owner. Since you dropped and recreated the procedure, you are now the owner and do not need to specify the owner, but other users will need to.

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • September 24, 2010 at 2:16 pm

    #1227232

    I created the sp first and then I gave exec permissions to other person. so the other person got the error which I pasted. we tried and tried but worked only after I recreated the proc. I was the one who created the proc the first time and the second time also.

  • September 24, 2010 at 2:17 pm

    #1227234

    Its SQL2008

  • September 24, 2010 at 2:20 pm

    #1227237

    satishseth143 (9/24/2010)

    Its SQL2008

    Thanks for finally posting the version number. Sorry I assumed this was 2000 as that's what the largest majority of articles I could find on this error number were dealing with. Glad you got it sorted.

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply