Failing to verify database

[former_member533461]

Hi there,

We need to fix something in an existing crystal report and need help..

We've been trying to verify database before fixing with the following steps

1. Database tab >> Verify Database >> Enter login information >> Enter parameter values

2. Then we're getting the below warning. and clicked the OK button.

3. Nothing is shown in the mapping screen. When clicked the OK button, all the fields in the report are gone.

We tried to connect the database from "Set Datasource Location". However, this mapping screen pops up in the end and it didn't work.

The stored procedure is used in multiple reports with different parameter values, and only this report is facing this problem..

Is there any other method to solve this issue? We appreciate any advice.

Happy reporting! and Regards,

Chrissa

[former_member533461 · Accepted solution]

Abhilash Kumar , Ludek Uher, Dell Stinnett-Christy

Could any of you please give me some advice as we have been struggling with this issue for a few weeks? Thank you in advance.

[abhilash_kumar · Accepted solution]

Hi Chrissa,

What version of Crystal Reports is this (Go to Help > About > Check the version number).

Also, what database are you reporting against?

-Abhilash

[former_member533461 · Accepted solution]

Hi Abhilash Kumar,

Thank you for your prompt response. We are using Version 14.0.2.364RTM.

And our database is SQL Server 2008.

[former_member11696 · Accepted solution]

Hi Chrissa,

On the Mapping screen uncheck the Match Type, it should then list the field(s) CR can't auto map too, it seems someone possibly changed the Stored Procedure and CR can't figure out what field type it is now. Or possibly your client has changed

Or have you updated the Server and Client recently?

Or find out who changed the SP and why... may explain what happened.

Don

[former_member183750 · Accepted solution]

Hi Chrissa

If the suggestions from Abhilash and Don do not help, about all I can suggest is creating a phone incident and work the issue there. E.g.; this may need more than forum communications.

To create a phone incident please go here: Crystal Single Case Technical Support - SAP Business Objects US Online Store | SAP Online Store

Or contact sale at 866-681-3435

- Ludek

Senior Support Engineer Product Support, Global Support Center Canada

Follow me on Twitter

  Got Enhancement ideas? Use the SAP Idea Place

[former_member533461 · Accepted solution]

Hi  Don Williams,

Thank you for your advice. We made sure that our stored procedure did not have any changes.

However, we found the solution for this. We did logoff and logon then, refresh parameter value of the stored procedure name. Then it worked out!

[former_member533461 · Accepted solution]

Hi Ludek Uher, thank you for your attention. We re-setup the parameter values of stored procedure name, then it worked out. 

[former_member183750 · Accepted solution]

Very good new. Happy you're back in business

-Ludek