Hey Amy. Here's some info from a doc I wrote about common problems. Try this and see if it helps, and if not, post your yaml (with sensitive info removed) here.
Exception was raised loading the config file .\config\vizalerts.yaml: Something something 'yaml.scanner.ScannerError'
Thank you Matt Coles. I was able to get passed this error. But not I am running into something new. When I exe the vizalerts the email I get shows this message.
"coercing to Unicode: need string or buffer, int found" I still think I am missing something in the yaml file. Any guidance is appreciated.
Matt Coles yes I parse in the https://codebeautify.org/yaml-validator and got no errors. Before I proceed would you recommend for us to install the latest version? We are currently on 10.5. I am thinking to start from scratch. I read the forum posted with the same issue but didn't find it too useful.
here is screenshot of what's in the config file.
Don't add "https://" to the server setting, that will be added automatically depending on your server.ssl setting.
Everything else looks fine. If you run it again and it still errors, could you screenshot or attach the ouput / logs?
Ok so I think what is causing the issue is due to the username being in number form. When I changed the user I no longer got the "coercing to Unicode: need string or buffer, int found". However I put our tableau admin account for the user and I got the following message instead.
for security purposes I excluded our information and placed bracket with the information that was in there.
generating trusted ticket: Temporary Redirect Request details: Server:
[server name], Site: , Username: [tableau admin account], Url: [server name/trusted],
Based on HTTPError generating trusted ticket - Vizalerts , the temporary redirect error likely means that SSL is required for your Tableau Server, but you've turned it off in the vizalerts.yaml file. Set server.ssl to true, then you should be on to either sucess, or the next error.
ok ok now I think I'm getting closer to success. So I made the change as you suggested but now I get a completely different errors message.
Could not process source viz data from
VizAlertsConfig/ScheduledTriggerViews for the following reasons:
HTTP error getting vizdata from url [link]
Code: 401 Reason: Unauthorized
Progress is progress!
A full screenshot of the logs, or attaching them would be helpful, but I'll wager a couple guesses:
1. When publishing the VizAlertsConfig workbook, maybe the connection was left as "prompt user" rather than "embed credentials"?
2. Does the server.user you set in vizalerts.yaml have access to the VizAlertsConfig workbook?
Hey Amy, I only see the temporary redirect errors in here...there is no 401 error in either the logs attached, or the screenshot. The fix for that is to set server.ssl to true. Conversely, it looks as though your SMTP server does not support SSL, so you will need to set smtp.ssl to false.
With regards to your users, are they all in int format? Could you create another test user that uses a string, as a workaround? The user you are putting in the config file really does not require any special access, as the trusted tickets it will generate will empower it to access the vizzes it needs to.
Thanks Amy. What authentication type are you using at present? If it's local authentication, then you'll need to leave server.user.domain as null. You would include that value if you're using Active Directory authentication, though.