April 10, 2014 at 1:44 pm
if you created a table that captures login info, then i think you need to GRANT INSERT ON [dbo].[rvvlogindata] TO PUBLIC so that any login would not fail inside the trigger.
i'd bet you a donut that login you mentioned doesn't have insert permissions to the table, and thus fails inside the trigger.
the error log would have the details, and it would probably say object [dbo].[rvvlogindata]( does not exist or you don't have permission to perform this action for the offending user.
Lowell
April 10, 2014 at 1:47 pm
Thanks for the suggestion, but I had already granted insert to public, which is why all the logins can login but the one with special character in the name(possibly due to the $ being the last character?)
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply