Splunk DB Connect 2: Why am I getting Winsock 10053 error trying to validate connections to MS-SQL and MySQL databases?d

[rob_lamb]

I have Splunk Enterprise installed on the same laptop as MS-SQL Server and MySQL. I'm trying to use Splunk DB Connect 2 to access the databases. In both cases I get "internal server error" messages when trying to validate and/or save connections. When I check splunkd.log, I see:

10-19-2015 09:32:31.036 -0700 ERROR HttpListener - Exception while processing request from 127.0.0.1 for /en-US/custom/splunk_app_db_connect/proxy/servicesNS/admin/-/db_connect/lookups?output_mode=json&count=-1&search=connection%3Dundefined&_=1445272313039: Connection closed by peer
10-19-2015 09:32:31.036 -0700 ERROR HttpListener - Handler for /en-US/custom/splunk_app_db_connect/proxy/servicesNS/admin/-/db_connect/lookups?output_mode=json&count=-1&search=connection%3Dundefined&_=1445272313039 sent a 0 byte response after earlier claiming a Content-Length of 251!
10-19-2015 09:33:22.178 -0700 WARN  HttpListener - Socket error from 127.0.0.1 while accessing /servicesNS/nobody/splunk_app_db_connect/db_connect/connections/-/status: Winsock error 10053
10-19-2015 09:33:24.863 -0700 WARN  HttpListener - Socket error from 127.0.0.1 while accessing /servicesNS/admin/-/db_connect/explore/mySQL_Test: Winsock error 10053
10-19-2015 09:33:25.390 -0700 WARN  HttpListener - Socket error from 127.0.0.1 while accessing /servicesNS/admin/-/db_connect/explore/mySQL_Test: Winsock error 10053

Note that I am also seeing an R6034 error on startup with Python.EXE. Not sure if this is related, it is logged as a separate question.

[rob_lamb · Accepted solution]

OK. Turns out it appears to be related to the Python runtime error I was seeing. I fixed that via renaming my Python folder:

1) I uninstalled Splunk
2) I renamed my Python folder from:
C:\Python27
to:
C:\Python_old
3) I reinstalled Splunk with no errors

When I reinstalled/reconfigured DB Connect 2 I am now able to access MySQL without any of the Winsock errors that I have seen previously.

[jcoates_splunk]

that is some serious "I can't talk to myself"... I would ask questions about Splunk roles, filesystem permissions, and firewalls.

[rob_lamb]

Thank you for the feedback, but I may need a little more guidance.

Firewall: I'm using a Symantec firewall, auto configured by our IT department. A co-worker is able to get Splunk/DB Connect 2 working with the same firewall config, so I don't think that is the issue?
Splunk roles: I'm using the Admin login, with the following roles (the default roles + can_delete):
admin
can_delete (I know, not a best practice)
db_connect_admin
db_connect_user

Filesystem: My domain login is an admin on the laptop, so I'm not sure what permissions would need to be checked?