Problem with .NET Merge module for Cystal XI R2 causing a reboot

[KevinNC]

I've been having lots of trouble with the .NET 2005 merge module. I've been having the same sort of problems with both the merge module that comes with VS 2005 and the one that you can download for Crystal Reports XI R2 (i'm currently using the XI R2 module). I'm installing the merge module from a setup built using Macrovision InstallShield Express 11.5.

The problem always occurs the first time I try to run an embedded report in the application after an installation or an upgrade of our software. One of three things will happen. Either the computer just reboots unexpectedly and without warning, or an exception is thrown and the computer reboots unexpectedly a few seconds later, or an exception is thrown but the computer does not reboot. The exact .NET exception message varies, one example is an exception in the type initializer for the ReportDocument class. Others include error messages loading various CrystalDecisions assemblies.

If the computer does not reboot itself unexpectedly, then the closing our application and running it again sometimes fixes the problem. In other circumstances, a manual reboot is required before the reports will work again. Once the reports are working successfully, they will continue to work fine on that computer until the software is reinstalled or upgraded. Also, we've tried performing the reboot ourselves after the installation, but this does not fix the problem. It has to occur after we've received the error message.

Our application is developed using VB .NET 2005 and .NET 2.0.

I haven't been able to find any information on this problem on the web. If anyone has encountered any similar problems and has any advice, your help would be greatly appreciated. Thanks.

 

[groggle]

The obvious troubleshooting things spring to mind.

1. Can you run the report successfully in Crystal Reports?
2. Can you run, embedded, the simplest of Crystal reports from your application? (one field, no sorting or grouping and minimal record selection)
3. Can your application call a blank text only report? (no data retrieved by the report?)
4. Progressively, increase the complexity of the Crystal report being called by your app.

Using steps like these you should be able to narrow down the cause of your problem. As with any troubleshooting it's all about finding that one difference between one stage and the next stage that triggers the problem...

I know it sounds like I'm telling you how to suck eggs but...

 

[LowellSKM]

We will be upgrading our runtime clients from Crystal 9 to Crystal XI. Any info on how to this? We are using Crystal X.