Link to home
Start Free TrialLog in
Avatar of Carla Romere
Carla RomereFlag for United States of America

asked on

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

I have a reports website that serves up Crystal Reports via our SharePoint intranet site. Just now, we have started receiving the above error on all the Crystal Reports pages followed by:

private void SetDBLogonForReport(ConnectionInfo connectionInfo)
Line 79:     {
==>>Line 80:         TableLogOnInfos tableLogOnInfos = crystalReportViewer.LogOnInfo;
Line 81:         foreach (TableLogOnInfo tableLogOnInfo in tableLogOnInfos)
Line 82:         {

These pages have been working correctly for months and as far as I know nothing has changed on the reports nor on the server itself. What do I need to be checking to see what is causing this error all of a sudden?
Avatar of Mike McCracken
Mike McCracken

Check the permissions on all the report files.  Also ensure no report files have be accidentally deleted.

What version of Crystal and Visual Studio?

mlmcc
Avatar of Carla Romere

ASKER

Nothing has changed on the permissions side and all the reports are still physically there. I'm using VS 2010 with the SAP Crystal Reports add in. We have the path defined in a constants file as:

        public static string ReportsFolder = "\\\\sdwinerp01\\d$\\Ross\\Soft\\ERPWebComponents\\CrystalPDFViewer\\reports\\";

And that path works perfectly. It's happening on ALL the Crystal Reports now.
SOLUTION
Avatar of Mike McCracken
Mike McCracken

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
GRrrrrrrr. We found the issue and have resolved the problem. The reports are located on a different server. We were having other issues on that server also and discovered there was an IP address conflict on that server with an access point someone had hooked up to a pc to configure. Once that access point was removed and the pc got its DHCP IP address back, the server was completely happy once again and reports are running as they should.