MSCRM CRM working with CRM 8.0 on-premise?

[bfallar3]

We are using MS CRM Dynamics 8.x on-premise and using Azure Devops hosted agent. Does this tasks work on this environment. I also tried self-hosted agent but there is always error. I'm initially using a simple tasks: Tool Installer and CRM Ping.

[warning]Unable to login to Dynamics CRM, Error was : Metadata contains a reference that cannot be resolved: 'https://idwicrmapt13.mlijkt01.manulife.com/XRMServices/2011/Discovery.svc?wsdl&sdkversion=9'.

Please advise.

[WaelHamze]

@bfallar3 the agent needs to have line of sight to the Dynamics instance. Do you have some sort of IFD setup that allows you instance to be accessible from outside your company network? If not you will need to use a private agent.

[bfallar3]

@WaelHamze I also tried private self hosted agent using my laptop network with line of sight on the CRM instance. Using my browser in my laptop I cajln access the on premise CRM.

[WaelHamze]

@bfallar3 in this case there could be two issues 1- connection string is incorrect 2- you may need to configure or bypass the proxy on the self hosted agent

[bfallar3]

@WaelHamze I verified the connection string is correct because I use the same connection string in my console app and it was able to connect and authentication using the WhoAmI request messsage.

[bfallar3]

@WaelHamze below is the exact error...

[warning]Unable to Login to Dynamics CRM

[error]Couldn't connect to CRM instance after 3 attempts: ERROR REQUESTING ORGS FROM THE DISCOVERY SERVER

ERROR REQUESTING ORGS FROM THE DISCOVERY SERVERThe caller was not authenticated by the service. => The request for security token could not be satisfied because authentication failed.Unable to login to Dynamics CRM, Error was : The caller was not authenticated by the service. The caller was not authenticated by the service. => The request for security token could not be satisfied because authentication failed.Unable to Login to Dynamics CRM Unable to Login to Dynamics CRM

[bfallar3]

@WaelHamze could also this been an issue with firewall where the on-premise is deployed?

[WaelHamze]

@bfallar3 unlikely as firewalls are normally for external and inbound traffic.

HAve you tried to run the console app on the agent server under the account that is running the agent and see what happens?

[BubunCTS]

I am facing the same issue.Can anyone please help me to sort out this issue.

[averyparkes]

Having same issue. I don't have OrgName in my front-end url. I visit https://URL (There is no OrgName at end)

However I must include it in my connection string. URL=https://URL/ORG;AuthType=IFD;Domain=DOMAIN;UserName=DOMAIN\USER;Password=PASS

Now, I have an incorrect discovery endpoint because OrgName was included. https://URL/XRMServices/2011/Organization.svc?wsdl&sdkversion=9 WORKS https://URL/ORG/XRMServices/2011/Organization.svc?wsdl&sdkversion=9 FAILS

ERROR: Metadata contains a reference that cannot be resolved

[averyparkes]

Changing Power DevOps Tool Installer to version 9 fixed my issue.

[BubunCTS]

Hi

Can u please provide the details how can u set up for on premises azure devops? Is there any specific tasks that need to be done?

Thanks & Regards Bubun Bhandari 8240122736

On Thu, 20 Aug 2020, 6:40 pm Avery Parkes, notifications@github.com wrote:

Changing to Power DevOps Tool Installer to version 9 fixed my issue. [image: image] https://user-images.githubusercontent.com/2277548/90774042-d8fabd80-e2c4-11ea-8e96-7b041af73fb1.png

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/WaelHamze/dyn365-ce-vsts-tasks/issues/156#issuecomment-677655063, or unsubscribe https://github.com/notifications/unsubscribe-auth/AISKAUPHIDMSXKCYSZBL6SDSBUOEHANCNFSM4LCB7JVQ .