I would verify that the WDC has been set up properly on the Tableau Server. Verifying the password for the data source is embedded in the connection as well as putting the WDC on the safe list for the Tableau Server.
More information can be found here on how to verify both of these things: Web Data Connectors in Tableau Server
If that does not work, can you possibly look in the backgrounder logs for any failures or errors that occur. They may not be the very last entry in the log file.
Hope this helps!
I have embedded the password and white-listed the WDC as best I can. I had this working on server v10.3 a few months ago, but now on v10.5 I can't get it to work (I'm not sure if the version upgrade has anything to do with it). When I tested it before I could see the errors in the log file but now i can't seem to see any errors.
- For some reason it looks as though the Server is "checking" if the web data connector is local .... not sure why, but then it throws an error.
- And we have nothing to do with Anaplan .. so where is this coming from? If I browse this URL my browser hangs.
2018-05-01 08:18:38.906 -0600 (Default,,,,4165206,:refresh_extracts,-) pool-4-thread-1 : INFO com.tableausoftware.model.workgroup.workers.RefreshExtractsWorker - Checking if web data connector url 'https://share.ahsnet.ca:443/teams/DIMR/SA-Team/Tableau/TableauLibrary/REDCapWDC.html' in Workbook '_End User Registrations via REDCap' with repository url '_EndUserRegistrationsviaREDCap' is whitelisted
2018-05-01 08:18:38.917 -0600 (Default,,,,4165206,:refresh_extracts,-) pool-4-thread-1 : INFO com.tableausoftware.core.util.WebDataConnectorHelper - Checking for webdataconnector at url http://localhost/teams/DIMR/SA-Team/Tableau/TableauLibrary/REDCapWDC.html
2018-05-01 08:18:38.935 -0600 (Default,,,,4165206,:refresh_extracts,-) pool-4-thread-1 : WARN com.tableausoftware.core.util.WebDataConnectorHelper - Caught an IO exception while trying to check if web data connector is local: http://localhost/teams/DIMR/SA-Team/Tableau/TableauLibrary/REDCapWDC.html
2018-05-01 08:18:38.937 -0600 (Default,,,,4165206,:refresh_extracts,-) pool-4-thread-1 : INFO com.tableausoftware.domain.content.WebDataConnectorService - Populating default whitelist config...
2018-05-01 08:18:38.950 -0600 (Default,,,,4165206,:refresh_extracts,-) pool-4-thread-1 : INFO com.tableausoftware.domain.content.WebDataConnectorService - Inserting authMode information for url https://beta-connectors.tableau.com:443/anaplan/anaplan/1/anaplan.html
I am stuck with this exact same log entries, did you get any luck in figuring out why the Server is "checking" if the web data connector is local. And where is the Anaplan coming from?
I have a call with tableau tech support tomorrow. Will update after.
I did notice that if i get rid of the secondary whitelist files it starts to work ... need to understand why as this in not how i understand it should work.
Thanks so much for your response! I just submitted a support ticket too, will update too after if it works on my end.
Were you able to resolve this WDC refresh error? It will be so great and helpful if you could share how this got fixed at your end?
Yes an no
I think the root cause is that the secondary whitelist URLs contain some special characters (a bunch of dashes). DOS is very picky with using the right dash. I always copy and paste my code from MS Word into Notepad++ and then copy and pasting again into DOS. I thought that Notepad++ would remove the custom dashes/formatting, but I am wrong, it was keeping the long dashes. So for now, I've removed the secondary whitelist altogether and both WDC are working.
I am still going to add the secondary whitelists back in as this is best practice. But for now I am fairly certain it is a formatting issue within the whitelist URLs.
Thanks for your quick response! A couple of questions I have here:
1. Does that mean "secondary whitelist" is optional?
2. Sorry I am new to WDC and I have been just given a single URL (.html) for the web connector. I have already added that URL to the server whitelist. How do I know if I should be configuring something as a secondary whitelist too?
1. I had previously thought that secondary whitelists were required .. but after this experience, it seems that they may be optional. Just my opinion.
2. Make sure you enable WDC on the server and restart the Tableau Server for the WDC to take effect. The secondary whitelist should be done for any 'resources' that the WDC uses. For me I added any remote .js or .css or .png files that the WDC html was referencing.
Thank you! I did everything you mentioned, still the refresh takes forever and eventually time outs after 2 hours.
From the server open Tableau desktop and test the WDC ... make sure it works there, before troubleshooting the refresh via the server.
Unable to refresh the extract locally from Tableau Desktop on the server box.
Also the WDC is only accessible from within the company's network whereas the Tableau Server is installed on AWS. Do you think this might cause this issue. I assumed no matter where the WDC is installed, the whitelisting should take care of this.