It can be done manually with the use of regedit.exe, but since it can be automated, here are the scripts:ĬHECK THE FILES CONTENT BEFORE RUNNING! (they are just text files) DON’T RUN THIS OR ANY OTHER SCRIPT WITHOUT CHECKING. To enable logging the first four should be set to 1 and the last to a existing directory path (it should also end with an \).
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\LogPath - Type String.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\LogResourceBinds - Type DWORD.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\ForceLog - Type DWORD.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\EnableLog - Type of DWORD.
In this case, it only needs to be turned on: Enable assembly binding logging (Fusion log)Īssembly binding is turned on using those registry settings: This post is an analysis of why this happens and how to diagnose it:
See you next time.The method 'XXXX' was not found on the interface/type 'YYYY, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null'. Hope the blog this week can ease your headache of email issue. Then, open Sage 50 again and verify if you can email or print your forms. Your browser will then has a popup asking you to either run or save the download.Īfter download is completed, please run and install it. Make sure you select VSU_4\vcredist_X86.exe (6.3MB) and then click Next. When you click the download button, you will be given different download options. This link to get the Microsoft Visual C++ 2012 Redistributable (X86) is written as follow: If it is not found, again, please manually download and install it from Microsoft. If you find it, please uninstall it and then reinstall it from Microsoft. You will go to Control Panel, Program and Features (Windows Vista, 7 & 8) or Add and Remove Programs (Windows XP), and look up Microsoft Visual C++ 2012 Redistributable (x86). The resolution of fixing this file is pretty simple. Due to the fact that in 2014.3, government forms gets migrated from Crystal form to PDF form, if the PDF create library file,, is missing or not registered properly in Windows, you will also see this unhandled exception error popping up. Therefore, this problem is not related to the 2014.3 release.īesides difficulty to email, some users may also have issue of printing T5018, T4 slips or ROE. In fact, this error can also happen before our product update or after a Windows update. Some customers may have experienced this email issue after updating to Sage 50 2014.3, especially for those clients who are still using Windows XP.
0 kommentar(er)
