Resolving SQL databases plan error 0x0000000a

Behavior

The checkup report may report error 0x0000000a in the result column of a SQL databases type protection plan execution. A second entry for the same plan starting at almost the same time may be present in the checkup report with an OK result. See image.

Further, if your support person initiated a SqlPlanLaunch log file, the SqlPlanLaunch.log may indicate a log truncation error.
2019-03-09 04:11:49,197 [6] DEBUG SqlPlanLaunch [(null)] - Trying to launch SMO Truncate
2019-03-09 04:11:49,213 [6] DEBUG SqlPlanLaunch [(null)] - MinerResultsSuceeded, 
TruncateLogs set to true
2019-03-09 04:11:49,213 [6] ERROR SqlPlanLaunch [(null)] - 
An error occurred while attempting to truncate logs!!!
System.IO.FileNotFoundException: 
Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=11.0.0.0,

Issue

SQL log truncation for databases configured with the full recovery model fails because components required for log truncation are not present on the SQL Server.

Resolution

To resolve the issue install the required items listed below.

Microsoft® System CLR Types for Microsoft® SQL Server® 2012
Microsoft® SQL Server® 2012 Shared Management Objects

Both items are available here: https://www.microsoft.com/en-us/download/details.aspx?id=29065# under the Install Instructions section.