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

Exceeded max number of connections. Waiting 60 seconds #135

Closed
jfrobichaud opened this issue Jul 5, 2019 · 9 comments
Closed

Exceeded max number of connections. Waiting 60 seconds #135

jfrobichaud opened this issue Jul 5, 2019 · 9 comments
Labels
Enhancement New feature or request

Comments

@jfrobichaud
Copy link

Hi, while running the Export-O365Configuration I get this:
Every 60 Seconds the same warning appear and it doesn't seem to go through.

Extracting EXOSharedMailbox...
WARNING: Exceeded max number of connections. Waiting 60 seconds
WARNING: Exceeded max number of connections. Waiting 60 seconds
WARNING: Exceeded max number of connections. Waiting 60 seconds
WARNING: Exceeded max number of connections. Waiting 60 seconds

Thanks

@NikCharlebois
Copy link
Collaborator

That is currently the expected behavior with the Exchange Online Management Shell, where there can only be 3 connections made. This normally happens if you ran Export-O365COnfiguration a few times. It is annoying and we are working with the team to find better alternatives that wouldn't require us to forcibly close the connections after every call to EXO, which would have a major negative impact on performance. Leave it running, and the moment one of the connection frees up, it will pick up the extraction. Note that this can sometimes take several minutes to happen.

@NikCharlebois NikCharlebois added the Enhancement New feature or request label Jul 5, 2019
@jfrobichaud
Copy link
Author

ok thanks

@jfrobichaud
Copy link
Author

Still doing this after 1h, is that something I can do to get a connection ? Thanks

@NikCharlebois
Copy link
Collaborator

Get-PSSession | Remove-PSSession will clear all potential connections, but DSC executes in a different context so you may not be able to close its sessions.

@NikCharlebois
Copy link
Collaborator

I have been able to reproduce a similar behavior where the Connect-EXO cmdlet retries to connect in an endless loop whenever I use an extraction account that doesn’t have Admin access to Exchange Online. Make sure the account has proper privileges or unchecks all EXO related components before trying the extraction.

@jfrobichaud
Copy link
Author

I'm trying to extract O365AdminAuditLogConfig and I don't seem to be able to get a connection after letting the script run for 1 hour.

@NikCharlebois
Copy link
Collaborator

Please see related issue opened within the Auth module

microsoft/MSCloudLoginAssistant#1

@NikCharlebois
Copy link
Collaborator

@jfrobichaud please confirm that this is now fixed for you.

@jfrobichaud
Copy link
Author

Fixed, thanks.

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

No branches or pull requests

2 participants