%11SMS Executive could not start this component because it could not determine the address of the ThreadMain() function exported by \"%1\" using the Win32 GetProcAddress() function.%12 Possible cause: The DLL was somehow corrupted or deleted. Solution: Restore the DLL by manually copying it from your installation media to \"%1\". Possible cause: This is a defective DLL that is part of an add-on product to Microsoft Configuration Manager. The DLL is defective because it does not export a ThreadMain() function. Solution: Contact the manufacturer of this product for more information.%0
Site System Status Summarizer successfully accessed the transaction log for the "%1" database on SQL Server "%2". The transaction ...
SMP Control Manager detected SMP is not responding to HTTP requests. The http error is %1.%12 Possible cause: IIS service ...
SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is %1, %2.%12 Possible ...
SMS CI Assignment has been directly deleted from the site Database. Deletion of collection may cause the deletion of all ...
SMS Executive could not start this component because it could not determine the address of the ThreadMain() function exported ...
SMS Executive could not start this component because it could not load \"%1\" using the MFC AfxLoadLibrary() function.%12 ...
SMS Executive detected that this component stopped unexpectedly.%12 Possible cause: The component is experiencing a severe ...
SMS Executive is scheduled to start this component now, but cannot because it is already running. Possible cause: The component ...
SMS Executive will never start this component because it is never scheduled to run. If you want SMS Executive to start the ...