Report Commander Knowledge Base

K00000396: Missing parameter error occurs after overriding database connection

Fri, 10 Feb 2012 14:02:33 GMT

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

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.

K00000394: Font size reduced when exporting to PDF

Tue, 29 Nov 2011 16:10:56 GMT

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.

K00000389: Report Commander writes "ORB::BOA_init" warning message during execution

Fri, 21 Oct 2011 16:59:23 GMT

Symptoms

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

Warning: ORB::BOA_init: hostname lookup returned 'localhost' (127.0.0.1/::1)

Use the -OAhost option to select some other hostname

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.

Resolution

This message can be ignored.

K00000374: Setup fails with "module failed to register" error

Mon, 10 Oct 2011 17:10:54 GMT

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.

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

Mon, 10 Oct 2011 17:10:30 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 was resolved in Report Commander version 1.5. See the download page to download the latest version.

K00000378: "Failed To Load Database Information" error with report that uses XML data source

Tue, 08 Feb 2011 22:39:50 GMT

Symptoms

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

Failed to export report: Failed To Load Database Information

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.

K00000377: "Load report failed" error when opening a report that uses an XML data source

Tue, 08 Feb 2011 22:27:44 GMT

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:

Cannot open report file: Load report failed

Cannot open report file: Load report failed: Buffer too small for string or missing null byte

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.

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

Tue, 01 Feb 2011 19:12:09 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 c:\windows\sysWOW64\odbcad32.exe to start the 32-bit ODBC Data Source Administrator, and add the DSN there.

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

Tue, 01 Feb 2011 19:11:06 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 "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.

K00000373: Installing Report Commander 1.4 may break Crystal Reports 2008

Sat, 25 Sep 2010 21:50:17 GMT

Summary

If you install Report Commander version 1.4.x 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.x installs 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.

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.

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.

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.

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.