Are you a member of the Splunk Community?
- Find Answers
- :
- Apps & Add-ons
- :
- All Apps and Add-ons
- :
- How do you resolve a Splunk DB Connect MSSQL Error...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
I was able to create 3 MSSQL connections using Generic Driver successfully. But the 4th connection fails with "DBX Server did not respond within 310 seconds, please make sure it is started and listening on 9998 port or consult documentation for details.
HTTPConnectionPool(host='127.0.0.1', port=9998): Read timed out. (read timeout=310)"
On log, I can see "Prelogin error: host 172.xx.x.xx port 1433 Error reading prelogin response: Connection timed out (Read failed)"
I am using DB Connect v 3.1.4.
Kindly advise how to resolve this issue. Thank you
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not sure, if this is your solution, but with DB Connect input, you can set a timeout (the time, Splunk waits for an answer, after query is fired). It is possible, that your data base is very large, which needs some more time to get a response. At first i would just try playing around with the time out value (in seconds).
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This issue has been resolved by enabling the application on firewall, previously only the ports were enabled.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This issue has been resolved by adding the application to whitelist on firewall, previously only the ports were enabled.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which application needs to be added
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not sure, if this is your solution, but with DB Connect input, you can set a timeout (the time, Splunk waits for an answer, after query is fired). It is possible, that your data base is very large, which needs some more time to get a response. At first i would just try playing around with the time out value (in seconds).
Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...
Splunk Observability for AI
🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler
