Scenario:  Fresh installation of DNN 4.5.1, DNN 4.4.1, DNN 4.3.7; Windows 2003 Server (IIS 6); SQL Server 2000 (running Win2k SP4); I have admin rights on all of the servers.  Note:  Using Remote Desktop to perform operations on servers.

Problem:  With all versions of DNN specified I get the following error upon opening the site:

The stored procedure 'dbo.dnn_GetPortalAliasByPortalID' doesn't exist.

As you can see, I am using dnn as my object qualifier.  When I look in my database I see the following objects:

• dbo.dnn_Version (table)
• dbo.dnn_FindDatabaseVersion (stored proc)
• dbo.dnn_GetDatabaseVersion (stored proc)
• dbo.dnn_UpdateDatabaseVersion (stored proc)

My SQL Server supports mixed mode authentication and I am using a SQL Server account called APP_DNN that has been granted db_owner on the DNN database.  So that is good.  The fact that these objects were created tells me that DNN can indeed communicate with the database and even execute some DDL.  Upon further investigation it would appear that only 00.00.00.SqlDataProvider gets executed and the remaining ones just don't happen or they are getting skipped or something.

Yes, I have followed the installation instructions to a T.  The APP_DNN account appears to work so I am just wondering WTF.  I know that people are running into this issue, but I have not found an actual solution in any of those posts.  They are all to the effect of "Check your settings, drop the database, recreate the database, ..., restart IIS and try again."  Of course, I have tried that.  Also, I have not found any dnn.config file in my Install directory and I AM using the UseDnnConfg setting with a value of true.  My file/folder permissions are set properly (full access to NETWORK SERVICE and ASPNET).  IIS and WWW Publishing are run using Local System account so hopefully that is the proper settings as well.

Like most people in this situation, this is driving me up the wall.  Is there any original, sound advice out there for me?

I think I am going to run a trace on my SQL Server to see what is being attempted.  Maybe that will give some insight.  I was able to get this working from a desktop installation (which is XP) so there is some difference between the server environment and my desktop that is botching things.  Perhaps it truly is a permissions thing and I just need to fiddle about with that a bit.  I am going to work on it and if I find the answer I will post it here.  Nevertheless, help is appreciated.

Thanks.