An exception was caught but handled while releasing a COM interface pointer through Marshal.Release or Marshal.ReleaseComObject or implicitly after the corresponding RuntimeCallableWrapper was garbage collected. This is the result of a user refcount error or other problem with a COM object's Release. Make sure refcounts are managed properly. The COM interface pointer's original vtable pointer was 0x%1$x. While these types of exceptions are caught by the CLR, they can still lead to corruption and data loss so if possible the issue causing the exception should be addressed
An exception occurred during the Commit phase of the installation. This exception will be ignored and installation will continue. ...
An exception occurred during the Rollback phase of the installation. This exception will be ignored and the rollback will ...
An exception occurred or a null was returned after calling the CreateConnection method on a store provider instance of type ...
An exception occurred while uninstalling. This exception will be ignored and the uninstall will continue. However, the application ...
An exception was caught but handled while releasing a COM interface pointer through Marshal.Release or Marshal.ReleaseComObject ...
An exception was caught but handled while releasing a COM interface pointer through Marshal.Release, Marshal.ReleaseComObject ...
An exception was thrown from the CleanupNativeData method of a custom marshaler of type '%1$s'. This may cause an unmanaged ...
An expected satellite assembly containing the ultimate fallback resources for a given culture was not found or could not ...
An Export specification convention that would apply to Member '{0}' of type '{1}' has been overridden by attributes applied ...