A document processed by the JRC engine cannot be opened in the C++ stack.

[Former Member]

Hi,

I have a web application running on a Windows server Standard 2008 with SP2 (64-bit), and when I open a crystal report I get this error:

Message: Operação não permitida. Um documento processado pelo mecanismo JRC não pode ser aberto na pilha de C++.

(A document processed by the JRC engine cannot be opened in the C++ stack.)

Source: clientdoc.dll

This problem exists only in some servers. I create a virtual machine with windows server Standard 2008 R2 with SP1 (64bit), and I didn´t get the error above.

So why, I have the problem on the 1st server and not on the VM?

1. One difference is that the 1st server is u201C2008u201D and the VM is u201C2008 R2u201D.

2. Another difference is that in the 1st server Iu2019ve my website outside the inetpubwwwroot folder, and I cannot put on that folder.

Can anyone help, please?

[former_member188030 · Accepted solution]

Hi,

Please provide-

- Version of CR

- Version of VS

The possible cause to the issue is, the application is not able to find the crystal reports (.rpt files).

Take a look at below threads

[http://forums.sdn.sap.com/thread.jspa?threadID=2011850|http://forums.sdn.sap.com/thread.jspa?threadID=2011850]

[http://forums.sdn.sap.com/thread.jspa?threadID=1975259|http://forums.sdn.sap.com/thread.jspa?threadID=1975259]

[http://forums.sdn.sap.com/thread.jspa?threadID=2031409|http://forums.sdn.sap.com/thread.jspa?threadID=2031409]

[1603477 - Error: A document processed by the JRC engine cannot be opened in the C++ stack |http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333633303333333433373337%7D.do]

Things to check the machine on which the error occurs,

- Check if the reports exist in the proper location. (location specified in code)

- Check if the rpt. files are itact. (compare the file sizes of the reports with your dev machine.

- Check if the application has the permissions to access the reports.

- Bhushan.