Jump to content

Recommended Posts

Posted

Hi all,

 

Got a problem with Forefront Security for Exchange. Late afternoon yesterday inbound and outbound weren't sending and the people would this initial message (attachments and body of the email) 'string_resource_283string_resource_414'.

 

When I googled it, it was relating to Forefront being corrupt and permissions issue (see below)

 

- My emails with attachments are received with the body

- string_resource_296

 

Anyway tried to troubleshoot the issue as forums mentioned security permission on the Forefront folder. When I took off scanning for both realtime jobs and transport jobs, then messages go through as they normally would. Restart the services for both Forefront and Exchange and tried turning scanning back on, and messages not sending or receiving (stuck in queue in logs so hitting the server but sending to Mailbox Server and then to the client).

 

Turning scanning off allows messages to come through. We use an external provider for our public records, and inbound emails receive scanning before arrival to our mail server so there is 1 layer of scanning before inbound items arrive at the moment. Done the following to summerise once I knew it must be Forefront: -

 

- Restarted all Forefront Services and Exchange Services

- Turned off Forefront scanning, restarted services, and emails route successful (inbound and outbound)

- Checked the permission of the Forefront folder - SYSTEM, ADMINISTRATORS, and LOCAL USERS

- Turned on Forefront scanning, restarted services, emails were not sending or arriving (stuck in queue).

 

Anyone got any ideas what I should try next? Just to confirm we're running Exchange Server 2007 SP3 and Forefront Security for Exchange SP2 which are all the latest packs for those versions.

 

Thanks very much.

Mo

Posted

We had something similar it was a bad/corrupted engine update. Look in the logs for any engine which was recently updated and disable that engine temporarily for testing.

 

Nick

  • Thanks 1
Posted

Thanks a lot, one of the scan engines became corrupt. Anyway to ensure I got rid of everything, did a complete uninstall and reinstall to ensure corrupt scan files are removed.

 

Mail flows seems to be working now - thanks again :-)

 

Mo

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...