Jump to content

Graham

Hornbill Developer
  • Posts

    66
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Graham

  1. @Ben Maddams In that case, as a final check that the SIS service is listening, can you run
     

    netstat -a | find "11117"


    from a command prompt on the machine running the SIS service? I'd expect to see:
     

      TCP    0.0.0.0:11117          <name of server>:0             LISTENING
      TCP    [::]:11117             <name of server>:0             LISTENING

    which means the service is listening on that port, and I would expect http://10.5.1.153:11117/ to produce the status page from a browser local to that machine (if there is one installed).

  2. @Ben Maddams Thanks for that. The fact that the job doesn't do what it's supposed to isn't a problem - running the job on the SIS service, rather than on the DC, was the key diagnostic.

    Regarding the "job successful", there are two things in play here:

    1) Was ITOM able to process the package?
    2) Did the package's processing produce the desired effect?

    The "job successful" refers only to the first of these. ITOM was able to connect to the target, start the package processing and received notifications that the processing "happened". 

    That does all point to there either being a communications issue, or something else is interfering with how the remote executable is being processed on the DC.

    Is there any anti-virus on the DC?

  3. @Ben Maddams This is proving to be a bit of a puzzle! 

    Can you try two things for me, please

    1) Run the job with a target of the machine running the SIS service itself
    2) Run the job targettting the DC, but without setting the "RunAs" credentials

    Hopefully the results from those will shed some light on what's going on.

    One other thought - is there any anti-virus software on the DC that could be seeing a new executable running and terminating it?

     

  4. @Ben Maddams Thanks for that. It rules out one thing for me.

    This still appears to be a comms issue. Can I ask that you run the job again (just so we know where to look in the logs) and then, on the machine running the SIS service, look in C:\ProgramData\Hornbill\Site Integration Server\log\EspSisService.log

    There should be some entries in there tying up with the new job run, and that will hopefully give us a better idea about what's going on. The first entry will be

    Processing job: <your job number in here>, type=package

     

  5. @Ben Maddams In that case, this is still a communications issue. With the change to the config file, are you now getting just one valid IP listed when you restart the service?

    Can you run the same job, but use the SIS service itself as the target? That probably won't work, since the RSAT tools probably aren't installed on the machine running the SIS service, but that won't matter. I'm interested in seeing if the job runs at all and reports back.

     

  6. 3 minutes ago, Ben Maddams said:

    Failed to post callback command 'log' to http://0.0.0.0:11117/_exec_callback/log/ No response was available.

    @Ben Maddams The log has been very useful, thank you.

    That 0.0.0.0 is going to be the problem. The code is making standard Windows API calls to get the list of addresses for the machine. We can override this in the config file, but would you mind checking a couple of things for me?

    First, as admin on the machine running the SIS service, run

    ipconfig /all

    and post the results

    Secondly, restart the SIS service and review the EspSisService.log file, located in C:\ProgramData\Hornbill\Site Integration Server\log. There will be a few lines in there - the one I'm interested in starts:

    Starting HTTP responder on port 11117

    and should contain a list of IP addresses at the end.

  7. @Ben Maddams Hello Ben,

    It is not necessary to have the SIS service on the DC for any of the Hornbill Library packages. It can run on any server on the network, but ideally one that is joined to the domain you are managing.

    As for your test jobs failing, the way the SIS service works is that when a job is run, an executable (EspSisExec.exe) is deployed to the machine specified as the target of the job, and it is this executable, rather than the SIS service itself, that does the heavy lifting and processes the package. While it is running, it reports back its progress to the SIS server, which then in turn reports activity to Hornbill, so that you can see the activity in real-time within the ITOM application.

    This communication between EspSisExec and the SIS service is over HTTP, but using TCP port 11117, from the EspSisExec process to the SIS service. The error you are getting is because the SIS service is not receiving any communication from the EspSisExec process. The most common reason for this is an internal firewall, either somewhere on the network path between the two, or on the system running the SIS service, preventing traffic on that port reaching the SIS service. It's also possible, but much less likely, that there is some sort of firewall doing egress filtering on the system running the EspSisExec process.

  8. @Berto2002 For the first query, the delete is processed throughout the day, but it will not remove all the messages in one go. Are you seeing the count drop at all? It should be processing approximately 1,000 every hour.

    For the second query, we do not automatically delete any emails not in Deleted or Sent Items, regardless of their age.

  9. Hi @Sam P

    Unfortunately, we can't add the Outcome column to the job queue. The reason for this is that the Outcome from a job r is not part of ITOM itself, but just one of the output parameters from the some of the packages in the Hornbill Package Library. The column would have no meaning for discovery jobs or any library or customer package that did not include this output parameter.

    It's been discussed internally, and the problem is that the Powershell scripts inside the packages are returning a success code even if one of the operations fails, and while this might seem incorrect, there are some valid reasons for this implementation.

    However, all is not lost. There is a change that is being considered that will allow the job to report a failure from an operation within the package. Nothing confirmed yet, but I'll be able to update you in the New Year.

    Graham

  10. @JanS2000 The package is calling the Powershell cmdlet "Get-ADUser", passing in the value of the MemberIdentify parameter as the value of the -Identity parameter to the cmdlet and it's that part which is failing.
    I understand the redactions, and while I'm not asking you to "unredact" them, can you confirm that the value passed into the job is one of:

    • A distinguished name
    • An object GUID
    • A security identifier
    • A SAM account name
  11. @JanS2000  No, the Group Management package is the one you need. That's me leading you astray by asking the wrong question! I should have asked about the Group Management package!

    Assuming that's on version 14 (the latest), then it would appear that the problem is that the user you're trying to add can't found. There's two possible reasons for that: either the user doesn't exist or the package is querying the wrong directory server.

    Which domain is the user you're trying to add in and which domain is the SIS server itself in?

     

×
×
  • Create New...