Are you using Tableau 7.0.5? This sounds like a bug we fixed recently. Upgrading to the latest version may fix this for you.
yes, I run 7.0.5 and just installed the what I thought was the newest version 7.0.5. (7000.12.0602.1810) - but it didnt fix the issue?
I'm having the same issue w/ Oracle as the database using Tableau 7.0.5, but I'm only seeing it when trying to "Refresh All Extracts" when I haven't already entered my db credentials in the same session. If I refresh extracts individually, it prompts for the password. But using "Refresh All Extracts" it is as though 7.0.5 has "forgotten" that it needs to prompt for a password before trying to connect to the database.
Hmmm when I download the latest version it is still the same, maybe the bugfixed version has not been published - Logan, can you help here please?
1 of 1 people found this helpful
I submitted a support request related to the problem with "Refresh All Extracts" not prompting for a password, resulting in failed refreshes, and they acknowledged a bug and indicated a fix should be coming in late July.... I have found that extracts refresh fine if you refresh them one at a time, by right-clicking on each connection in the data panel in the upper-left corner of a worksheet, and choose Extract ->Refresh... Tedious, but not as bad as a couple versions ago, when all the connections in use in a workbook were not displayed in that same panel. (Then you had to find a worksheet for each connection before you could refresh it--a real pain in a large workbook.)
Vince is exactly right. We are working on the bug and in the meantime you can workaround it by refreshing the extracts individually.
I have a user running an OEM version of 7000.12.0602.1810 as well, and running in to this same issue (refreshing individual works, refreshing all errors with a login problem). Has any progress been made on this?
Hi, we're seeing the same problem. ie Uploading a workbook with an embedded password fails to embed the password and instead prompts the user to enter the password. This happens intermittently and is quite strange.
We are using the latest version of 8.1.
- Version 8.1.1 (8100.13.1202.0916) 64-bit