locked
Orchestrator Connector for SCSM RRS feed

  • Question

  • When attempting to create the Orchestrator 2012 connector for SCSM I receive the below error message. I am putting in for the Orchestrator Web Service URL: http://servername:81/orchestrator2012/orchestrator.svc

    The account I am using is the Operational Database account. It is a Local Admin on our Orchestrator box, it is a Domain Admin account, it is a SCSM Admin account, and it is also a member of the user group we created when setting up Orchestrator.

    I've read through both http://blog.scsmfaq.ch/2011/11/12/news-in-scsm12-beta-8-permissions-for-triggering-system-center-orchestrator-runbooks/ and http://blog.scsmfaq.ch/2011/11/01/news-in-scsm12-beta-7-connectors/ and am not sure what I am missing.

    Any help would be greatly appreciated.

    Date: 2/29/2012 1:21:24 PM
    Application: System Center Service Manager
    Application Version: 7.5.1464.0
    Severity: Error
    Message: Could not connect to the Orchestrator web service.


    System.Data.Services.Client.DataServiceQueryException: An error occurred while processing this request. ---> System.Data.Services.Client.DataServiceClientException: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
    <title>401 - Unauthorized: Access is denied due to invalid credentials.</title>
    <style type="text/css">

    Wednesday, February 29, 2012 6:28 PM

Answers

  • Finally got this to start working once we went to SCSM 2012 RTM.
    • Marked as answer by Mike Neal Thursday, May 24, 2012 2:09 PM
    Thursday, May 24, 2012 2:09 PM

All replies

  • Always create the connector from your SCSM server and not from a SCSM Console on a desktop :(.... Lesson learned.

    Still having issues though with being able to see the Runbooks I create in SCORCH populating in to SCSM.

    Wednesday, February 29, 2012 6:37 PM
  • Hey

    Are your runbooks starting with an "Initialize Data" activity and are they checked in?

    regards
    Marcel


    SCSMfaq // Blog --> http://blog.scsmfaq.ch // Twitter --> #scsmfaq // Business --> http://www.itnetx.ch

    Wednesday, February 29, 2012 6:43 PM
  • I was trying to start off with building the SharePoint announcement piece: http://contoso.se/blog/?p=2817 

    So as of right now its just Monitor Ojbect -> RTF To Plain Text -> Create List Item

    And the Runbook is indeed checked in.

    Another interesting thing is we have an additional Runbook for just a new Service Request, which when i go to the Orchestration Console I can see it visible out there, but I do not see the one I created for the SharePoint piece. Neither, however, are showing up in SCSM even after syncing the SCORCH connector.

    Wednesday, February 29, 2012 6:52 PM
  • Hey

    This solution uses a different approach as it checks for new objects (announcements) in SM and then triggers the runbook. In this case it's not needed to sync this runbook to SM. Sync is only needed then you want to use trigger a runbook from a CR or SR (or other Work Items). In this case you use a "Initialize Data" activity to start the runbook.

    Create a test runbook with "Initialize Data", check it in and start the SCO connector sync. Then check if the runbook is visible ...

    regards
    Marcel


    SCSMfaq // Blog --> http://blog.scsmfaq.ch // Twitter --> #scsmfaq // Business --> http://www.itnetx.ch

    Wednesday, February 29, 2012 6:56 PM
  • Just created one with "Initialize Data" and then checked it in. After the sync still nothing coming in to SCSM related to it, and it also does not show up in the Orchestration Console either.

    When I try to run the SharePoint runbook I am getting an error as well, so it just feels as if something is off and I can't put my finger on it as of yet.

    Wednesday, February 29, 2012 7:04 PM
  • The error says "Unauthorized", means you have an authentication problem.

    SCSMfaq // Blog --> http://blog.scsmfaq.ch // Twitter --> #scsmfaq // Business --> http://www.itnetx.ch

    Wednesday, February 29, 2012 7:09 PM
  • The account we are using is a SharePoint site administrator on top of admin access to all the other items mentioned before. We also tried our Farm Administrator account and both continued to get that error message.

    When I create the SharePoint Connection, it is able to access SharePoint to know/pull the data related to creating the announcements as well. So I'm not sure where that is referring to as having an Authorization Issue.

    • Edited by Mike Neal Wednesday, February 29, 2012 7:16 PM
    Wednesday, February 29, 2012 7:15 PM
  • Hmmmm, strange. But I'm not a SharePoint Specialist and therefore cannot help you out there. But it's still strange that you are also not able to sync a simple runbook to SM.

    SCSMfaq // Blog --> http://blog.scsmfaq.ch // Twitter --> #scsmfaq // Business --> http://www.itnetx.ch

    Wednesday, February 29, 2012 7:17 PM
  • Yeah we can't even find any sort of failure audits on the SharePoint server, SCSM Server, or even SCORCH Server that is showing this 401 Unauthorized issue. I also agree it seems odd we can't sync just a Initialize Data to SCSM, not sure where else to go or look for this.
    Wednesday, February 29, 2012 7:49 PM
  • Finally was able to get Runbooks to sync to the SCSM Console. Still having the problem though with the Create Announcement piece from Orchestrator. We registered SPN's for our service account to get the other piece working but still the same 401 Unauthorized when running the SharePoint item in Runbook tester.
    Friday, March 2, 2012 6:59 PM
  • Curious if anyone else has been successfully able to get this working in their Test Environment, be interested in knowing what all steps you took or your set up. I've rebuilt a test environment from scratch and still get the same 401 Unauthorized error. All SPN's are correctly registered, I used 1 domain admin account to do all of the set up, and its the sole account for Farm Administrator, Service Manager, Orchestrator, etc...
    Tuesday, March 6, 2012 6:00 PM
  • Hi Mike

    I had the same issue. My config below. Works perfect. Where support is I create a new site and change the name from smportal to support. Hope this helps.


    Steven Lokanan System Center

    Thursday, April 12, 2012 2:52 PM
  • Finally got this to start working once we went to SCSM 2012 RTM.
    • Marked as answer by Mike Neal Thursday, May 24, 2012 2:09 PM
    Thursday, May 24, 2012 2:09 PM