Symptom
- .Net Framework update causes Crystal Reports for Visual Studio to create a unique folder path to the Crystalreportsviewer13 folder in IIS and IISExpress DEV.
- Each time the framework is updated by Microsoft Windows, it gets a new generated number X_X_xx\crystalreportviewers13.
Environment
- Crystal Reports for Visual Studio
- Windows 7
- Windows 8.x
- Windows 2012 Server
- Windows 2016
- Windows 10
- Businessobjects Enterprise Platform .NET SDK 4.x
Reproducing the Issue
- Install a new Microsoft Windows update.
- Notice that the path to crystalreportviewers13/14 has been chaged and a new .Net Framework related number has been generated in the path X_X_xx\crystalreportviewers13/14.
Cause
- MS provide the update to .Net Framework (e.g: .Net 4.6) via Windows Update.
- .NET web site will target the .Net 4.6 app pool, CR viewer will try to find the viewer resource file(js & icon) from ..\system_web\4_6_xx\crystalreportviewers13/14\
- The xx is the small version of .Net Framework 4.6.
- For example on Win10 RTM, it is 4_6_79;
- on Win7+ it is 4_6_81,
- if a user installed KB3098786 it will be 4_6_118x.
- The version number will change again when the next KB update for .Net Framework 4.6 is installed.
Resolution
The issue has been fixed:
Crystal Reports for Visual Studio SP20
Crystal Reports for Visual Studio SP21
BOE 4.0 - no fix available due to end of patch cycle
BOE 4.1 SP 10 or higher
BOE 4.2 SP 4 or higher
Any release after April 2017.
Workaround:
Manually update the Web.Config file to include the updated version of the Framework and then to copy the \CrystalReportsViewer13 folder into the new path: ..\system_web\4_6_xx\crystalreportviewers13\
See Also
Keywords
Crystal Reports for Visual Studio, cr for vs, \aspnet_client\system_web\4_X_xx\crystalreportviewers13\, 4.6 framework, iis, \aspnet_client\system_web\4_X, BOE .NET , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Problem