Ive followed docs, copied the crystal runtime msi that comes with vs2008 and installed it on the server 2003 x86. To make sure udt is working, please use below workaround. Im assuming you want to know how to fix this problem, as you dont seem to ask a question. Adodotnetinterop is not an option in the list of references. Engine dll and instantiate a new reportdocument object. Stack overflow for teams is a private, secure spot for you and your coworkers to find and share information. Try creating a new console project, and crystalreports. Have you checked you have crystal reports or a suitable runtime if. Also we find the main crystal report engine dlls are available in the following.
It scans your pc, identifies the problem areas and fixes them completely. If that works keep adding to it by importing a report and running it. Hi, we have installed the sap crystal reports support pack 9 64 bit. As well as the above, you need to point our assembly to gac folder ie c. These sites distribute dll files that are unapproved by the official crystaldecisions. The file and the associated crystal reports for visual studio. Make sure the same version is available on client machine.
435 92 587 1456 495 982 841 1590 1290 1124 137 1057 639 568 321 1404 275 511 1034 6 890 451 129 882 960 376 55 1429 217 751 601 1419 437 209 473 506 1301