• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1436
  • Last Modified:

Exchange 2010 Forefront Issues

Good Morning Experts,

We are having an issue on our exchange server, two actually.

Our Forefront expired.  The scans that happen daily to update the definitions failed.  I disabled the scans.  Yesterday I got the cod and licensed it and all definition file updates were successful however the event log is filled with these:

None of the antimalware engines selected for transport scanning have been initialized.

Could not initialize Spyware Scanner properly.  As a result the system will not function.  Please check the Antispyware engine and signatures.

They are filling our event log.  In addition some users are reporting errors when they log into web mail.  Outlook works fine.  They are getting this error:

Exception
Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException
Exception message: The process failed to get the correct properties.

Looks like some other weird things are happening.  Please help.  I am hoping this is related to the forefront, that is when everything started.

Thank you,

Karen
0
klsphotos
Asked:
klsphotos
  • 4
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
The easiest thing to do is remove Forefront, reboot and reinstall it.
If you download the Forefront service pack from Microsoft it will be the latest build.
Then apply your new key to it.

Do you have Exchange 2010 SP3 installed on the server? If not then you aren't supported, as SP2 and SP1 are now end of life.

Simon.
0
 
klsphotosAuthor Commented:
Does it have to be uninstalled?  It's not going to work with just restarting or restarting the services after the key has been installed?

We are on Exchange 2010 sp3.  Is this why some of the users are getting errors on webmail?

Also, Forefront is licensed on our old exchange server that is still in existence.  We cannot remove it until the end of the school year.

Thanks, lost on this.
0
 
Simon Butler (Sembee)ConsultantCommented:
If you are on Exchange 2010 SP3 then you should be fine for OWA access. The error you have posted is usually something around AD account permissions - missing inheritance is the first thing I would check.

Sometimes restarting Forefront and even the entire server will correct issues, but a lot of the time I just remove it. If you haven't got the latest build of Forefront on the server, then try updating it in place instead.

Simon.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
klsphotosAuthor Commented:
ok thank you, where can I find the latest version of Forefront?

I checked permissions and did a uncheck and recheck of inheritance on permissions and it didn't do anything, so I am really hoping this is why.
0
 
klsphotosAuthor Commented:
We have 11.0.713.0
0
 
klsphotosAuthor Commented:
Thank you very much, the reboot resolved both the Forefront and the error on web mail!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now