| Event Id | 4128 |
| Source | Transaction Server |
| Description | The run-time environment was unable to load an application component due to either an error obtaining its properties from the catalog, loading the DLL, or getting the procedure address of DllGetClassObject. This error caused the process to terminate. <path and file name for the component DLL> (Package: <package name>) (Microsoft Transaction Server Internals Information: File: <file name and line number>) |
| Event Information | According to microsoft: This error indicates that Microsoft Transaction Server (MTS) cannot access the component dynamic-link library (DLL) that is referenced in the error description. The three most common causes of this error are insufficient permissions, a missing DLL, or a corrupt DLL. This error message does not occur in Microsoft COM+ under Microsoft Windows 2000. Troubleshooting 1. Verify that the component DLL exists at the location that is indicated in the error description. If you have moved the DLL for any reason, you must remove it from MTS and reinstall it from its current location. 2. Verify that the identity of the MTS package has sufficient NTFS permissions to access the DLL. The identity account must have at least Read permission on the folder where the DLL resides. For more information about how to troubleshoot permissions errors on MTS DLLs, see the "References" section. 3. Confirm that the DLL is not corrupt. The easiest way to do this is to verify that the component can be instantiated through OLEView, which comes with Visual Studio . You can download the stand-alone version of OLEView by clicking this link <a href="http://www.microsoft.com/com/default.mspx" target="_blank">COM: Component Object Model Technologies</a> |
| Reference Links | More Info |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.