Last post Mar 31, 2006 02:59 AM by wwwalker
Dec 29, 2005 02:48 AM|sauser|LINK
Hi all, I just installed DNN 3.2.2 on Framework 1.1 with SQL Server 2000.
It installed successfully but when I tried running this error appearred.
The url shows :
Any help is appreciated. Thanks.
Jan 01, 2006 12:38 PM|nbc|LINK
Jan 01, 2006 03:44 PM|smehaffie|LINK
Jan 01, 2006 10:22 PM|nbc|LINK
Thanks, I will try that although (using source version) the same set of code ran fine when upgrading the site at localhost.
I did notice that although the install dialog ran, the sql scripts never executed.
EDIT: Just realised that I replied to the wrong post - but I've still got the same problem after recompile. Beginning to think there is a missing/corrupted file caused by the FTP to remote server.
Jan 01, 2006 10:36 PM|sauser|LINK
It is a new install. I ran the installed files not the source code. The SQL scripts ran just fine, it built the database for me.
Jan 03, 2006 02:10 AM|wwwalker|LINK
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of
the exception can be identified using the exception stack trace below.
[NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.Framework.Reflection.CreateObjectNotCached(String ObjectProviderType) +24 DotNetNuke.Services.Cache.CachingProvider.CreateProvider() +27 DotNetNuke.Services.Cache.CachingProvider..cctor() +13[TypeInitializationException: The type initializer for 'DotNetNuke.Services.Cache.CachingProvider' threw an exception.] DotNetNuke.Framework.Reflection.CreateObject(String TypeName, String CacheKey) +53 DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName) +481 DotNetNuke.Services.Log.EventLog.LoggingProvider.CreateProvider() +36 DotNetNuke.Services.Log.EventLog.LoggingProvider..cctor() +13[TypeInitializationException: The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception.] DotNetNuke.Framework.Install.NoUpgrade() +39 DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e) +391 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +47 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
Jan 03, 2006 02:16 AM|wwwalker|LINK
Jan 03, 2006 02:54 AM|wwwalker|LINK
Jan 03, 2006 02:55 AM|nbc|LINK
You should really do this the other way around. Rename release.config to web.config (backup web.config first!) and only copy over the first 3-lines under <appsettings> from your backup.
<add key="SiteSqlServer" value="Server=xxxxx;Database=xxx;uid=xxx;pwd=xxx;" />
<add key="MachineValidationKey" value="EFBD818FD2E95D02721B83CBC4FDXXXXX4F99D" />
<add key="MachineDecryptionKey" value="D6BE8F5BD0F896D427B8076D6F6EFFDXXXXXE561DCE148" />
Jan 03, 2006 07:43 AM|nbc|LINK
Huh - we posted at exactly the same time.
But if you didn't copy the Machine Keys and this is an upgrade, you're going to have problems (login/passwords etc).
Jan 03, 2006 04:18 PM|asanten|LINK
I've done some experiments:
DNN 3.2.2 Compiled 12/23/2005
DNN 4.02 Compiled 12/23/2005
ALL combinations of the above fail. BUT... there is a big but on my installation.
When I hit REFRESH, often the page DOES reload and complete.
I found a reference to ASP.1.1 with regards to the GAC (Gacutil /i adodb.dll) but this KB article seems to be specific to ASP1.1 and after installation and another 3 clean installs, I came to the conclusion that the installation isn't more stable.
My latest thoughts... I'm just sharing, because it may help trigger a solution
My latest thoughts is that there may be a component in the compiler's machine that's not on mine....
I found something similar to that when I ran DNN3.2.2 with ASP1.1... there was a reference to a .js file which is available only in ASP2.0.
I guess my next attempt includes downloading VS-Lite and compiling from scratch?
If anyone has a better answer than this, please let me know.... I've spent so much time on this, my head hurts.
Jan 03, 2006 06:00 PM|paulsoren|LINK
Jan 03, 2006 08:54 PM|asanten|LINK
Went back to DNN3.2.1 on ASP1.1
I haven't seen this error back. It's been running for over 4hrs without Object+reference+not+set+to+an+instance+of+an+object
It looks like DNN3.2.1 wasn't ported to ASP2.0 (so the 'missing .js' problem is no longer an issue when trying to run in ASP1.1)
I'm sure that DNN4 will be great on ASP2.0, but for now I think DNN3.2.1 is my option[:)]
I'll be back with this post if I run into more snags. I hope it contributes for others running into the same problem.
Mar 31, 2006 02:59 AM|wwwalker|LINK