I don't have experience with SQL Server, but I did find something potentially relevant with a bit of Google-fu; feel free to ignore it if it's something you already know.
According to a quick Google search (on 'SQL Server ASP "procedure not found"'), two possible causes for this are the connection string being incorrect (i.e. it's not actually connecting to the database properly) and the rights on the server not being correct (i.e. the thing doing the connecting can't access the context where the procedure would be found).
I would expect that there might be something more useful in the SQL Server 2008 documentation, available for apparently free download from Microsoft, but that requires .NET and various hoop-jumping which means it's inaccessible to me since I run Linux.
I hope that's helpful, unlikely though the possibility may be...
According to a quick Google search (on 'SQL Server ASP "procedure not found"'), two possible causes for this are the connection string being incorrect (i.e. it's not actually connecting to the database properly) and the rights on the server not being correct (i.e. the thing doing the connecting can't access the context where the procedure would be found).
I would expect that there might be something more useful in the SQL Server 2008 documentation, available for apparently free download from Microsoft, but that requires .NET and various hoop-jumping which means it's inaccessible to me since I run Linux.
I hope that's helpful, unlikely though the possibility may be...