Skip to main content

Exchange/Outlook synchronization errors

I shut down our ESX hosts last night, and after the EqualLogic debacle, I powered everything back up. Exchange came up, but refused to send emails properly. I couldn't receive any emails at all, and sending them to my gmail account gave this:

Please note that a critical failure occurred on the sender's messaging system at the virus scanning stage.

The sender should be notified and reference made to this tracking number: src53_failed_f7e789cd-9a1a-


GFI Content Security.

While a very polite message, it failed to mention that GFI also does not provide technical support outside of business hours. They will not be renewed if that continues to be the case.

With that, I googled, and checked out their Kbase - nothing. I tried stopping all the GFI services, nothing. Tried restarting the Information Store - nothing. Tried deleting my Outlook profile - nothing. Tried logging in on another computer and setting up a new profile - nothing.

I downloaded the latest version of MailEssentials and MailSecurity (I was already on the latest for both), and uninstalled/reinstalled both.

Rebooted Exchange - and everything worked again!!! Stupid. Took up another two hours to troubleshoot and fix that issue - ended up leaving at 3:15am.


  1. Saw this myself and i believe it has to do with the Antivirus Scanning Engines within GFI. I disabled them within MailSecurity which disabled Information Store Protection, then i manually re-enabled each.

    Problem went away.

  2. This is incredible. I have run into the same problem on our Exchange server. I can't even access MailSecurity but it must be running in the middle, because I receive the same kind of notifications. This is extremely frustrating, I am not a satisfied customer.

  3. Thanks to Aaron I focused on the Antivirus Engines. For some reason our GFI MS had enabled some antivirus engines we didn't had licence to. When I disabled these everything worked fine.


Post a Comment

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…