Microsoft Knowledge Base Email Alertz

(836637) - Explains errors that occur when MCMS and SharePoint Portal Server are installed on separate virtual servers but on the same physical server.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 836637 - Last Review: February 14, 2004 - Revision: 1.2

Configuration errors occur when you run MCMS 2002 and SharePoint Portal Server 2003 on different virtual servers

SUMMARY

When you run Microsoft Content Management Server (MCMS) 2002 and Microsoft Office SharePoint Portal Server 2003 on the same physical server, but you run the programs on different virtual servers, you may receive configuration error messages. This behavior is by design.

SYMPTOMS

When you load the Document Finder dialog box for the Microsoft SharePoint Services document placeholder, you may receive the following error message:
Exception Details: System.Runtime.InteropServices.COMException: The virtual server that is referenced here is not in the config database.
You may also receive the following error message when you load your Microsoft Content Management Server (MCMS) 2002 applications:
Exception Details: System.UnauthorizedAccessException: An attempt was made to perform an unauthorized registry operation.

CAUSE

This problem occurs because MCMS 2002 and SharePoint Portal Server or Windows SharePoint Services (WSS) are installed on the same physical server, but MCMS 2002 and SharePoint Portal Server or WSS are installed on different virtual servers.

RESOLUTION

To resolve this problem, make sure that you install MCMS and SharePoint Portal Server on the same virtual server if you install MCMS and SharePoint Portal Server on the same physical server. Note that although you must install MCMS and SharePoint Portal Server on the same virtual server, you do not have to install them both on the server that contains the default Web site. You can install MCMS and SharePoint Portal Server on any virtual server as long as you intall them on the same virtual server.

STATUS

This behavior is by design.

MORE INFORMATION

The following are the stack traces for the errors that are described in the "Symptoms" section:
Stack Trace: 


[COMException (0x81070552): The virtual server that is referenced here is not in the config database.]
   Microsoft.SharePoint.Library.SPRequestInternalClass.OpenSite(String bstrUrl, Boolean bGetUrlOnly, String& pbstrServerRelativeUrl, Guid& pgSiteId, Int32& pOwnerID, Int32& pSecondaryContactID, DateTime& pdtLastContentChange, DateTime& pdtLastSecurityChange) +0
   Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7)

[SPException: The virtual server that is referenced here is not in the config database.]
   Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7)
   Microsoft.SharePoint.SPSite.c()
   Microsoft.SharePoint.SPSite.get_ID()
   Microsoft.SharePoint.Portal.PortalApplication.GetContext(HttpContext context)
   Microsoft.SharePoint.Portal.PortalApplication.GetContext()
   Microsoft.SharePoint.Portal.PortalContext.get_Current()
   Microsoft.SharePoint.Portal.PortalContext.get_Current()
   Microsoft.SharePoint.Portal.WebControls.SiteInfo.GetSiteInfo()
   Microsoft.SharePoint.Portal.WebControls.ResourceFilePath.SharedImageUrl(String strImageFileName)
   Microsoft.SharePoint.Portal.WebControls.ResourceFilePath.SharedImageUrl(String strImageFileName)
   Microsoft.SharePoint.Portal.WebControls.ResourceFilePath.GetResourceFileUrl(ResourceFileContext rfcFile, String strFileName)
   Microsoft.SharePoint.Portal.WebControls.ResourceFilePath.GetResourceFileUrl(ResourceFileContext rfcFile, String strFileName)
   Microsoft.SharePoint.Portal.WebControls.CategoryNavigationWebPart..ctor()
   _ASP.InternalChannelScript_aspx.__BuildControl__control7() +167
   _ASP.InternalChannelScript_aspx.__BuildControlPageBody() +216
   _ASP.InternalChannelScript_aspx.__BuildControlTree(Control __ctrl) +306
   _ASP.InternalChannelScript_aspx.FrameworkInitialize() +30
   System.Web.UI.Page.ProcessRequest() +85
   System.Web.UI.Page.ProcessRequest(HttpContext context) +18
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +179
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87

 
Stack Trace: 

[UnauthorizedAccessException: An attempt was made to perform an unauthorized registry operation.]
   Microsoft.SharePoint.Portal.PortalApplication.d()
   Microsoft.SharePoint.Portal.PortalApplication.GetContext(HttpContext context)
   Microsoft.SharePoint.Portal.PortalApplication.GetContext()
   Microsoft.SharePoint.Portal.PortalContext.get_Current()
   Microsoft.SharePoint.Portal.PortalContext.get_Current()
   Microsoft.SharePoint.Portal.WebControls.SiteInfo.GetSiteInfo()
   Microsoft.SharePoint.Portal.WebControls.ResourceFilePath.SharedImageUrl(String strImageFileName)
   Microsoft.SharePoint.Portal.WebControls.ResourceFilePath.SharedImageUrl(String strImageFileName)
   Microsoft.SharePoint.Portal.WebControls.ResourceFilePath.GetResourceFileUrl(ResourceFileContext rfcFile, String strFileName)
   Microsoft.SharePoint.Portal.WebControls.ResourceFilePath.GetResourceFileUrl(ResourceFileContext rfcFile, String strFileName)
   Microsoft.SharePoint.Portal.WebControls.CategoryNavigationWebPart..ctor()
   ASP.InternalChannelScript_aspx.__BuildControlHorizontalNavBar() in C:\Program Files\Microsoft Content Management Server\Sample Data\CmsSharePointConnector\Templates\InternalChannelScript.aspx:45
   ASP.InternalChannelScript_aspx.__BuildControl__control7() in C:\Program Files\Microsoft Content Management Server\Sample Data\CmsSharePointConnector\Templates\InternalChannelScript.aspx:39
   ASP.InternalChannelScript_aspx.__BuildControlPageBody() in C:\Program Files\Microsoft Content Management Server\Sample Data\CmsSharePointConnector\Templates\InternalChannelScript.aspx:38
   ASP.InternalChannelScript_aspx.__BuildControlTree(Control __ctrl) in C:\Program Files\Microsoft Content Management Server\Sample Data\CmsSharePointConnector\Templates\InternalChannelScript.aspx:1
   ASP.InternalChannelScript_aspx.FrameworkInitialize() in c:\WINNT\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\cmssharepointconnector\66af1009\faee8571\booflusq.0.cs:0
   System.Web.UI.Page.ProcessRequest() +84
   System.Web.UI.Page.ProcessRequest(HttpContext context) +18
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +179
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87

 

REFERENCES

For additional information about problems that may occur when MCMS and SharePoint Portal Server are installed on the same virtual server, click the following article numbers to view the articles in the Microsoft Knowledge Base:
835248  (http://kbalertz.com/Feedback.aspx?kbNumber=835248/ ) You experience configuration errors when you run Microsoft Content Management Server 2002 and Microsoft Office SharePoint Portal Server 2003 on the same virtual server
835323  (http://kbalertz.com/Feedback.aspx?kbNumber=835323/ ) Known issues with Microsoft Content Management Server 2002 Connector for SharePoint Technologies

APPLIES TO
  • Microsoft Content Management Server 2002
  • Microsoft Office SharePoint Portal Server 2003
  • Microsoft Content Management Server 2002 Connector for SharePoint Technologies
Keywords: 
kbprb KB836637
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate