Friday, June 29, 2012 5:33 PM
I have an installation of forefront protection 2010 for exchange server installed on a windows server 2008r2 machine with exchange 2010 (both machine and exchange are fully updated)
With my forefront installation i constantly get an error stating that the information store is running but the forefront VSAPI library is not registered (error 7027). I have followed the instructions here
and when i do the information store is successfully hooked but within 30 seconds it goes back to the error state.
scanning is enabled, and there is a scan scheduled.
I have tried a full re-installation as well to no avail.
the only line in the instructions (linked above) that i could not complete was confirming the registry value as the instructions are for exchange 2007 not 2010. does anyone know what the corresponding registry key is or how to resolve this error?
Tuesday, July 03, 2012 2:12 AMModerator
Thank you for the post.
I’d like to confirm if you have install FPE in a clustered environment. This error message should be seen on the Passive node when connecting using the FPE Administration console. This is normal behavior for FPE. Not everything is available on the Passive Node, so seeing the error “MS Information Store is running but the Forefront VSAPI Library is not registered" should be expected. This should not be something that is seen on the Active Node.
Nick Gu - MSFT
Tuesday, July 03, 2012 4:27 PMThis is not a clustered environment, it is a stand alone server.
Friday, July 06, 2012 8:43 AMModerator
Thank you for the update.
You may refer to this thread and see if it helps: http://social.technet.microsoft.com/Forums/en-US/exchangesvrantivirusandantispam/thread/16bb2797-7a46-4df3-a201-2f946b988b53
Nick Gu - MSFT
Friday, July 06, 2012 1:26 PMI have confirmed that scanning is enabled for both realtime and transport as well as a scheduled scan.
Tuesday, July 17, 2012 7:16 PMno other suggestions?
Friday, August 17, 2012 8:34 AM
Have you tried running:-
Friday, August 17, 2012 1:38 PM
yup, that was the first thing i tried. Those were the instructions i referenced in the original post.
ultimately succeeded by removing the product, manually removing all the associated registry keys, manually deleting the old installation folders and doing another clean reinstall.
- Marked As Answer by LSUChillin Friday, August 31, 2012 1:52 PM
Thursday, August 30, 2012 1:50 PMI'm glad to hear you resolved this. Often an uninstall/reinstall is the quickest way to resolve issues and has a high probability of success :)
Friday, August 31, 2012 1:52 PMthe uninstall reinstall didn't fix it on its own, it was manually deleting the registry information before the reinstall that ultimately resolved the problem