Consultor Eletrônico



Kbase P115979: EXPORT method fails with error 5890 caused by Logon issues in Crystal Reports
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   11/05/2006
Status: Unverified

FACT(s) (Environment):

Progress 9.1D
Progress 9.1E
OpenEdge 10.x
Crystal Reports 9
Crystal Reports 10
Crystal Reports 11 (XI)
Windows

SYMPTOM(s):

Trying to export a Crystal report to a file or other location

Using the COM Report Designer Component (RDC)

Error 5890 occurs when calling the EXPORT method

Error occurred while accessing component property/method: <property or method name>.
<COM message>
Error code: <Program name> (5890)

Error occurred while accessing component property/method: EXPORT.
Logon failed.
Error code: 0x80020009 (5890)

Error occurred while accessing component property/method: EXPORT.
Failed to open the connection.
Error code: 0x80020009 (5890)

Error varies slightly depending on the version of Crystal that is in use

Using the LogOnServer method to establish the initial connection to the database for the report

Parameter values used in the LogOnServer method (specifically the ODBC DSN) differ from those used when the report was created

CAUSE:

The EXPORT method of the Crystal RDC needs to establish a connection but fails because the ConnectionProperties saved in the report are different from those supplied in the LogOnServer method. The EXPORT method fails to override these properties and therefore cannot connect causing the error.

FIX:

Programmatically override the ConnectionProperties stored in the Crystal report

Option #1
Completely override the ConnectionProperties collection stored in the report and replace it with a Connection String. This method would remove the need to setup an ODBC DSN.
Refer to solution P115877 for more information.

Option #2
Use the ConnectionProperties collection to override the properties stored in the report, replacing saved values with new ones.
Refer to Option #1 in solution P55350 for more information.

Option #3
Override the DSN property stored in the report only and continue to use the LogOnServer method.
Refer to solution P47202 for more information.