Skip to main content
All CollectionsCommon Errors
Error executing SQL command - Could not find stored procedure
Error executing SQL command - Could not find stored procedure

Executing SQL command error explained.

Praise Magidi avatar
Written by Praise Magidi
Updated over a week ago

Step

SQL Server

Message

Error executing SQL command - Could not find stored procedure '**********'.

Cause

This SQL Server error indicates that the database engine could not find the specific stored procedure that your Synatic step is trying to execute.

This error can occur for several reasons:

1. The stored procedure doesn't exist (it was never created)

2. The stored procedure was deleted

3. You don't have permission to access it

4. You're connected to the wrong database

5. There's a typo in the name (schema, procedure name, or database)

6. The stored procedure exists but in a different schema or database than specified

Resolution

To resolve this issue, you could:

1. Verify that the database exists and you're connected to it

2. Check if the schema exists in that database

3. Confirm that the stored procedure exists in that schema

4. Ensure your user account has permission to execute stored procedures in that schema

5. Double-check the spelling of all components of the stored procedure name

Error Detail

{
"message": "Error executing sql command",
"statusCode": 400,
"errorMessage": "Could not find stored procedure '**********'.",
"error": {
"message": "Could not find stored procedure '**********'.",
"code": "EREQUEST",
"number": 2812,
"state": 62,
"class": 16,
"serverName": "**********",
"procName": "",
"lineNumber": 1
},
}
Did this answer your question?