Upgrading Express Reports to Version 5.0 Using the Command Line
Technical Note 1327
Last Reviewed 14-Dec-2000
Applies To
Express Software Manager version 4.x
Summary
This technical note describes how to upgrade the Express reports database (Express.mdb) to version 5.0 using a command line. The command-line option allows you to use a scheduling tool to run the upgrade program during off-peak hours.
Reasons to Upgrade Express Reports
Express Reports are generated using a Microsoft Access database, Express.mdb, which contains both reporting logic and user data. By upgrading Express reports to version 5.0, you can
- Retain your data -- with your customized reports.
- Run three new Business Answers reports available in 5.0 using the data you have already collected:
- Unused Software by Machine
- Unused Software by Application
- Migration Planner
Reasons to Use the Command Line to Upgrade Reports
The upgrade program requires exclusive access to the library. Only one library can be upgraded at a time, and the process can be time-consuming. Although the Upgrade Reports program can be run from the Library Maintenance Tool in Express Console (see Technical Note 1254), this method may not be convenient during off-peak hours.
Alternatively, you can run the Express Reports upgrade program as a command line option and use an administrative scheduling tool (such as the AT command in Windows NT) to automate the process during off-peak hours.
Running the Express Reports Upgrade Command
The Express Reports upgrade program is contained within the Exclean.mdb file on the Express Console machine. (Exclean.mdb is the template used to create a new Express library database.)
Before running the upgrade command, determine which libraries need upgraded reports and when you want to run the upgrade.
CAUTION: Before you upgrade, turn off OpenGL screen savers on all Express Console and Express Enterprise Services machines. (Some 3D OpenGL screen savers consume the majority of the CPU cycles, causing Express performance to slow down dramatically.)
Determining the Libraries That Need Upgraded Reports
The Upgrade Reports program should be run on every Express library that uses Microsoft Access to generate reports. Follow these guidelines.
Parent Libraries: If you consolidate data from child libraries into a parent library for reporting, upgrade the reports in the libraries (parent or grandparent) from which Access reports are run.
Child Libraries: If you run reports from a linked child library, upgrade the reports in the child library as well as the reports in the parent library.
Express Reports for Microsoft SQL Server: If you export data to a Microsoft SQL server for reporting, you do not need to upgrade the Access reports in these libraries (because Express.mdb is not used for SQL reports).
Note: If you do not upgrade a library's reports (Express.mdb), you will not be able to use Express Console 5.0 to view a machine's configured applications (in the Properties dialog box) from a previous library. You can, however, view that information in the library's Software Inventory by Machine report.
Using the Library Maintenance Tool to Detect Libraries
To identify the parent and child libraries, use the Auto-detect feature in the Library Maintenance Tool. Follow these steps:
- On the Tools menu in Express Console, point to Library, and click Library Maintenance Tool.
- On the Actions menu, click Auto-Detect Libraries.
- Select all of the libraries (or click the Check All button).
- On the Actions menu, click Check Versions of Reports.
The tool lists all of the detected libraries and whether they need to be upgraded. The parent and child libraries are displayed in a tree structure. Click the [+] to view the related child libraries.
- Using the list, note which libraries run reports from Microsoft Access. If you are not sure, open each library in Express Console, and click Library Properties on the File menu.
- On the Consolidate tab, look for the parent and related child libraries.
- On the Export tab, check whether the data is exported to a SQL server. If the data is exported to an ODBC database, Express reports do not use Microsoft Access, and the Express.mdb does not need to be updated.
Close the Library Maintenance Tool.
Determining When to Run the Upgrade Program
Express Metrix recommends upgrading Express.mdb during off-peak hours when clients are not logging data and the libraries are not being updated or consolidated (by Express Library Manager or Express Console). If the Upgrade Reports program encounters a locked object, the upgrade will stop. You will need to determine when the upgrade program could have exclusive use of the database.
Verifying that a Printer Driver is Installed
To successfully run the upgrade command, a printer driver must be installed on the machine (usually a file server) where Express.mdb is located. This is a Microsoft Access requirement.
Entering the Command
Use the machine where Express Console version 5.0 is installed to run the command. Follow these steps.
- Choose a library to upgrade. In Express Console, close the library (if it is not already closed).
- Back up the existing library. (Copy the existing Express.mdb and rename it.)
- Create a text file on the library server, named Upgrade.log for instance, that will record the success or failure of the upgrade. The path to this file will be used in the command line.
- From the Start menu, click Run. Enter the command line syntax (below) on one continuous line. Include the quotation marks and enter the angle brackets without spaces.
MSAccessPath "ExcleanPath" /Cmd "Upgrade<DestDBPath><ExpressLogPath><DBDesc>"
- Replace the text in the command above with the information described in the table below.
Replace this text...
|
...with this information
|
MSAccessPath
|
Full path to Microsoft's Msaccess.exe (on the Express Console machine)
|
ExcleanPath
|
Full path to the Express Exclean.mdb (on the Express Console machine)
|
DestDBPath
|
Full path to the Express Reports database to be upgraded
|
ExpressLogPath
|
Full path to the Express upgrade log, a simple text file (created in step 3) located in the library on the server
|
DBDesc
|
Optional database description or comment
|
Follow this example: This command would upgrade Express Reports for a library's Access database located in L:\Express.mdb and write to a log file in L:\Upgrade.log:
C:\progra~1\Micros~1\office\msaccess.exe "C:\Progra~1\WRQ\Expres~1\Exclean.mdb" /Cmd "Upgrade<L:\Express.mdb><L:\Upgrade.log><My5_0database>"
- Verify the correct paths for the four required parameters. If any of the paths are incorrect, the process will stop without beginning the upgrade.
- Open the Upgrade.log to verify whether the upgrade process succeeded or failed.
- Repeat steps 1-8 to upgrade the database in each library that uses Microsoft Access to generate Express Reports.
If the Upgrade Fails
The two most common reasons for a failed upgrade are the absence of a printer driver and a corrupt Exclean.mdb file. If the upgrade fails, as noted in the Upgrade.log, trouble shoot as follows:
- Verify that a printer driver is installed on the server where Express.mdb is located.
- On the machine where Express Console is installed, replace Exclean.mdb with the original Exclean.mdb from the Express Software Manager product CD.
- Run the Reports Upgrade program again on the same Express.mdb. Choose a time when no clients are logging data and when the data is not being updated or consolidated. If the upgrade failed because the tool did not have exclusive access to the library, the upgrade program will repair and upgrade the Express.mdb the next time you run it.
- Open Expupgd.log, located in the same directory as the Express.mdb file (DestDBPath) that you entered in the command line. This text file is created by the upgrade program and records details about where the failure occurred.
- If you need to contact Express Metrix technical support, be prepared to send the Expupgd.log file.
Related Technical Notes
| 1254 |
Upgrading to Express Software Manager 5.0 |
| 9989 |
Express Software Manager Technical Notes |
|