I have SQL server not updating even though discovery seems to recognize the SQL exe is running
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2024 09:42 AM - edited 05-17-2024 11:37 AM
We recently noticed that ServiceNow was discovering some SQL server's we have and sometime early February stopped. We looked into it and we can see that ServiceNow still recognizes the sqlservr.exe in running processes but for some reason the servers aren't being updated anymore. Maybe I don't understand exactly how ServiceNow associates or creates the SQL instances. I originally thought it would just check for that sqlservr.exe on the server and update accordingly. If I go into the PID is sees that exe. Has something changed on this type of discovery or am I looking in the wrong spot?
Any guidance on this would be appreciate and if there is some piece of information I'm leaving out let me know.
Edit: We reached out to ServiceNow as well and they let us know we had a scripting issue as well that once corrected fixed our problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2024 09:52 AM
I think you will need applicative credentials for SQL server.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1096053
Mark it Helpful and Accept Solution !! If this helps you understand.
