3.1.4 LDAP error - 'Search failed! Bad filter' -REWRITTEN

[kruegerM]

We have our production (PROD), at 3.1.4 with PERL v5.10, Net::LDAP 0.44 - OS is Linux - Fedora 12.

When you do a queue listing (Ticket > Queue view) - the CUSTOMERID column will have some blanks. - For each blank displayed, the system log shows 'Search failed! Bad filter'. The tickets missing the CUSTOMERID information are consistent.

Examination of the HTTPD error_log file shows the following (once for each blank spot in CUSTOMERID column):

Message: Search failed! Bad filter

Traceback (10736):
Module: Kernel::System::CustomerUser::LDAP::CustomerName (v1.62) Line: 246
Module: Kernel::System::CustomerUser::CustomerName (v1.63) Line: 240
Module: Kernel::Output::HTML::TicketOverviewSmall::Run (v1.50) Line: 497
Module: Kernel::Output::HTML::LayoutTicket::TicketListShow (v1.141) Line: 927
Module: Kernel::Modules::AgentTicketQueue::Run (v1.79) Line: 245
Module: Kernel::System::Web::InterfaceAgent::Run (v1.64) Line: 868
Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 46
Module: (eval) (v1.90) Line: 204
Module: ModPerl::RegistryCooker::run (v1.90) Line: 204
Module: ModPerl::RegistryCooker::default_handler (v1.90) Line: 170
Module: ModPerl::Registry::handler (v1.99) Line: 31[/b]


ideas?

[kruegerM]

obvious - the database had columns where the CUSTOMER_ID or CUSTOMER_USER_ID were blank (how they got that way I still don't know).
I have fixed those rows using SQL - however, I am still getting the LDAP errors. No where as many now, but still occuring.