Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Exchange 2003 Categorizer errors

Posted on 2009-06-29
12
Medium Priority
?
976 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
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 

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

Tech or Treat! - Giveaway

Submit an article about your scariest tech experience—and the solution—and you’ll be automatically entered to win one of 4 fantastic tech gadgets.

Question has a verified solution.

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

Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
The core idea of this article is to make you acquainted with the best way in which you can export Exchange mailbox to PST format.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.

609 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