Could not find stored procedure 'dbo.InsertUpdateLocation'. SQL SERVER 2008

Question

1.00/5 (1 vote)

See more:

SQL-Server-2008

, +

Hi..

I am using remotely connected database and when i try to use the stored procedures getting the following error- Could not find stored procedure 'dbo.InsertUpdateLocation'.

I tried changing the schema name from dbo but the problem still exists and it works perfectly fine in local.

Can anyone please help me??

Thanks in advance.

Posted 8-Jul-13 23:15pm

bhagyap

Add a Solution

3 solutions

Solution 1

When you moved this to your production database, did you remember to copy the stored procedure over? Because the error message is quite explicit - and if you haven't changed the code between local and production, then there is one obvious cause...

Posted 8-Jul-13 23:32pm

OriginalGriff

Solution 2

error- Could not find stored procedure 'dbo.InsertUpdateLocation' This type of error generate when you code not getting this store procedure.
So check you data base did you create this procedure.Or make sure match store procedure name properly.

Posted 8-Jul-13 23:36pm

jaideepsinh

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Amol_B · Accepted Answer · 2013-07-09T00:48:00

Solution 3

Simplest way will be to execute script for stored procedure in server.

Posted 9-Jul-13 0:48am

Amol_B

Comments

bhagyap 9-Jul-13 7:08am

I have tried doing it.

Amol_B 9-Jul-13 8:13am

oh... in that case you can check
select * from INFORMATION_SCHEMA.ROUTINES WHERE SPECIFIC_NAME = 'InsertUpdateLocation' OR ROUTINE_NAME = '_InsertUpdateLocation'

and check here if specific schema is DBO . if it is not then you can face this problem.