none
Not getting Any relationship from Get group replationship RRS feed

  • Question

  • I have two request offerings.  Test1 (RB1) & Test2 (RB2)

    both request offering does same tasks. both are identical. even runbook for both are same. RB1 is similar to RB2

    both runbooks (RB1 & RB2) adds user into AD group.

    but if i raised SR from Test2 and do testing in runbook designer  RB2 then it shows 0 count in "Get Group Relationship"

    i know RB2 & RB1 both are same and have no configuration issues. 

    if i raised SR from Test1 and do testing in runbook designer  RB1 then it shows 1 count in "Get Group Relationship"

    if i use RB1 ID to test in RB2 then also RB2 works fine and show object count in  "Get Group Relationship" at RB2

    if i use RB2 ID to test in RB1 then  RB1 does not and show object count in  "Get Group Relationship" at RB1.

    but not sure why SR raised from Test2 and its RB does not creates relationship.

    below is the configuration and structure of RB


    Monday, April 15, 2019 7:58 AM

All replies

  • It could be down to permissions, can you confirm that both runbooks are using the exact same SCSM Connections in the runbook designer settings.

    It clearly seems like RB2 has an issue so if any permissions were cause of issues it would be specifically on there, but as the ID is being passed from your SCSM SR it may even start from there

    You have said that they both do the same thing, both request offerings.
    Can you explain in further detail what both Request Offerings do exactly, so we can trace it and see where there could be a problem?


    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Monday, April 15, 2019 9:19 AM
  • I dont see Runbook RB2 has any problem 

    1

    Service offering 1 -> Request offering 1 (it takes User name and group name  from querying AD) -> one Review Activity -> RB1 ( it adds mentioned user into mentioned group)


    2

    Service offering 2 -> Request offering 2 (it takes User name and group name  from querying AD) -> one Review Activity -> RB2 ( it adds mentioned user into mentioned group)

    Both Have same SCSM connection

    both runs from same account 

    hence it does not seems to be permission issue

    Issue :- 

    In Service offering 2 -> RB2 - > "Get Group membership" does not gets an object (object count 0)

    if i use "Service offering 1 -> RB1's"  ID and do testing on RB2  in runbook tester i am able to get 

    "Get Group membership"  and object (object count 1)

    So it means both RB1 and RB2 are configured correctly. 

    but dont know why if i raise SR In Service offering 2 -> RB2 - > "Get Group membership" does not gets an object (object count 0)

    Monday, April 15, 2019 9:44 AM
  • Ok, so with Runbook tester it will run with the account you are currently logged in with. Do you get the exact same result when running both runbooks when they are triggered from SCSM rather than using the runbook tester? Even though runbook tester can be helpful it doesn't always capture a proper scenario unless you are using the runbook service account to do it.

    So both Service offerings are configured exactly the same or do they pull different groups/accounts for different reasons? Do they have a completely different purpose from each other? If they are both configured exactly the same then may I ask why do you have two service offerings that do the same thing, attached to runbooks that are configured exactly the same?

    There has to be a fundamental difference between both service offerings. I would say something has to be wrong in your second service offering, where it could be passing an object guid to find an AD group which doesn't exist.

    I would try taking the ID you are passing from your 2nd Service Request manually, then have a test runbook that specifically checks the object either with a Get AD Group activity from your AD Integration pack or Get relationship in your SCSM integration pack and go from there.


    Also you could do a step-through on runbook tester so that you can see exactly to what your Object guid resolves to


    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro


    • Edited by Dwalsham Monday, April 15, 2019 10:22 AM more words
    Monday, April 15, 2019 10:21 AM
  • The Runbooks have both a related "Runbook Automation Activity" (RBA) in SCSM?

    Which parameter(s) are you providing in the "Initialize Data" actvity in the 2 runbooks?

    If you look in the SCSM console in the RBAs both have a related Group?

    Both related Groups are the same in each RBA?

    I am doing always an additional step in my runbooks similar to yours:

    • Initilize Data is getting the mapped ID (not the GUID!) of the RBA (for instance RBA1234)
    • "Get RBA object" filter on ID = ID of Initialize Data (this way I am sure I get the right related RBA object in my Runbook, because I am bad with comparing GUIDS ;-))

    From there I am doing the same like you:

    • Get Relationship of RBA-2-Group, RBA Class -> Filter on SC Object Guid of "Get RBA object", Target class AD Group
    • Same with the Get Relationship of RBA-2-User

    Never had any problems with doing it this way (beside I screwed something up by my miss-clicking :-))

     

    Andreas Baumgarten

    Monday, April 15, 2019 10:27 AM
  • Yes I do get same result from runbook tester and scsm 

    because both uses same account.

    I have created two request offering which performs almost same task. Add users into group (only difference between request offering 2 is in Group query result i have allowing specific groups to be query to AD depends on floors so we have naming convention) 

    and in 1st request offering Group query results is open to search all AD groups. 

    Sure i will try to check each steps to find out what object guids resolves to.

    Monday, April 15, 2019 11:41 AM
  • Hi Andreas :)

    Both Runbooks are not related to each other but both are independent. 

     "Initialize Data" actvity in the 2 runbooks -- i am providing runbook ID generated from SCSM portal.

    Monday, April 15, 2019 11:45 AM
  • That was not my question ;-)

    "The Runbooks have both a related "Runbook Automation Activity" (RBA) in SCSM?" means: Each runbook in SCORCH has a related "RBA in SCSM"? These individual RBA objects are related to the SRs via SR template in SCSM.

    With ID do you mean the "RBA123x" value? Or the GUID of the RBA, for instance "d3525757-9b00-4768-b946-d99a1fe33400"


    Andreas Baumgarten

    Monday, April 15, 2019 11:55 AM
  • my BAD, :)

    its GUID, that i am using to test in runbook tester, for debug. and yes  These individual RBA objects are related to the SRs via SR template in SCSM.

    Monday, April 15, 2019 12:42 PM
  • Hi,

    is it the GUID of the actual service request in SCSM you are passing through or the AD group object?
    If using the GUID of the service request then yes get a couple test runbooks with just one step to validate fully all the details of the one you are forwarding from the your 2nd Service offering to ensure its details. this will tell you if you have an issue that side


    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Monday, April 15, 2019 1:18 PM
  • Hey Dwalsham, 

    Sorry for late reply i was on leave.

    let me explain you what i am doing 

    please see below diagram. i am using Runbook GUID to test in runbook tester. i am not sure but this is how i have found solution to debug runbook. i am using this method since last 2 months and created many runbook by testing in this way. 

    earlier if i select any runbook GUID and start debugging in runbook tester it was working fine. but now from last week what happen i dont know while debugging its not creating relationship. 

    as you have mentioned in your earlier reply, i checked directly without runbook tester, the same affected runbook, voila !!!!! it worked fine. but only in runbook tester dont know what happening. i have changed nothing at permission level, everything is same as earlier. then not sure what is the problem, i want to continue this testing method to find out if any issue occurs in future, once these will come into production  to support.

    Thursday, April 18, 2019 9:36 AM
  • Thanks for the reply

    I figured it would work using it that way without runbook tester.

    How it works is not necessarily permissions but the accounts that are used when you run them.

    So using the Start Runbook option would use the Runbook service account in orchestrator. Where as the runbook tester, would use your account specifically that you are logged in with, unfortunately there isn't a really a way to elevate permissions or use a different account in those steps.

    it could be your account might not have permissions on the SCSM DB level which is why it cannot find any relationships. could this be the case with your account or is yours an admin in SCSM?


    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Thursday, April 18, 2019 12:25 PM
  • how did you manage to get on with this?

    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Tuesday, April 23, 2019 9:59 AM