You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to create a CDS --kind Authentication through PAC and gives me this error
Error: Failed to connect to Dataverse
There was no endpoint listening at https://< organization-URL >.crm4.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.0.46.3082 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote server returned an error: (407) Proxy Authentication Required.
Our environment is accessing dynamics through a proxy that is installed properly.
I am able to perform other tasks of PAC such as create --kind ADMIN or create a Backup of environment.
In Azure we have an app registration that is pointing at the enterprise application Dynamics CRM and it has user-impersonation with admin consent
The text was updated successfully, but these errors were encountered:
@fadyyeta the error to not be able to connect to Dataverse is caused by your local network that requires proxy authN: The remote server returned an error: (407) Proxy Authentication Required.
The Dataverse service client that is used by pac CLI has no support for handling local proxy authentication; before trying to connect via pac CLI to your Dataverse environments, ensure that your PC has authenticated to your network's internet proxy, e.g. via browser.
This behavior is currently by design, with no backlog work items to address this
@fadyyeta I have also come across this issue, but when using pac via CLI. To fix this I added the following to the configuration section of pac.exe.config file :
Trying to create a CDS --kind Authentication through PAC and gives me this error
Error: Failed to connect to Dataverse
There was no endpoint listening at https://< organization-URL >.crm4.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.0.46.3082 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote server returned an error: (407) Proxy Authentication Required.
Our environment is accessing dynamics through a proxy that is installed properly.
I am able to perform other tasks of PAC such as create --kind ADMIN or create a Backup of environment.
In Azure we have an app registration that is pointing at the enterprise application Dynamics CRM and it has user-impersonation with admin consent
The text was updated successfully, but these errors were encountered: