FAQs >
Installation and deployment
If you have previously uninstalled and reinstalled ASP.NET on the server, this issue may be caused by the ASP.NET Web Service Extensions permissions had been reset to “Prohibited”. Please change it to 'Allowed' instead. You can find more details at
http://support.microsoft.com/kb/315122
This error message occurs if you don't have sufficient permissions for writing to disk. Please check disk permissions of process used by application.
This error can be caused by some content in the App_Data folder. Could you please try to delete content of ~\App_Data\CMSTemp directory in appropriate project folder and then try to import again?
Could you please check unless you use SSL? You may see it when you edit content root -> Properties -> Security -> Requires SSL
If so, please configure it to “No” and check the live site. If it is all right now, you did not configure SSL properly. Please see this article for more information about SSL configuration on your server.
This issue is most probably caused by Kentico CMS site has been put into sub-directory of another web site and is inheriting web.config setting from parent folder. If you use same version of 'system.web.extensions' library in parent folder, you can just remove following line from web.config file of Kentico CMS site:
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
Otherwise you can change following lines:
<configSections>
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
to:
<configSections>
<clear/>
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
If you’re running on Windows Vista and all IIS settings are correct, please check if you have the Service Pack (at least SP1) applied. Installation of the Service Pack should solve this issue (confirmed for Vista Ultimate, 64-bit, IIS7.0).
You can specify max file size by setting max request length parameter in the web.config file. Please open the web.config file, find the <system.web> section and insert the following line into it:
<httpRuntime maxRequestLength="8000"/>
This will increase the max file size to 8MB. You can find more information at: http://msdn2.microsoft.com/en-us/library/e1f13641(vs.71).aspx.
Please see also The IIS6/7 is set by default to allow only 30MB files to be uploaded article.
The main reason why this error occurs is renaming the database after installation of CMS or database malfunction caused by improper creation of it’s part. Recreating site using Web installer should solve the problem.
To solve this issue you should edit your web.config file and try to find this tag:
<httpRuntime executionTimeout="xxx" />
If you find it, try to increase the executionTimeout attribute value.
If the tag is not present in the web.config. Add it in the <system.web> section with executionTimeout attribute value set to 150 or higher.
If you are importing documents to an existing site, only new documents are imported and created. Existing documents are not updated. For this you can remove the site and import the package as a new one or use content staging -
www.kentico.com/docs/devguide/overview11.htm
You need to insert the license as you have recieved it. This means also with the domain name, product and expiration. Please make sure you are entering license for appropriate version (2.x, 3.x, 4.x, etc.) and that there are no white spaces or lines.
The error is usually thrown on this line of code <uc1:ForumUserPicture ID="picUser" runat="server" />. This happens when using precompiled web sites which are allowed to be modified. It may help to uncheck (set to false) "Allow this precompiled site to be updatebale" when precompiling the web site and/or to clear .Net cache.
We have tested our product on MS Windows Server 2003 with MS SQL Server 2005 (both 64-bit editions) and it works with no problem. We use only standard .NET/SQL2005 features. Kentico CMS is compiled for 32bit OS, so if you wish to fully leverage the 64bit OS, you may need to recompile the full source code using Visual Studio 2005/2008 for the 64bit environment.
If you're using version before 2.2, you may receive an error message like this:
Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
You need to upgrade to version 2.2 and adjust the security settings as described in the KB article Kentico CMS in a Medium Trust Environment.