CRCAF00000030 error from OpenDocument

[Former Member]

Running 4.1 SP1 Patch 2 (on Windows, with Tomcat) and we run into an error

"This error occurred: org.apache.jasper.JasperException: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 [CRCAF00000030]"

when opening Crystals via OpenDocument links. The issue appears to be that OD is expecting prompt parameters and fails if it does not get them. I have found that by appending "&lsS" anywhere in the existing link query parameters it will work as intended, but there is nothing in the documentation that indicates the prompt parameters are required. The same works fine in XI3.1.

My only possible workaround right now is to use a URLRewriteFilter to correct the URL, but it's a bit brutish, and I'm wondering if anyone else has encountered this issue? If so how did you resolve it?

(Yes, I have an open support case, but they are "not able to reproduce the issue")

[Former Member · Accepted solution]

Hey Brian,

We have that exact issue in 4.1 SP2 Patch 1 (happened when we upgraded from 4.0 to 4.1 SP1). We found that a user preference setting in the BI launch pad causes the error for crystal reports with parameters of the DateTime data type (steps to recreate below). Can you try these steps in your environment? Please keep us posted with any updates.

1. Log into http://<BOE_SERVER>/BOE/BI and open the user's preferences

2. Click on 'Crystal Reports' in the left panel

3. Under 'Select printing control (for Web):' select the option for 'PDF one-click printing' and Save

4. Attempt to open a crystal report with at least one date parameter through it's OpenDocument URL using the same user as in step 1

5. Verify CRCAF00000030 error message

6. Repeat steps 1 and 2

7. Under 'Select printing control (for Web):' select the option for 'ActiveX one-click printing' and Save

8. Repeat step 4 with the same OpenDocument URL

9. Verify the report parameter form opens (no error)

By the way, appending "&lsS" to the OpenDoc URL works in our environment as well. However, we have a custom Java SDK component that this workaround may not work for.

Regards,

Justin

[Former Member · Accepted solution]

Great stuff Justin!

This could explain why the sledge hammer approach in my scratch environment resolved the situation.

If the issue kicks in on another environment I'll try your steps and feedback here.

[Former Member · Accepted solution]

I can confirm the issue kicks in when the preference setting "Crystal Reports -> PDF one-click printing (Adobe Acrobat required)" is applied.

[Former Member · Accepted solution]

Thanks for the confirmation, James. Looks like we might have a bug on our hands.

[former_member230846 · Accepted solution]

Hi Justin and James,

I will test this in-house to reproduce the issue.  If I can reproduce it, I'll submit a bug to my internal teams and create an SAP Note.

Regards,

Wallie

[Former Member · Accepted solution]

Thanks Wallie. Please keep us posted

[former_member230846 · Accepted solution]

Thank you for the in depth testing you've done on this.  I was able to reproduce the issue following your steps and will move forward with the bug submission.

Regards,

Wallie

[Former Member · Accepted solution]

That's great, thanks again. Please let us know if a fix becomes available.

[Former Member · Accepted solution]

Wallie,

We upgraded our 4.0 server to SP08 FP03 from SP07 FP02 this weekend and have found that the upgrade is causing this issue in that environment now. Is there any schedule for a fix?

I ask because the '&lsS' and user print preference workarounds do not help us with our custom Java apps accessing the environment through the BOE Java API.

[former_member249128 · Accepted solution]

Hi Justin,

The fix for this issue should be available in BI 4.1 SP2 Patch 4 which is expected to be released by 3rd week of March.

Thanks,

Rahul

[Former Member · Accepted solution]

Thanks for the follow up Rahul!

[former_member183781 · Accepted solution]

Did the FIX for this BUG make it into BI 4.1 SP3 release..?

We are having the same issue with the Users preference set to 'PDF one-click printing' when calling the RPT from the BOE 4.1 SP2 platform via an iView CUID call from the SAP Portal.

We prefer to use the 'PDF one-click printing' as it is easier for end-users that don't use IE browsers - or who have locked-down IE and can't install ActiveX plug-ins.

[former_member249128 · Accepted solution]

The fix is available in Patch 1 for BI 4.1 SP3 and BI 4.1 SP4.

[Former Member]

Hello,

We are on BI 4.1 SP3, we went live 2 weeks ago with this version and everything was working fine until today that we start experiencing this error.

The proposed solution appending the "lsS" works, but just wanted to let everyone know that still on BI 4.1 SP3 has not been resolved.

Thanks,

Daniel

[former_member249128]

Daniel,

As I mentioned earlier, the fix is available in Patch 1 for BI 4.1 SP3 and BI 4.1 SP4.

Please try Patch 1 and let us know.

Thanks,

Rahul

[Former Member]

This post has been helpful, but I have a question.  Using the below URL, if I want to test the work around of adding the &IsS where in this URL would I put this?

http://pdboe01:8080/BOE/OpenDocument/opendoc/openDocument.jsp?iDocID=Aegxxem8RHpOuN0Cf3N2M9o&sIDType...

thanks!

[former_member249128]

Hi Lloyd,

You can add &lsS at the end of the URL in your case and it should work fine.

Regards,

Rahul

[former_member230846]

Hi Brian,

I've encountered this message before,  however I was unable to reproduce this in-house with my own systems.  It seems to be be environment specific.

The discovered workaround is to append the end of the OpenDoc URL with:

&lsS

For reasons unknown it's been successful.  Give it a try and let me know.

Regards,

Wallie

[Former Member]

I managed to resolve this issue but unfortunately I still don't know the exact cause of the problem, however I will add that it would appear to relate to an issue in the system database rather than the web application deployment.

The fix below is good enough for a scratch environment but I might need to do some comparisons against the before and after system databases to see if I can identify the root cause. I'd like to avoid carrying out the the below post deployment of 4.1 in production.

Rebuilding the system database via the properties of the SIA in the CCM, followed by a reimport of the content using UMT resolved the issue. This fixed the problem in Chrome and Firefox however I was still seeing an issue in IE. After a bit of troubleshooting I spotted an issue with the cookies being sent back in the POST of view.do, flushing the winINET cache and winINET cookies using Fiddler fixed the residual problem in IE - hence the earlier questioning.

[Former Member]

Hi Brian,

I've replicated this issue in 4.1 SP2 Patch 1. Did you have any luck in finding the cause of this issue? Let me know as it might save me some investigative work.

Cheers

James

[Former Member]

No, I have not been able to determine where the issue is occurring. Using Firebug and comparing output from when it works vs. when it doesn't, it appears to go wrong somewhere after the POST to view.do, but I've no idea beyond that. SAP seems to have stopped troubleshooting it since they can't reproduce it.

[Former Member]

I have a few environments with this version and not all of them are showing the issue.

Couple questions:

Are you seeing this issue across all browsers?

If you look at cookie info for OpenDocumentPLATFORMSVC_COOKIE_CMS, does it list the correct CMS?

If you look at the POST body sent with view.do, note the &objIds=??? &containerId=??? ids, do they match the id of the object and the parent folder of the object in enterprise for which you specified a CUID?