Loading...

Knowledge Base
Categories:

Server Error in Application "WEBSITEPANEL ENTERPRISE SERVER"

Share

When creating a website or making changes to it, you may start to receive:

Server Error in Application "WEBSITEPANEL ENTERPRISE SERVER"

when viewing the website through the control panel (instead of the website properties). As websitepanel is simply a web frontend for IIS, this error outlines an issue with one of the following -

  1. You removed the wwwroot the website was pointing at. The folder the website was pointing at must always be present. IE, by default, each website in WSP is under domain.com/wwwroot . So, if you remove either wwwroot or domain.com, you'll need to recreate that structure.
  2. The web.config you are using is malformed. To check this, simply move the web.config to outside of the wwwroot or remove it. If that was the cause then the websitepanel website properties will show up fine. You can do this using the file manager.
  3. The permissions on the wwwroot or the files within (mainly web.config) are not correct. Simply go to the file manager, and click on the lock box beside wwwroot of the domain name in question and set it to have read (at least) and write for the domain.com user in question.

In some cases, if you have your files uploaded prior to creating the website, if one of the issues above exist (2 or 3) it is possible that the website is not properly created (website is created but not app pool or vice versa). This will cause a situation that you will need to contact our support staff about as they'll have to manually remove the website and app pool entries for you to be able to create the website.

Note: As a best practice, always make sure that the folder domain.com does not exist inside your root before creating a website for domain.com. This way, the process does not fail due to malformed web.config or improper permissions on the folders.

You will also receive this error when switching to ASP .NET 1.1 . As the IIS GUI itself throws an error under a 1.1 App pool, this is unfortunately a cause of running the website under the old framework. Your website however will function fine. If you wish to change out of this framework or remove the website, simply contact our support staff.

Did you find this article helpful?

 
* Your feedback is too short

Loading...