Hey, everyone -
Here's the problem. I took a perfectly working VB.NET app, zipped up all the code, detached the databases, and copied it all to a different server (Windows 2000 Server). I have the site set up in IIS and working fine, it would seem, except for the database.
The database was installed on SQL Server 2000, and that's what I'm running the new copy on, as well. I used the "Attach Database" function in Enterprise Manager, and everything seemed to go swimmingly. Problem is, I really don't know too much about the ASP.NET and SQL Server user schemes, so I've had a couple errors here and there. First I couldn't connect to the database at all, until I reattached using owner "TestUser". TestUser's also the user who owns the stored procedure I'm trying to access (they were all moved over with the rest of the database). Now I can connect to the database, but I get the error specified in the subject: "Could not find stored procedure 'User_Proc'."
The ASP.NET authentication mode (set in Web.config) is Windows, if that makes any difference, and I've created a Windows user called 'TestUser'. I'm not sure what groups he has to be a member of, if any in particular. Right now he's in Users and Administrators.
Now, the code is exactly as it was on the other server, and it's running. The database contents (and I suppose all the settings that get moved with the database mdf and ldf files) are also as they were. I've read elsewhere online that the problem could be that the SP name isn't fully qualified (prefixed with database and/or owner name); I've done a direct query, and I'm able to execute the SP if I prefix it with the owner name...so that's probably the deal. BUT...the code is pretty extensive, and makes calls to dozens of SPs all over the place, and I don't want to edit them all to do these prefixes, recompile, etc.
So is there a way to change the setup of the server and/or SQL Server to allow the code to work as before? Do I have to run IIS as TestUser or something?