I get the following error whenever I run dnn for the first time. I thought dnn automatically invokes the installer itself, but for some reason, sometimes it does not. How do I call it manually?

DotNetNuke Upgrade Error

huray for great documentation ... page 12 of the dotnetnuke installation guide reads:

The AutoUpgrade function will detect that the Database is empty.  If the ?AutoUpgrade? setting is set to false then an ?Under Construction? will indicate that the site is not available. The administrator can then trigger the Install by using the url ? ?Install/Install.aspx?mode =Install?.

i wonder though that this is your problem here. Did you check connection string ... access rights of the asp.net process etc ...

cheers,

erik

Erik van Ballegoij, The Netherlands

Ok, I have been having serious issues with the install of DNN.  The person helping me seemed to have dropped off the face of the earth so I am reaching out to yet another area for some assistance.  

First - How to read this message:
All text in red is the soltion my other helper told me to do. 
All text in navy blue are actions I took. 
All text in black are the errors. 

THE PROBLEM: I installed DNN 3.0.1 and got

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

Login failed for user 'dnnadmin'. Reason: Not associated with a trusted SQL Server connection. 

SOLUTION TO THE PROBLEM: "Set SQL authentication must be in mixed mode, this will allow non-windows (dnnadmin in your case) accounts to access the server"

In Enterprise manger, right click your SQL server and select properties, then select the Security tab. Select the radio-button for SQL Server and Window, click 'OK'...

THIS DID NOT WORK I GOT THIS ERROR: 

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

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

SOLUTION TO THIS PROBLEM:  "Find and delete file "Install/dnn.config". This will allow the installation to run again."

DID NOT WORK:  I could never find the dnn.config file under my root director so I completely uninstalled everything, IIS, SQL & DNN.  I reinstalled DNN the new version and named the file something completly diffrent from the default name of, DotNetNuke.  Reinstalled and configured SQL, IIS etc., and now I get this error message:

Server Error in '/DNN_test' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Framework.Reflection.CreateObjectNotCached(String ObjectProviderType) +26
   DotNetNuke.Services.Cache.CachingProvider.CreateProvider() +11
   DotNetNuke.Services.Cache.CachingProvider..cctor() +15

[TypeInitializationException: The type initializer for "DotNetNuke.Services.Cache.CachingProvider" threw an exception.]
   DotNetNuke.Services.Cache.CachingProvider.Instance() +0
   DotNetNuke.Framework.Reflection.CreateObject(String TypeName, String CacheKey) +46
   DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectNamespace, String ObjectAssemblyName) +295
   DotNetNuke.Services.Log.EventLog.LoggingProvider.CreateProvider() +22
   DotNetNuke.Services.Log.EventLog.LoggingProvider..cctor() +15