A Configuration Error occurs when you run other ASP.NET applications on the same Web site as Business Portal


TechKnowledge Content


SYMPTOMS


When you run other ASP.NET applications on the same Web site as Business Portal, you may receive the following error:


Configuration Error

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: File or assembly name Microsoft.BusinessFramework, or one of its dependencies, was not found.


Source Error: [No relevant source lines]


Source File: web.config Line: 72


CAUSE


The error may be due to the Windows SharePoint Services Web.config file existing at the root of your Web site. Business Portal adds settings to this file and those settings could be conflicting with the settings inyour otherASP.NET Web.config files that exist at any other virtual folders below the root.


Other ASP.NET applications such as CRM and SharePoint Portal Server may create conflicts with the Business Portal Global.asax and Web.config files if they are installed to the same Web site. With ASP.NET Web applications it is recommended to use a separate Web site with its own home directory.


The home directory is the root of your Web content subdirectories, for example ‘wwwroot’ is used on an initial install of IIS for the Default Web Site so for a second Web site, you could create a directory called ‘wwwroot2.’


RESOLUTION


There are two solutions to this issue:


1. If you are developing an ASP.NET application to run with Business Portal, the virtual directory that holds your application files should be configured using IIS Manager so that it is not an “Application Directory”.
You may do this by right-clicking on the virtual directory in IIS Manager and choose Properties. On the Virtual Directory tab, make sure that the field named Application Name is grayed-out. If it is not, click Remove next to the field. By removing the application directory designation from the virtual directory, your application will be a part of the Default Application, and will run in the same context as Business Portal.

Your application will inherit its configuration settings from the same web.config file that Business Portal uses (c:\inetpub\wwwroot\web.config by default). Any assemblies required by your application should be placed in the same bin folder as the Business Portal assemblies, which is c:\inetpub\wwwroot\bin by default.



2. If your ASP.NET application is not using Business Portal's Business Framework, move either your custom ASP.NET application to another Web site or move Business Portal and WSS to another Web site.


Note Make sure to create a new windows directory for your new web site, otherwise you will have problems with the Global.asax and Web.config files for each Web application.



This article was TechKnowledge Document ID:35178