locked
CRM 4.0 Email Router Inbound Error "Incoming Status: Failure - The operation has timed out" RRS feed

  • Question

  • Hi Folks,

    I'm having some issues configuring the Email Router to work with inbound emails.

    I get a message saying "Incoming Status: Failure - The operation has timed out" when I test access.


    I have checked previous posts and believe that I have all the settings correct.
    My environment is  CRM 4.0 installed with Rollup 17. I also have Exchange 2007 SP2. I  also have a valid digital certificate from Digicert on Exchange.


    Here's my inbound  configuration:

     

    E-mail server type = Exchange 2007
    Protocol = Webdav

    Authentication Type = Windows

    Location = https://(machinename.headoffice.mycompany)

    Access Credentials = user Specified

     

    Deployments

     

    Deployment = My Company

    Microsoft Dynamics Server = http://(crmservername):5555/(MYCOMPANYSystems)

    Access Credentials = Other Specified

    Username = mydomain\crmadmin

    Password = CRM Admin password

    Correct Associations for Incoming and Outgoing profiles

     

    Any suggestions?

     

    Thanks,

    Adam

     


    Thursday, November 3, 2011 9:07 PM

Answers

  • Hi Adam,

     

    Open the email router -> Incoming profile and enter the details as mentioned below.

    Email Server Type: Exchange 2007

    Protocol: Exchange Web Services

    Authentication Type: Windows Authentication

    Location: https://machinename.headoffice.mycompany/ews/exchange.asmx

    Access Credentials: User Specified

     

    Thanks,

    Vikash

    • Marked as answer by Agilbert2003 Tuesday, December 6, 2011 12:46 AM
    Monday, December 5, 2011 2:13 PM

All replies

  • Hi,


    Can anyone assist me with this issue please?

     

    Thanks,

    Adam

    Thursday, November 24, 2011 8:38 PM
  • Hi Adam,

    Can you just open  https://(machinename.headoffice.mycompany) in to the browser of CRM Router server?

    Let me know, what you are get.

     

    thank you


    Many Thanks -Bhautik Desai xRM Technologies
    Friday, November 25, 2011 11:20 AM
  • Hi Bhautik,

     

    Thanks for your reply.

    Yes I can open the link https://(machinename.headoffice.mycompany). It displays the IIS 7 splash page.

     

    Thanks very much,

     

    Adam

    Thursday, December 1, 2011 9:47 AM
  • Hi Adam,

     

    In email router we need to access MS exchange service with URL https://machinename.headoffice.mycompany/ews/exchange.asmx instead of https://machinename.headoffice.mycompany.

    Please let me know if it solves your problem.

     

    Thanks,

    Vikash


    Friday, December 2, 2011 10:50 AM
  • HI Vikash,

     

    I've followed your suggestion.

     

    I'm not receiving the following error message.

    I'm 100% certain the user / mailbox is created correctly. the user account in CRM is crmcasetoemail with an email address of crmcasetoemail@mydomain.com  I have configured the account to receive email in CRM --> Workplace --> Personalize Workplace --> Email. I have also tested using my account.

    I should also mention that when I tested the URL https://machinename.headoffice.mycompany/ews/exchange.asmx  from the CRM host machine I was presented with a login screen. Upon entering credentials and clicking OK the following page displayed https://machinename.headoffice.mycompany/ews/Services.wsdl

     

    Incoming Status: Failure - The remote Microsoft Exchange e-mail server returned the error "(404) Not Found". This user or queue does not have a mailbox. Create a mailbox and try again. The remote server returned an error: (404) Not Found.

     

    Thanks

    Adam


    Saturday, December 3, 2011 6:48 AM
  • Hi Adam,

     

    Open the email router -> Incoming profile and enter the details as mentioned below.

    Email Server Type: Exchange 2007

    Protocol: Exchange Web Services

    Authentication Type: Windows Authentication

    Location: https://machinename.headoffice.mycompany/ews/exchange.asmx

    Access Credentials: User Specified

     

    Thanks,

    Vikash

    • Marked as answer by Agilbert2003 Tuesday, December 6, 2011 12:46 AM
    Monday, December 5, 2011 2:13 PM
  • Thanks so much Vikash, changing Protocol to Exchange Web Services has resovled my issue!

     

     

    Thanks,

    Adam,

    Tuesday, December 6, 2011 12:47 AM