Troubleshooting Projectwise DMSCONV issues

Overview: When a new version of Projectwise is released, there are often updates to the database schema. This requires the user to run the DMSCONV.exe when upgrading to the latest version.

This document will describe steps for logging and troubleshooting errors if the database conversion (DMSCONV) fails.

Products and versions:

• Projectwise Design Integration Server, all versions.
• Projectwise Administrator, all versions

Pre-requisites \ Assumptions \ Preliminary setup:

• Before upgrading, it is best practice to setup a test environment to run through the database conversion (DMSCONV).
• Items needed
  • Windows server compatible with the version of Projectwise you are upgrading
  • Projectwise Integration and Administrator installed on the test machine
  • A copy of your production database restored to a compatible database server with the version of Projectwise you are upgrading.
  • Administrative login to the Integration test server.
  • Access to the SQL or Oracle Server managers for viewing tables if needed.
• Knowledge and experience
  • DOS commands
  • setup an ODBC connection from integration server to database server.
  • Use of SQL or Oracle Management interface
  • Reading log files and understanding SQL statements

Steps

Configure logging The DMSCONV utility can log the actions it takes when converting the database. The resulting log can help when troubleshooting issues.

• Go to C:\Program Files\Bentley\ProjectWise\bin and open dmsconv.log.xml in notepad.
• Set the following priority values to ALL, then save and exit the file.

<category name="pwise.database.schema">        <priority value="ALL"/>

<root>        <priority value="ALL" />

Running DMSCONV

Detailed steps for running the dmsconv utility are in the Projectwise Implementation guide

Review the Log

1. After running the DMSCONV utility go to the C:\Users\Public\Bentley\Logs and open the dmsconv.log file in notepad or your favorite ascii text editor.
2. Scroll to the bottom of the file to see the status of the dmsconv and any error messages.

Known issues

1. Dmsconv fails because of a custom index.

Remove any custom indexes before running dmsconv. The custom indexes can be added back to the database once the database has been successfully converted.

1. Dmsconv fails to run because of an incorrect username or password

See Also