This article has been archived. It is offered "as is" and will no longer be updated.
When you run Microsoft Content Management Server (MCMS) 2002 and Microsoft Office SharePoint Portal Server 2003 on the same virtual server, you may experience many configurations errors. This article describes some symptoms of these errors. This article also describes how to configure your virtual server to make both products work correctly.
You may receive the following error messages when your MCMS application loads:
Assembly mcmswebcontrollibrary.dll security permission grant set is incompatible between appdomains
The XML file c:\inetpub\wwwroot\web.config could notbe loaded. Access to the path "c:\inetpub\wwwroot\web.config" is denied. Required permissions cannot be acquired
Debugging is not supported under current trust level settings
When you start Site Manager, you receive the following error message:
Error: Could not connect to the Microsoft Content Management Server ServerName. Either the web service is not running, or there are network problems that are keeping you from connecting to the server, or the server is not accessible through MCMS Site Manager.Source: LinkConfig::LaunchLogon
When you run Site Deployment, you receive the following error message:
Error: 0 Description: The remote server returned an error: (500) Internal Server Error. Severity: 5 Source: SystemDebug info: N/A Extra info: N/A Client Source: CExProgress::ProcessPackage Recommended Action: N/A
You may also experience some of the following problems:
You receive a prompt to provide authentication and, although you type the correct user credentials, access is denied.
Forms authentication stops working.
You receive a 404 error message when you load http://servername/channels.
You receive a 404 error message when you perform Site Deployment.
You receive a 404.3 error message when you load any MCMS application.
You receive a 403.18 error message when you load your MCMS application.
To resolve these problems:
Exclude the following paths in the SharePoint Portal Server central administration tool:
All other top level channels in MCMS 2002
Any MCMS Web application virtual directories that do not have a matching top-level channel
In your MCMS Web application virtual directory, in your SiteDeployment Web application virtual directory, and in any other MCMS application that you have created, modify the Web.config files to include the following settings:
Verify that the application pool that your MCMS application runs in is the same across the virtual server.
Remove the MicrosoftSharePointTeamServices HTTP Header on the MCMS application Web application virtual directory for each MCMS application that you have.
Verify that you have set the SDO MIME type on the /NR/RdOnlyRes virtual directory. When you set this MIME type, use the .sdo file name extension. For the MIME type, use application/x-mcmscontentpackage.
This behavior is by design.
For additional information about MCMS 2002 Connector for SharePoint Technologies, click the following article number to view the article in the Microsoft Knowledge Base:
835323 Known issues with Microsoft Content Management Server 2002 Connector for SharePoint Technologies