September 28, 2009 at 9:55 am
I've done this hundreds of times before but now for some reason I can't call a sproc.
Keep getting the following error:
Error: 0xC002F210 at Execute SQL Task, Execute SQL Task: Executing the query "[MyDatabase].[MySchema].[test] " failed with the following error: "Could not find stored procedure ''.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
When I check sql profiler this is the command I find:
exec [MyDatabase].[MySchema].[test] @TestGuid='A8FB1934-5481-48F6-A5AD-E68CBCA575BE'
If I run this command in mgnt studio it runs fine. I've never come across this. Anyone have a suggestion.
September 28, 2009 at 11:28 am
I would first make sure you are using the connection you think you're using. Then make sure that connection is pointing where you think it's pointing.
September 28, 2009 at 12:44 pm
It shows up in the profiler log and the call is fully qualified. It's using integrated authentication on my local sql server of which I am a sysadmin.
I checked the connection about 3 times.
September 28, 2009 at 2:43 pm
The next thing to check is that the user for that connection has Execute privileges for the stored procedure (which includes access to that database).
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
September 28, 2009 at 3:20 pm
thanks for the replies. I believe there was corruption in the package. I recreated and now the stored procedure runs.
I'm at a loss on this one. Not sure what happened.
Thanks - tom
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply