Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection not established. Last CRM error message: Unable to Login to Dynamics CRMOrganizationServiceProxy is null #7

Closed
seefernando opened this issue Jan 17, 2018 · 5 comments

Comments

@seefernando
Copy link

seefernando commented Jan 17, 2018

When using the VSTS export task a connection can not be made and the following error is thrown:

2018-01-17T15:39:29.3492395Z ##[error]Connection not established. Last CRM error message: Unable to Login to Dynamics CRMOrganizationServiceProxy is null

I used the same Connection String for both this task as well as Wael's Ping CRM Task:
AuthType=Office365;Username=$(SourceUsername);Url=https://$(SourceDomain).crm.dynamics.com;Password=$(SourcePassword)

image

Using Hosted VS2017 agent.

@rappen
Copy link
Member

rappen commented Jan 17, 2018

That is strange....
Can you try running it again with system.debug = true ?

image

@seefernando
Copy link
Author

Thanks for a fast responses! I'm totally new to devops with CRM so I really appreciate your efforts!
Question, should the shuffle data file be define as part of the export task in my build? My assumption is no, as the build task will need to get this during the build?
image

Here is the debug log, I included both Wael's ping and the export task:
debug_JanFeb.txt

@rappen
Copy link
Member

rappen commented Jan 18, 2018

The data file only has to be set if you want to specify other output file name than default. Default would in your case be JanFebContentSnippet.data.xml

Still don't really understand connectivity problems. Could you contact me off air to discuss connection? Email jonas dot rapp at innofactor dot com.

@seefernando
Copy link
Author

The issue disappears when using the Hosted agent vs Hosted VS2017

@rappen
Copy link
Member

rappen commented Feb 17, 2018

This issue should now be solved for all agents by commit 6abf29b.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants