SAP Crystal Reports Forms Viewer - Undefined Error

[anders_gustafsson]

Or rather "Odefinierat fel" which is Swedish. This is from a Windows 32-bit app that uses the latest runtime (sp21). Seems to affect reports that prompt for parameters, but not all reports that does that. Does not happen on all machines, but I have seen it on three so far. Have logs, but they do not tell me much.

It errors out BEFORE the parameter prompts.

Any ideas?

[former_member11696 · Accepted solution]

The odd part is why is it working on some PC's an not other?

I wonder if it has anything to do with the Data sources you guys are using?

Possibly the DB clients need to be updated...

Don

[former_member11696]

Hi Anders,

SP 22 was just released, see if that makes any difference.

I assume you did the update to 3500 assemblies also?

Are all of the Framework updates installed on those Windows 7 PC's?

Don

[anders_gustafsson]

Glad to see I am not alone.. Just had another customer call in with the same issue ysterday. Have you heard anything back from DEV, Don? Meanwhile, "All framework updates" - Would the standard windows update suffice or should I apply anything else?

[anders_gustafsson]

Yes Don the assemblies are updated as nothing will work if not. I assume that all framework updates have been applied as the installer we use has those set as prerequisite. I recoded those few reports to use a string parameter instead as a workaround. I will see if I can find another Windows 7 machine to test.

[former_member11696]

Hi Anders,

I too am getting odd behaviour from time to time... some work flow work and then they don't or odd results or it will generate an exception...

I think it may have something to do with the record selection formula....

I'll ping DEV and see if they changed anything in that part...

Don

[Former Member]

Don,

The error I am getting is "Unspecified error". I am using 13.0.16.1954 but I believe it was also a problem in 13.0.9. I didn't get any reports from people that were using 13.0.5.

I ran across this last summer and couldn't find a solution for several weeks. I finally found the Number parameters were causing the problem. Convert to String and the problem goes away. I literally just finished testing this again because I came across it while beta testing my application and didn't realise I was using an rpt with a number prompt. It doesn't seem to matter if I pass the value to let it prompt the user, it still gets an error.

I just thought I would look around again in case there was another solution or an update had fixed it when I found this thread, but it looks like it is still part of the engine.

[anders_gustafsson]

OK. Replying to my own posting here. The error happens on two out of three machines and after the upgrade to SP21 (from SP13). The affected machines are both Windows 7, the machine where it works is Windows 10.

The problem does NOT happen if you run the report from the Crystal Reports 2013 editor. Only happens when you call the report from our app

The culprit was number parameters that were not passed from our app. Instead the report prompts for them. These reports are all customer-specific and launched from a menu prompt that provides default parameters only. Such a "toxic" parameter is below. The simple fix was to change all of those into String parameters and adjust the formulas.

To trigger the error, all that was needed was for the parameter to exist and to be present on the page. It did not need to be part of a formula.

Any hints as to why this happened?