We didn't clone the service. We created a new service, removed any dependencies for the initial service and dropped it. Rename the new one. (I.E Create a new service SQL-Server_new, dropped SQL-Server, and rename SQL-Server_new to SQL-Server). PS: The Splunk support asked us to not clone because the issue could be inherited in the new service. ... View more

Yes, we resolved. We opened a ticket with Splunk. The support person instructed us to create a new service same as the original service and before dropping the original service we had to remove any dependencies for that original service. When we finally dropped the original service with the hanging child services, everything went away.,Yes, we did. I opened a ticket with Splunk. The support person instructed us to create a new service same to the original service were the child services were hanging and to remove any dependency with that original service and drop the original services afterward. When I dropped the original service everything went away and I start to use the new service. ... View more

Current Application: IT Service Intelligence App Version 3.1.3 App Build 4536798501 ... View more

Current Application: IT Service Intelligence App Version 3.1.3 App Build 4536798501 ... View more

Thanks for your reply. We have removed the services over a week ago. We restarted the entire Splunk environment including ITSI and the services removed are still showing as children of another service (they were children before). It looks like that only the name of the services were removed but the dependencies hasn't. The services shows as "Undefined". Attached is a picture showing the issue. Regards, Ernando. ... View more