OPC,

When I tested it at the SQL level I was logging into the sql server as the user in the limitedlogins table.

At the application level I would receive the attached error message.

I then added the principal logon_trigger_login to the sysadmin role and the application error went away. Also I was able to login as a user not in the limited login table, which is the ideal scenario.

I still want to test a few scenarios but with your suggestions this looks to be working.

Do you see any issue with having the logon_trigger_login principal a member of the sysadmin role? Would a lesser role accomplish the same thing?

Thanks for your help.