All Apps and Add-ons

Can not communicate with task server, please check your settings.


Hi Team,

Can some on help to solve this issue, I have installed DB connect on Splunk enterprise after launch the apps I am getting following error message

Error: Can not communicate with task server, please check your settings.

JDK 8 is installed

I have followed the following article but does not help me


Hi All,

I have gone though all the answers and done all required changes in config but nothing will happend.
Finally, I use below steps to reslove this issue.

  1. Backup your files, if exist, ex: db_input.conf and drivers
  2. Stop splunk. Remove db_connect app from app folder.
  3. Restart Splunk.
  4. Upgrade your splunk with just new version.
  5. install > db connect app

check your db it will be okay now.

Happy Splunking !..

Path Finder

Thanks so much!

0 Karma


DBConnect 3.3.1 Initial Setup Encountering "cannot communicate with task server" & python script error DBConnect has this issue  our environment when a user’s setting for Time Zone is set to anything other than "–Default System Timezone-". 

  1. Remove splunk_app_db_connect folder from $Splunk Home\etc\apps
  2. Download DB Connect 3.1.3 from splunk base
  3. Install DB Connect (by choosing install from file)
  4. Select DB Connect All and click setup
  5. Under Settings -> General -> Task Server Port remove 9998 and add 1025
  6. Click Save
  7. The task server restarts
  8. Again Change Task Server Port to 9998 and click save
  9. The task server restarts

That's all folks!!!


I have the same problem. I can see that the task Server is properly responding at:


netstat -a -b

shows me, that the TaskServer is up and listening to the port. Maybe this might be helpful.

The splunkd.log is showing the following output after restarting Splunk:

ERROR ExecProcessor - message from
""C:\Program Files\Splunk\etc\apps\splunk_app_db_connect\windows_x86_64\bin\server.exe""

Which is not really helpful for me.

0 Karma

Path Finder

Seems it is still not able to find java. Go to configurations/settings can put in the path to your java.


thank you. 100% my case.

0 Karma


I did the change to 1025 - it didn't work. and I turned it again to 9998 - same result.
In both cases, when I start Splunk I have the following output:

[splunk@srvsplunk bin]$ ./splunk start

Splunk> CSI: Logfiles.

Checking prerequisites...
    Checking http port [8000]: open
    Checking mgmt port [8089]: open
    Checking appserver port []: open
    Checking kvstore port [8191]: open
    Checking configuration...  Done.
    Checking critical directories...    Done
    Checking indexes...
        Validated: _audit _internal _introspection _telemetry _thefishbucket history main omega_ca_nt omega_ds omega_ds_idx_01 omega_nt_ora summary
    Checking filesystem compatibility...  Done
    Checking conf files for problems...
        Invalid key in stanza [dbx_java_installation_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 17: doc_title  (value:  DB Connect JVM installation).
        Invalid key in stanza [dbx_driver_installation_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 41: doc_title  (value:  DB Connect JDBC Driver installation).
        Invalid key in stanza [dbx_connections_configuration_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 69: doc_title  (value:  DB Connect connection configuration,DB Connect identity configuration).
        Invalid key in stanza [dbx_data_lab_configuration_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 85: doc_title  (value:  DB Connect input configuration,DB Connect output configuration,DB Connect lookup configuration).
        Invalid key in stanza [dbx_java_server_configuration_health_check] in /opt/splunk/etc/apps/splunk_app_db_connect/default/checklist.conf, line 98: doc_title  (value:  DB Connect Java Server configuration).
        Your indexes and inputs configurations are not internally consistent. For more information, run 'splunk btool check --debug'
    Checking default conf files for edits...
    Validating installed files against hashes from '/opt/splunk/splunk-6.5.2-67571ef4b87d-linux-2.6-x86_64-manifest'
    All installed files intact.
All preliminary checks passed.

Starting splunk server daemon (splunkd)...  
 [  OK  ]

Waiting for web server at to be available........ Done

If you get stuck, we're here to help.  
Look for answers here:

The Splunk web interface is at http://srvsplunk:8000

the very strange thing on the above - is that the startup problems DO NOT appear with the 9998 port as an original setting after the DB Connect App Install, but they DO appear even when the port is set again to 9998 (after trying 1025).


0 Karma


thank you, but how can this be performed when I am re-directed to the URL?

which then hangs. the original (title) message "Can not communicate with task server, please check your settings." - I can fully see only with a Print-screen to Bmp


ps. and I did all on the URL given above to no result

0 Karma


Any updates to this problem. I am facing a similar issue in Mac Env. The Splunk Enterprise version is crashing and indicating that it is not able to communicate with the Task Server.

0 Karma
Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...