Our IT applied some security patch a few months ago and now the same command I used to generate early bound classes no longer working.
Here is the command that worked before:
CrmSvcUtil.exe /out:myProxy.cs /url: devcrm.myco.com/.../Organization.svc /username:un@myco.com /password: pwd /serviceContextName:myContext
Now I am getting error:
Microsoft.Xrm.Tooling.Connector.CrmServiceClient Error: 2 : ERROR REQUESTING ORGS FROM THE DISCOVERY SERVER
Microsoft.Xrm.Tooling.Connector.CrmServiceClient Error: 2 : Source : mscorlib
Method : HandleReturnMessage
Date : 8/17/2018
Time : 5:33:33 PM
Error : Access is denied.
What could have caused this? user permission level changed? There is no change in Svc url as I was able to browse to it and render the .wsdl.
The user un is still valid as I was able to use VS2017 new Dynamics 365 Solution Template to connect to it and saw existing entities.
My CrmSvcUtil.exe version is 9.0.0.9340
The unknown (IT didn't remember what upgrade they did but they assured me there was not change in user security privilege ) driving me nuts - why was this tool so brittle to break?
*This post is locked for comments