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 ...Unable to access Admin Site settings after fresh DNN 6.2 InstallUnable to access Admin Site settings after fresh DNN 6.2 Install
Previous
 
Next
New Post
10/26/2012 1:32 PM
 
It is worth a shot to try, but I am not sure if that will do anything or not.

another thing you might try is looking at the data in the Portal Settings table, and comparing the results to another installation that works, seeing if any of the settings appears to be different types of data than the one that works?

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
10/26/2012 1:40 PM
 

Clearing out PortalAlias table of any extra entries didn't help.

Did a redgate SQL Data Compare on the PortalSettings table and the only records that are different are default skins, favicons, RecordsPerPage etc.

I did notice that there is a DefaultPortalAlias row that was set to localhost on the instance in question, so I changed that to match what the alias should be, but that didn't help either.

 It looks like the PortalSettings table for the working instance has quite a few more rows though..... Wondering if maybe the PortalSettings table for the nonworking instance is incomplete? 

 The working instance has 66 rows for Portal 0 and the non-working has 31 rows for Portal 0

 

 
New Post
10/26/2012 1:47 PM
 
That gave me an idea. How about you create a new Portal in the instance that doesn't work (child portal is fine) see if you can access the site settings on that new portal

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
10/26/2012 1:53 PM
 

Well after pushing a SQL Data Compare script over to the database and trying to create a child portal, the child portal still exhibits the same issue. Still the same exception as well

DotNetNuke.Services.Exceptions.PageLoadException: The type initializer for 'FormatterGenerator' threw an exception. ---> System.TypeInitializationException: The type initializer for 'FormatterGenerator' threw an exception. ---> System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.ArgumentException: SessionPageStatePersister can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. at System.Web.UI.SessionPageStatePersister..ctor(Page page) at Telerik.Web.UI.RadSessionPageStateCompression.GetStatePersister() at System.Web.UI.Page.get_PageStatePersister() at System.Web.UI.Page.LoadPageStateFromPersistenceMedium() at System.Web.UI.Page.LoadAllState() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace --- at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.Mvc.AntiForgeryDataSerializer.FormatterGenerator.TokenPersister.CreateFormatterGenerator() at System.Web.Mvc.AntiForgeryDataSerializer.FormatterGenerator..cctor() --- End of inner exception stack trace --- at System.Web.Mvc.AntiForgeryDataSerializer.get_Formatter() at System.Web.Mvc.AntiForgeryDataSerializer.Serialize(AntiForgeryData token) at System.Web.Mvc.HtmlHelper.GetAntiForgeryTokenAndSetCookie(String salt, String domain, String path) at System.Web.Mvc.HtmlHelper.AntiForgeryToken(String salt, String domain, String path) at DotNetNuke.Framework.ServicesFrameworkImpl.RegisterAjaxAntiForgery(Page page) at DotNetNuke.Framework.PageBase.OnPreRender(EventArgs e) at DotNetNuke.Framework.DefaultPage.OnPreRender(EventArgs evt) in c:\webapps\InCareTraining\Default.aspx.cs:line 759 at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

 

 
New Post
10/26/2012 2:45 PM
 

Also found this post and tried clearing cookies from IE and doing InPrivate Browsing just to make double sure and still had the error

 http://www.dotnetnuke.com/Community/Community-Exchange/Question/2084/Anti-forgery-token-error-when-accessing-Site-Settings-on-a-fresh-installation.aspx 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Unable to access Admin Site settings after fresh DNN 6.2 InstallUnable to access Admin Site settings after fresh DNN 6.2 Install


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