Issue with Template Connecting to SMA Connector

Robert_AutenRobert_Auten Customer IT Monkey ✭

I am trying to getup SMA Connector in our DEV environment.  I have the SMA Server configured, Azure Pack Server configured, installed the SMA Powershell Module on the SCSM server, and the Cireson SMA Connector installed on my SCSM Server.  I have imported the Management Pack, Created the SMA Connector, and configured my license.  I have been able to use Azure pack to create a few runbooks. 

I now am trying to create a request that kicks off one of the runbooks.  I am creating a template based off the SMA Connector.  Under Runbook, I am selecting the SMA connector and when I put in my credientals I get the following error.  Has anyone ran across this issue before?

Best Answer

  • Robert_AutenRobert_Auten Customer IT Monkey ✭
    Accepted Answer
    Yes I did.  If you are running SMA 2016 servers, you must run SCSM 2016 with the Cierson 2016 connector.  SCSM 2012 with the Cierson SMA 2012 Connector does not work with SMA 2016.  The Cierson SMA 2016 Connector is not supported with SCSM 2012 so therefore we have to upgrade to SCSM 2016 as well.

Answers

  • Robert_AutenRobert_Auten Customer IT Monkey ✭
    I would also like to point our we are running SCSM 2012 and our SMA servers are 2016.  Would that be part of the issue?
  • Robert_AutenRobert_Auten Customer IT Monkey ✭
    Something else is that if I add the Helper DLL reference to a C# application, RunbookWorker is not a member of the Runbook class.  So the question is, why is SCSM trying to find this object that does not exist?
  • Kristoffer_StormarkKristoffer_Stormark Customer IT Monkey ✭
    edited April 25
    Did you find a solution to this ? 




  • Robert_AutenRobert_Auten Customer IT Monkey ✭
    Accepted Answer
    Yes I did.  If you are running SMA 2016 servers, you must run SCSM 2016 with the Cierson 2016 connector.  SCSM 2012 with the Cierson SMA 2012 Connector does not work with SMA 2016.  The Cierson SMA 2016 Connector is not supported with SCSM 2012 so therefore we have to upgrade to SCSM 2016 as well.
  • Kristoffer_StormarkKristoffer_Stormark Customer IT Monkey ✭
    Thanks


Sign In or Register to comment.