Crystal Runtime Engine .NET 32-bit - cannot connect to JD Edwards EnterpriseOne ERP

[Former Member]

We have 2 products that both use the Crystal Runtime to execute reports developed using a developer install of Crystal Reports XI 2 (Business Objects). The older of the two products uses an older runtime component and it is able to establish a connection to JD Edwards EnterpriseOne, pass credentials and run reports no problem. The other uses a newer runtime component, specifically version 13.0.15.1840. That product, using that runtime, *cannot* run those reports. It fails to properly connect / pass credentials (I do not know the exact issue). My question to the community is, does anyone know why this is? Current versions of Crystal come "pre-configured" to establish connections to EnterpriseOne (minus .jar files). It's difficult to believe the runtime used to be able to make that connection, but now cannot. We're stumped. Any help greatly appreciated. - Regards, Chris

[Former Member]

Don,

Thanks again for your answer and your assistance. Bummer that Crystal Reports (not for VS) includes support for a connection type "JD Edwards EnterpriseOne", but that the runtime doesn't.

If it helps you, the path for the .jar files in our install of XI 2 is:

C:\Program Files (x86)\Business Objects\BusinessObjects 11.5 Integration Kit for PeopleSoft\JarDir\default\peoplesoft

(JD Edwards was owned by PeopleSoft at the time. Now it is an Oracle product w/ their acquisition of PeopleSoft)

The Crystal Reports 2013 / 2016 folder is:

C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib\jdedwards\default\jdedwards

Thanks again Don for your attention - really appreciated!

Chris

[former_member11696]

Hi Chris,

Sorry my mistake. The JDE driver is all JAVA based, no dll's.

I have to talk to the Report Designer guys to see what it takes to implement the drivers for CRD and see if CR for VS will use them.

I suspect likely it just needs the updated JAR files and the path to them so they can be found.

BUT, according to the PAM : http://scn.sap.com/docs/DOC-21990

CR for VS does not support any of the OEM Database drivers like JD Edwards.

I'll ask DEV if it's possible to add them.

Don

[Former Member]

Hello Don, and Happy New Year to you.

Were you able to get any additional insight into this issue? I have a separate technical support case open for the issues we're seeing with Crystal Reports 2013/2016 and JD Edwards. Certainly hope that the powers that be can see value in allowing the more recent Runtime(s) to leverage reports built using the "EnterpriseOne" connection type.

Regards,

Chris

[Former Member]

Don, thank you for your quick input!

I apologize for what may be a silly question, but does your comment "The XI R2 dll's will not work with CR for VS..." imply that reports created (or possibly opened, and then saved) by, say, Crystal Reports 2013 or 2016, could then do away with the dll issues? We've wanted to upgrade anyway, perhaps this is our excuse?

[edit] Follow-up: apologies, but where may I find / how may I find, the dll files you mentioned? Apologies for not understanding more of the architecture of these products. Are these downloadable, or...?

[former_member11696]

Hi Chris,

CR for VS does not include any of those older "OEM" DB drivers so when your app runs it can't find the drivers.

The XI R2 dll's will not work with CR for VS but possibly the CR 2011 dll's will, You could try copying them over to this folder:

C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86

Not supported but may work.

Request your enhancement in Idea Place.

Don