Service Mapping - Get_Process_Info.exe not always ending on devices, stacking multiple times.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2024 10:30 AM
All,
Just curious if anyone else has seen this issue before, and if so if there are any suggestions for dealing with it. Occasionally we are seeing a situation where Service Mapping running against Database Servers is causing CPU usage on the target device to spike to 100%.
We've only encountered the issue so far twice. However in both instances we are seeing multiple get_process_info.exe processes running in task manager on the target device. The cumulative CPU usage of the stacked get_process_info.exe process is pushing CPU usage to 100% and is causing a negative situation for our Application Support teams.
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2024 10:44 PM
Hi @Scott Braden ,
I am not seen this type if issue for any database server while running the Service Mapping.
Can you please let me know how you have made the connection to App Server to Database server.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ
Linkedin:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community Rising Star 2024

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2024 03:29 PM
Hi @Scott Braden ,
we have come across this issue in the past for a client while running discovery. This is happening because there can be few database commands in the pattern steps that are taking long time to run. In order to debug this issue, you need to check discovery logs of the database pattern and then look for pattern steps which are running longer.
As it is a database pattern, it can have applicative credentials steps sometimes takes longer to run.
We have two solutions, simply disabled those pattern steps in the pattern or get permissions to run the commands. these two approaches, fastened our discovery process
Please mark my solution as helpful, if it is resolving your problem.
- Srinija