I was just searching for this error as it just occurred on my instance as well. Although it wasn't identical, I wanted to put this out there if anyone else runs into the same problem when searching.
SQL Server Standard 2017 (14.0.2027.2)
SSMS 2018 (v.18.5.1)
Went to create a new maintenance plan (the first one on this server and named instance) ...