SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 HELP - Could not find stored procedure
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Fat Boy
Starting Member

2 Posts

Posted - 02/04/2010 :  17:18:48  Show Profile  Reply with Quote
New to this forum and this is my first post. I am new and way out of my class and hoping someone can help with my current problem. I am using a contact management program called "Wired Contact" and resently moved the database files to a new faster server and upgraded from SQL 2000 to SQL 2005. I am getting the below error. The only difference that can be seen is that when the user database was setup the name was change from "WCUser" to "WCuser" would this be case sensitive? or any other help. THANK YOU!




Could not find stored procedure 'spSelectWCECompanyStatus'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Could not find stored procedure 'spSelectWCECompanyStatus'.

Source Error:


Line 107: cmd4.CommandType = CommandType.StoredProcedure;
Line 108: cmd4.Parameters.Add("@actid", actid);
Line 109: SqlDataReader reader4 = cmd4.ExecuteReader();
Line 110: reader4.Read();
Line 111: CompanyName = reader4.GetString(0);

vmenon
Starting Member

India
17 Posts

Posted - 02/05/2010 :  00:43:31  Show Profile  Reply with Quote
Please can you check the server collation on both the server instances. to check SQL server instance collation using SSMS, right click the instance name, select properties, in the properties window - general section look for "server collation" value.

Compare the collations at the instance level or at the database level and determine whether the upgraded system is using a case sensitive collation.
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

India
52317 Posts

Posted - 02/05/2010 :  08:47:06  Show Profile  Reply with Quote
Also make sure the SP exists in your default schema or schema that you do have access to. If not check the current schema where sp exists and make it your default schema or give access for you to that
Go to Top of Page

Fat Boy
Starting Member

2 Posts

Posted - 02/05/2010 :  10:58:36  Show Profile  Reply with Quote
Thank you VERY much for these helps and I will do and report back. So is the general consensus is that it is not because I moved from 2000 to 2005 that creates this problem and have to go back to 2000?
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

India
52317 Posts

Posted - 02/05/2010 :  11:03:32  Show Profile  Reply with Quote
I dont think it has anything to do with migration. Only question is whether you tried executing the above code after transfer to new server before you did upgrade?
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.09 seconds. Powered By: Snitz Forums 2000