Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install Fails After Optional Skins PageInstall Fails After Optional Skins Page
Previous
 
Next
New Post
9/29/2008 10:04 PM
 

DNN version 4.9 install

everything looks correct

All permissions are set correctly, DB connection/tables get created. going through the setup just fine. once I get to the Install Optional Skins page and I click next, I get a run time error. anyone run into this problem?  see below

 

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

 
New Post
9/30/2008 1:27 AM
 

What happens if you refresh the page after receiving the error?

Also, have you tried making the change noted in the error message you received and then trying running the install again so you can see the actual error message and not the custom error not set page?  If so, can you post the actual/new error message.


Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
9/30/2008 2:08 PM
 

now I find out that this only happens when I do a custom install. if I do a typical install it installs fine. there must be an issue with something I am selecting during custom install.

 
New Post
9/30/2008 3:53 PM
 

we found a similar problem with our custom install.

The "unfriendly" error is as follows:

Value cannot be null.
Parameter name: value 
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.ArgumentNullException: Value cannot be null.
Parameter name: value

Source Error: 

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.  

Stack Trace: 


[ArgumentNullException: Value cannot be null.
Parameter name: value]
   System.Web.Caching.CacheEntry..ctor(String key, Object value, CacheDependency dependency, CacheItemRemovedCallback onRemovedHandler, DateTime utcAbsoluteExpiration, TimeSpan slidingExpiration, CacheItemPriority priority, Boolean isPublic) +3599655
   System.Web.Caching.CacheInternal.DoInsert(Boolean isPublic, String key, Object value, CacheDependency dependencies, DateTime utcAbsoluteExpiration, TimeSpan slidingExpiration, CacheItemPriority priority, CacheItemRemovedCallback onRemoveCallback, Boolean replace) +88
   System.Web.Caching.Cache.Insert(String key, Object value) +83
   DotNetNuke.Services.Cache.FileBasedCachingProvider.FBCachingProvider.Insert(String CacheKey, Object objObject, CacheDependency objDependency, DateTime AbsoluteExpiration, TimeSpan SlidingExpiration, CacheItemPriority Priority, CacheItemRemovedCallback OnRemoveCallback, Boolean PersistAppRestart) +134
   DotNetNuke.Services.Cache.FileBasedCachingProvider.FBCachingProvider.Insert(String CacheKey, Object objObject, CacheDependency objDependency, DateTime AbsoluteExpiration, TimeSpan SlidingExpiration, Boolean PersistAppRestart) +70
   DotNetNuke.Common.Utilities.DataCache.SetCache(String CacheKey, Object objObject, TimeSpan SlidingExpiration, Boolean PersistAppRestart) +72
   DotNetNuke.Entities.Portals.PortalController.GetPortal(Int32 PortalId) +280
   DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +121
   DotNetNuke.Common.Globals.GetHostPortalSettings() +214
   DotNetNuke.Common.Globals.GetPortalSettings() +79
   DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.OnAuthenticateRequest(Object s, EventArgs e) +67
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

 
 
New Post
9/30/2008 5:53 PM
 

 Do you have any other ASP.Net 2.0 (or higher) Web Applications running on this same server?  The reason I ask is because the error appears to be coming from the .Net Framework itself and not DNN specifically.  DNN can cause a .Net error, but most often the error is in or bubbles up to the DNN components when it is a DNN error.  Either way, it appears to be a caching issue. I am going to do some searching on DNN and known Caching issues that may result in this type of error.


Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install Fails After Optional Skins PageInstall Fails After Optional Skins Page


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out