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 - Installation FAQ - Table of Contents

Can MCMS 2002 be installed in unattended mode?
Credentials are not accepted in DCA on Windows XP
DCA log
Disconnected Laptop
Error message: "Need Server Side Includes"
Error Message: "Please uninstall older version of Content Management Server"
Installing MCMS 2002 without JavaVM
MCMS and Windows Server 2003 Web Edition
Roll back when installing Woodgrove sample site
Visual Studio .NET 2003 not recognized

Topic: Can MCMS 2002 be installed in unattended mode?

Can MCMS be installed in unattended mode?

Answer

From the MCMS 2002 readme:

Unattended installation is not supported. The option to install MCMS 2002 unattended is not provided for this release.

[Back to Top]

Topic: Credentials are not accepted in DCA on Windows XP

My credentials are not accepted when trying to enter the system account in the Database Configuration Assistant on Microsoft Windows® XP. What could be wrong?

Answer

This is an issue with the default XP security policy. To fix it, go to your Local Computer Policy and click Computer Configuration, Windows Settings, Security Settings, Local Policy, and then Security Options.

Change the "Network access: Sharing and security model for local accounts" setting to "Classic - local users authenticate as themselves".

[Back to Top]

Topic: DCA log

Where can I find a log of the Database Configuration Application (DCA)?

Answer

The default location for the DCA log is:

<system_drive>:\Program Files\Microsoft Content Management Server\LogFiles

[Back to Top]

Topic: Disconnected Laptop

I would like to install MCMS on my laptop and be able to use it even if I am not connected to any networks. However, when I try to login to the Site Manager I get an error that the "local security authority cannot be contacted".

Answer

These steps will allow you to use MCMS while disconnected from any network:

1. Connect to network and install MCMS.
2. Use a local account as the 'CMSSystem' account.
3. Add the local machine as a supported domain in the Server Configuration Application (SCA).
4. Add a local account as an MCMS administrator.
5. Disconnect from the network.
6. Login to MCMS as the local administrator account.
[Back to Top]

Topic: Error message: "Need Server Side Includes"

When I try to install the MCMS client I get an error message.

Installation Failed and the changes were reversed.
Need Server Side Includes (required by MCMS Server)


How can I resolve this?

Answer

You need to install the 'Server Side Includes' component in Windows.

Here are the steps to resolve this issue:

1. Start -> Control Panel  -> Add or Remove Programs
2. Choose 'Add/Remove Windows Components'
3. Application Server -> Details -> Internet Information Server (IIS) -> Details -> WWW Web Service -> Details -> Add 'Server Side Includes'
[Back to Top]

Topic: Error Message: "Please uninstall older version of Content Management Server"

We encountered problems installing MCMS with SP1a on Windows Server 2003. After running the DCA to set up the database, attempted to install Site Manager and received this error "Please uninstall older version of Content Management Server before install this Microsoft Content Management Server SP1a".

We have no older version of MCMS or any other CMS. Installation of MCMS with SP1a went smoothly on our development and staging servers, but failed on our production server. All have the same configuration.

So, we attempted to uninstall MCMS with SP1a via Control Panel and Add/Remove Programs and received exactly the same error message. Any help would be appreciated.

Answer

The error message can be misleading.

Please check if you find the following event log entries in the Application Event log:

"Error 1719. The Windows Installer service cound not be accessed"

If this entry is listed, please use the procedure below to resolve the problem:

Unregister and then reregister Windows Installer

1. Unregister Windows Installer:
1. Click Start, and then click Run.
2. In the Open text box, type msiexec /unregister, and then click OK.
3. Verify the Windows Installer service is NOT listed under Computer Management - Services.
   
2. Reregister Windows Installer:
1. Click Start, and then click Run.
2. In the Open text box, type msiexec /regserver, and then click OK.
3. Verify the Windows Installer service IS listed under Computer Management - Services.
   
[Back to Top]

Topic: Installing MCMS 2002 without JavaVM

When installing MCMS 2002 I'm asked to install the Microsoft® JavaVM. As this component cannot be downloaded any more, how can I install MCMS 2002?

Answer

The JavaVM is only required by the Site Manager and Site Stager in the original version of the MCMS 2002. MCMS 2002 Service Pack 1a ships with a version of these components which do no longer require the JavaVM.

[Back to Top]

Topic: MCMS and Windows Server 2003 Web Edition

Is it possible to use MCMS 2002 on Windows Server 2003 Web Edition?

Answer

No. It is a licensing violation to use MCMS 2002 on Windows Server 2003 Web Edition.

[Back to Top]

Topic: Roll back when installing Woodgrove sample site

At the end of the Woodgove sample site installation process, the setup rolls back for some unknown reason. The following event is getting added to my event log: 

Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11708
Date:  10/20/2003
Time:  1:51:56 PM
User:  N/A
Computer: TIMOL-DEV
Description:
Product: Microsoft Content Management Server Sample Data -- Installation operation failed.

Any idea what might have happened?

Answer

This can happen when you install the sample site on a different Web site as the Default Web Site. This is not officially supported. Also ensure that you did not rename the Default Web Site to another name.

The workaround is to copy the files from another machine onto <CMS_Root>\Sample Data\ manually, and then manually create the web application mapping. The files under the <Cms_Root>\Sample Data\ hierarchy are basically Microsoft Visual Studio® .NET project files.

The next step is to create a web application named "WoodgroveNet" (i.e. the original MCMS template project name) under the root of the Web site where MCMS is installed and map it to <Cms_Root>\Sample Data\WoodgroveNet\.

Then create a virtual directory named "CMS" and map it to: <Cms_Root>\Server\IIS_CMS\ (under the root of the WoodgroveNet web application). This "CMS" virtual directory (ensure that it is not a web application) is required. Without it, you will have problems switching to edit mode using Web Author.

After this has done, you should be able to browse the WoodgroveNet sample site as http://<ServerName>/WoodgroveNet.

[Back to Top]

Topic: Visual Studio .NET 2003 not recognized

I currently have Microsoft® Visual Studio® .NET 2003 installed. I am trying to install MCMS 2002 but I keep receiving the following error message:

"Microsoft Visual Studio .NET not found (needed by Dev Tools)"

Answer

Microsoft Visual Studio .NET 2003 is not recognized by the MCMS 2002 installer because this product was not out when MCMS 2002 was released. Microsoft Visual Studio .NET 2003 support is added with MCMS 2002 SP1.


To get around this problem do the following:

1. Install MCMS 2002 server component only (no Site Manager, no Site Stager, no Developer Tools)
   
2. Install MCMS 2002 SP1. The SP1 install will give you the chance to install updated versions of the above components including Microsoft Visual Studio .NET 2003 support.
   
   - or -
   
   Install MCMS 2002 SP1a. After installing this service pack use Control Panel - Add/Remove Programs - Select MCMS in the list - use the change option to install the missing components now.
[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.