Recently when deploying an application out to IIS we had the need to deploy a sub application within the same domain. Essentially, what we were trying to do was make the sub application an extension of the parent application, but live in separate app pools and the code base would be kept separate as well.
(ie: www.awesomeApp.com is the parent application and www.awesomeApp.com/subAwesomeApp is the separate sub application living in the same awesomeApp domain)
This is simple to set up in IIS, however, when we tried to deploy the second sub application we got this reoccurring error when we tried to hit www.awesomeApp.com/subAwesomeApp.
Server Error in ‘/subAwesomeApp Application.
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load type…
This was a question popup about a year ago when the client SPS 2003 virtual directory is hosed on a drive other the default C:\Inetpub\wwwroot location.
It all began with a gradual migration, the new targeted web application for MOSS 2007/WSS 3.0 is created automatically at C:\Inetpub\wwwroot\VirtualDirectories\
while the SPS 2003 site is at E:\Inetpub\wwwroot. At that time, I only know to manually change the virtual directory physical path location in IIS manager after the targeted web application is created.
Yesterday, I came across Bill Baer‘s blog and one of his posts answered my questions of changing the default location for virtual directory creation.
The method turns out to be not a “SharePoint configuration” but rather a “IIS configuration”. Not at all an experienced server/IIS administrator myself, I feel like his post is “good to know” and one of the gotcha situation