FIM is throwing the below error message every minute or so. This error also relates to the fact that Email Notification is not working. This is a lab setting, so everything (SQL, FIM and exchange) are on the same machine. Product info: Exchange 2010 (SSL enabled), FIM 2010 and SQL 2008. Accessing to https://<servername>/ews/exchange.asmx works fine, but accessing the http report HTTP 403 error forbidden. Here's the error message: System.Web.Services: System.Net.WebException: The request failed with HTTP status 404: Not Found. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.ResourceManagement.WebServices.Mail.Exchange.ExchangeServiceBinding.CreateItem(CreateItemType CreateItem1) at Microsoft.ResourceManagement.Mail.ExchangeProxy.ExecuteCreateItem(CreateItemType request) at Microsoft.ResourceManagement.Mail.ExchangeServer.SendNotification(NotificationMessage message) at Microsoft.ResourceManagement.Mail.NotificationMessage.Send() at Microsoft.ResourceManagement.Workflow.Hosting.SendMailWorkItemProcessor.SendMailMessage(MessageContent messageContent) at Microsoft.ResourceManagement.Workflow.Hosting.SendMailWorkItemProcessor.ProcessWorkItem(WorkItem workItem)

Can you copy paste the value from the FIM Service configuration file. It's located at C:\Program Files\Microsoft Forefront Identity Manager\2010\Service\Microsoft.ResourceManagement.Service.exe.config This is the section I'm interested in: <appSettings> <add key="mailServer" value="https://yourserver/ews/exchange.asmx" /> <add key="isExchange" value="1" /> <add key="sendAsAddress" value=email@domain.com /> <add key="synchronizationServerName" value="syncserver" /> </appSettings>http://setspn.blogspot.com

here's what I have <appSettings> <add key="mailServer" value="https://<servername>/ews/exchange.asmx" /> <add key="isExchange" value="1" /> <add key="sendAsAddress" value="FIMService@<domainname>" /> <add key="synchronizationServerName" value="<servername>" /> </appSettings>

Is your FIM Service user account mailbox enabled? Besides that, I'm a bit confused, is the above error still occuring? You seem to have a related topic: http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/7697048b-3cf1-48ce-a8eb-b5c51104c279http://setspn.blogspot.com

Hello Tomas, After an iisreset to IIS7 (FIM) the 403 error seems to have disappeared. Now I am getting the following error: System.Web.Services: System.InvalidOperationException: Client found response content type of '', but expected 'text/xml'. The request failed with an empty response. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.ResourceManagement.WebServices.Mail.Exchange.ExchangeServiceBinding.FindItem(FindItemType FindItem1) at Microsoft.ResourceManagement.WebServices.Mail.Exchange.MailChannel.ExchangeMailChannelListener`1.ExchangeMailListener.<OnPollTimerExpired>b__0(Boolean findUnreadItems) at Microsoft.ResourceManagement.WebServices.Mail.Exchange.MailChannel.ExchangeMailChannelListener`1.ExchangeMailListener.OnPollTimerExpired(Object state) the FIM Service account has a recipient mailbox account and I can send to it. and in regard to my other post, I was able to resolve that issue by simply assigning Exchange Server Certificate to port 443 on the Default Site.

I'll give the same advice as in this thread ( Email Notification doesn't work ) If you'd enable advanced logging for the FIM Service, I'm pretty sure you should see the communication kick off between the FIM Service and Exchange. The explanation is here, 2nd part of the article: FIM 2010 Enable Advanced Error Logging As for how to read the trace file, check the 2nd part of the following article: How to Configure FIM Portal Tracing http://setspn.blogspot.comhttp://setspn.blogspot.com

Thank you Thomas for your input. I was able to resolve the problem as follow: 1. Edited Exchange Server web.config to support SSL 2. Ensured that the Default Web Site is using Exchange Certificate for SSL, Port 443 3. Enabled Kerberos for the FIM Portal Admin