Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

crmsvcutil.exe: Unable to generate entity classes for early binding - Dynamics CRM Online

I am trying to generate early bound entity classes from my Dynamics CRM Online instance.

I have CRM SDK installed on my machine.

I am running following command from the "Bin" folder of SDK.

crmsvcutil.exe /url:<<OrganizationServiceUrl>> /out:crmexams3.cs /username:"<<username>>" /password:"<<password>>"

But this gives me following error:

Error requesting orgs from the discovery server
Access is denied

I have replaced the OrganizationServiceUrl with the organization service url which I could found from Developer resources in CRM instance.

My instance is CRM 2016 Online.

Any idea why this is failing?

Thanks

like image 252
Nirman Avatar asked Aug 04 '16 11:08

Nirman


People also ask

How do I generate early-bound classes in Dynamics 365?

Run the code generation tool Run the CrmSvcUtil.exe tool from the Tools\CoreTools folder created when you downloaded the tools using the script described in Dataverse development tools. If you run the tool from another folder location, make sure that a copy of the Microsoft. Xrm. Sdk.

How do you generate early-bound classes in dynamics 365 using Xrmtoolbox?

On the left pane, users can choose to generate the early-bound . NET files for the Entities, the Option Set, and/or and Actions. A click on the button will launch a command prompt and the command line used to create the classes will be displayed on the left pane.

Where is CrmSvcUtil EXE?

Solution- CrmSvcUtil.exe is available in Microsoft. crmsdk. coretools package and you can download this package from nuget.

What is CrmSvcUtil?

CrmSvcUtil.exe is a command-line code generation tool for use with Dynamics 365 for Customer Engagement. This tool generates early-bound . NET Framework classes that represent the entity data model used by Dynamics 365 for Customer Engagement.


1 Answers

If you put /il as an argument and remove the username and password you can enter the credentials, domain, etc through a XRMTooling Login Control. Entering it in manually has the benefits of:

  • It will potentially fix your problem.
  • It makes it so you aren't storing credentials somewhere, which is a little bit of a security faux paux.
like image 112
Brendon Colburn Avatar answered Oct 30 '22 16:10

Brendon Colburn