Most of them appear to be upgading to Reporting Services rather than Crystal 10 - so perhaps this is not that much of an issue - but I would be interested to hear other viewpoints to establish where the industry is heading with one. Personally - I find this very disaapointing as I have a lot of customers still using Version 8 of Crystal Reports. Crustal themselves are horribly silent, saying only “8.x versions are not supported on Windows 2003”. Judging by the number of postings in Google Groups, it appears that a lot of people have found this issue, when upgrading to Windows Server 2003. I suspect the locked-down and hardened security found in Windows Server 2003 has hurt Crystal and this CRAXDRT.dll – and I suspect we may see the same issue in Windows XP SP2? These are assumptions - I don't fully know the reasonĮither way – I was able to resolve the issue by creating a COM+ Package (As a Server Application) and registering the craxdrt.dll in that package.
The common thread in all the above messages is “CRAXDRT”.ĬRAXDRT.dll appears to be the library responsible of rendering and exporting reports.
The problem manifests itself in the form of several errors when trying to export reports from the ActiveX Viewer
It appears as though Crystal Reports Version 8.x has incompatibility issues with Windows Server 2003.
0 kommentar(er)
