Get-Tag : 3/15/2018 5:55:27 AM Get-Tag There was no endpoint listening at
https://tavc.itislab.com/lookupservice/sdk that could accept the message. This is often caused by an incorrect address
or SOAP action. See InnerException, if present, for more details.
At line:1 char:1
+ Get-Tag
+ ~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-Tag], VimException
+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTag
Hello All,
This is the issue being faced, where I am trying to automate, using Powercli command.
If someone, can please help me find a solution or link to follow the document, would be a great help.
Regards,
Suhail
I assume you are not yet using PowerCLI 10?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
I have been using PowerCLI 6.5.3, issues are faced anything related to Tag and Categories.
Also, went through the blog of VMware PowerCLI 10 beta version release.
Is it the issue faced due the version issue of PowerCLI?
There are some issues with Tag related cmdlets in PowerCLI 6.4.*.
In PowerCLI 10 all Tag related cmdlets now use the REST API, and the issues seem to have been resolved.
You have 2 options:
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Hello LucD,
Thanks for the reply,
I have been using PowerCLI 6.5.3 version, initially the script was developed 10months back, and was working perfectly fine.
After the migration of scripts of the newer version, the above issue is faced.
I will take your suggestion and download PowerCLI 10 version and try to run the script.
Using the rCISTag module, do you have any particular link to download the module and import.
The rCisTag module is not in the PowerShell Gallery, but on the PowerCLI Examples repository.
See the hyperlink above.
But if you plan to upgrade to PowerCLI 10, you will also be using the REST API
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference