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

Credentials are not accepted in DCA on Windows XP
DCA log
Error message: "ActiveX component can't create object"
Error message: "Cannot create a file when that file already exists"
Error message: "error '76' - Path not found"
Error Message: "Failed to get connection string from ODBC."
Error message: "Invalid column name 'ID'"
Error message: "Method '~' of object '~' failed"
Error message: "Must Declare the varible @InsertedParentGuid"
Error message: "Rollback transaction request has no corresponding begin tran"
Error message: "Run-time error '91' - Object variable or With block variable not set"
Error message: "The roll back transaction request has no corresponding begin transaction"
Error message: "User or role 'CMSSystem' already exists in current database"
GPF in DCA
SQL Server database not available in the DCA

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: Error message: "ActiveX component can't create object"

The DCA fails with the error message: "ActiveX component can't create object" or "automation error". What could be wrong?

Answer

The DCA requires Windows Script version 5.6. This error message occurs if Windows Script 5.6 is not correctly installed.

Either reinstall Internet Explorer 6 SP1 or download Windows Script 5.6 from the following location and reinstall it:

http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?url=/msdn-files/027/001/733/msdncompositedoc.xml

Attention: this is necessary even if Windows Script 5.6 is already installed on the server.

[Back to Top]

Topic: Error message: "Cannot create a file when that file already exists"

When running the SCA or DCA, the following problem may be encountered:

An unknown error has occured
800700b7: Cannot create a file when that file already exists.
-2147024713
(ISOK File nrvirtualWeb site.cpp, Line 2335)

Answer

MCMS is trying to create an Internet Information Services (IIS) Metabase entry that already exists.

To resolve this problem remove the NR, CMS and/or MCMS virtual directory on the Web site you are trying to set the entry point to. Then run the SCA or DCA again.

[Back to Top]

Topic: Error message: "error '76' - Path not found"

After installing a hotfix, the DCA doesn't start up anymore - we get an error saying "error '76' - Path not found". The event log then shows some sort of VB error occured. We've tried un-installing the hotfix, but that does not fix the problem.

How can we get the DCA working again without re-installing MCMS?

Answer

This is a known problem with some hotfixes if your MCMS installation path differs from the standard path C:\Program Files\Microsoft Content Management Server.

Please ensure that the following registry keys points to your MCMS installation directory:

\HKLM\Software\NCompass\CmsInstallLocation
\HKLM\Software\NCompass\Resolution Content Server\dir

[Back to Top]

Topic: Error Message: "Failed to get connection string from ODBC."

I am getting the following error when I run the DCA. It occurs when I click the "Select Database" button. It appears as a popup, and in the event log as a VBRuntime error. Failed to get connection string from ODBC.

Failed to get connection string from ODBC.
Extended error: [What='Error in getting the ODBC connection'][LCID='1033'] [SourceFile='establishodbcconnection.cpp'][SourceFileLine='143'][DebugInfo=''][RecommendedAction=''] [ExtraInfo=''][UniqueErrorId='1'][Severity='5'][Source='NRDBHelper.dll'][CategoryId='0'] -2147352567 NRDBHelper.dll

How can I solve this problem?

Answer

There are two known reasons for this:

1. the user running the DCA does not have the SeImpersonatePriviledge
   
   

   To assign impersonation privileges

   1. Click Start, click Control Panel, click Administrative Tools, and then click Local Security Policies.
   2. In the Local Security Settings window, expand Local Policies, click User Rights Assignment.
   3. In the User Rights Assignment folder, right-click Impersonate a client after authentication, and then click Properties.
   4. In the Properties dialog box, click Add User or Group.
   5. In the Select Users, Computers, or Groups dialog box, add the appropriate user or group, and then click OK.
   6. In the Properties dialog box, click OK.
      
2. There is a known bug in MCMS. Please request the following hotfix from Micrsoft support:
   
   836259 - You receive an error message in the DCA when you select a database
[Back to Top]

Topic: Error message: "Invalid column name 'ID'"

When configuring a new MCMS database using the DCA I receive the following error:

Database creation failed
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'ID'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'ID'.
207
Microsoft SQL-DMO (ODBC SQLState: 42S22)

How can I correct this problem?

Answer

This problem can happen if the DCA is run against a SQL database that has been configured with case sensitive database collation.

MCMS only supports databases with case insensitive collation.

[Back to Top]

Topic: Error message: "Method '~' of object '~' failed"

When the DCA is being run during the installation, I receive the following error message: "Method '~' of object '~' failed". What is the problem?

Answer

This can happen when Windows Script is not installed correctly or the latest version is not installed.

Please re-install the latest version from here: http://msdn.microsoft.com/scripting.

[Back to Top]

Topic: Error message: "Must Declare the varible @InsertedParentGuid"

After running the Database Configuration Application (DCA), the database population process stops with the following error message:

Database creation failed [Microsoft][ODBC SQL Server Driver][SQL Server]Must Declare the varible @InsertedParentGuid'. -2147221367 Microsoft SQL-DMO(ODBC SQLState : 42000)

Answer

This could be caused by case-sensitive collation or locale settings on the SQL server. Ensure that you are using case-insensitive SQL Server settings.

[Back to Top]

Topic: Error message: "Rollback transaction request has no corresponding begin tran"

While running the conversion from MCMS 2001 to MCMS 2002 I get the following error:

-2147217601 ('80040f3f')
Rollback transaction request has no corresponding begin tran

What can be causing the problem?

Answer

This can happen when the transaction log file is full.

Extend the transaction log to increase without limit and try the upgrade again.

[Back to Top]

Topic: Error message: "Run-time error '91' - Object variable or With block variable not set"

The DCA fails with the error "Run-time error '91'  - Object variable or With block variable not set". What could be wrong?

Answer

The DCA requires Windows Script version 5.6. This error message occurs if Windows Script 5.6 is not correctly installed.

Either reinstall Internet Explorer 6 SP1 or download Windows Script 5.6 from the following location and reinstall it:

http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?url=/msdn-files/027/001/733/msdncompositedoc.xml

Attention: this is necessary even if Windows Script 5.6 is already installed on the server.

[Back to Top]

Topic: Error message: "The roll back transaction request has no corresponding begin transaction"

When migrating my CMS 2001 database to CMS 2002 about 12% into the upgrade it gives the fiollowing runtime error:

2147217601 (80040f3f),
[microsoft] [odbc sql server driver] [sql server] The roll back transaction request has no corresponding begin transaction.

How can I correct this problem?

Answer

The upgrade routine tries to create a role named "CMSSystem" in the database. If a user with the same name already exists this problem occurs.

To resolve the problem, open the SQL Server Enterprise Manager and go to the Users of the selected database. Delete the user named "CMSSystem".

After the installation is complete you can create the account again, but it is recommended that you do not use the name "CMSSystem".

[Back to Top]

Topic: Error message: "User or role 'CMSSystem' already exists in current database"

After upgrading to MCMS 2002 SP1, I get the following error message while running the DCA:

Error encountered applying script C:\Program Files\Microsoft Content Management Server\Server\Setup Files\SQL Install\_Sp1Upgrade.sql
[Microsoft][ODBC SQL Server Driver][SQL Server]User or role 'CMSSystem' already exists in current database.
-2147206481
Microsoft SQL-DMO (ODBC SQLState: 42000)

What could be wrong?

Answer

The upgrade routine tries to create a role named "CMSSystem" in the database. If a user with the same name already exists this problem occurs.

To resolve the problem, open the SQL Server Enterprise Manager and go to the Users of the selected database. Delete the user named "CMSSystem".

After the installation is complete you can create the account again, but it is recommended that you do not use the name "CMSSystem".

[Back to Top]

Topic: GPF in DCA

When running the DCA setup I encountered a General Protection Fault (GPF). It happened in the stage "Select Database". This is repeatable on two Windows XP machines, and all patches are applied to both Microsoft Windows XP and Microsoft SQL Server™ 2000.

Answer

The machines had PGP (encryption of disks, mails etc) installed for securing project documents. Once PGP was uninstalled, and Windows Script 5.6 was reinstalled, the DCA worked.

Download Windows Script 5.6 from the following location and reinstall it:

http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?url=/msdn-files/027/001/733/msdncompositedoc.xml

[Back to Top]

Topic: SQL Server database not available in the DCA

Is there any reason why a SQL Server Database would not appear in the Database drop down list of the DCA? I've created a new Database using SQL Server Enterprise Manager and I can’t select it from the DCA because it isn't in the list.

Answer

There are 2 tasks involved when running the DCA. There are also 2 scenarios to consider.

Scenario 1 (Using trusted connection):

1. The user who runs the DCA needs db_owner permission to the MCMS database
   
2. The MCMS system account (i.e. trusted connection) needs db_ddladmin (for SiteDeployment), db_datareader, db_datawriter for MCMS day-to-day operations
   
3. The DCA uses the desktop user (who runs the DCA) to access the database and assign database permissions to the MCMS system account

Scenario 2 (Using SQL Login):

1. The SQL Login needs db_owner permission to the MCMS database
   
2. The SQL Login needs db_ddladmin (for SD), db_datareader, db_datawriter for MCMS day-to-day operations
   
3. DCA uses the SQL Login to access the database and assign database permissions to the SQL Login

Hence, the db_owner permission is needed for assigning permission to the account which performs MCMS day-to-day operations. That MCMS system account needs db_ddladmin, db_datareader & db_datawriter.

[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.