Symptoms

When you attempt to export a report to Excel, Excel Record, or RTF format, the export fails with the following error message:

Cause

This error is caused by a problem with the Crystal Reports runtime components used by Report Commander.

Resolution

This problem can be resolved by modifying the PATH environment variable for the computer.

If Report Commander is installed on a 32-bit computer, add the following to the end of the PATH variable:

; C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86

If Report Commander is installed on a 64-bit computer, add the following instead:

; C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86

If you currently have a command prompt window open that you are using to run Report Commander, you must close it and open a new command prompt window so that the new path takes effect.

Symptoms

The Report Commander setup program fails with the following error message:

If you click the Ignore button, the error is repeated for many additional DLLs.

Cause

This error occurs because the computer is missing some shared software components that are required by the Crystal Reports runtime.

Resolution

Abort the Report Commander installation. Then download and install the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86). Then rerun the Report Commander installation.

Note: You should install the x86 components linked to above, even if you are running a 64-bit version of Windows. This is because Report Commander and the Crystal Reports runtime components run as 32-bit, and therefore require the 32-bit version of the libraries.

Status

• Report Commander
  Arcana Development is currently investigating this issue.

Symptoms

When you export a report to HTML 4.0 format and send it by e-mail using the Use the report output as the message body option, the report may not appear to be formatted correctly when viewed in some e-mail clients (such as Outlook 2007).

Cause

When you export using HTML format, Crystal Reports makes extensive use of dynamic positioning and other CSS attributes to format the HTML. The Outlook 2007 client (and some others) ignore much of the formatting code and therefore display the output incorrectly.

Workaround

There are two workarounds for this problem:

1. Send the report output as an attachment, rather than as the body of the e-mail message. When the recipient opens the attachment, it will be opened by the recipient's Web browser, which will display the HTML correctly.
2. Choose the "HTML 3.2" format instead of "HTML 4.0." With this older HTML standard, Crystal Reports does not use CSS positioning, and the report will display better in affected e-mail clients.

Status

Symptoms

When you export your report to the CSV format, an empty file is created. If you export to another format (such as PDF), the data appears.

Cause

This can occur if your report is designed so that there is no data being displayed in the Detail section, or so that the Detail section is suppressed, and are instead displaying data in a group header or footer.

Resolution

You must select the correct formatting option so that Report Commander will include the headers and footers in the export file.

On the command line, use the option "-csvstyle=crstyle" to accomplish this.

In the Command Line Builder, select the "Crystal Reports default" setting in the "Section Export" section of the CSV Export Options page.

Summary

If you install Report Commander version 1.4 or 1.5 on a computer where Crystal Reports 2008 is installed, Crystal Reports may subsequently fail to start due to DLL errors.

More Information

Report Commander 1.4 and 1.5 install the Crystal Reports 2008 SP2 runtime components, which includes files that are also shared by the Crystal Reports 2008 standalone product. If your Crystal Reports 2008 installation is not at Service Pack 2 or later, this will result in a mix of DLL versions that will break Crystal Reports 2008.

To resolve this problem you must install Crystal Reports 2008 SP2 or later. Alternatively you can remove Report Commander and reinstall the Crystal Reports 2008 base product.

Obtaining Crystal Reports 2008 SP2

Crystal Reports 2008 SP2 can be downloaded from SAP at here. Note that it may be necessary to first install SP1 (available here) if you have not already done so.

To determine which version of Crystal Reports 2008 you have installed, select the About box on the Help menu and refer to the version number:

• Original Crystal Reports 2008 RTM: 12.0.0.549
• Service Pack 0: 12.0.0.683
• Service Pack 1: 12.0.0.892
• Service Pack 2: 12.2.0.290

Many users have reported that the service pack installation takes an extremely long time to complete (several hours in some cases).

We cannot provide assistance with installing and configuring Crystal Reports.

Summary

This article discusses issues you may encounter when using Report Commander in a 64-bit environment.

More Information

Because the Crystal Reports runtime components that Report Commander uses are only available in a 32-bit version, Report Commander installs and runs as a 32-bit application when it is installed on computers running 64-bit versions of Windows.

This can have implications for database client installation and configuration, as discussed in the following sections.

ODBC Aliases

Windows maintains separate ODBC configuration information for 32-bit and 64-bit applications. When you run the default ODBC administrator from the Windows Control Panel, this configuration only applies to 64-bit applications. Any ODBC aliases defined here will not be available to Report Commander, causing Report Commander to issue a "failed to open connection" error.

If your report uses an ODBC connection, you must configure your ODBC alias using the 32-bit version of the ODBC configuration tool. To run this tool, run "c:\windows\sysWOW64\odbcad32.exe" from Start/Run or a command prompt. Then configure the alias as required.

Oracle Client

If your report connects to an Oracle database, you must install the Oracle database client on the computer where Report Commander runs. For Report Commander to work on a 64-bit computer, you must install the 32-bit version of the Oracle client.

It is possible to install both the 32-bit and 64-bit clients on the same computer. If both are installed, your environment must be correctly configured to use the 32-bit version before you run Report Commander. To do this, the ORACLE_HOME environment variable must be set to the 32-bit home directory, and the PATH environment variable must include the "bin" directory below the 32-bit home directory.

Some customers have reported that Report Commander fails when run against the 32-bit Oracle 10.2 client. In these cases, Report Commander has worked successfully after installing the 32-bit Oracle 11g client.

Other Database Drivers

Many database drivers (such as SQL Server) do not require any additional software installation or configuration.

For drivers that do require client installation or configuration, be sure to install the 32-bit version of the client software. If the database driver requires any Registry-based configuration, the configuration must be set in the 32-bit Registry, not the default 64-bit Registry.

Symptoms

Report Commander returns the following error message when you try to preview a report that uses an ODBC connection in the Command Line Builder or to process the report from the command line:

Cause

This error may occur if the ODBC alias (DSN) used by the report has not been configured on the computer where Report Commander is running. On 64-bit versions of Windows, it may occur if the alias has not been configured using the 32-bit ODBC manager.

Resolution

Use the Windows ODBC manager to verify that the ODBC alias used by the report is configured correctly. Make sure the alias is defined as a System DSN, or that it is defined as a User DSN for the user account under which Report Commander is running.

On 64-bit versions of Windows, Report Commander runs as a 32-bit application and therefore requires 32-bit ODBC drivers and DSNs. To configure the alias as a 32-bit DSN, you must run c:\windows\sysWOW64\odbcad32.exe to start the 32-bit ODBC Data Source Administrator, and add the DSN there.

Symptoms

When you try to open a report using the Command-Line Builder or by running a Report Commander command from the command line, Report Commander issues one of the following errors:

or

Cause

This error is caused by a problem in the Crystal Reports runtime components used by Report Commander. This problem is discussed in SAP Note 1481430.

Resolution

This problem was resolved in Crystal Reports 2008 SP3. To obtain this service pack:

• If Crystal Reports 2008 is installed on the computer where you are running Report Commander, download Crystal Reports 2008 SP3 using this link.After downloading, run the file to update your Crystal Reports installation and the runtime files used by Report Commander.
• If Crystal Reports 2008 is not installed on the computer where you are running Report Commander, download the Crystal Reports 2008 SP3 redistributable package using this link instead. After downloading, unzip the files and run the "CRRuntime_12_3_mlb.exe" program to install the update.

Symptoms

When you try to export or print a report that uses an XML data source, Report Commander issues the following error message:

This problem does not occur if Crystal Reports 2008 is installed on the computer where Report Commander is running.

Cause

This error occurs because Business Objects/SAP did not include some necessary software components in the Crystal Reports runtime components that Report Commander uses.

Resolution

This problem can be resolved by installing the Java Runtime Environment (if not already present) and copying some files to the computer from a Crystal Reports 2008 installation on another computer. See this SAP blog post for information and instructions.

If you need assistance completing these steps, or if you do not have access to a Crystal Reports 2008 installation, submit a support request for assistance.

Symptoms

You activate Report Commander using a temporary or permanent license. However, when you run Report Commander to print or export a report it still displays the evaluation message:

Cause

This problem occurs because the License Manager may save the license file to the wrong location when running on 64-bit versions of Windows.

Resolution

To resolve this problem you must set a Registry value so that Report Commander can find the license:

1. Start the Windows Registry Editor (regedit.exe).
2. Nevigate to the following key:
   HKEY_LOCAL_MACHINE\Software\Wow6432Node
3. Create a new key named "Arcana Development" below the "Wow6432Node" key.
4. Create a new key named "License Repository" below the "Arcana Development" key.
5. Create a new String (REG_SZ) value named "RepositoryFileName" below the "License Repository" key.
6. Set the "RepositoryFileName" value to:
   C:\Program Files\Arcana Development\Licensing\licenses.adlr 
7. Export or print a report from Report Commander to confirm that it now recognizes the license correctly.

Status

This problem was resolved in Report Commander version 1.5. See the download page to download the latest version.

Symptoms

When you install Report Commander on a computer running Windows Vista, Windows 7, Windows Server 2008, or later, setup may display the following error message:

Error 1904.Module C:\Program Files\Common Files\Business Objects\2.7\bin\ExportModeller.dll failed to register. HRESULT -2147010895. Contact your support personnel.

The message may mention one a different file name than the one listed above, for example:

• cachemanager.dll
• cereportsource.dll
• clientdoc.dll
• commonobjmodel.dll
• crqe.dll
• localcon.dll
• objectfactory.dll
• sacommlayer.dll
• crtslv.dll
• cubedefmodel.dll
• datadefmodel.dll
• rptcontrollers.dll
• requestmodel.dll
• rptdefmodel.dll
• saxmlserialize.dll
• undomanager.dll

If you click the Ignore button, the message is repeated for the additional files:

Cause

This error may occur if some Microsoft software components required by the Crystal Reports runtime used by Report Commander are not present on the target computer.

Workaround

You can resolve this issue using one of the solutions listed below.

If you are installing on one of the affected operating systems and have not yet begun installation, you can avoid the problem by installing the components before you begin Report Commander installation (solution 1).

1. Pre-install the required components

Click the Abort button to cancel installation. Download and install the Microsoft C++ Redistributable Package using the following link, then rerun the Report Commander setup.

Note: You must install the x86 version of the runtime package listed below, even if you are using a 64-bit version of Windows. This is because Report Commander runs as a 32-bit application on 64-bit systems.

• Download Microsoft C++ Redistributable Package for x86 platforms

2. Allow the installation to complete, then repair

Click the Ignore button for each of the "failed to register" messages and allow setup to complete. Then rerun the setup program and choose the Repair option when prompted.

Status

This problem was resolved in Report Commander version 1.5. See the download page to download the latest version.

Symptoms

When you use Report Commander to export a report to PDF format, the font size is slightly reduced compared to the size that appears in the Crystal Reports designer and in printed output.

Cause

This is not a problem with Report Commander but is a documented issue with Crystal Reports. Because Report Commander uses the Crystal Reports runtime components to produce the export, the PDF produced by Report Commander will match the PDF created by exporting directly from Crystal Reports.

Resolution

It is possible to force Crystal Reports and therefore Report Commander to use a larger font by setting a Registry option.

Run the Registry Editor and navigate to the appropriate key based on your operating system:

• On 32-bit platforms: "HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports"
• On 64-bit platforms: "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\Crystal Reports" 

Under this key, create the subkeys "\Export\Pdf". The full path of the new key will be

• On 32-bit platforms: "HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf"
• On 64-bit platforms: "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf"

Under this key, create a new DWORD value named "ForceLargerFonts" and set it to "1".

Add the "ForceLargerFonts" value under the user key as well:

• On 32-bit platforms, put the value under key "HKEY_CURRENT_USER\Software\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf"
• On 64-bit platforms, put the value under key "HKEY_CURRENT_USER\Software\Wow6432Node\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf"

Note: If you will be running Report Commander from different user accounts (e.g., running it from a scheduler that uses a different account), you will need to set the Registry option under the user key for each user.

Crystal Reports and Report Commander should now use a larger font when exporting.

Side Effects

In some cases this change may result in truncation of text. In this case you can apply the changes discussed in the following technical note from SAP: 

ADAPT00940675

Description:

When exporting a report to PDF format, the font size is reduced by a small factor in the export. To address this, users can set the "ForceLargerFonts" registry key to maintain the correct font size in the export. However, exports with this option turned on can occasionally have truncated data along the right page margin. This truncation occurs due to a mismatch of how character widths are calculated between PDF and Microsoft Windows.

New Behavior:

The PDF export engine has been modified to incorporate a new algorithm that positions characters precisely to prevent truncation from ocurring while maintaining the correct font size. This algorithm is activated and controlled by two new registry keys. These keys are:

[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf]

"UsePrecisePositioningForText"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf]

"TruncationAdjustment"=dword:00000002

The "UsePrecisePositioningForText" key turns on the new functionality when it is set to 1. When this functionality is activated, the "ForceLargerFonts" key is ignored. The "TruncationAdjustment" key controls a width calculation rounding function in the new algorithm and accepts values between 0 and 10 inclusively. The default value of 2 has been tested to sufficiently eliminate most truncation issues. If truncation is still observed, this value can be increased for added granularity.

Known Limitations:

When the "UsePrecisePositioningForText" key is turned on, there are several side-effects. Exporting to PDF may take slightly longer, but no more than 10% longer. The exported PDF document will increase in size over the standard outputand Crystal Reports will consume more GDI resources during the export.

Symptoms

If you override the report's database connection (that is, tell Report Commander to use a different database connection than the one saved in the report), Report Commander may fail to print/export the report with the following error message:

One or more database connections overridden. Verifying database.
Error: Failed to export report: Missing parameter values.

Status

This issue has been corrected and the fix will be included in the next maintenance update or software release.

Customers currently using version 1.5 can apply the latest Report Commander hotfix.

Symptoms

Report Commander has been working correctly but begins failing with an error message similar to the following:

This problem may appear after Windows updates are installed, or after another program is installed or removed.

Cause

This problem may occur if an update to Windows or to another program corrupts the installation for Report Commander, the Crystal Reports runtime components, or the Microsoft .NET Framework.

Resolution

This problem can generally be resolved by repairing the Report Commander installation. This can be done through "Add/Remove Programs" or "Programs and Features" in the Windows Control Panel.

If Repair does not resolve the problem, or the Repair fails to run correctly, try uninstalling and reinstalling Report Commander. After you remove Report Commander, check the Report Commander program directory (generally "c:\program files\arcana development\report commander" or "c:\program files (x86)\arcana  development\report commander") and be sure that no .exe or .dll files were left behind (delete them if there are any).

If you no longer have the Report Commander setup program (or if the version you have is older than the current version), you can download the current version from the Report Commander download page.

Uninstalling and reinstalling will not affect your Report Commander license.

Symptoms

When you run Report Commander to process a report, the following message may be written to the console:

Cause

This message is written by the Crystal Reports runtime components used by Report Commander, due to a problem in those components. It does not affect Report Commander execution.

More Information

This message may occur if IPv6 is installed on the computer where Report Commander is running but is not enabled.

Resolution

This message can be ignored. It does not represent an error condition or affect Report Commander execution.

Symptoms

A licensed installation of Report Commander starts reporting that it is running in evaluation mode, without a valid license.

When you run the Report Commander License Manager, a license is shown, but the license has an expiration date.

Cause

In some cases the license file contains information about the end of the initial support and maintenance period for the license. The License Manager is incorrectly treating this date as the expiration date for the license.

Resolution

To resolve this problem you must deactivate and reactivate the software to get a new license file without the expiration date.

Follow the steps below to complete this process. If you need assistance please contact the sales department.

1. Run the License Manager tool from the Report Commander group on the Start menu.
2. Your license should be shown in the License Manager, with an expiration date. If the Status column does not show an expiration date, you do not need to continue this process.
3. Right-click the license and select the Properties command.
4. Make a note of the License Account number shown in the license details.
5. Click Close to return to the main License Manager screen.
6. Right-click the license and select the Remove command.
7. Follow the steps in the wizard to return the license/deactivate the software.
8. From the License menu, select the Activate Software command.
9. Follow the steps in the wizard to activate the software using the account number you noted in step 4.

If the computer where Report Commander is running is not connected to the Internet, the deactivation and activation wizards will provide instructions for logging on to the licensing Web site to complete portions of the process there.

Additional Information

When you purchase a Report Commander license, the license itself should never expire. You are entitled to continue using the version of the software you are licensed for, even if you choose not to renew your support and maintenance subscription.

Summary

This article explains how you can configure Report Commander to send output from more than one report in a single e-mail message.

Overview

When you run Report Commander, each execution of Report Commander will only export a single report. Report Commander can then e-mail the output to designated recipients. However, there may be scenarios where you want to include the output from several reports in a single e-mail message. While this cannot be accomplished with a single run of Report Commander, it can be done using multiple runs: for all but one of the reports, you will run Report Commander (once for each report) to export the report to a file without e-mailing that file. For the final report,  you will run Report Commander to export the report and e-mail it along with the previously-created output files, using the "-attachfile" command-line option.

Steps

Suppose you have four reports that you want to export and send in a single e-mail message: report1.rpt, report2.rpt, report3.rpt, and report4.rpt. To accomplish this, you would run the following four Report Commander commands (with additional command-line options as needed to supply parameters, logins, and other settings):

adcrutil -report="report1.rpt" -exportformat=pdf -exportfile="c:\temp\report1.pdf"

adcrutil -report="report2.rpt" -exportformat=pdf -exportfile="c:\temp\report2.pdf"

adcrutil -report="report3.rpt" -exportformat=pdf -exportfile="c:\temp\report3.pdf"

adcrutil -report="report4.rpt" -exportformat=pdf -exportfile="c:\temp\report4.pdf" -emserver=mail.example.com -emsender="test@example.com" -emrecipient="test@example.com" -emsubject="Reports 1-4" -emtext="Reports 1-4 are attached" -attachfile="c:\temp\report1.pdf" -attachfile="c:\temp\report2.pdf" -attachfile="c:\temp\report3.pdf" -parameters 2012-12-01 2012-12-31

Notes:

The "attachfile" option is not available in the Command Line Builder. you will need to edit the command line generated by the Command Line Builder to include the "attachfile" options. When editing the command line, be sure you add the "attachfile" commands before the "-parameters" or "-namedparameters" option, as the parameters must always appear last on the command line.

It is not necessary to include an "attachfile" option for report4, because Report Commander is automatically including report4 in the message.

Limitations

The "-attachfile" option will not work properly with "dynamic" output file names (file names specified with date/time tokens) unless you have version 1.5.0.100 or later. The version installed by the version 1.5 installer is version 1.5.0.61, which does not include the necessary change. You can download the latest hotfix to update to a version that includes the update. If you are using Report Commander 1.6 or later, no hotfix is required.

Summary

Report Commander requires an SMTP server to e-mail reports. If you have a GMail account, Report Commander can send mail through the GMail SMTP server, but must be configured to use a secure e-mail connection.

Configuration

When using the Command Line Builder to create your command line, set the mail server to "smtp.gmail.com". Enter your GMail  address and password in the Authentication section, and be sure to check the "Use TLS (SSL) connection".

If you are creating the command line manually, be sure to include the "-emusetls" option on the Report Commander command line.

When specifying your user ID ("-emuserid" option on the command line, or in the Command Line Builder) you must use specify a valid GMail login, including the domain name. For example, if you are using a basic gmail account, you would use "-emuserid:userid@gmail.com". If you are using Google Apps to host your domain e-mail for "example.com", you would use "-emuserid:userid@example.com".

More Information

If you do not set the TLS option for Report Commander, the e-mail send will fail with an error similar to the following:

Symptoms

After specifying database credentials for your report, you are able to preview the report in the Report Commander Command Line Builder. However, when you execute the generated command from a command prompt, Report Commander fails with a database login error. The error message may include any of the following:

Cause

This problem may occur if the database password contains extended ASCII characters (such as the UK Pound (£) symbol) or Unicode characters. The encryption routine that Report Commander uses to encrypt the password for use on the command line fails to encode/decode these characters correctly.

Status

• Report Commander
  This issue has been corrected and the fix will be included in the next maintenance update or software release. Customers affected by the problem may contact us to obtain the fix now.

Symptoms

When exporting a report to Excel format, Report Commander fails with the following error:

Cause

This problem is caused by an issue in the Crystal Reports runtime components used by Report Commander.

Resolution

This problem can be resolved by installing Service Pack 5 for Crystal Reports 2008 on the computer where you are running Report Commander.

Please contact us for assistance in obtaining this update as it is not currently available for download from the SAP Web site.