-
Notifications
You must be signed in to change notification settings - Fork 603
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
Connect-VIServer fails with "Object reference not set to an instance of an object" #585
Comments
I had the same error with a domain joined Server 2019 VM today with version 12.0.0.15939655 and it still does it with a newly launched PowerShell session which it doesn't on my Win10 laptop. Still gives the error after a reboot of the Server 2019 VM so I cannot use PowerCLI on there currently where I could previously. Output from Trace-Command attached in case it is of use |
Turned out there is a limitation of the VAPI endpoint for the length of the session and by default it's set to 24 hours. To change it you have to modify in "/etc/vmware-vapi/endpoint.properties" the values of maxSessionLifespanMilliseconds and minSessionLifespanMilliseconds. By default minSessionLifespanMilliseconds is set to 24 hours and maxSessionLifespanMilliseconds is set to 48. You should change the minSessionLifespanMilliseconds to whatever session length you need and maxSessionLifespanMilliseconds to the same value or higher. |
But I should be able to then start a new session, authenticating if necessary - it should not give this error requiring the whole PowerShell session to be restarted. No other vendor's API/SDK I use doe this - it's a bug somewhere in PowerCLI |
Yes, this part is a bug in PowerCLI. We'll take a look at it. |
Is there any fix for this yet? |
Hello @kamennikolov Need this functionality to connect, restart vmhost, reconnect. Is there any decent workaround for now? |
Hi @eren-kemer |
Describe the bug
Having connected to a vCenter server via Connect-VIserver, when the connection expires, Connect-VIserver will not work again in the same PowerShell instance
![connect-viserver error](https://user-images.githubusercontent.com/11651939/184623461-3320631b-0b55-4555-b3b3-58b076edf01f.png)
![connect-viserver no error](https://user-images.githubusercontent.com/11651939/184623463-178a8b8d-62fd-4e6b-a940-d4a1f7cc3f56.png)
Reproduction steps
Expected behavior
Connect to the given Vcenter server
Additional context
Recently moved from a non-domain joined Windows 10 21H2 laptop where this issue never occurred to a domain-joined Windows 10 21H2 laptop (both where I logon as a non-local admin user and PowerShell is run non-elevated) where the issue occurs 100% of the time.
The text was updated successfully, but these errors were encountered: