title: Problem calling stored procedure from another stored procedure via classic ASP
body: <p>We have a classic ASP application that simply works and we have been loathe to modify the code lest we invoke the wrath of some long-dead Greek gods.</p>
  
  <p>We recently had the requirement to add a feature to an application.  The feature implementation is really just a database operation requires minimal change to the UI.</p>
  
  <p>I changed the UI and made the minor modification to submit a new data value to the sproc call (sproc1).</p>
  
  <p>In sproc1 that is called directly from ASP, we added a new call to another sproc that happens to be located on another server, sproc2.</p>
  
  <p>Somehow, this does not work via our ASP app, but works in SQL Management Studio.</p>
  
  <p>Here's the technical details:</p>
  
  <ol>
  <li>SQL 2005 on both database servers.  </li>
  <li>Sql Login is authenticating from the ASP application to SQL 2005 Server 1.  </li>
  <li>Linked server from Server 1 to Server 2 is working.  </li>
  <li>When executing sproc1 from SQL Management Studio - works fine.  Even when credentialed as the same user our code uses (the application sql login).  </li>
  <li>sproc2 works when called independently of sproc1 from SQL Management Studio.  </li>
  <li>VBScript (ASP) captures an error which is emitted in the XML back to the client.    Error number is 0, error description is blank.  Both from the ADODB.Connection object and from whatever Err.Number/Err.Description yields in VBScript from the ASP side.  </li>
  </ol>
  
  <p>So without any errors, nor any reproducibility (i.e. through SQL Mgmt Studio) - does anyone know the issue?  </p>
  
  <p>Our current plan is to break down and dig into the code on the ASP side and make a completely separate call to Server 2.sproc2 directly from ASP rather than trying to piggy-back through sproc1.  </p>