on the SQL server itself, someone has created a logon trigger on all server.
that trigger is preventing the login...it might be doing it on purpose, or it might be an artifact of bad coding or insufficient permissions(ie writing to a table). you need to get with the DBA and tell him it is preventing the logins, and he can disable the logon trigger; if it is you, then disable it yourself:
DISABLE TRIGGER TR_LogonTriggerAuditingName ON ALL SERVER-- change to the REAL name of the trigger
you can make a logon trigger that might prevent a login any of the following things: track a history of logins, prevent logins due to explicit loginname, time of day, or number of connections, hostname, application name not in expected values, for example.
if you are sysadmin on the server, you can see the list of server triggers and their definition like this:
Object Explorer -> Server Objects -> Triggers
or via TSQL:
'DISABLE TRIGGER '
+ QUOTENAME(trz.name) COLLATE SQL_Latin1_General_CP1_CI_AS
+ ' ON ALL '
+ trz.[parent_class_desc] COLLATE SQL_Latin1_General_CP1_CI_AS AS DisableCommand,
ssmod.definition AS [Definition],
FROM master.sys.server_triggers AS trz
LEFT OUTER JOIN master.sys.server_assembly_modules AS modz ON modz.object_id = trz.object_id
LEFT OUTER JOIN sys.server_sql_modules AS ssmod ON ssmod.object_id = trz.object_id
--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!