![]() So uninstall of update with KB3102429 seems to fix the problem for now. He also refer to the SAP Forum for more information. I can confirm that uninstalling KB3102429 reverted to v6.87 of both fonts and solved the problem for me. I have not yet tried to reproduce the problem on Windows 7 but I have seen reports that this update does cause a similar problem on Windows 7.Ī workaround is to replace the TNR and Arial fonts in the report with other fonts, at design time or runtime. We had a similar problem with TNR v6.85 (initial Windows 8.1 release) but it seems to have been fixed by v6.87. KB3102429 has different versions of fonts for Windows 7. V6.90 of both fonts (Windows 10) also seem to work fine. ![]() Previous v6.87 of both fonts worked fine. (I suppose it is possible it’s not the font files causing the problem but some other file included in the update. Problem observed with v6.88 of both of those fonts, included in KB3102429, installation of which definitely caused the problem. It was released for download on November, 17, but rolled out during the December, 8 patch day.īen Dafydd Gillard has posted on the Microsoft Community and seems to found the problem is within the font updates, especially the version : This time it is “Update that supports Azerbaijani Manat and Georgian Lari currency symbols in Windows” ( KB3102429). ![]() Like yesterday, it seems that another update is rolled out that will break your clients that using the export function of Crystal Reports to PDF. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |