Deploying File Filter via FSSMC Error
- When i change the file filter and then deploy it via FSSMC on the host I get the following event errors:
Event Type: Error
Event Source: AEXMLAdapter
Event Category: None
Event ID: 100
Date: 2009/10/25
Time: 06:38:33 PM
User: N/A
Computer:
Description:
Sun Oct 25 18:38:33 2009 ERROR Code: 50.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: AEXMLAdapter
Event Category: None
Event ID: 100
Date: 2009/10/25
Time: 06:38:33 PM
User: N/A
Computer:
Description:
Sun Oct 25 18:38:33 2009 ERROR Message: The request is not supported..
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: AEXMLAdapter
Event Category: None
Event ID: 100
Date: 2009/10/25
Time: 06:38:33 PM
User: N/A
Computer:
Description:
Sun Oct 25 18:38:33 2009 ERROR ***Exception:error in inplace edit job settings.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
this is Antigen 9 and forefront for Exchange 2007 SP1..
Any ideas ?
Answers
Hi,
Thank you for your post.
I did some research regarding the error message. This issue may related to one of the engines that AEM is unable to retrieve information.Before going any further, I’d like to confirm is that your Exchange server(s) that you are trying to manage with AEM are not in a cluster, correct? AEM does support clusters, and if you have a clustered environment, that would explain why you’re having problems with AEM.
If not, we need to run AEM logging on AEM and Exchange Server to find out which engine is having the problem. Due to the complexity of this issue we are unable to effectively assist with this request in the forum. I would like to suggest that you contact Microsoft Product Support Services via telephone so that a dedicated Support Professional can assist with this request. Please be advised that contacting phone support will be a charged call. However, if you are simply requesting a hotfix be sent to you and no other support then charges are usually refunded or waived.
To obtain the phone numbers for specific technology request please take a look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for regional support phone numbers.
Thank you for your patience and understanding.
Regards,
Nick Gu - MSFT- Marked As Answer byNick Gu - MSFTMSFT, ModeratorTuesday, October 27, 2009 8:28 AM
All Replies
Hi,
Thank you for your post.
I did some research regarding the error message. This issue may related to one of the engines that AEM is unable to retrieve information.Before going any further, I’d like to confirm is that your Exchange server(s) that you are trying to manage with AEM are not in a cluster, correct? AEM does support clusters, and if you have a clustered environment, that would explain why you’re having problems with AEM.
If not, we need to run AEM logging on AEM and Exchange Server to find out which engine is having the problem. Due to the complexity of this issue we are unable to effectively assist with this request in the forum. I would like to suggest that you contact Microsoft Product Support Services via telephone so that a dedicated Support Professional can assist with this request. Please be advised that contacting phone support will be a charged call. However, if you are simply requesting a hotfix be sent to you and no other support then charges are usually refunded or waived.
To obtain the phone numbers for specific technology request please take a look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for regional support phone numbers.
Thank you for your patience and understanding.
Regards,
Nick Gu - MSFT- Marked As Answer byNick Gu - MSFTMSFT, ModeratorTuesday, October 27, 2009 8:28 AM
- Hi Nick,
This is not on any clusters. I will escalate this with our local MCS guys .......
Regards,
Deon

