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
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
Ok, I'm at a loss. I have a script that creates multiple VMs, make some interface modifications, powers on VMs and then changes IPs. All works well when I set my count for 1 VM but anymore then that and I get the XML Parsing error. I have modified the max execution time in php.ini to 9000 and the issue still exists. Not sure if there is some other timer that is being used which needs to be modified. I'm running Windows 2012 Server and connecting to Vcenter 6.5. I connecting to the webcommander interface directly on the webcommander server. Any assistance will be greatly appreciated!
The text was updated successfully, but these errors were encountered:
Your script may output some special strings or characters that result in the XML parsing error.
To debug, run your script from powershell console directly and redirect its output to a file such as debug.xml.
Then open the file with any xml editor or viewer to check if there is any invalid entity.
To prevent such invalid output, add " | out-null " to powershell commands in your script.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ok, I'm at a loss. I have a script that creates multiple VMs, make some interface modifications, powers on VMs and then changes IPs. All works well when I set my count for 1 VM but anymore then that and I get the XML Parsing error. I have modified the max execution time in php.ini to 9000 and the issue still exists. Not sure if there is some other timer that is being used which needs to be modified. I'm running Windows 2012 Server and connecting to Vcenter 6.5. I connecting to the webcommander interface directly on the webcommander server. Any assistance will be greatly appreciated!
The text was updated successfully, but these errors were encountered: