This is a expected behaviour. Even though that is not working, is the meta data related to logshipping getting updated if they are then you can ignore this error.

Also if...