on 06-22-2011 9:57 AM
Hy everybody,
I develop a Wpf application FrameWork 4.0 on Windows 7 64 bit with VS 2010 and Cr 13.
On my machine, no problem with Crytal Report
When I deploy my application on a Windows 7 32 bit : no problem with my crystal reports
When I deploy my application on a Windows XP 32 bit : the crystal reports doesn't work.
When the code arrive to rpt.SetDataSource or rst.SetParameterValue, my application close without any error message.
Strange : I deploy my application on 3 XP. On 2 XP, just after de deployement It has work (two times it has show the report) but then the application close. Uninstall all and reinstall, it has never worked again.
Some help please
Regards
Gridin
See if [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx] tells you anything
Use [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] to compare the runtimes.
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
can you supply some code?
ie - app.config
code on how you call the report may then able to help more?
I remember the bad old days - what as called dll hell -
One other option (this I have done):
Uninstalled the program then .NET4 runtime, then crystal , rebooted then re installed .NET4 runtime do a reboot , then install crystal runtime then a reboot then finally the program, run program if any issues check event viewer and post any error messages from the event viewer. ( I had to do this on one XP machine, turned out a old app had some ddl's register for crystal 9 , causing the issue).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Had same issue -
Install full verison of .net 4 - not client
ensure you install crystal runtime, and the following is in your App.Config file
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
</startup>
this did the trick for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the feedback Michael. Excellent. Forgot that XP more than likely will not have framework 4...
The app.config file suggestion may only be useful if the app is consuming ADO .NET Datasets, but perhaps not...
Gridin, I'd really appreciate your feedback on Michael's suggestions.
- Ludek
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.