ODBC User/Password Prompt for Embedded Crystal Report After Epicor Upgrade

Hello EpiUsers,

After upgrading our Epicor system from 10.2.400.14 to 2024.1.8, we are encountering an issue where an embedded Crystal Report in a dashboard prompts for an ODBC user ID and password.

This report uses an XML file generated by the dashboard as its data source. Since the XML file is directly used, we believe there is no need for an ODBC connection. The report worked without any such prompt in the older version of Epicor but now fails to print correctly due to this issue.

Steps Taken to Troubleshoot:

  1. Verified that the Crystal Report is uploaded into the new Epicor version.
  2. Generated a sample data file – the report works fine using this data in Crystal Reports directly.
  3. Manually ran the Crystal Report outside of Epicor using the sample data, and it worked as expected.
  4. Cleared the recycle pool and re-logged into Epicor.

Request for Assistance:
Has anyone experienced this issue after upgrading to Kinetic? If so, how can we resolve or bypass the ODBC user/password prompt for a report that uses an XML file as the data source?

Are there any specific configurations in the new Kinetic version that could be causing this behavior?

Any guidance or suggestions to resolve this would be highly appreciated. I’m happy to provide additional details or replicate the issue if needed.

Thank you for your help!

Regards,
Dnyanraj Patil

Also verify Company Maintenance

Raj,

I would double check the Crystal Report Connections. There may have been one left in that was unused after switching to the XML datasource.

Where was this run? On a client machine? On the App Server?

Currenlty, testing on server with crystal editor.

Are any of these BAQs external by chance?

Mr. Raj: If you are testing on the server - do you have the Epicor Crystal Runtime installed?

The runtime needs to be installed locally on all client workstations that will print from Crystal.

Also, one other Gotcha i run into is since you are running an upgraded version - are you running on a new server? if so, you will have to update the DataSource for all of your Crystal reports to point to the new server XML location.

1 Like

Hello @Doug.C , @Mark_Wonsil @DaveOlender ,

I would like to clarify that this is not a standard or BAQ-based Crystal Report. It is a Dashboard Crystal Report, which was a functionality available in older Epicor versions like Epicor 9. Using this feature, we could create Crystal Reports based on dashboard results.

I understand that this functionality is no longer available. While this Dashboard Report is currently working fine in Epicor 10, it is not functioning as expected in Kinetic 2024.x.

For more details, please refer to the following link:
Dashboard Crystal Report Issue - EpicCare

I’ve also attached a relevant screenshot for your reference.

Looking forward to your thoughts or guidance on this matter.

Can you even make these types of reports (crystal based off dashboard) in Kinetic anymore?

No, we can not create a crystal report in Kinetic.
An upgrade is Apple to Apple, so Crystal to SSRS is in its second phase.

I’m pretty sure they allowed crystal starting in 2024.1, but don’t quote me. I haven’t tried to make an XML crystal in a minute. I do know that you can now hang a crystal on menu and view it in web.

Here I am in 2024.1.7 or 8 I think and that’s a custom crystal report hung on the menu… Just not sure you can use a crystal report in the normal way, as a report style.

What I am getting at is, if they added this crystal functionality to 2024.1, what else did they add or are they intending to add… Could you see your crystal reports be raised again from the dead?