Quantcast
Viewing all articles
Browse latest Browse all 82002

CRM 2011 Email Router - Issues with Outgoing SMTP

My email router has been installed and working for quite some time. Today I noticed that the router was not working and went into the configuration. Everything looks the same and does not appear to have been changed. My configuration profile has a basic outgoing SMTP setup which is all we are using. The router and applicaion are on the same server with a remote SQL box. The same configuration is on my production CRM deployment and it works without any issues. Any advice or ideas are apprecated.

When I click on Users/Queues/Forward Mailboxes I can pick the ORG and Load the data, however when I click on Test Access for a user I get the following error:

Server: SMTPServerName

Outgoing Status: Failure - An error occurred while checking the connection to the Microsoft Dynamics CRM server http://hostname/orgname. Metadata contains a reference that cannot be resolved: http://hostname/orgname/XrmServices/2011/Organization.svc?wsdl'. The operation has timed out

I have uninstalled / Reinstalled / reconfigred and still get the same error. I uninstalled reinstalled deleting the left over program files directory and got the same error. I can telnet to the SMTP server from the CRM box and I can load the website fine and if I click the link reference that can not be resolved it displays the XML file below, so how is it not resolved?

<?xml version="1.0" encoding="utf-8" ?>

-<wsdl:definitions name="OrganizationService" targetNamespace="http://schemas.microsoft.com/xrm/2011/Contracts" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:tns="http://schemas.microsoft.com/xrm/2011/Contracts" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:i0="http://schemas.microsoft.com/xrm/2011/Contracts/Services" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">

<wsdl:importnamespace="http://schemas.microsoft.com/xrm/2011/Contracts/Services" location=http://servername/orgname/XrmServices/2011/Organization.svc?wsdl=wsdl0 />

<wsdl:types/>

-<wsdl:service name="OrganizationService">

-<wsdl:port name="CustomBinding_IOrganizationService" binding="i0:CustomBinding_IOrganizationService">

<soap12:addresslocation=http://servername/orgname/XrmServices/2011/Organization.svc />

-<wsa10:EndpointReference>

<wsa10:Address>http://servername/orgname/XrmServices/2011/Organization.svc</wsa10:Address>

-<Identity xmlns="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity">

<Upn>service account</Upn>

</Identity>

</wsa10:EndpointReference>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

 

 


Viewing all articles
Browse latest Browse all 82002

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>