Hi, we're using OTRS 2.4.6 with AD authentication. Today we had an short outage of our LDAP/AD authentication server. Now all tickets which have been created *during* the LDAP/AD outage are neither readable nor writable. New tickets *after* the LDAP/AD resurrected are readable and writeable indeed. This is the log while trying to access the ticket as OTRS admin user: Feb 5 11:05:21 OTRS-CGI-10[64066]: [Error][Kernel::System::Ticket::TicketGet][Line:997]: No such TicketID (658)! Feb 5 11:05:21 OTRS-CGI-10[64066]: [Error][Kernel::System::Ticket::TicketGet][Line:997]: No such TicketID (658)! Feb 5 11:05:21 OTRS-CGI-10[64066]: [Error][Kernel::System::Queue::GetQueueGroupID][Line:583]: Need QueueID! Feb 5 11:05:21 OTRS-CGI-10[64066]: [Notice][Kernel::System::Ticket::Permission] Permission denied (UserID: 3 'ro' on TicketID: 658)! Feb 5 11:05:22 OTRS-CGI-10[64067]: [Error][Kernel::System::Ticket::TicketGet][Line:997]: No such TicketID (658)! Feb 5 11:05:22 OTRS-CGI-10[64067]: [Error][Kernel::System::Ticket::TicketGet][Line:997]: No such TicketID (658)! Feb 5 11:05:22 OTRS-CGI-10[64067]: [Error][Kernel::System::Queue::GetQueueGroupID][Line:583]: Need QueueID! Feb 5 11:05:22 OTRS-CGI-10[64067]: [Notice][Kernel::System::Ticket::Permission] Permission denied (UserID: 3 'ro' on TicketID: 658)! How can I regain all permissions to this ticket? This seems like a bug to me. Maybe OTRS should not accept new tickets if the AuthModule is not available. Regards Frank