"System Message 6909 - Another process has already added the roidetail item" in ROI of SL 2015 CU1

(0) Share

Report

Posted on by Community Member

Hello All,

Our Client has recently upgraded to SL 2015 CU1. During the Print preview of the crystal reports, we see the system message "Another process has already added the roidetail item. The program must be terminated". This error shows up once in a while but not every time.

Any ideas on how to fix/workaround to avoid this message would be appreciated!

Thanks

Siva

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Suggested answer

Ram Peru 2,830 on at

Like (0)

Report

Hello Siva,

You have to check couple of things for this issue.

• Did you check to see if the index of ROIDetail has been properly upgraded to current version? Please verify the indexes with Standard Demo version. There might be the chances that Index was not properly updated with the Current version while doing the upgrade.

• If the Index was properly updated, I would recommend to run a SQL trace to identify the exact issues

Hope that helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I know your thoughts but I believe this issue is with the ROI. I see the behavior change in ROI in SL 2015 to build the RI_where clauses in the RPTRuntime table and this issue happens during the Print preview which makes me believe this is one among the ROI issue. FYI, the indexes are built correctly.

SQL trace would help to identify the data that the system is trying to update in ROI detail table but I’m inclined to consider this as an ROI issue but not environment specific. Curious to see if others are able to reproduce this issue.

Thanks

Siva

Was this reply helpful? Yes No
Lewis Shaw 641 on at

Like (0)

Report

We are also experiencing a similar issue.

I'm able to print preview reports without issue, however after I load some report templates (we created) I get an error message "Group Footer not available for total break. Total break request ignored." . After I get this message the report screen crashes and when I try to run the same report again I get the error you described above.

I am able to print preview other reports after this crash, and then return to the previous report and run it without issue. Assuming I don't load the same template again.

I suspect that there could be a template being used that is not compatible with the current CU1 2015 version of Dynamics which locks up the ROI and prevents the same report from being run.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (1)

Report

Hello,

We are encountering the same problem after upgrading to SL 2015CU1. It appears that the templates created in SL 2011 upgraded successfully but the templates created on SL 7 are causing errors. Every time the roi crashes it leaves a stray record in roidetail which eventually causes the 6909 Another process... error.

As a workaround/fix we have been deleting the templates and recreating as we come across the error. Not ideal when we have hundreds of templates.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello,

Yes, We recreated few templates in SL 2015 after migration to overcome the issue.

Thanks!

Was this reply helpful? Yes No
tknow 817 on at

Like (0)

Report

Stacie - can I safely clear the ROIDetail table?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes, you can delete from roidetail in sql.

Was this reply helpful? Yes No