title: Stored Procedure doesn't exist, or does it?
body: <p>I'm having a problem:</p>
  
  <p>I have a db connection where I run stored procedures on. This same connection is used to create said stored procedures earlier on.</p>
  
  <p>When I attempt to call a given stored procedure, later on, I get the following message:</p>
  
  <blockquote>
    <p>Could not find stored procedure
    'dbo.yaf_prov_upgrade'.</p>
  </blockquote>
  
  <p>The problem is it actually does exist on the database. And there's also the fact that it shows up on the SQL Server Profiler.</p>
  
  <blockquote>
    <p>RPC:Completed exec
    [dbo].[yaf_prov_upgrade]
    @PreviousVersion=46,@NewVersion=46    .Net
    SqlClient Data
    Provider  Nico    Matrix\Nico</p>
  </blockquote>
  
  <p>I was wondering what could be the causes a particular query would throw such an exception even when it exists, it's called, and the call reaches the database.</p>
  
  <p>It can't be a problem with the connection because it already executed other stored procedures. It can't be a problem with the procedure because it does exist, in fact the very same application, the very same web page, created it and put it there.</p>
  
  <p>Update: forgot to mention I'm used integrated security, and I did run the SP on the database with the same user the application connects with, and I had no problem running it.</p>
  
  <p>So what <em>can</em> it be?</p>