Report Commander Knowledge Base

K00000371: Report Commander produces empty CSV export file when data is not in detail section

Wed, 28 Jul 2010 21:15:00 GMT

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.

K00000370: HTML output does not appear correctly when used as e-mail body

Mon, 19 Jul 2010 19:34:08 GMT

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:

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

This is an issue with the HTML rendering by Outlook and other e-mail clients, and is not a problem with Report Commander or Crystal Reports.

K00000368: Considerations when running Report Commander on 64-bit systems

Thu, 15 Jul 2010 19:17:34 GMT

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

K00000367: Installation fails with "failed to register" error

Tue, 13 Jul 2010 20:20:23 GMT

Symptoms

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

Error 1904.Module C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\CEReportSource.dll failed to register. HRESULT -2147010895. Contact your support personnel.

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.

K00000360: Report Commander may fail to recognize a valid license when running on 64-bit computers

Thu, 17 Dec 2009 21:02:38 GMT

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:

This software is unlicensed and may be used for evaluation purposes only for up to 30 days. Purchase a license to eliminate this 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:

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

Status

This problem will be fixed in the next release of the Report Commander.

K00000363: "Invalid export DLL or export format" error when exporting

Thu, 10 Dec 2009 20:29:49 GMT

Symptoms

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

Invalid export DLL or export format

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.

K00000351: "Failed to open the connection" error when ODBC alias is missing

Wed, 13 May 2009 15:55:29 GMT

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:

Failed to open the connection.: Failed to open the connection

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 odbcad32.exe to start the 32-bit ODBC Data Source Administrator, and add the DSN there.

K00000344: CSV Export file is empty or missing data from group headers and footers

Tue, 05 May 2009 13:28:11 GMT

Symptoms

You export a report to CSV format, but the export file is empty or is missing some lines of data.

Cause

This problem can occur if your report uses group headers and footers. By default, Report Commander does not export headers and footers when you use CSV format.

If your report does not have any fields in the "Details" section but instead uses headers and footers to display data, the export file would be empty, because Report Commander would be pulling only from the Details section.

If you report has fields in the "Details" section and in the headers and footers, the output file would be lacking the lines that come from the headers and footers.

Resolution

Include the following option on the Report Commander command line:

-csvstyle:crstyle

This will cause Report Commander to include all header and footer data.

K00000343: Subreport data is not displayed when fields extend past the edge of the subreport

Tue, 05 May 2009 13:28:11 GMT

Symptoms

When you export or print a report through Report Commander, data from a subreport may not be included in the output if that subreport has fields that extend past the edge of the subreport.

For example, you may have a text field that is 2.5 inches wide, but the subreport has been sized to be only 2 inches wide. In the Crystal Reports designer, you can see that the field extends past the edge of the subreport.

Cause

A defect in the Crystal Reports runtime components used by Report Commander causes the subreport data to be ignored altogether in this scenario, even though the same report can be exported successfully from the Crystal Reports application.

Resolution

Modify your subreport so that no fields extend past the edge of the report.

K00000342: Report Commander fails when using PostgreSQL ODBC driver with SSL connection

Tue, 05 May 2009 13:28:11 GMT

Symptoms

You use Report Commander to process a report that uses the PostgreSQL ODBC driver, with the driver configured to require an SSL connection. Report Commander successfully exports, prints, or e-mails the report, but then terminates with an application failure message similar to the following:

Report Commander has encountered a problem and needs to close. We are sorry for the inconvenience.

Note: This article applies only if you are using the driver configuration described. If you are not, the application failure is caused by a different issue and this article does not apply.

Cause

This problem appears to be caused by an issue in the PostgreSQL driver.

Resolution

This problem is the result of a defect in the PostgreSQL software. To address this issue you can:

Look for assistance in the PostgreSQL community.
Switch to a different PostgreSQL driver.
Use the PostgreSQL ODBC driver without SSL support.
Ignore the application failure, since it occurs only after report processing has been completed.

Additional Information

Testing has shown that this problem occurs when using the Crystal Reports runtime components used by adTempus, but not when using the same report and driver from the Crystal Reports designer. However, reviews of PostgreSQL logs and of the technology involved indicate that the problem is in the database driver, and not in the Report Commander or Crystal Reports software.

The PostgreSQL driver log file from a failure scenario shows the following as the last line before the failure:

[SQLDisconnect for 068D3E38][5744-7.662]PGAPI_Disconnect: entering...

Whereas a successful operation (through Crystal Reports) shows the following:

][SQLDisconnect for 074E3DD0][4324-21.750]PGAPI_Disconnect: entering...
]PGAPI_Disconnect: about to CC_cleanup
]in CC_Cleanup, self=074E3DD0
]after CC_abort
]SOCK_Destructor
]after SOCK destructor
]exit CC_Cleanup
]PGAPI_Disconnect: done CC_cleanup
]PGAPI_Disconnect: returning...
][[SQLFreeHandle]][4324-21.750]PGAPI_FreeConnect: entering...
]**** in PGAPI_FreeConnect: hdbc=074E3DD0
]enter CC_Destructor, self=074E3DD0
]in CC_Cleanup, self=074E3DD0
]after SOCK destructor
]exit CC_Cleanup
]after CC_Cleanup
]after free statement holders
]exit CC_Destructor
]PGAPI_FreeConnect: returning...
][[SQLFreeHandle]][4324-21.750]**** in PGAPI_FreeEnv: env = 074E2940 ** 
]in EN_Destructor, self=074E2940
]clearing conns count=128
]exit EN_Destructor: rv = 1
]   ok
]DETACHING PROCESS
]LIBPQ.dll unload success=1

K00000340: Specifying a negative number as a report parameter

Tue, 05 May 2009 13:28:11 GMT

Symptoms

You are trying to pass a negative number as a report parameter on the Report Commander command. For example:

adcrutil.exe -report="report.rpt"  -exportformat=html -exportfile="report.htm" -parameters "-1"

Report Commander fails with the following message:

Error: Option "parameters": No value specified
Error: Unrecognized parameter: "1"

Cause

When processing the command-line options, Report Commander sees the "-" symbol as the start of a new option named "1", which it does not recognize.

Resolution

To avoid this problem, you must "escape" the value by including a backslash ("\") character in front of the minus sign (hyphen) as in this example:

adcrutil.exe -report="report.rpt"  -exportformat=html -exportfile="report.htm" -parameters "\-1"

K00000339: Diagnosing "Load report failed" errors

Tue, 05 May 2009 13:28:11 GMT

Symptoms

Report Commander returns the following error message when you try to open a report in the Command Line Builder or to process the report from the command line:

Cannot open report file: Load report failed

Cause

This is a generic error message returned from the Crystal Reports runtime components used by Report Commander whenever it encounters a problem loading the report file. Unfortunately the Crystal Reports runtime does not return additional information about the problem, making it difficult to diagnose the cause. This article discusses some possible causes for the error.

Report was created using an older version of Crystal Reports

This message is common when you try to use Report Commander with a report that was created in Crystal Reports 8.5 or earlier. The report file structure and database drivers changed significantly between Crystal Reports 8.5 and 9.0, and as a result the newer runtime components used by Report Commander often cannot read the report, even though the Crystal Reports designer can. Because of this, Arcana Development does not support the use of Report Commander with reports created by Crystal Reports 8.5 or earlier (this is noted in the system requirements for Report Commander).

Older Crystal Reports files are still quite common, especially if you are using a report provided as part of another application.

If you have access to a newer version of Crystal Reports (version 9.0 or later), you can generally convert your report file to the newer format so that it can be used with Report Commander. To do this:

Open the report in the newer version of Crystal Reports.
Use the Verify Database command to ensure that the database driver is updated and the data can be retrieved.
Preview the report to make sure that it works correctly.
Save a copy of the report under a new name and use this copy with Report Commander.

Important: If the report is being used by another application, be sure to save a copy of the report under a new name. If you overwrite the original report file with the updated format, the other application that uses the file may not be able to open the file.

Report uses User Function Libraries

The error may occur if your report uses functions in a user function library (UFL), and the UFL (or one of its dependencies) is not present on the computer where you are running Report Commander. See article K00000279 for more information on this scenario.

Report uses non-standard database driver

The error may occur if your report uses a non-standard database driver and that driver is not installed on the computer where Report Commander is running. Make sure all the necessary files for your database driver are present on the computer.

Report file name is wrong, or file is inaccessible

This error may occur if you have specified an invalid report file name on the Report Commander command line, or if the report is on a drive or network resource that is inaccessible.

If Report Commander is being run from a scheduler or automation tool, be sure that the account being used to run Report Commander has access to the report location.

If the path contains a mapped drive letter, make sure that drive letter has been mapped for the logon session in which Report Commander is running, or use a UNC path to refer to the file instead.

K00000273: Report Commander fails when run in evaluation mode from a Web application or non-interactive service

Tue, 05 May 2009 13:28:11 GMT

Symptoms

When you run Report Commander in evaluation mode (i.e., you have not activated Report Commander using a license) from a Web application or other application (such as adTempus) that runs Report Commander in a non-interactive mode (without a desktop), Report Commander may fail with the following .NET Framework exception message:

It is invalid to show a modal dialog or form when the application is not running in UserInteractive mode. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application.

Alternatively, Report Commander may fail with a generic error message similar to the following:

adcrutil.exe - Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.

Cause

This occurs because when you run Report Commander in evaluation mode, the program tries to display a dialog box with an evaluation notice. Because Report Commander is running in a non-interactive session, it is not permitted to display the dialog box.

Resolution

This error will not occur if Report Commander is running with a license. If you are evaluating Report Commander, obtain a temporary license to avoid this problem.

K00000331: "Unrecognized authentication type" error when e-mailing report output

Tue, 05 May 2009 13:28:11 GMT

Symptoms

When you attempt to e-mail report output using Report Commander, an error message similar to the following is reported:

Error: E-mail send failed: 504 5.7.4 Unrecognized authentication type

Cause

This message usually indicates that the mail server you are using is not configured to use authentication (a user ID and password) when sending mail. In rare cases it may indicate that the server requires an authentication method other than the one that Report Commander is trying to use.

Resolution

Remove the "emuserid" and "empassword" options from the Report Commander command line and rerun the command. If the e-mail send now fails because authentication is required, check with the administrator of the mail server to determine what authentication method(s) the server supports, and contact Arcana Development for assistance.

K00000324: "Page header plus page footer is too long for the page" error when no default printer configured

Tue, 05 May 2009 13:28:11 GMT

Symptoms

When you try to print, export, or preview a report in Report Commander, you receive one of the following error messages:

Page header plus page footer is too long for the page

Page header or footer longer than a page

This error only occurs if there is no default printer designated for the computer.

Cause

Crystal Reports requires that a default printer be designated for the computer, as it uses layout settings from the default printer even if you are not printing the report.

Resolution

In the Windows Printers view, make sure that a default printer has been designated.

If no printers are configured for the computer, you will need to add a printer and set it as the default. It does not matter whether the printer configured for the computer is valid or usable (unless you really plan to print); it just needs to be defined. Go through the Printer Configuration Wizard and select the "Generic" printer manufacturer, and the generic text-only printer driver.

K00000323: Adjusting formatting when exporting to plain text

Tue, 05 May 2009 13:28:11 GMT

Summary

When a report is exported to the "plain text" format, you may encounter formatting problems such as truncated text and improper column alignment.

More Information

The plain text output format often does not work well for reports that have not been specifically designed with plain text export in mind. Report Commander should produce the same output as the Crystal Reports designer.

Before you export to plain text using Report Commander, you should export to plain text using the Crystal Reports Designer and adjust the report layout and formatting if the output does not look correct.

The characters-per-inch and lines-per-page options available when exporting from the Crystal Reports Designer can often be adjusted to improve the look of the output.

Corresponding options are available when exporting the report using Report Commander (though these options do not appear in the interactive command-line builder):

-linesperpage=number	The number of lines per page (default 60). Specify 0 for no pagination.
-charactersperinch=number	The number of characters per inch (default 12). Recommended to be between 8 and 16.

For example, these options sets the output to 12 characters per inch, with no pagination:

-charactersperinch:12 -linesperpage:0

For additional information on plain text output formatting, refer to the Crystal Reports documentation.

K00000314: Report Commander Support for Crystal Reports 2008

Tue, 05 May 2009 13:28:11 GMT

Summary

This article discusses Report Commander support for Crystal Reports 2008

More Information

The current version of Report Commander (version 1.2) uses runtime components from Crystal Reports version XI and is backward-compatible with reports created using Crystal Reports versions 9 and 10.

Report Commander is compatible with most reports created using Crystal Reports 2008, as long as those reports do not use new reporting features introduced in Crystal Reports 2008 (see www.businessobjects.com/product/catalog/crystalreports/features.asp for information on new features).

A new version of Report Commander with full support for Crystal Reports 2008 will be released later this year.

K00000281: How To: Change printer settings when printing with Report Commander

Tue, 05 May 2009 13:28:11 GMT

Summary

Report Commander does not allow you to specify printer settings (other than selecting a printer) when printing a report, due to limitations of the Crystal Reports runtime components used by Report Commander. If you need to use special printer settings, you can accomplish this by creating a new printer definition that uses the appropriate settings.

More Information

To create a printer definition with the correct settings, open the Windows Printers and Faxes folder, and locate the printer you want to use. Make a note of the configuration for that printer definition, then create a new printer item for the same device, using the same initial settings. Then modify the new printer definition to use the settings you need. For example, use the Printing Defaults button on the Advanced page to set the paper source, duplexing options, print quality, or other options.

Now when you print the report from Report Commander, specify the new printer name you have created, using the "-printer" command-line option for Report Commander.

K00000280: Report Commander fails with error "A Crystal Reports job failed because a free license could not be obtained"

Tue, 05 May 2009 13:28:11 GMT

Symptoms

When you try to print or export a report using Report Commander, Report Commander fails with an error message similar to the following:

A Crystal Reports job failed because a free license could not be obtained

Cause

This error may occur if you have installed or updated Crystal Reports after installing Report Commander. In some cases, this corrupts the license information Report Commander needs in order to use Crystal Reports runtime components.

Resolution

To resolve this issue, uninstall and reinstall Report Commander.

K00000279: "Load report failed" error when running Report Commander with a report that uses a user function library

Tue, 05 May 2009 13:28:11 GMT

Symptoms

Report commander gives error "Cannot open report file: Load report failed" when you try to open a report that uses functions in a user function library (UFL). This error may occur when you try to open the report using the Report Commander Command Line Builder, or when you run Report Commander in command-line mode to export or print the report.

Note: The "Load report failed" message is a generic error message from Crystal Reports and may occur due to other causes. This article applies only if the report uses user function libraries. For other possible causes of this message see article K00000339.

More Information

Crystal Reports allows reports to call functions defined in user function libraries supplied by a third party. When you use the report, the user function DLL (and any files it depends on) must be present on the computer. If you are running Report Commander on a different computer than you developed the report on, these files may not be present.

To resolve this problem, you must determine which user function libraries your report depends on, and install or copy the necessary software on the computer where Report Commander is being run.