This is a collection of questions and answers about Microsoft® Content Management Server (MCMS) gathered from the MCMS newsgroup. This content is provided "AS IS" with no warranties, and confers no rights. If you have feedback about one of these topics or would like to add information, please post your comments to the MCMS newsgroup.

 

Thank you,

Stefan Goßner Escalation Engineer

Steve Cawood Program Manager

MCMS 2002 - SharePoint Portal Server Integration FAQ - Table of Contents

0x80041206 Error indexing your MCMS site
403 Error when loading MCMS Site
404.3 When Performing Site Deployment after Installing SharePoint
500 Error after installing Office SharePoint Portal Server 2003
501 error when attaching an SharePoint Portal Server document
All CMS content ends up in the non_portal_content index when using SearchSetup.exe
Are WordML and InfoPath the only supported formats for Spark
Connector for SharePoint Technologies and MCMS 2002 Standard Edition
Creating a content source
Does MCMS 2002 Connector for SharePoint Technologies require the use of SharePoint Portal Server?
Enabling TraceListener Support
Error Appears with SharePoint Portal Server Controls in Visual Studio.NET
Error loading WoodgroveNet - Required permissions cannot be acquired
Error message: "Invalid object name 'RepositorySynchronization'."
Error when reading registry
Error when using SearchSetup.exe
Error: Could not connect to the Microsoft Content Management Server
Forms authentication
How do I configure CMS with Forms Authentication on a Portal Server
How do I configure MCMS and SPS 2003 to work on the same virtual server
How do I create search scopes for MCMS Channels
MCMS and Connector for SharePoint Technologies
MCMS Template Hyperlink Style Does Not Display Correctly
SearchPropertyCollection.xml and Custom Properties
SharePoint Portal Server and Secure Sockets Layer
SharePointDocumentPlaceholderDefinition not available in Placeholder Definition Editor in VS.NET
SPS Sites do not show in the SharePoint Library Document Finder Dialog
The search engine was unable to process your request
The virtual server that is referenced here is not in the config database
Why are my documents not synchronized between CMS and SPS
You have not specified a valid Channel

Topic: 0x80041206 Error indexing your MCMS site

When performing an index on your non-portal content with http://localhost/channels. The index does not work, and the following is logged in your gatherer log:

"The address could not be found, (0x80041206 - A server error occurred. Check that the server is available.)"

If you browse to http://localhost/channels you see the following error:

"Debugging is not supported under current trust level settings."

Answer

Remove the channel rendering script on /Channels or modify the web.config file located in <drive>:\Program Files\Microsoft Content Management Server\Server\MCMS\McmsHomeport and ensure that you have set <trust level="Full" originUrl="" />

For details on "trust level" see the following article:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrftrustsection.asp

[Back to Top]

Topic: 403 Error when loading MCMS Site

After installing the MCMS Connector for SharePoint Technologies and SharePoint Portal Server 2003, I now get a 403 when I load an MCMS site.

Answer

Look in the Internet Information Server (IIS) log. You will see a 403.18 which means "Cannot execute requested URL in the current application pool." Ensure that MCMS and Sharepoint Portal Server are configured to use the same application pool.

This is also explained in the following KB article: 835248

[Back to Top]

Topic: 404.3 When Performing Site Deployment after Installing SharePoint

After installing the MCMS Connector for SharePoint Technologies and SharePoint Portal Server 2003, I receive a 404 when I perform Site Deployment.

Answer

If you look in the IIS log you will se a 404.3 which means "MIME map policy prevents this request." Here is the snippet:

2003-10-14 03:59:04 157.60.92.190 GET /NR/rdonlyres/SD-50CF196B-ED35-4815-B87C-E3B1B10107D2-10758.SDO - 80 domain\username 157.60.92.190 - 404 3 50

You must apply the SDO MIME type to the /NR/RdOnlyRes virtual directory.

Ensure to configure the mime type as follows:

Extension: ".sdo"
MIME type: "application/x-mcmscontentpackage."

[Back to Top]

Topic: 500 Error after installing Office SharePoint Portal Server 2003

When performing Site Deployment or using Authoring Connector after installing MCMS 2002 SP1 and SharePoint Portal Server 2003 on the same virtual server, the following error occurs:

"The remote server returned an error: (500) Internal Server Error."


Answer

Ensure you have set <trust level="Full" originUrl="" /> in the following web.config files:

/MCMS/SiteDeployment/web.config
/MCMS/web.config

Note: ensure that this setting is NOT(!) added to the following file:

../IIS_CMS/OfficeWizard/web.config

For details see the following article:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrftrustsection.asp

See also the following KB article: 835248

[Back to Top]

Topic: 501 error when attaching an SharePoint Portal Server document

I'm trying to attach a document from Microsoft® SharePoint™ Portal Server 2001 to my current MCMS document. In the Microsoft Internet Information Server (IIS) log of the MCMS server machine I have found a 501 error for a 'PUT' request that copies the document to the MCMS server machine. What might be wrong?

Answer

A 501 error means "Method not implemented". It seems WebDav is not enabled on your MCMS 2002 box.

Do the following checks:

• Ensure that the following registry value does not exist:
  \HKLM\System\currentcontrolset\services\w3svc\parameters\DisableWebDav
  
• Ensure that Everyone has read and read/execute permissions on the httpext.dll.
  
• Check the advanced ACL settings as the IIS Lockdown may add a custom 'Deny' for 'Everyone' here.
[Back to Top]

Topic: All CMS content ends up in the non_portal_content index when using SearchSetup.exe

The sample data contains \cmssharepointconnector\internal, and \cmssharepointconnector\external.  I’ve run SearchSetup once for each of these:

searchsetup.exe -url "http://localhost/cmssharepointconnector/internal/" -user "domain\user" -password "password" -crawl "1" -portalurl "http://servername/"

searchsetup.exe -url "http://localhost/cmssharepointconnector/external/" -user "domain\user" -password "password" -crawl "1" -portalurl "http://servername/" 

What I’ve noticed is that you get the index created in the default non_portal_content index.  If I enable advanced SPS search, is there a way to create separate indexes for each channel?

Answer

No. This behavior is by design. When you use SearchSetup.exe, which is required for the MCMS Connector for SharePoint Technologies search control to function properly, it places all the content into the non_portal_content index.

You can setup seperate indexes and scopes, but you will not be able to utilize the MCMS Connector for SharePoint Technologies search control to search on the content. You will only be able to use the SPS Search control and by doing so you will not have the benefit of MCMS rights filtering.

For more information on this, see the following article: How do I create search scopes for MCMS Channels

[Back to Top]

Topic: Are WordML and InfoPath the only supported formats for Spark

Will the requirement for inline viewing of documents be maintained for the release of Spark or are WordML and InfoPath the only supported formats?

Answer

Currently we only support InfoPath and WordML documents for this feature.

[Back to Top]

Topic: Connector for SharePoint Technologies and MCMS 2002 Standard Edition

Will Connector for Sharepoint Technologies for MCMS 2002 and Microsoft SharePoint™ Portal Server 2003 which is currently in Beta be supported with MCMS 2002 Standard Edition.

Answer

Yes.

[Back to Top]

Topic: Creating a content source

I would like to setup a content source for Connector for SharePoint Technologies. How can I do this?

Answer

There are two possible ways to achieve this:

1. Use the SearchSetup.EXE which does everything required automatically
   
2. Use the following steps to create the content source manually by ensuring that the content index is named "Non_Portal_Content" and that the Content Source Group is named "CMSChannels". These criterias are required by the SearchResultControl coming with Connector for SharePoint Technologies.
[Back to Top]

Topic: Does MCMS 2002 Connector for SharePoint Technologies require the use of SharePoint Portal Server?

Does MCMS 2002 Connector for SharePoint Technologies require the use of Microsoft® SharePoint™ Portal Server?

Answer

The only feature that requires Microsoft SharePoint™ Portal Server is the search feature.

The Web Part feature allows MCMS content to be published through and visible on a Microsoft SharePoint Portal Server site. Web Part pages can also be created when only Windows SharePoint Services is installed, therefore it is also possible to use this feature when only Windows SharePoint Services is installed.

The ability to publish content from Microsoft SharePoint Portal Server into MCMS uses the underlying WSS Object Model, therefore WSS is required for this to work, but not Microsoft SharePoint Portal Server.

On a production MCMS server where no authoring should take place only MCMS is required. Not Microsoft SharePoint Portal Server and not WSS as the content is already stored in the MCMS placeholders.

[Back to Top]

Topic: Enabling TraceListener Support

When using Connector for SharePoint Technologies I'm having problems synchronizing and/or retrieving my content from my SharePoint Document Libraries. Are there any troubleshooting steps I can take?

Answer

The WssDocumentUpdater tool is a stand-alone command line utility that is included with MCMS 2002 Connector for SharePoint Technologies. With the WssDocumentUpdater tool, you can update the content of the WssPlaceholder objects in the MCMS repository. When  TraceListener support is enabled, Microsoft® Product Support Services (PSS) can more effectively troubleshoot issues with the WSSDocumentUpdater tool.

The WssDocumentUpdater tool provides TraceListener support for errors, warnings, and verbose trace messages. The TraceSwitch class that the WSSDocumentUpdater tool uses is Microsoft.ContentManagement.SharePoint.Updater.


Enable TraceListener support for the WSSDocumentUpdater tool

1. In the directory that contains the WssDocumentUpdater.exe file, create a configuration file that is named WssDocumentUpdater.exe.config.
2. Add the following code to the configuration file:

     <configuration>
       <system.diagnostics>
         <switches>
           <add name="Microsoft.ContentManagement.SharePoint.Updater" value="4" />
           <add name="Microsoft.ContentManagement.RepositoryInterfaces" value="4" />
         </switches>
         <trace autoflush="true" indentsize="4">
           <listeners>
             <add name="myTracingListener"
                      type="System.Diagnostics.TextWriterTraceListener"
                      initializeData="WssDocumentUpdater.log" />
           </listeners>
         </trace>
       </system.diagnostics>
     </configuration>

3. Save the file.
4. Run WssDocumentUpdater.exe. A log file that is named WssDocumentUpdater.log is created in that directory. To change the path and file name, change the initializeData property in the configuration file.

Note You can use this same method of tracing with the WSS Document Library Finder tool that is used with the SharePointPlaceholder server control. To do this, change the Web.config file for the application instead of the WssDocumentUpdater.exe.config file for the application.

[Back to Top]

Topic: Error Appears with SharePoint Portal Server Controls in Visual Studio.NET

Error Appears with SharePoint Portal Server Controls in Visual Studio.NET

Answer

In Microsoft Visual Studio .NET, when you open the intranet sample data that has the SharePoint Portal Server look and feel, the SharePoint Portal Server controls show the following error message: "Error Creating Control." This error message is displayed because SharePoint Portal Server controls do not support design-time behavior in Visual Studio .NET. You can ignore this error message and edit the page as usual.

Note: This is documented in the readme file.

[Back to Top]

Topic: Error loading WoodgroveNet - Required permissions cannot be acquired

After installing Windows® SharePoint Services or SharePoint Portal Server, I get the following error when loading WoodgroveNet:

"Required permissions cannot be acquired."

Answer

Ensure you have set <trust level="Full" originUrl="" /> in the web.config files for your application and the MCMS virtual application.

For details on "trust level" see the following article:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrftrustsection.asp

[Back to Top]

Topic: Error message: "Invalid object name 'RepositorySynchronization'."

When saving a document using the SharePoint Document Placeholder I get the following error message:

Save Placeholder Failed
Error Details: Invalid object name 'RepositorySynchronization'.

What can I do to correct this problem?

Answer

This problem can happen when the MCMS database does not contain the RepositorySynchronization table. This can happen if the database was switched after Connector for SharePoint Technologies was installed.

To correct the problem do run the PostMSIConfig.exe tool located in the following directory:

\Program Files\MCMS Connector for SharePoint Technologies\CMS\Bin\

This tool will create the table.

[Back to Top]

Topic: Error when reading registry

When I try to use the Content Integration Pack 2 between MCMS 2002 and Microsoft SharePoint™ Portal Server2001 I am having trouble publishing modifications to documents. I can publish the SharePoint document in MCMS the first time, but I am not able to republish the modifications.

I get the following error in the SharePoint Portal Server server event log:

The VB Application identified by the event source logged this Application
VBRuntime: Thread ID: 1580,
Logged: Application Name = The Title is not provided
Method = ReadFromRegistry
UserID = Administrator
Error in reading value from registry,

and

The VB Application identified by the event source logged this Application
VBRuntime: Thread ID: 1576 ,Logged:
Application Name = ModConstants
Method = ReadRegistry
UserID = Administrator

Error in reading value from registry: SPSServerName,

The VB Application identified by the event source logged this Application
VBRuntime: Thread ID: 1572 ,Logged:
Application Name = The Title is not provided
Method = GetWorkSpaces
UserID = Administrator Invalid argument,

The VB Application identified by the event source logged this Application
VBRuntime: Thread ID: 1600 ,Logged:
Application Name = GetWorkSpaces
Method = GetWorkSpaces
UserID = Administrator
Invalid argument,

The VB Application identified by the event source logged this Application
VBRuntime: Thread ID: 1596 ,Logged:
Application Name = SPSCMSAttachments
Method = CheckSubscriptions
UserID = Administrator Failed to create object : GetWorkspaces.ClsWorkspaces,

Answer

To resolve this, go to Control Panel, Administrative Tools, Component Services, Computers, COM+ Applications, and then CIP Common.  In the Identity tab of CIP Common, ensure that the given user is a local administrator.

[Back to Top]

Topic: Error when using SearchSetup.exe

When using SearchSetup.exe, I keep getting the following error:

Error in search setup : Object reference not set to an instance of an object.

Answer

You cannot use "localhost" for the -portalurl parameter. You must specify a server name. Here is an example of the correct usage:

SearchSetup.exe -url "http://localhost/Channels" -user "domain\user" -password "password" -crawl "1" -portalurl "http://servername/"

[Back to Top]

Topic: Error: Could not connect to the Microsoft Content Management Server

After installing Microsoft® SharePoint™ Portal Server, you cannot launch the MCMS Site Manager.

This is the error:

"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"

Answer

You need to ensure that you have excluded the /NR path from Windows SharePoint Services.

[Back to Top]

Topic: Forms authentication

If I install MCMS 2002 and SPS 2003 into the Default Web site, I’m only able to support Windows Authentication. I haven’t been able to get Forms authentication to work on my MCMS site. What could be wrong?

Answer

The reason this does not work is that the SPS web.config file clears all modules and adds back only Windows authentication.

As a workaround you can add the following to the HttpModules section in the web.config file for your application:

<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule"/>

The MCMS site needs to be running as its own virtual application (i.e. not in the root).

[Back to Top]

Topic: How do I configure CMS with Forms Authentication on a Portal Server

After I extend my virtual server to be a Microsoft® Office Microsoft SharePoint™ Portal Server 2003 (Microsoft SharePoint Portal Server) portal, the Microsoft Content Management Server 2002 (MCMS) application running on that virtual server fails to authenticate with Forms Authentication. How do I get around this?

Answer

The problem stems from the fact that all the modules in the Microsoft SharePoint Portal Server web.config are cleared by the <clear /> element and then the WindowsAuthentication HTTP Module is added back in forcing windows authentication to take place since it is now in the ASP.NET request processing pipeline and Forms Authentication no longer exists. Since configuration settings are inheritable, the child directories inherit configuration settings of the parent. As a consequence, your application could inherit some unwanted HTTP modules as part of the parent configuration; therefore, you need a way to remove those unwanted modules or add back in the appropriate ones. Here is the Http Modules section of the Microsoft SharePoint Portal Server web.config

<httpModules>
      <clear />
      <add name="OutputCache" type="System.Web.Caching.OutputCacheModule" />     
      <add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule" />
      <!--<add name="Session" type="System.Web.SessionState.SessionStateModule"/>-->
</httpModules>

You will see they clear it out and then add only WindowsAuthentication back in. There are a couple workarounds:

1. Use the <remove> node in the web.config of your MCMS application to remove the WindowsAuthentication module and then add back in FormsAuthentication as in my example below.
   
   <httpModules>
               <remove name="WindowsAuthentication"  />
   <add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule"/>
   <httpModules>
   
2. Add only the FormsAuthentication module to your MCMS application.
   
   <httpModules>
               <add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule"/>
   <httpModules>
   
3. Modify the Microsoft SharePoint Portal Server Web.Config and add back in the FormsAuthentication module.
   
   

   <httpModules>
         <clear />
         <add name="OutputCache" type="System.Web.Caching.OutputCacheModule" />     
         <add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule" />
   <add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule"/>
         <!--<add name="Session" type="System.Web.SessionState.SessionStateModule"/>-->
   </httpModules>

Note: Using Forms Authentication with MCMS Connector for SharePoint Technologies is not supported. This FAQ topic was created to assist those that are running MCMS and Microsoft SharePoint Portal Server on the same virtual server without the integration piece.

[Back to Top]

Topic: How do I configure MCMS and SPS 2003 to work on the same virtual server

How do I configure MCMS and Microsoft® Office SharePoint™ Portal Server 2003 to work on the same virtual server?

Answer

Please see the following article for information on configuring MCMS and Microsoft Office SharePoint Portal Server 2003 to work together when they are on the same server:

835248 - You experience configuration errors when you run MCMS 2002 and Microsoft Office SharePoint Portal Server 2003 on the same virtual server

[Back to Top]

Topic: How do I create search scopes for MCMS Channels

How do I create search scopes for MCMS Channels using the MCMS Connector for SharePoint Technologies?

Answer

Search scopes allow users to narrow their searches based on the topics, areas, and content sources of items on the portal. The same concept can be applied for your MCMS Channel structure.

There are a few things to take into account when deciding to do this:

1. Creating search scopes for Microsoft® SharePoint™ Portal Server will only work if you enable Advanced Search Administration mode in Microsoft SharePoint Portal Server.
2. You will not be able to utilize this scoping feature from the MCMS Connector for SharePoint Technologies Search Control and will not be able to return a result set from this control using the newly defined indexes.
3. You will be searching from the Microsoft SharePoint Portal Server Search Control which does not do any rights filtering on the MCMS content based on your role.
4. You will not use SearchSetup.exe that ships with MCMS Connector for SharePoint Technologies to setup your content sources as this places everything in the non-portal content index.

Note: The following example assumes you have a MCMS/SPS small farm configuration (single machine deployment) with the CmsSharePointConnector sample data installed.

1. Create two indexes to separate the content
   1. Name index 1 "Internal"
   2. Name index 2 "External"
2. Create the content sources to place in the indexes.
   1. Create a content source called "InternalSource" and place it in the "Internal" index. Map this to http://<server>/CmsSharePointConnector/Internal/.
   2. Create another content source called "ExternalSource" and place it in the "External" index. Map this to http://<server>/CmsSharePointConnector/External/.
3. Crawl and populate the indexes.
4. Create two scopes, one for each source/index and limit the scope to the appropriate content source.

After doing so you will be able to search only internal content or only external content from the sample data using the Microsoft SharePoint Portal Server Search Control.

[Back to Top]

Topic: MCMS and Connector for SharePoint Technologies

The new Connector for Sharepoint Technologies can be integrated with Microsoft® SharePoint™ Portal Server and with Windows SharePoint Services (WSS). What exactly needs to be installed on my MCMS server to use the features of this connector?

Answer

1. MCMS and Microsoft SharePoint Portal Server must be installed on the same machine to author or view a page using a template containing Microsoft SharePoint Portal Server navigation controls.
2. MCMS and WSS must be installed on the same machine to author a page using a template containing the SharePoint library placeholder.
3. Only MCMS is required to view pages created using a template containing the SharePoint library placeholder.
[Back to Top]

Topic: MCMS Template Hyperlink Style Does Not Display Correctly

The MCMS Template Hyperlink Style Does Not Display Correctly for the sample data that ships with the MCMS Connector for SharePoint Technologies.

Answer

When you insert a WordML document inline using the SharePoint library placeholder, the style used for all hyperlinks on the page may use the default style of underlined blue or purple, even though you specified a different style in the MCMS template. This happens because the style output by the WordML style sheet in MCMS Connector for SharePoint Technologies is hard-coded to use the default style. To resolve this, open the .xslt file for WordML documents and change or remove the following code:

a:link {color:blue;text-decoration:underline;text-underline:single;}
a:link {color:purple;text-decoration:underline;text-underline:single;}

Note: This is documented in the MCMS Connector for SharePoint Technologies Readme file.

Another workaround would be to add the !important clause to the following entry in the SPS.CSS stylesheet located in the following directory: \Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\LAYOUTS\1033\STYLES. This forces the required style to be applied to the main menu links and prevents you having to touch any documents.

.ms-phnavtableone a
{
  font-family: Tahoma;
  font-size: 8pt;
  font-style: normal;
  font-weight: bold;
  color: #666666!important;
  text-decoration: none;
}

This change prevents a later defined <A> class from overriding the style.

[Back to Top]

Topic: SearchPropertyCollection.xml and Custom Properties

I set the PropertyType property of the SearchMetaTagGenerator to be PropertiesFromXMLFile. When viewing the meta tags generated by the SearchMetaTagGenerator control - on postings based on this template - no custom properties appear. Only the standard properties from the xml file are listed. What am I doing wrong?

Answer

The help document for the MCMS Connector for SharePoint Technologies incorrectly describes how you should modify the SearchPropertyCollection.xml file. To fix this, for each custom page property that you want the SearchMetaTagGenerator control to output, add the following line to the .xml file:

<PropertyDefinition uri="urn:schemas.microsoft.com:htmlinfo:metainfo:<custom property name>" type="string" name="<custom property display name>" PropertyName="<custom property display name>"  indexable="1" retrievable="1" />

Note: The help document omits the PropertyName attribute which is required.

[Back to Top]

Topic: SharePoint Portal Server and Secure Sockets Layer

When modifying the properties of my web part, the following error appears:

"This page contains both secure and nonsecure items."

Answer

If your SharePoint Portal Server site is accessed through Secure Sockets Layer (SSL), the following warning may appear when you edit the custom properties of the MCMS Page Listing Web Part: "This page contains both secure and nonsecure items." To resolve this, set your MCMS server to use SSL, and in the MCMS Page Listing Web Part Site URL text box, use https://.

Note: This is documented in the readme file.

[Back to Top]

Topic: SharePointDocumentPlaceholderDefinition not available in Placeholder Definition Editor in VS.NET

We installed MCMS 2002 Connector for SharePoint Technologies on our development server. We are able to use the sample content and templates to add an XML document from a SharePoint site and display it inline as HTML in the MCMS page. However, we are not able to add a SharePoint Document placeholder definition using the Placeholder Definition Collection Editor in Visual Studio .NET. When I click the arrow to the right of the Add button, I see several choices for different placeholder definitions to add, but there is no
SharePointDocumentPlaceholderDefinition choice. I

What could be the problem?

Answer

Please check in the Microsoft.ContentManagement.Publishing.config file and if the SharePointDocumentPlaceholderDefinition has been added by the installation process.

[Back to Top]

Topic: SPS Sites do not show in the SharePoint Library Document Finder Dialog

When browsing for Microsoft® SharePoint™ Portal Server "Sites" in the SharePoint Library File Finder for MCMS Connector for SharePoint Technologies, my SPS "Sites" do not appear in the "Sites" node of the treeview control. In fact, nothing appears.

Answer

This is a WSS behavior and it is by design. The current implementation performs the following: 

• It enables easy access to any "Site" [SPWeb/SPS area] within the current "Site Collection" [SPSite/SPS portal] that the MCMS page is running under.  This current site collection is selected by default and the "…" browse button will allow you to select a site from the tree view.
  
• The sites created using the Microsoft SharePoint Portal Server "Create site" features described below are each different "site collections" of WSS team sites that are somewhat accessible and connected to the Microsoft SharePoint Portal Server portal, but not part of the same "site collection" as the portal.
  
• For any Site [SPWeb] accessible through the object model on that server, whether or not it is on the current site, you can paste in a URL to that site and the doc finder dialog will be able to find it and list the doc libs and files in that Site.  This allows access to anything you cannot browse to and also allows quick access to things on the current site collection without browsing.
  
• If you want to restrict document selection for a specific placeholder control to only allow docs from one site [SPWeb] then you can specify it in the calatog.xml file for that placeholder control.  In that case the dialog will initialize already pointing to that location and no browsing will be required.  (details are in the customization docs)

The idea is that, by default, browsing will help you select docs from the current site collection and it will help you get access to any accessible site collection.

Another noteworthy comment here is that a server can handle thousands of SPS "Sites". The dropdown box or treeview control would not be a good delivery method for this.

[Back to Top]

Topic: The search engine was unable to process your request

I have Microsoft® SharePoint™ Portal Server 2003 and MCMS 2002 installed on seperate machines. I've installed Microsoft Content Management Server 2002 Connector for SharePoint Technologies and when I try to search using the search control, the following is returned:

Search Status: The search engine was unable to process your request. This problem may be the result of a query that only contains common words, such as "a","the", or "about", which are ignored by the search engine, or you do not have sufficient search privileges.

Answer

This problem most likely occurs because you have not assigned search rights to the application pool identity account that your MCMS application runs under. Please see the "Assigning Search Rights to the Application Pool Identity Account" section in the help file. This is also documented in the installation guide.

[Back to Top]

Topic: The virtual server that is referenced here is not in the config database

I get the following error when clicking on a SharePointDocumentPlaceHolder control in a new page:

Server Error in '/CmsSharePointConnector' Application.
--------------------------------------------------------------------------------

The virtual server that is referenced here is not in the config database.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: The virtual server that is referenced here is not in the config database.


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

Answer

This is a configuration problem in your environment. If you install Microsoft Content Management Server 2002 (MCMS) and SharePoint Portal Server (SPS) or Windows SharePoint Services (WSS) on the same computer, you must also install them on the same virtual server (a virtual server is equivalent to an IIS Web site).

MCMS and SPS/WSS can either be installed on the same virtual server (Web site), or different virtual servers on different boxes, but not different virtual servers on the same box.

Please refer to the installation docs that shipped with the MCMS Connector for SharePoint Technologies.

See also:

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

[Back to Top]

Topic: Why are my documents not synchronized between CMS and SPS

How do I keep Microsoft® SharePoint™ Portal Server documentation in MCMS pages synchronized? I have set the checkboxes in the Microsoft SharePoint Portal Server placeholder to keep the content synchronized, but it doesn't seem to work. I update the document in SharePoint Portal Server, but do not get the new version in MCMS. Does this happen automatically or is there a tool that needs to be run?

Several places mention the Data Synchronization tool to synchronize SharePoint Portal Server documents that have been included in MCMS pages. In other words, the tool with pull the newest version of the document from SharePoint Portal Server into MCMS; however, I cannot find this tool.

Answer

You must synchronize the documents that you copy into MCMS 2002 with the Microsoft SharePoint Portal Server document placeholders that change in the Windows SharePoint Services environment. To update the documents you must run the WssDocumentUpdater tool in the folder where MCMS 2002 is installed.

For example: C:\Program Files\Microsoft Content Management Server\Server\bin\WssDocumentUpdater.exe.

You can run the WssDocumentUpdater tool from the command line, or you can use Windows Task Scheduler or a similar service to run it on a regular basis.

Note: Only those documents that you specify to synchronize when you attach a Windows SharePoint Services document to a SharePoint placeholder will synchronize.

You can schedule your document synchronization on a regular basis. You may want to adjust this based on how often they are modified in your SharePoint libraries. If you make a lot of modifications, it is recommended that you synchronize your documents on a daily basis. If you modify your documents infrequently, you can schedule them to run on a weekly basis.

[Back to Top]

Topic: You have not specified a valid Channel

When I am configuring the custom properties of my Page Listing Web Part in the Microsoft Content Management Server (MCMS) 2002 Connector for SharePoint Technologies, it always throws the following error when choosing a channel:

You have not specified a valid Channel

Answer

This can be caused by any of the following:

• Having the "Map Channel Names to Host Header Names" feature enabled in the Server Configuration Application (SCA) for MCMS 2002.
• Specifying an invalid path to your channel.
• Specifying an invalid channel name or a name that does not exist.
• Incorrect syntax for the path that is required. The syntax should be in the form of "/ChannelName/"

Please also see the following:

831796 - The Map Channel Names to Host Header Names feature is not supported


[Back to Top]

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2004 Microsoft Corporation. All rights reserved.

Microsoft, ActiveX, Visual Studio, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.