?
Solved

Exchange 2003 Categorizer errors

Posted on 2009-06-29
12
Medium Priority
?
974 Views
Last Modified: 2012-05-07
I have been getting some categorizer errros on my exchange 2003 server running on 2003 SBS.  Mail is being delivered, but I'm worried these warnings will become problems in the future.  All windows and exchange service packs have been installed.

The error messages are as follows:

Categorizer received error 0x00000051 from WLDAP32!
ldap_search_extW(GetPLDAP(), "", 2,
"(ProxyAddresses=smtp:Jim_White@gov.nt.ca)",
rgszAttributes, ...), PLDAP = 0x09ce4cb0
for server server.domain.COM

Categorizer is temporarily unable to process a message.  
The function 'CCfgConnection::AsyncSearch' called
'CBatchLdapConnection::AsyncSearch' which returned
error code '0xc004051f' ().
( f:\tisp2hot\transmt\src\phatq\cat\ldapstor\cnfgmgr.cpp@2353 )

Categorizer is temporarily unable to process a message.  
The function 'CLdapConnection::AsyncSearch' called 'AsyncSearch'
which returned error code '0xc004051f' ().
( f:\tisp2hot\transmt\src\phatq\cat\ldapstor\ldapconn.cpp@3224 )

Categorizer is temporarily unable to process a message.  
The function 'CSearchRequestBlock::HrSendQueryDefault'
called 'pBlock->m_pConn->AsyncSearch' which returned error code
'0xc004051f' ().
( f:\tisp2hot\transmt\src\phatq\cat\ldapstor\asyncctx.cpp@725 )

Categorizer is temporarily unable to process a message.  
The function 'CICategorizerAsyncContextIMP::CompleteQuery' called
'--async--' which returned error code '0xc004051f' ().
( f:\tisp2hot\transmt\src\phatq\cat\ldapstor\icatasync.cpp@172 )

A categorization is failing over to a new connection.  
The old connection was to DS host "server.domain.COM".  
The new connection is to DS host "server.domain.COM".  The retry count is 1.


0
Comment
Question by:jarrodlbell
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 8
  • 4
12 Comments
 
LVL 13

Expert Comment

by:FearNoMore
ID: 24738817
I recently worked with a client on the same issue.
Turned out to be an issue with the AV. In this case it was Trend Scanmail
We found out that there was a new patch from Trend and after applying it, no more errors in the event logs.
 
 
0
 

Author Comment

by:jarrodlbell
ID: 24738920
I already tried uninstalling the antivirus program.  Same results.  Thanks for the prompt reply though!
0
 
LVL 13

Expert Comment

by:FearNoMore
ID: 24739056
After uninstalling the AV did you reboot the server?
If you cannot reboot the server then restart all Exchange services and the SMTP service and then check
0
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:jarrodlbell
ID: 24739192
It's been restarted about six times since then in an effort to get rid of these warning messages.
0
 
LVL 13

Expert Comment

by:FearNoMore
ID: 24739216
Very strange....
What other third party software are you running on the server?
Did you try disabling all of the third party?
0
 

Author Comment

by:jarrodlbell
ID: 24739322
The server is also running GFI mail essentials.  Disabling that software would create a flood of spam for the users, so I would prefer not to shut it down.  If necessary, I can open up a support call with GFI for additional troubleshooting.
0
 
LVL 13

Expert Comment

by:FearNoMore
ID: 24739393
Yes I would suggest opening up a support call with GFI.
I suspect its GFI
0
 

Author Comment

by:jarrodlbell
ID: 24739653
I'll open one up tomorrow and post the results afterwards.  Thanks for all the help FearNoMore.
0
 

Author Comment

by:jarrodlbell
ID: 24739994
Opened up a case with GFI.  The only place that any LDAP calls would be made is with it's directory harvesting.  In my case, harvesting is setup to use native active directory lookups, not L
DAP.  The case is still open and I'll post information as I get it.  Thanks for all the help!
0
 

Author Comment

by:jarrodlbell
ID: 24754505
Exported the log file and sent it to GFI.  I was told that GFI isn't using any LDAP calls the way I have it configured, so the error wasn't generated by GFI.
0
 

Author Comment

by:jarrodlbell
ID: 24796107
Still waiting on an answer from GFI.
0
 

Accepted Solution

by:
jarrodlbell earned 0 total points
ID: 24898499
GFI blames MIcrosoft, Microsoft blames GFI, and I still don't have an answer.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question