![]() ![]() I was curious if I could fix this issue without creating an MST. The OP of that issue was able to resolve it by creating an MST to shorten the file and registry paths. NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86 ![]() NET Framework 4.0\Common\Crystal Reports 2011\crystalreportviewersĬ:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for. I checked out the installation path for the Crystal runtime and it sure has some long paths!Ĭ:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for. Which in turn ‘broke’ crystal integration with the application. It appears Microsoft fixed some issues with buffering in the updated Service Pack. I found a similar issue on the TechNet forums where an application that used Crystal runtime 13 worked properly in App-V 5.0 RTM, but not with SP2+. It complained about a particular GUID and not being able to locate some DLLs. The application worked properly when natively installed on a machine, but thew errors when it was virtualized with App-V 5. I recently ran into an issue sequencing an application that uses the Crystal Reports runtime 13. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |