Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

EPiServer.Configuration.Settings.Instance has not been initialized and the siteId="" has no corresponding <site> element.


has anyone else had this error and know how to get rid?!?

Jun 30, 2010 12:58

Do you have the siteid attribute in the site tag?

<episerver xmlns="http://EPiServer.Configuration.EPiServerSection">
    <site description="Customer" siteId="">

Jul 02, 2010 11:23

Are you running multiple sites?  We found this happens when there's a mis-match between what site a domain name is configured in IIS and what the EPiServerFramework.config file says should be in that site.

When a request comes in, IIS maps it based on domain name.  This initializes EPiServer inside the AppDomain of that site, and sets constants like PageReference.StartPage.  If EPiServerFramework.config later says that a page from a different EPiServer site should be delivered within that same AppDomain, then you have this problem.

Jul 02, 2010 15:16

I got the same problem, for future reference check that in episerverframework.config in tag automaticSiteMapping the siteId match siteId in episerver.config

Nov 08, 2011 15:17

I had the same problem and I solved it by not using Cassini ;)

My web.config wasn't compatible with Visual Studio's IIS 6 compatible internal web server.

Oct 23, 2012 15:03
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.