Resetting MIMEsweeper LDAP lists

Posted by: Anthony Drewery | August 3, 2006

Resetting MIMEsweeper LDAP lists

Another problem we get from time to time with MIMEsweeper for SMTP 5.2 is corruption of the LDAP lists. This initially manifests itself with an error like this in the event log on the configuration server:

———————————
Event Type: Error
Event Source: InfrastructureService
Event Category: (539)
Event ID: 10265
Date: 27.07.2006
Time: 11:47:28
User: N/A
Computer: CRWEXMSW1
Description:The PCS LDAP node configuration processor was unable to update the consolidated digest file for the PCS LDAP address list ’78f39c28-cf8c-440c-84ac-67e4533c4f4c’.
The domain index file for the address list ‘PMM Users’ is invalid.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
———————————

If you reboot the configuration server you’ll find that the Infrastructure Service won’t start. If you run pmi.is.exe -debug you will see errors relating to PCS LDAP in the output.

To fix this try the following:

Stop all the MIMEsweeper services on the PCS.

Move the files in the following folders to a safe location.

C:\Program Files\Clearswift\MIMEsweeper for SMTP\Data\Configuration\Server\PcsLdapAddressLists

C:\Program Files\Clearswift\MIMEsweeper for SMTP\Data\Operations\Configuration\PcsCache\PcsLdapAddressLists

Restart the MIMEsweeper services.

Now go into your policy editor and update all of your LDAP lists. Once this is complete save/apply your policy.

[tags]MIMEsweeper[/tags]

Like this:

Be the first to like this post.

Posted in MIMEsweeper

Responses

This saved my weekend. I had this problem and had no idea how to solve it. Did a routine backup before the weekend and the services would not start. Had visions of re-installing, etc. THANX!
By: James on November 3, 2006
at 12:46 pm

Reply
Hi from Germany!
This did not only save my day, but also my bosses’ ‘behind’ as we were running into this very issue while doing a post-merger integration. Nobody knew of the old MIMEsweeper machine, as all of the old sysadmins were gone. After a reboot of the server, which had an uptime >300 days (and ALL the patches inbetween, ‘of course’ ), the service just didn’t want to start.
It turned out to be an issue with LDAP sync a long time ago, which didn’t have to to with anything we did that day. Just nobody noticed that new email addresses were not reachable from the Internet
Thanks again!
Dave
By: Dave on January 27, 2009
at 9:14 am

Reply
This was great advice although i had to copy the server ones back again before the services would start.

But effectively this had the same effect.

Thanks for the help.
By: Matt Woolven on June 15, 2010
at 12:36 pm

Reply

Ant Drewery