This post is more than 5 years old
31 Posts
0
156826
January 1st, 2014 21:00
Error trying to import VMWare templates
Hi Everyone,
This error just started happening a couple of days ago, before then everything was fine. We can't think of anything that's changed.
The error is:
The following error occured while retrieving the virtual machine or templates from [vCentre Server].
Required parameter container is missing
while parsing call information for method CreateContainerView
at line 1, column 218
while parsing SOAP body
at line 1, column 207
while parsing SOAP envelope
at line 1, column 38
...
Strangely if I try to import folders or datastores from VMWare it has no problem doing that, and if I go into the VMWare setup and click the "Test connection" button, it completes successfully. It's just when I try and import templates that I get the error.
I have tried rebooting the vCentre server, and the vWorkspace CB, no luck. We only actually have 3 templates in VMWare, I tried converting them all to VMs and that didn't help either.
Any ideas?
Thanks!
Nick.
nicholas.fletch
31 Posts
1
January 2nd, 2014 21:00
Hi David,
Thanks for the reply. I tried creating a new template, but no luck.
However, I thought I might try creating a whole new computer group. During the import datacentre step, the wizard noted that the datacentre name had changed. It offered me the old and the new datacentre name, I chose the new (current) one, and then template importing for this new group worked!
So that was the problem.
Strangely, it appears you just have to import the datacentres somewhere in the console for it to update everywhere. In the above steps I imported the datacentres when creating a new group, and then quit the wizard when the templates part worked. This was all it required to allow me to successfully import templates on my pre-existing computer group.
Thanks,
Nick.
david.caddick-q
16 Posts
0
January 2nd, 2014 04:00
Hi Nick,
If this is occuring only when you check the template - what happens if you create a brand new template and try to import that?
Do you still get the same error?
As much as nothing should have changed - when this typically happens it might be a case of Windows Updates might have kicked in?
Has there been any auto updates applied?
Cheers,
Dave