<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: get-tagassignment error after vcenter upgrade in VMware PowerCLI Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2840590#M100933</link>
    <description>&lt;P&gt;We ran into same issue after VSCA 7.0.2 upgrade, we are going to open SR.&lt;/P&gt;&lt;P&gt;PS W:\&amp;gt; get-tagassignment&lt;BR /&gt;get-tagassignment : 4/8/2021 10:13:23 AM Get-TagAssignment com.vmware.vapi.std.errors.operation_not_found {'messages': [com.vmware.vapi.std.localizable_message {'id':&lt;BR /&gt;vapi.method.input.invalid.interface, 'default_message': Cannot find service 'com.vmware.cis.data.svc.resource_model'., 'args': [com.vmware.cis.data.svc.resource_model], 'params': ,&lt;BR /&gt;'localized':}], 'data': , 'error_type': OPERATION_NOT_FOUND}&lt;BR /&gt;At line:1 char:1&lt;BR /&gt;+ get-tagassignment&lt;BR /&gt;+ ~~~~~~~~~~~~~~~~~&lt;BR /&gt;+ CategoryInfo : NotSpecified: (:) [Get-TagAssignment], CisException&lt;BR /&gt;+ FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTagAssignment.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetT&lt;BR /&gt;agAssignment&lt;/P&gt;</description>
    <pubDate>Thu, 08 Apr 2021 08:18:05 GMT</pubDate>
    <dc:creator>degvm</dc:creator>
    <dc:date>2021-04-08T08:18:05Z</dc:date>
    <item>
      <title>get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837529#M100522</link>
      <description>&lt;P&gt;We have two datacenters and thus two vCenter environments. Recently one DC received an update from vCenter 7.0.1 to 7.0.2. The other one is still on 7.0.1.&lt;BR /&gt;On the upgraded environment the get-tagassignment and get-tag commands now error out :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;get-vm alani001|get-tagassignment

Get-TagAssignment: 3/23/2021 1:13:50 PM Get-TagAssignment               com.vmware.vapi.std.errors.operation_not_found {'messages': [com.vmware.vapi.std.localizable_message {'id': vapi.method.input.invalid.interface, 'default_message': Cannot find service 'com.vmware.cis.data.svc.resource_model'., 'args': [com.vmware.cis.data.svc.resource_model], 'params': , 'localized':}], 'data': , 'error_type': OPERATION_NOT_FOUND}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this a known issue, and if so, what can we do to resolve this, please ?&lt;/P&gt;&lt;P&gt;Before I forget, I tried this on both PowerCLI on Windows (v. 6.5.1) and Linux (v. 12.0). Both go wrong....&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 13:12:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837529#M100522</guid>
      <dc:creator>PA3CRZ</dc:creator>
      <dc:date>2021-03-23T13:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837540#M100525</link>
      <description>&lt;P&gt;Is your environment and vCenter configured in En-US or a local language?&lt;BR /&gt;PowerCLI 6.5.1?&lt;BR /&gt;That is a very old version, I suggest you upgrade that version.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 14:04:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837540#M100525</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2021-03-23T14:04:29Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837545#M100528</link>
      <description>&lt;P&gt;Does the error return after you stop your PowerShell/PowerCLI session and start it again?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 14:14:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837545#M100528</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2021-03-23T14:14:04Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837569#M100539</link>
      <description>&lt;P&gt;Already asked our Wintel guys to hurry up and upgrade PowerCLI asap......&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@C2A029D8F56497C0B9F536A9C279C6DF/emoticons/1f644.png" alt=":face_with_rolling_eyes:" title=":face_with_rolling_eyes:" /&gt;&lt;/P&gt;&lt;P&gt;But..the error also occurs when I do the same on Linux in Powershell Core and PowerCLI 12.0.0&lt;/P&gt;&lt;P&gt;vCenter is configured EN-US.&lt;/P&gt;&lt;P&gt;And yes, after starting a fresh powershell session and reissuing the command&amp;nbsp;get-vm alani001 | get-tagassignment, I &lt;U&gt;do&lt;/U&gt; get the right output, but only in Linux, NOT in Windows...&lt;/P&gt;&lt;P&gt;I'm curious why you asked that question, and more curious to the solution it leads to...&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 15:44:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837569#M100539</guid>
      <dc:creator>PA3CRZ</dc:creator>
      <dc:date>2021-03-23T15:44:57Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837571#M100540</link>
      <description>&lt;P&gt;There have been cases reported when a PS/PowerCLI got corrupted, and a restart helped.&lt;BR /&gt;&lt;BR /&gt;I'm afraid I have no solution, I would advise opening an SR.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 15:48:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2837571#M100540</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2021-03-23T15:48:43Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2840590#M100933</link>
      <description>&lt;P&gt;We ran into same issue after VSCA 7.0.2 upgrade, we are going to open SR.&lt;/P&gt;&lt;P&gt;PS W:\&amp;gt; get-tagassignment&lt;BR /&gt;get-tagassignment : 4/8/2021 10:13:23 AM Get-TagAssignment com.vmware.vapi.std.errors.operation_not_found {'messages': [com.vmware.vapi.std.localizable_message {'id':&lt;BR /&gt;vapi.method.input.invalid.interface, 'default_message': Cannot find service 'com.vmware.cis.data.svc.resource_model'., 'args': [com.vmware.cis.data.svc.resource_model], 'params': ,&lt;BR /&gt;'localized':}], 'data': , 'error_type': OPERATION_NOT_FOUND}&lt;BR /&gt;At line:1 char:1&lt;BR /&gt;+ get-tagassignment&lt;BR /&gt;+ ~~~~~~~~~~~~~~~~~&lt;BR /&gt;+ CategoryInfo : NotSpecified: (:) [Get-TagAssignment], CisException&lt;BR /&gt;+ FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTagAssignment.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetT&lt;BR /&gt;agAssignment&lt;/P&gt;</description>
      <pubDate>Thu, 08 Apr 2021 08:18:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2840590#M100933</guid>
      <dc:creator>degvm</dc:creator>
      <dc:date>2021-04-08T08:18:05Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843102#M101154</link>
      <description>&lt;P&gt;Yes, we have the same problem. After upgrading vCenter 7.0.1 to 7.0.2 we can not read or write the tags. All other information like name, network, notes we can read.&lt;/P&gt;&lt;P&gt;Different PowerShell versions on Windows 10, Windows Server and linux clients tried. All have the same issue:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PS V:\&amp;gt; (Get-TagAssignment -Entity $vm -Category "Administator").Tag&lt;BR /&gt;Get-TagAssignment : 21.04.2021 15:09:09 Get-TagAssignment Der Wert darf nicht NULL sein.&lt;BR /&gt;Parametername: collection&lt;BR /&gt;In Zeile:1 Zeichen:2&lt;BR /&gt;+ (Get-TagAssignment -Entity $vm -Category "Administator").Tag&lt;BR /&gt;+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;+ CategoryInfo : NotSpecified: (:) [Get-TagAssignment], VimException&lt;BR /&gt;+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTag&lt;BR /&gt;Assignment&lt;/P&gt;&lt;P&gt;PS V:\&amp;gt; Get-TagAssignment -Entity $vm&lt;BR /&gt;Get-TagAssignment : 21.04.2021 15:10:17 Get-TagAssignment com.vmware.vapi.std.errors.operation_not_found {'messages':&lt;BR /&gt;[com.vmware.vapi.std.localizable_message {'id': vapi.method.input.invalid.interface, 'default_message': Cannot find&lt;BR /&gt;service 'com.vmware.cis.data.svc.resource_model'., 'args': [com.vmware.cis.data.svc.resource_model], 'params': ,&lt;BR /&gt;'localized':}], 'data': , 'error_type': OPERATION_NOT_FOUND}&lt;BR /&gt;In Zeile:1 Zeichen:1&lt;BR /&gt;+ Get-TagAssignment -Entity $vm&lt;BR /&gt;+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;+ CategoryInfo : NotSpecified: (:) [Get-TagAssignment], CisException&lt;BR /&gt;+ FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTagAssi&lt;/P&gt;&lt;P&gt;gnment.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTagAssignment&lt;/P&gt;</description>
      <pubDate>Wed, 21 Apr 2021 14:37:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843102#M101154</guid>
      <dc:creator>Renturem</dc:creator>
      <dc:date>2021-04-21T14:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843315#M101183</link>
      <description>&lt;P&gt;Updating to Powercli 12.3.0 solved the issue for us.:&lt;/P&gt;&lt;P&gt;&lt;A href="https://code.vmware.com/web/tool/12.3.0/vmware-powercli" target="_blank"&gt;https://code.vmware.com/web/tool/12.3.0/vmware-powercli&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 13:18:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843315#M101183</guid>
      <dc:creator>degvm</dc:creator>
      <dc:date>2021-04-22T13:18:33Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843322#M101184</link>
      <description>&lt;P&gt;No changes&amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@A5AF993F89FC883B1750F8915C03D452/emoticons/1f615.png" alt=":confused_face:" title=":confused_face:" /&gt;. The Powercli-Module was on Windows-client already with version 12.3.&lt;/P&gt;&lt;P&gt;PS V:\&amp;gt; Find-Module *powercli&lt;/P&gt;&lt;P&gt;Version Name Repository Description&lt;BR /&gt;------- ---- ---------- -----------&lt;BR /&gt;12.3.0.... VMware.PowerCLI PSGallery This Windows PowerShell module contains VMware.P...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also tried with downloaded powercli-Script &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@8D3AC78033E090809829B1C8262B7619/emoticons/1f61e.png" alt=":disappointed_face:" title=":disappointed_face:" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 13:49:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843322#M101184</guid>
      <dc:creator>Renturem</dc:creator>
      <dc:date>2021-04-22T13:49:38Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843328#M101185</link>
      <description>&lt;P&gt;Not sure if it helps, but I ran upgrade with -force parameter and it didn't work until I rebooted the machine.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 14:08:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843328#M101185</guid>
      <dc:creator>BjornJohansson</dc:creator>
      <dc:date>2021-04-22T14:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843335#M101188</link>
      <description>&lt;P&gt;Yes. First -force install&amp;nbsp;grumbles some of the modules are in use. Reboot, install again with -force no problems. Reboot again. Now it works.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 14:26:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2843335#M101188</guid>
      <dc:creator>Renturem</dc:creator>
      <dc:date>2021-04-22T14:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2850457#M101730</link>
      <description>&lt;P&gt;hello&lt;/P&gt;&lt;P&gt;our vcenter was updated to&amp;nbsp;&lt;SPAN&gt;6.7.0.48 and&amp;nbsp;"get-tag" command have the same error.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1. powercli on pc was updated to 12.3&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. pc rebooted&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;result: not&amp;nbsp;&lt;/SPAN&gt;successful&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;3. deleted vmware Modul - rebooted pc - install vmware modul - rebooted pc&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;result: not successful&amp;nbsp;again&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;pls help&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 12:48:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2850457#M101730</guid>
      <dc:creator>VitaliyKovalen1</dc:creator>
      <dc:date>2021-06-02T12:48:07Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2850509#M101734</link>
      <description>&lt;P&gt;I suggest opening an SR&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 16:13:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2850509#M101734</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2021-06-02T16:13:57Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2855810#M102178</link>
      <description>&lt;P&gt;PA3CRZ,&lt;BR /&gt;Did you open an SR? What's the status now?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Lars&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 08:34:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2855810#M102178</guid>
      <dc:creator>larstr</dc:creator>
      <dc:date>2021-07-05T08:34:51Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2858534#M102484</link>
      <description>&lt;P&gt;Has anyone been able to find a way to get this working. I am having the same issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jul 2021 10:33:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2858534#M102484</guid>
      <dc:creator>jrodriguez007</dc:creator>
      <dc:date>2021-07-21T10:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2858599#M102485</link>
      <description>&lt;P&gt;jrodriguez00,&lt;/P&gt;&lt;P&gt;Not sure what OP did, but I opened SR 21235836807 and support has opened a PR with engineering.&lt;/P&gt;&lt;P&gt;Lars&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jul 2021 14:29:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2858599#M102485</guid>
      <dc:creator>larstr</dc:creator>
      <dc:date>2021-07-21T14:29:23Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2869249#M103485</link>
      <description>&lt;P&gt;It seems that the tag commands work fine on Windows Server 2019, but not on 2012R2.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Lars&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 08:02:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2869249#M103485</guid>
      <dc:creator>larstr</dc:creator>
      <dc:date>2021-09-29T08:02:43Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2870933#M103627</link>
      <description>&lt;P&gt;Hi, has anyone found a solution for this? We still have this problem by using PowerCLI&amp;nbsp;12.4.0.18633274 and Windows Server 2016. Thanks for any help&lt;/P&gt;</description>
      <pubDate>Fri, 08 Oct 2021 11:12:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2870933#M103627</guid>
      <dc:creator>thomku</dc:creator>
      <dc:date>2021-10-08T11:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2877647#M104110</link>
      <description>&lt;P&gt;Maybe this has something to do with the Powershell version.&lt;/P&gt;&lt;P&gt;On Server 2012R2 you get&lt;/P&gt;&lt;P&gt;&amp;gt; $PSVersionTable.PSVersion&lt;/P&gt;&lt;P&gt;Major Minor Build Revision&lt;BR /&gt;----- ----- ----- --------&lt;BR /&gt;5 0 10586 117&lt;/P&gt;&lt;P&gt;Windows 10 (1909):&amp;nbsp; 5 1 18362 1801&lt;/P&gt;&lt;P&gt;Windows 10 (21H1):&amp;nbsp; 5 1 19041 1320&lt;/P&gt;&lt;P&gt;Server 2019: 5 1 17763 2268&lt;/P&gt;&lt;P&gt;Linux ($ pwsh --version):&amp;nbsp;PowerShell 7.2.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Server 2012 R2 is out of date. I cannot test which version you have on Server 2016.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Nov 2021 07:49:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2877647#M104110</guid>
      <dc:creator>Renturem</dc:creator>
      <dc:date>2021-11-12T07:49:07Z</dc:date>
    </item>
    <item>
      <title>Re: get-tagassignment error after vcenter upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2877649#M104111</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;thanks for your reply. You're right, after I updated the Powershell version the script works again.&lt;/P&gt;&lt;P&gt;$PSVersionTable.PSVersion&lt;/P&gt;&lt;P&gt;Major Minor Build Revision&lt;BR /&gt;----- ----- ----- --------&lt;BR /&gt;5 1 14393 4583&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Nov 2021 08:05:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/get-tagassignment-error-after-vcenter-upgrade/m-p/2877649#M104111</guid>
      <dc:creator>thomku</dc:creator>
      <dc:date>2021-11-12T08:05:54Z</dc:date>
    </item>
  </channel>
</rss>

