this error:
The check for encryption trigger fails with the infamous ‘login fails due to trigger execution’ error when using any .Net app (SSIS, SSRS, VB program, etc.).
is normal for a login trigger;
the connecting user cannot get any custom error message raised by the trigger...that error goes into the SQL log, but not to the connecting user.
they get stopped, but it might not be obvious what the error was.
some issues might be raised because you are using tables the connecting user has no access to at all: ie the specific table (DatabaseLogonAudit.dbo.AuditDatabase) ; and maybe some of the sys views the end user might not have access to: you might need to grant SELECT ON DatabaseLogonAudit.dbo.AuditDatabase to public to fix that issue.
Lowell