Uninstall all Crystal Reports runtimes, if any. NET Framework (this rolls back the system to the default version. NET Framework 4.6.1 (Visual Studio 2010 and ALL it's dependencies, including SQL Data tools, etc.) NET Framework 4.6.1 will not do the trick, because it leaves files lingering around unless programs that use it are also uninstalled first! To add fun to the party, just uninstalling. They simply won't play game, and there's no command-line switch to the Crystal Reports Runtime installer to skip VC++ Runtime checks. NET Framework 4.6.1, then all Crystal Reports Runtime installations will fail with very obscure messages related to WinSxS and so on. So if you're on Windows 7 and you have already installed, for example. This wouldn't normally be much of a problem, but it turns out that the installer is also somehow incompatible with. It will not recognize itself or later 2005 builds as already installed, so an install will always be attempted, even if unnecessary. The reason is that the installer for Crystal Reports Runtime v13.x declares a dependency on the Visual C++ Runtime 2005, but that installer is in turn very broken. I fought this exact problem today with both 圆4 and x86 versions of the Crystal Reports runtime, and I found a (painful) way to install them after all.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |