CRVS 2010 RTM issues locking and crashing VS2010

[Former Member]

I finally had some time to test the RTM of Crystal Report 2010 for Visual Studio 2010 on a new machine but I have not had much luck getting it to work. When I try to use "Database Expert" VS 2010 locks up. Trying to use "Set datasource location" causes VS2010 to crash. I seen a few related posts with similar issues but nothing that really fixes it.

Faulting application name: devenv.exe, version: 10.0.30319.1, time stamp: 0x4ba1fab3

Faulting module name: saxserialize.dll, version: 13.0.0.99, time stamp: 0x4cc41568

Exception code: 0xc0000005

Fault offset: 0x0000398a

Faulting process id: 0x16c8

Faulting application start time: 0x01cb98a76e2ceb65

Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe

Faulting module path: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\saxserialize.dll

Report Id: 2071bad8-049e-11e0-a2f7-842b2ba5b870

[former_member208657 · Accepted solution]

Can you please check to see if there is any conflicting Crystal Reports runtime loaded when you are editing your report? You can use tools like Process Explorer or [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] to check. You'll want to specifically look for the version 13.0.0.99 files, plus anything else Crystal from the past.

Such as

9.1

10.0

10.2

10.5

11.0

11.5

12.0

[former_member11696]

Hi Brad,

See this and other threads for more info:

Is this only with old reports or when creating a new report?

So far we have not been able to duplicate the issue in Support and all logs and various process explorers are not helping to determine the cause of this issue. It's not happening on many users PC's so there is likely a unique combination of install orders or missing deep down dependencies causing the problem.... I think...

If you can please use the other links to add your notes and tests to so they are in one place.

One of the suggestions was to rename the dll. See if that works for you? Side effect may be that you can't open old reports.

Thank you

Don

[Former Member]

Both new, old and converted old reports all lockup or crash VS2010. Renaming saxserialize as suggested fixed the newly created reports but old or converted reports will not open after the rename like you have said.

I tried creating a new report and importing a old report but it still would crash.

[Former Member]

Hi,

I have exactly the same problem. Is there any solution? It this realy frustrating..

Bostjan

[former_member11696]

Hi Guys,

On another case of this type it was noted that once all of the database tables that were not used in the report were removed and then the Report Verified all reports started to work. After saving, closing VS down and then opening and testing again.

Please test, open up a report in which ever version of CR Designer you have. Remove all objects that are not used starting with the tables and then moving to formula etc.... and see if that works.

Also curious to know if you have any OLE Objects or Pictures embedded in your reports?

If so what happens if you double click on that type of image outside of Crystal Designer or Visual Studio? What opens the image up or does the OS prompt you to select a program?

Thank you

Don

[Former Member]

I don't have any extra unused parameters, tables or formulas. So I just deleted everything from parameters to fields on the report I been testing with. Once cleared and I then verified the database. The report did start to work at that point. So deleteing eveything worked. I next tried to delete one group of things at a time. I started with parameters only but had no change. Next I deleted the sub-report. After I deleted that the main report started to work the next time I restarted VS2010. I restored my report and deleted just the sub-report this time hoping it was just that casuing the issue but that did not fix it. I'm not sure why removing the parameters then the sub report worked.

[former_member11696]

Hi Brad,

Thank you for the test info. The subreports use parameters also when you link the main to the subreport which explains why not removing both did not work.... I think we are getting closer.... Our Parameters UI uses the Java JDK and both the saxserialiser and the log4net are both java extensions....

mmmmmm.... Need to do more testing now...

Thank you so much for testing

Don

[Former Member]

Hi,

I have got this error even if I created new report

[former_member11696]

HI Guys,

Check this post out.. We have made progress on possible causes...

Thank you

Don