Server Error in Application "WEBSITEPANEL ENTERPRISE SERVER"
Posted by on 12 January 2011 08:35 AM
|
|
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.
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. | |
|
(I needed to set the ASP version to 4.0..which I'm CERTAIN that I did at setup...but I did not take the time to double check because it already takes and hour to do 10 minutes of work due to the slowness of the control panel).
Nothing worked.
Finally, I stopped the web site then again I reset ASP to 4.0.
That took. Now I'm working.
-dave
To be clear, one day I was able to access the properties through the control panel, and the next day I could not. I have three other sites and they work fine.
Is there any limit to the number I can have for secure directories?