It sounds as if the stored procs didn't get transferred to the new server, even though the data tables and data did.  You can script out all the stored proc objects, along with user-defined functions, and then run that script against the new db server to restore those sprocs. 

Since the provider skipped out and you can't get to the old db server, then I would recommend getting a copy of the .sql script thta DNN uses during installation, and editing out the CREATE TABLE and CREATE INDEX statements (and any other statements that don't make sense in this scenario), so that it can be pared down to a script that just creates your sprocs, user-defined functions, etc.  Then, run that script against your new db server.

Steve

You can chack all procedures in the database using the MS SQL Management Studio.  This needs a local install of it on the remote server wehre your SQL Server is installed, or the open port to cennect to the SQL Server.

Also make sure you have the correct maschinekey, setting up both connection strings in the web.config file, and you have set the right databaseOwner in it.

Here is my connection string. I know the IP, Username & Password is correct. As far as I know it is in the correct format for connectiong to SQL 2005.

<connectionStrings>
     <add name="SiteSqlServer" connectionString="Data Source=97.74.205.***;Initial Catalog=pgt_main;User Id=pgt;Password=****;" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
     <add key="SiteSqlServer" value="Data Source=97.74.205.***;Initial Catalog=pgt_main;User Id=pgt;Password=****;" />
     

When browsing through the Database on SQL Server Management Studio, under Database>Programability>Stored Procedures I have

A Folder of "System Stored Procedures"

dbo.FindDatabaseVersion

dbo.GetDatabaseVersion

dbo.GetDatabaseVersion

So I guess I am missing some stored procedures..... now what?