Closed AdCodicem closed 8 years ago
I should have clarified —- this was an issue with the CrmSvcUtil itself when using ADFS/IFD, and I was not using XrmToolBoxTooks; I just wanted to point out that Microsoft’s took has this bug that requires double qualifying the org name with a fake URL to work in this situation.
On Jan 25, 2018, at 3:26 PM, Daryl LaBar notifications@github.com wrote:
@danielcrenna so what url did the EBG build? Looks like org.domain.no/org is what you need? Did it at least ask you to login?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Hi, I am getting the same error when trying to run CrmSvcUtil to re-generate Dynamics proxy classes:
Executed this command against on-premise service: CrmSvcUtil.exe /out:DynamicsCRMProxy.cs /url:https://myCrm.myOrg.com/XRMServices/2011/Organization.svc /domain:myOrg /username:uid@myOrg /password:12345 /namespace:Billing.DynamicsCrm.Contracts.Proxy /serviceContextName:DynamicsProxyContext
Couple of key facts: 1) I was able to browse to the Svc url and the existing codes from backend, using same connection url and credential still working fine, except for when trying to call service.CreateIncident 2) I have seen similar error when we upgraded from 2011 to 2016 but resolved it after I downloaded the MicrosoftDynamics365SDK.exe and used the CrmSvcUtil tool from the Sdk/Bin ( version is 8.2.1.8676) folder. 3) I tried a few things suggested from this board, including replacing Url with connectionString, replacing XRMServices with myOrg, etc but none of them worked at this point.
Your help will greatly appreciated. Thanks
What version are you running? Both of tools and CRM.
Was it working before and has stopped?
Can you connect with other SDK tools?
CRM version is 8.2.2.112
and CrmSvcUtil.exe version is 8.2.1.8676
On Fri, Jul 27, 2018 at 9:35 AM, Daryl LaBar notifications@github.com wrote:
What version are you running? Both of tools and CRM.
Was it working before and has stopped?
Can you connect with other SDK tools?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/daryllabar/DLaB.Xrm.XrmToolBoxTools/issues/14#issuecomment-408420084, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ7IWEfFq1DUaalQM5XsinzX5EFCCZ5nks5uKxcVgaJpZM4HXWJC .
I'm confused. Are you using the early bound generator, or any of it's assemblies?
Yes, we've been using the CrmSvcUtil to generate all the early bound classes.
One thing was the key when we upgraded to 2016 - I had to add domain to the user name:
Before upgrading to 2016, this worked: CrmSvcUtil.exe /out:DynamicsCRMProxy.cs /url: https://crm.myOrg.com/devinstance/XRMServices/2011/Organization.svc /domain:myOrg /username:uid /password:pwd /serviceContextName:DynamicsProxyContext
After 2016, had to add domain name to user name: CrmSvcUtil.exe /out:DynamicsCRMProxy.cs /url: https://crm.myOrg.com/devinstance/XRMServices/2011/Organization.svc /domain:myOrg /username:uid@myOrg.com /password:pwd /serviceContextName:DynamicsProxyContext
On Fri, Jul 27, 2018 at 11:34 AM, Daryl LaBar notifications@github.com wrote:
I'm confused. Are you using the early bound generator, or any of it's assemblies?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/daryllabar/DLaB.Xrm.XrmToolBoxTools/issues/14#issuecomment-408455665, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ7IWOCaTJmpLCcgatMuy442Nzi9Es1Qks5uKzL8gaJpZM4HXWJC .
@yangs2016 I don't see any DLaB assemblies in your connection string. If you're unable to connect with just the CrmSvcUtil that is a Microsoft issue. Contact them.
Hello Daryl,
I use the early bound generator on the following environment : CRM 2016, on premises, with ADFS. The following exception appeared after generating the Entities files :
This organization was updated from CRM 2015 and, at that time, it generated successfully the files. After the update to CRM 2016 it doesn't work anymore.
As the #12 issue's message was different I opened a new issue.
Let me know if you need more information.