Connection Failure

Hi @deeganjx,

can you please send your organization url to [email protected], please?

Thanks
AlexaCRM

Hello, is there any chance that this problem is a generalized one and so the solution could be shared? Our organisation is running Dynamics version 2016 at full throttle since quite some time, but also for us we get “Could not find definition of Service <Organization Service> in provided WSDL when trying to make a connection to CRM” when trying to connect.

@pierinux it’s quite possible that the problem is more wide-spread than we think but we need some assistance from you, guys, to help us in nailing it down.

To start with, we need to know your org external URL – that will allow us to check that the wsdl returned by your servers is what we expect. Can you please email your org URL to [email protected] to help our troubleshooting? Note that we don’t need any credentials or any other information at this point.

Thanks
George

Thank you for your assistance George, the problem seems to be linked to some firewall issues. Unfortunately, there is no visible log of the curl attempts to reach the endpoint and the subsequent authentication peer whose URL reference is in the WSDL return during handshaking, but I’m trying to track down the problem with the help of the PHP Dynamics library where I can analyse the returned XML streams step by step. Will let you know if I succeed. The visible error in the WordPress plugin page is a bit misleading.
Unfortunately, I can’t submit a public url as it’s an internal system. Thanks anyway.
Pierinux

• This reply was modified 7 years, 10 months ago by pierinux.

@pierinux I appreciate the need for privacy hence the ask to contact us directly via email. We are adding some troubleshooting facilities to tackle exactly this type of errors but that would require additional logs being accessed by our support. Those logs would contain endpoint information so we would require your consent even when the facilities are available.

As a shot in a dark, try checking the box to ignore SSL errors – we’ve seen all sort of bizzare issues with 3rd party certificates