Exchange 2003 Categorizer errors

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.


jarrodlbellAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

FearNoMoreCommented:
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
jarrodlbellAuthor Commented:
I already tried uninstalling the antivirus program.  Same results.  Thanks for the prompt reply though!
0
FearNoMoreCommented:
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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

jarrodlbellAuthor Commented:
It's been restarted about six times since then in an effort to get rid of these warning messages.
0
FearNoMoreCommented:
Very strange....
What other third party software are you running on the server?
Did you try disabling all of the third party?
0
jarrodlbellAuthor Commented:
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
FearNoMoreCommented:
Yes I would suggest opening up a support call with GFI.
I suspect its GFI
0
jarrodlbellAuthor Commented:
I'll open one up tomorrow and post the results afterwards.  Thanks for all the help FearNoMore.
0
jarrodlbellAuthor Commented:
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
jarrodlbellAuthor Commented:
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
jarrodlbellAuthor Commented:
Still waiting on an answer from GFI.
0
jarrodlbellAuthor Commented:
GFI blames MIcrosoft, Microsoft blames GFI, and I still don't have an answer.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.