Export report Excel-Data Only works not,'not enough memory for operation'

Question

Hi all,
we are using in our Software CrystalReport Version 11 Service Pack 5. Crystal report is intergated for .NET. We can not uninstall CrystalReport Version 11 Service Pack 5 to install another Version or another Service Pack.
We are haveing problems to export report as Excel 97-2000 Data Only, "not enough memory for operation" message pop up after you try to export report as Excel data Only.
Export Report as PDF is working fine.
This problems are on Windows XP Sp3 and Vista. On Windows 7 we have no problem.
Please, can somebody help me solving this problem, or to finde a workaround for Windows XP. Memory from PC is not the problem.
Mit freundlichen Grüßen / Kind regards
Odisej Nujiq

Answer 1

Odisej, unfortunately, processes such as remote sessions are reserved for phone cases only. You can create a phone case here;
http://store.businessobjects.com/store/bobjamer/en_US/pd/productID.98078100?resid=S6I@hgoHAkEAAGsiyVkAAAAR&rests=1282226845369
Also, just as an FYI, see the blog [What are these 'support' forums good for anyhow?|/people/ludek.uher/blog/2011/04/07/what-are-these-support-forums-good-for-anyhow]
Without phone support, you are left to do most of the foot work your self. On the forums, we can provide suggestions and guidance, but that is about it.
Couple of things to note though. If you do create a phone case, one of the 1st things that you will be asked is to update your app to SP6 - unless you can prove the same issue exists with SP6 (see more bellow).
Something I would recommend you try is to take an XP box, install SP6 on it, then install your app on it. If this works, your options are highly limited. E.g.; SP6...
One other utility that may be worthwhile to use is [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx]. Run that on the XP box. In the logs, look for "Access Denied" error messages. Look for load or other issues with crxf_xls.dll, exportmodeller.dll and crtslv.dll.
From your responses I am still not sure if you actually did run Modules and compared the results. This is much, much easier to do than working with ProcMon and I'd start there. To summarize, my troubleshooting plan (irrespective of the limits imposed on you) would be:
1) Use Modules as this is the easiest thing you can do
2) Try this with SP6 - more work that (1) above, but at least you are on the latest. If this works, banging your head into an SP5 wall will do you no good (like I said, irrespective of what ever limits...)
3) Use ProcMon - not too difficult, but time consuming as you will be looking over 100s, possibly 1000s of lines and not being familiar with details of CR, this will take time.
- Ludek