Getting "The web site doesn't contain any content. Sign in to administration and edit the content."

Jordyn Thompson asked on August 10, 2020 15:42

Running site locally and cannot get it to load, it just displays a blank page that says, "The web site doesn't contain any content. Sign in to administration and edit the content."

When I click administration and log in using my credentials I get this error message:

Server Error in '/' Application. Task type 'CMS.DataEngine.DictionaryCommandWebFarmTask' is not supported. The task needs to be registered using CMS.Helpers.WebFarmHelper.RegisterTask method. 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.NotSupportedException: Task type 'CMS.DataEngine.DictionaryCommandWebFarmTask' is not supported. The task needs to be registered using CMS.Helpers.WebFarmHelper.RegisterTask method.

Source Error:

Line 506: try Line 507: { Line 508: e.Authenticated = Membership.Provider.ValidateUser(Login1.UserName, Login1.Password); Line 509: } Line 510: catch (ConfigurationException ex)

Source File: C:\TQLSite\tql-tql.com\CMS\CMSPages\logon.aspx.cs Line: 508

Stack Trace:

[NotSupportedException: Task type 'CMS.DataEngine.DictionaryCommandWebFarmTask' is not supported. The task needs to be registered using CMS.Helpers.WebFarmHelper.RegisterTask method.] CMS.WebFarmSync.WebFarmTaskManager.SerializeDataInternal(WebFarmTaskBase data) +237 CMS.WebFarmSync.WebFarmTaskCreator.CreateTaskInternal(WebFarmTaskBase task) +285 CMS.WebFarmSync.WebFarmService.CreateTask(WebFarmTaskBase task) +36 CMS.DataEngine.ProviderDictionary2.Add(TKey key, TValue value, Boolean logTask) +137 CMS.DataEngine.AbstractInfoProvider3.UpdateObjectInHashtables(TInfo info) +138 CMS.DataEngine.AbstractInfoBase1.UpdateData() +349 CMS.DataEngine.AbstractInfoProvider3.SetInfo(TInfo info) +741 CMS.Membership.UserInfoProvider.SetUserInfoInternal(UserInfo user) +613 CMS.Membership.AuthenticationHelper.FinalizeAuthenticationProcess(UserInfo user, Int32 siteId) +273 CMS.Membership.AuthenticationHelper.AuthenticateUser(String userName, String password, String siteName, Boolean login, AuthenticationSourceEnum source) +1536 CMS.MembershipProvider.CMSMembershipProvider.ValidateUser(String username, String password) +48 CMSPages_logon.Login1_Authenticate(Object sender, AuthenticateEventArgs e) in C:\TQLSite\tql-tql.com\CMS\CMSPages\logon.aspx.cs:508 System.Web.UI.WebControls.Login.AttemptLogin() +147 System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +111 System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +50 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1964

Recent Answers

Brenden Kehren answered on August 10, 2020 16:17 (last edited on August 10, 2020 17:09)

Start out by providing what version you're working in.

Secondly, what method are you developing in? Portal Engine, MVC, or Portal + ASPX Pages?

Lastly, the error looks like an error with the database connection string. You can load the Login page without a connection to the database, but the minute you try to actually log in, it will fail.

0 votesVote for this answer Mark as a Correct answer

Jordyn Thompson answered on August 10, 2020 17:07

Thanks Brenden - Just confirmed with another developer that the connection string is correct. Using ASPX Templates.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on August 10, 2020 17:17

Hmm interesting a v12 site is using ASPX templates.

Looking at the error message a bit more, it looks like there is problems with the web farms and registering them properly. Is the site using web farms? Does the user account running the site locally have permission in the IIS App pool to run the site? Typically this is set to ApplicationPoolIdentity and not NetworkService.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on August 11, 2020 07:41

What is the environment setup? I assume you have some working environment - so what is different? For the no content error - this looks like there is an issue with the master page template. If oyu are using ASPX templates, check the code nad inheriting. Maybe you restored the project into some different physical folder structure and now the file paths do not match in the markup and in the code file attributes.
For the DictionaryCommandWebFarmTask error - I have seen this in older Kentico version (v9) where the project was hosted in medium trust environment, which is not supported anymore. Full trust environment is required.

0 votesVote for this answer Mark as a Correct answer

Jordyn Thompson answered on August 11, 2020 15:17

For IIS App permissions we are using a custom account rather than ApplicationPoolIdentity or NetworkService. We have cloned the project a few times and have ensured the same physical folder structure. We are not sure if the site is using web farms. We have not heard of that before so do not think we are using that.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on August 11, 2020 15:25

Does that custom account have read/write abilities to the directory the website is running in IIS? When you received the website, did you unzip the site from a compressed file? If so, did you unblock the zip file prior to unzipping the site? Are there other lock restrictions on the file(s) from when you received the website? Is it in a web app format and needs to be rebuilt prior to running it?

0 votesVote for this answer Mark as a Correct answer

Jordyn Thompson answered on August 11, 2020 16:55

Wanted to provided the resolution to this problem in case anyone else experiences it. To fix, we changed Managed Pipeline Mode in IIS from Class to Integrated.

We then received this error:

HTTP Error 500.24 - Internal Server Error : system.web/identity@impersonate is set to true

We then, under IIS authentication, set ASP.NET Impersonation to disabled and that fixed everything.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.