SMA connector occasionally fails to start runbooks.
Curious if anyone else is running into this issue wherein very, very, very occasionally the SMA connector fails at kicking off the runbook. The result returned in the runbooks is always the following:
Execution of the job failed.
The 'Start-SMARunbook' command was found in the module 'Microsoft.SystemCenter.ServiceManagementAutomation', but the module could not be loaded. For more information, run 'Import-Module Microsoft.SystemCenter.ServiceManagementAutomation'.
The error alone seems to point to the PS module being at fault, but the fact it works an overwhelmingly large majority of the time only further clouds the troubleshooting here.
Is there any verbose logging that could be enabled for this connector beyond the above output?
I've had no experience with SMA, but I've had SCSM/SCORCH issues recently. With any luck this is also relevant to your instance.
Actually @Leigh_Kilday, I believe point number 3 of yours I think was fixed in a UR release. But if you're on the latest version across the board, I'm clearly in error.
I wonder if the best way to go about this (although I'm not even sure what i'm looking for at this point) is procdumping this, and even still if that would reveal anything than the above error message.
Thanks @Adam_Dzyacky, we haven't applied UR9 yet. Between the reissue and us going live with SCSM/Cireson we forgot about it.