Hmm, 401 is a little weird. Typically when VizAlerts tries to export a viz, and it fails, it comes back as a 406. I guess it's possible the developers finally fixed that and it's now returning the proper code? At any rate, I'd check to ensure that you've still got the credentials embedded in the workbook. To test it, try clicking the link you provided and manually downloading the CSV. Make sure you are logged in as the user that you set for the server.user value in vizalerts.yaml.
sorry for my late reply. I just checked and I am able to download the file and can see the schedules I am using. in the yaml file I used the Server Admin account and with this it was working as expected.
So no clue what changed
I'm also having the same problem on 2018.3.2:
Could not process source viz data from VizAlertsConfig/ScheduledTriggerViews for the following reasons:
HTTP error getting vizdata from url https://*****************/views/VizAlertsConfig/ScheduledTriggerViews?&:format=csv&:refresh=y. Code: 401 Reason: Unauthorized
Jens's reply is a bit ambiguous so I'm unsure whether the issue has been resolved on their end.
As for me by manually pasting URL into my browser it will download the csv file. I followed every step on the install guide word for word including the following:
- Trusted auth (Tested with: Test Trusted Authentication - Tableau)
- Embedded password
- logged in as user set in vizalerts.yaml
Does someone have the same issue after upgrading to latest Version?
no it is not solved. Still have the issue
I am also receiving this error; note that the actual unauthorized error appears to originate at http://<server>/vizportal/api/web/v1/auth/signin - requests are being redirected here first (presumably for SSO) so the behaviour appears to have changed in 2018.3.2 (as I see you didn't get this error in 2018.3.1)
This is confirmed to be a bug introduced in Server 2018.3.2. It is specific to exporting CSVs using trusted ticket authentication, which is why it causes VizAlerts to fail when exporting the CSV. Other kinds of trusted ticket operations work fine. This is planned to be fixed in 2018.3.3.
I'll post a larger update so that others can avoid this issue. Thanks for letting us know!
We are having the same problem. If it's a bug and it's planned to be fixed in version 2018.3.3. Does anyone know when will be this release avaible?
Has anyone been able to solve this issue with any workaround?
Thank you very much!