topic Re: DB Connect 3.1.4 not working in All Apps and Add-ons

Why is DB Connect 3.1.4 not working?

mguissine — Mon, 07 Aug 2023 18:57:53 GMT

DB Connect 3.1.4 not loading, gets stuck on https:///en-US/app/splunk_app_db_connect/ftr#/welcome page, just seeing spinning wheel
Tried on Splunk Enterprise 7.2.2 and 7.2.3

Re: DB Connect 3.1.4 not working

vishaltaneja070 — Thu, 24 Jan 2019 07:37:51 GMT

Did you try to restart splunk?

Re: DB Connect 3.1.4 not working

mguissine — Thu, 24 Jan 2019 14:56:50 GMT

I did, few times, still not able to load DB connect app

Re: DB Connect 3.1.4 not working

muralikoppula — Thu, 24 Jan 2019 16:24:06 GMT

Did you see any error warning messages under settings page?

Re: DB Connect 3.1.4 not working

mguissine — Thu, 24 Jan 2019 16:43:03 GMT

I can't get to the app settings page, just seeing a spinning wheel; in dev tools I see this error:

[object Error]: {description: "Unable to get property 'Symbol(Symbol.iterator)' of undefined or null reference", message: "Unable to get property 'Symbol(Symbol.iterator)' of undefined or null reference", number: -2146823281, stack: "TypeError: Unable to get property 'Symbol(Symbol.iterator)' of undefined or null reference at Anonymous function (https://ops.ci.nudge.land/en-GB/static/@B6BD0C1627EF113B2390A90588827AAB0D02E1F78BDDB3ECC31EB0EEB85DBF68:43/app/splunk_app_db_connect/build/pages/ftr.js:1:7195) at run (https://ops.ci.nudge.land/en-GB/static/@B6BD0C1627EF113B2390A90588827AAB0D02E1F78BDDB3ECC31EB0EEB85DBF68:43/app/splunk_app_db_connect/build/pages/common.js:3:17620) at Anonymous function (https://ops.ci.nudge.land/en-GB/static/@B6BD0C1627EF113B2390A90588827AAB0D02E1F78BDDB3ECC31EB0EEB85DBF68:43/app/splunk_app_db_connect/build/pages/common.js:3:17902) at flush (https://ops.ci.nudge.land/en-GB/static/@B6BD0C1627EF113B2390A90588827AAB0D02E1F78BDDB3ECC31EB0EEB85DBF68:43/app/splunk_app_db_connect/build/pages/common.js:3:25465)"}"

Re: DB Connect 3.1.4 not working

muralikoppula — Thu, 24 Jan 2019 16:49:45 GMT

Check the below Splunk answer:
https://answers.splunk.com/answers/658841/db-connect-not-working.html

Re: DB Connect 3.1.4 not working

mguissine — Thu, 24 Jan 2019 17:03:17 GMT

thanks @muralikoppula, wasn't looking forward to rebuilding Splunk installation but looks like that's the only option to get DB Connect working, not fun

Re: DB Connect 3.1.4 not working

fhemmeld — Thu, 27 Jun 2019 17:52:17 GMT

Reinstalling Splunk (as suggested in https://answers.splunk.com/answers/658841/db-connect-not-working.html) is not an option in our case, anybody else a solution?

Looking at what the system is doing, the following URL comes back with a 503 every time:
http://server:8000/en-US/splunkd/__raw/servicesNS/admin/splunk_app_db_connect/db_connect/dbxproxy/taskserver

The system seems to loop on this.

Re: DB Connect 3.1.4 not working

rslama — Thu, 27 Jun 2019 18:12:41 GMT

one of my DB connection also got stuck, I created a new one for the same connection, and deleted the old one.

Re: DB Connect 3.1.4 not working

skalliger — Thu, 27 Jun 2019 18:17:35 GMT

Task server not running? Can you restart it?

Re: DB Connect 3.1.4 not working

microgag — Tue, 17 Dec 2019 07:42:04 GMT

Am having the error as well. Not sure if need Splunk Enterprise License in order to work? Currently, testing in lab with free 500MB trial License.

Re: DB Connect 3.1.4 not working

edhealea — Wed, 22 Mar 2023 16:09:14 GMT

I know this is an old thread but thought I would post an answer for future reference.
I was getting https:///en-US/app/splunk_app_db_connect/ftr# with a blank screen.
I am using Chrome. After upgrading from 3.11.1 to 3.12.1, I was still only getting a blank screen so I removed DB connect and installed 3.11.1. No luck - still a blank screen.
Finally, I cleared the browser cache and was able to access DB Connect without any issues.

Re: DB Connect 3.1.4 not working

aaronbarry73 — Mon, 07 Aug 2023 15:21:12 GMT

Yes - clearing my browser cache worked for me on upgrade from 3.2 to 3.13.

Re: DB Connect 3.1.4 not working

gesa_behrens — Wed, 10 Apr 2024 12:50:11 GMT

Thank you so much for this post!!!

It solved my problem upgrading from3.9.to 3.16