1 2 Previous Next 17 Replies Latest reply on Feb 9, 2018 5:32 AM by LucD

    Get-Tag fails with Specified argument was out of the range of valid values

    chaston Novice

      We recently migrated our Windows/SQL vCenter 5.5 Update 3 to the VCSA 6.5. I connect with PowerCLI (updated to latest version from PowerShell Gallery, all other versions are uninstalled), when I run the command Get-Tag I get the following results:

      H:\> get-tag

      get-tag : 8/8/2017 8:54:54 PM   Get-Tag         Specified argument was out of the range of valid values.

      At line:1 char:1

      + get-tag

      + ~~~~~~~

          + CategoryInfo          : NotSpecified: (:) [Get-Tag], CisException

          + FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTag.Error,VMware.VimAutomation.

         ViCore.Cmdlets.Commands.Tagging.GetTag

       

      Even if I specify -Name and -Category I geta slightly different message:

      H:\> get-tag -Category Recovery -Name No-Recovery

      get-tag : 8/8/2017 8:55:42 PM   Get-Tag         Value cannot be null.

      Parameter name: collection

      At line:1 char:1

      + get-tag -Category Recovery -Name No-Recovery

      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

          + CategoryInfo          : NotSpecified: (:) [Get-Tag], VimException

          + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTag

       

      PowerShell version is current as well:

      H:\> $PSVersionTable

      Name                           Value

      ----                           -----

      PSVersion                      5.1.14393.1198

       

      I can run the get-tag against my primary site's vCenter which is still a Windows/SQL install. Anyone else seeing this seemingly 'bug' with a migration?

       

      We are planning to migrate the primary site in the next month. Any assistance would be greatly appreciated!

        • 1. Re: Get-Tag fails with Specified argument was out of the range of valid values
          LucD Guru
          User ModeratorsCommunity WarriorsvExpert

          No, haven't seen that one before.

           

          Is Get-TagCategory also showing errors?

          Is that an embedded VCSA?

          Is the Inventory service running ok (without warnings)?

          Are the tags visible in the Web Client?

          Does the error appear everytime, even after a restart of the VCSA?

          • 2. Re: Get-Tag fails with Specified argument was out of the range of valid values
            stephan87 Novice

            We have the same issue. Migrating windows vcenter 6.0 u1 to vcsa 6.5u1. Now some cmdlets did not work. Get-VM works, Get-Tag did not work

            Tags are visible in webclient. Restart of vcsa did not solve the problem (with embedded psc). Tried it also with administrator@vsphere.local

            I have opened now a SR.

             

            Get-PowerCLIVersion

            PowerCLI Version

            ----------------

               VMware PowerCLI 6.5.1 build 5377412

            ---------------

            Component Versions

            ---------------

               VMware Cis Core PowerCLI Component 6.5 build 6230110

               VMware VimAutomation Core PowerCLI Component 6.5 build 6234650

               VMware Storage PowerCLI Component 6.5 build 5374001

             

            Get-Tag -Name "2012"

            Get-Tag : 8/14/2017 1:08:09 PM    Get-Tag        com.vmware.vapi.std.errors.unauthenticated {'messages': [com.vmware.vapi.std.localizable_message {'id': vapi.method.authentication.required, 'default_message': This method requires authentication., 'args':

            []}], 'data':}  

            At line:1 char:1

            + Get-Tag -Name "2012"

            + ~~~~~~~~~~~~~~~~~~~~

                + CategoryInfo          : NotSpecified: (:) [Get-Tag], CisException

                + FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTag.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTag

             

            Get-Tag : 8/14/2017 1:08:09 PM    Get-Tag        Tag with name '2012' was not found using the specified filter(s).  

            At line:1 char:1

            + Get-Tag -Name "2012"

            + ~~~~~~~~~~~~~~~~~~~~

                + CategoryInfo          : ObjectNotFound: (:) [Get-Tag], VimException

                + FullyQualifiedErrorId : Core_OutputHelper_WriteNotFoundError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTag

             

             

             

            Get-TagCategory

            Get-TagCategory : 8/14/2017 1:10:56 PM    Get-TagCategory        com.vmware.vapi.std.errors.unauthenticated {'messages': [com.vmware.vapi.std.localizable_message {'id': vapi.method.authentication.required, 'default_message': This method requires

            authentication., 'args': []}], 'data':}  

            At line:1 char:1

            + Get-TagCategory

            + ~~~~~~~~~~~~~~~

                + CategoryInfo          : NotSpecified: (:) [Get-TagCategory], CisException

                + FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetCategory.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTagCategory

            • 3. Re: Get-Tag fails with Specified argument was out of the range of valid values
              stephan87 Novice

              If I use the fqdn with connect-viserver it works fine. Found similar problems in Re: Does Get-Tag work on vcsa 6.5?

              • 4. Re: Get-Tag fails with Specified argument was out of the range of valid values
                LucD Guru
                vExpertCommunity WarriorsUser Moderators

                I suggest you add yourself on that thread you referred to.you alread

                 

                Did you already try with the latest PowerCLI 6.5.2?

                • 5. Re: Get-Tag fails with Specified argument was out of the range of valid values
                  stephan87 Novice

                  I tried to update it with "Update-Module -Name VMware.PowerCLI". Get-PowerCLIVersion still reports 6.5.1

                  But I have the following new folder:

                  C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCLI\6.5.2.6268016

                   

                  And in C:\Program Files\WindowsPowerShell\Modules\:

                   

                  PS V:\> ls 'C:\Program Files\WindowsPowerShell\Modules'

                   

                      Directory: C:\Program Files\WindowsPowerShell\Modules

                   

                  Mode                LastWriteTime         Length Name

                  ----                -------------         ------ ----

                  d---s-        5/11/2016   1:11 PM                PackageManagement

                  d---s-        5/11/2016   1:11 PM                PowerShellGet

                  d-----        8/10/2017   1:03 PM                VMware.DeployAutomation

                  d-----        8/10/2017   1:03 PM                VMware.ImageBuilder

                  d-----        8/10/2017   1:03 PM                VMware.PowerCLI

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.Cis.Core

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.Cloud

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.Common

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.Core

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.HA

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.HorizonView

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.License

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.PCloud

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.Sdk

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.Srm

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.Storage

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.StorageUtility

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.Vds

                  d-----        8/10/2017   1:03 PM                VMware.VimAutomation.vROps

                  d-----        8/10/2017   1:03 PM                VMware.VumAutomation

                   

                  Get-PowerCLIVersion

                  PowerCLI Version

                  ----------------

                     VMware PowerCLI 6.5.1 build 5377412

                  ---------------

                  Component Versions

                  ---------------

                     VMware Cis Core PowerCLI Component 6.5 build 6230110

                     VMware VimAutomation Core PowerCLI Component 6.5 build 6234650

                   

                   

                   

                  Same problem with get-tagassignment using FQDN or IP makes no difference. PowerCLI 6.5.1

                   

                  Get-TagAssignment -Entity <VM Name>

                  Get-TagAssignment : 8/14/2017 2:35:55 PM    Get-TagAssignment        Specified argument was out of the range of valid

                  values.

                  At line:1 char:1

                  + Get-TagAssignment -Entity <VM Name>

                  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

                      + CategoryInfo          : NotSpecified: (:) [Get-TagAssignment], CisException

                      + FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTagAssi

                     gnment.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTagAssignment

                  • 6. Re: Get-Tag fails with Specified argument was out of the range of valid values
                    LucD Guru
                    vExpertCommunity WarriorsUser Moderators

                    6.5.2 was minor update, only a couple of modules changed their version.

                    Do a

                    Get-Module -Name VMware* -ListAvailable

                    • 7. Re: Get-Tag fails with Specified argument was out of the range of valid values
                      stephan87 Novice

                      Ok. Seems that some module have the new version:

                       

                      PS V:\> Get-Module -Name VMware* -ListAvailable

                       

                       

                       

                       

                          Directory: C:\Program Files\WindowsPowerShell\Modules

                       

                       

                       

                       

                      ModuleType Version    Name                                ExportedCommands

                      ---------- -------    ----                                ----------------

                      Binary     6.5.1.5... VMware.DeployAutomation             {Add-DeployRule, Add-ProxyServer, Add-ScriptBundle, Copy-D...

                      Binary     6.5.1.5... VMware.ImageBuilder                 {Add-EsxSoftwareDepot, Add-EsxSoftwarePackage, Compare-Esx...

                      Manifest   6.5.2.6... VMware.PowerCLI

                      Binary     6.5.2.6... VMware.VimAutomation.Cis.Core       {Connect-CisServer, Disconnect-CisServer, Get-CisService}

                      Binary     6.5.1.5... VMware.VimAutomation.Cloud          {Add-CIDatastore, Connect-CIServer, Disconnect-CIServer, G...

                      Manifest   6.5.1.5... VMware.VimAutomation.Common

                      Binary     6.5.2.6... VMware.VimAutomation.Core           {Add-PassthroughDevice, Add-VirtualSwitchPhysicalNetworkAd...

                      Binary     6.0.0.5... VMware.VimAutomation.HA             Get-DrmInfo

                      Binary     7.1.0.5... VMware.VimAutomation.HorizonView    {Connect-HVServer, Disconnect-HVServer}

                      Binary     6.5.1.5... VMware.VimAutomation.License        Get-LicenseDataManager

                      Binary     6.5.1.5... VMware.VimAutomation.PCloud         {Connect-PIServer, Disconnect-PIServer, Get-PIComputeInsta...

                      Manifest   1.0.0.5... VMware.VimAutomation.Sdk            {Get-PSVersion, Get-InstallPath}

                      Binary     6.5.1.5... VMware.VimAutomation.Srm            {Connect-SrmServer, Disconnect-SrmServer}

                      Binary     6.5.1.5... VMware.VimAutomation.Storage        {Copy-VDisk, Export-SpbmStoragePolicy, Get-NfsUser, Get-Sp...

                      Script     1.0        VMware.VimAutomation.StorageUtility Update-VmfsDatastore

                      Binary     6.5.1.5... VMware.VimAutomation.Vds            {Add-VDSwitchPhysicalNetworkAdapter, Add-VDSwitchVMHost, E...

                      Binary     6.5.1.5... VMware.VimAutomation.vROps          {Connect-OMServer, Disconnect-OMServer, Get-OMAlert, Get-O...

                      Binary     6.5.1.5... VMware.VumAutomation                {Add-EntityBaseline, Copy-Patch, Get-Baseline, Get-Complia...

                      • 8. Re: Get-Tag fails with Specified argument was out of the range of valid values
                        stephan87 Novice

                        - SR number: 17538756108

                        - vCenter logs uploaded to SR

                        - fqdn or ip address plays no role with latest powercli version.

                         

                        Get-TagAssignment

                        Get-TagAssignment : 8/15/2017 3:58:19 PM    Get-TagAssignment        com.vmware.vapi.std.errors.internal_server_error {'messages': [com.vmware.vapi.std.localizable_message {'id': vapi.bindings.method.impl.unexpected, 'default_message': Provider method

                        implementation threw unexpected exception: Read timed out, 'args': [Read timed out]}], 'data':}   

                        At line:1 char:1

                        + Get-TagAssignment

                        + ~~~~~~~~~~~~~~~~~

                            + CategoryInfo          : NotSpecified: (:) [Get-TagAssignment], CisException

                            + FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTagAssignment.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTagAssignment

                         

                        At the same time i see the following errors on the vcsa:

                         

                        tail -f /storage/log/vmware/vsphere-client/logs/vsphere_client_virgo.log

                        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)

                        at com.vmware.vapi.internal.protocol.client.rpc.http.HttpClient.invoke(HttpClient.java:147)

                        at com.vmware.vapi.internal.protocol.client.rpc.http.HttpClient.send(HttpClient.java:166)

                        ... 73 common frames omitted

                         

                        [2017-08-15T13:52:55.561Z] [INFO ] http-bio-9090-exec-1330      70045861 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:52:59.218Z] [INFO ] http-bio-9090-exec-1330 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:52:59.613Z] [INFO ] http-bio-9090-exec-1330      70045863 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint ds-core-amf received request.

                        [2017-08-15T13:53:03.085Z] [INFO ] http-bio-9090-exec-1330      70045864 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint ds-core-amf received request.

                        [2017-08-15T13:53:03.213Z] [INFO ] http-bio-9090-exec-1330      70045865 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint ds-core-amf received request.

                        [2017-08-15T13:53:12.070Z] [INFO ] http-bio-9090-exec-1330      70045866 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint ds-core-amf received request.

                        [2017-08-15T13:53:13.619Z] [INFO ] health-status-61 com.vmware.vise.vim.cm.healthstatus.AppServerHealthService Memory usage: used=595,754,088; max=1,116,733,440; percentage=53.34792231170225%. Status: GREEN

                        [2017-08-15T13:53:13.619Z] [INFO ] health-status-61 c.v.v.v.cm.HealthStatusRequestHandler$HealthStatusCollectorTask Determined health status 'GREEN' in 0 ms

                        [2017-08-15T13:53:14.208Z] [INFO ] http-bio-9090-exec-1330      70045867 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:53:14.212Z] [INFO ] http-bio-9090-exec-1320 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:53:15.007Z] [INFO ] http-bio-9090-exec-1331      70045869 101013 200485 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:53:19.750Z] [INFO ] http-bio-9090-exec-1320      70045870 101107 200508 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint ds-core-amf received request.

                        [2017-08-15T13:53:22.265Z] [INFO ] http-bio-9090-exec-1320      70045871 101107 200508 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:53:24.255Z] [INFO ] http-bio-9090-exec-1326 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:53:29.282Z] [INFO ] http-bio-9090-exec-1326      70045873 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:53:30.907Z] [INFO ] http-bio-9090-exec-1326      70045874 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint ds-core-amf received request.

                        [2017-08-15T13:53:31.313Z] [INFO ] http-bio-9090-exec-1326      70045875 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint ds-core-amf received request.

                        [2017-08-15T13:53:32.275Z] [INFO ] http-bio-9090-exec-1326      70045876 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint ds-core-amf received request.

                        [2017-08-15T13:53:37.329Z] [INFO ] http-bio-9090-exec-1320 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:53:37.803Z] [INFO ] http-bio-9090-exec-1326      70045878 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint ds-core-amf received request.

                        [2017-08-15T13:53:37.983Z] [INFO ] http-bio-9090-exec-1326      70045879 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:53:39.121Z] [INFO ] http-bio-9090-exec-1331 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        [2017-08-15T13:53:44.031Z] [WARN ] http-bio-9090-exec-1328 com.vmware.vapi.provider.local.LocalProvider Implementation method reported unexpected exception: com.vmware.vapi.client.exception.ConnectionException com.vmware.vapi.client.exception.ConnectionException: Read timed out

                        at java.lang.Thread.getStackTrace(Thread.java:1559)

                        at com.vmware.vapi.bindings.client.AsyncCallbackSyncAdapter.get_aroundBody1$advice(AsyncCallbackSyncAdapter.java:49)

                        at com.vmware.vapi.bindings.client.AsyncCallbackSyncAdapter.get(AsyncCallbackSyncAdapter.java:1)

                        at com.vmware.vapi.internal.bindings.Stub.invokeMethod(Stub.java:126)

                        at com.vmware.cis.tagging.BatchStub.listAllAttachedObjectsOnTags(BatchStub.java:329)

                        at com.vmware.cis.tagging.BatchStub.listAllAttachedObjectsOnTags(BatchStub.java:322)

                        at com.vmware.cis.data.internal.adapters.tagging.TaggingFacadeImpl.listAllAttachedObjectsOnTags(TaggingFacadeImpl.java:188)

                        at com.vmware.cis.data.internal.adapters.tagging.TaggingFacadePerfLogging.listAllAttachedObjectsOnTags(TaggingFacadePerfLogging.java:171)

                        at com.vmware.cis.data.internal.adapters.tagging.TagAssociationDataProviderConnection.collectAllAssociations(TagAssociationDataProviderConnection.java:171)

                        at com.vmware.cis.data.internal.adapters.tagging.TagAssociationDataProviderConnection.collectAssociationsFor(TagAssociationDataProviderConnection.java:141)

                        at com.vmware.cis.data.internal.adapters.tagging.TagAssociationDataProviderConnection.executeQuery(TagAssociationDataProviderConnection.java:84)

                               at com.vmware.cis.data.internal.provider.profiler.OperationThresholdDataProvider.executeQuery(OperationThresholdDataProvider.java:38)

                        at com.vmware.cis.data.internal.adapters.federation.FederationConnection$1.call(FederationConnection.java:179)

                        at com.vmware.cis.data.internal.adapters.federation.FederationConnection$1.call(FederationConnection.java:170)

                        at com.vmware.cis.data.internal.util.TaskExecutor.executeDirectly(TaskExecutor.java:184)

                        at com.vmware.cis.data.internal.util.TaskExecutor.submitForExecution(TaskExecutor.java:154)

                        at com.vmware.cis.data.internal.util.TaskExecutor.invokeTasks(TaskExecutor.java:99)

                        at com.vmware.cis.data.internal.adapters.federation.FederationConnection.executeQueryWithSelectedSortProps(FederationConnection.java:150)

                        at com.vmware.cis.data.internal.adapters.federation.FederationConnection.executeQuery(FederationConnection.java:117)

                        at com.vmware.cis.data.internal.provider.QueryExecutor.executeQuery(QueryExecutor.java:95)

                        at com.vmware.cis.data.internal.provider.QueryDispatcher.executeQuery(QueryDispatcher.java:123)

                        at com.vmware.cis.data.internal.provider.QueryQualifyingConnection.executeQuery(QueryQualifyingConnection.java:45)

                        at com.vmware.cis.data.api.QueryService.executeQuery(QueryService.java:93)

                        at com.vmware.cis.data.service.impl.ResourceModelProviderImpl.query(ResourceModelProviderImpl.java:66)

                        at com.vmware.cis.data.ResourceModelSyncApiInterface$QueryApiMethod.doInvoke(ResourceModelSyncApiInterface.java:42)

                        at com.vmware.vapi.internal.bindings.ApiMethodSkeleton.invoke(ApiMethodSkeleton.java:175)

                        at com.vmware.vapi.provider.ApiMethodBasedApiInterface.invoke(ApiMethodBasedApiInterface.java:82)

                        at com.vmware.cis.data.legacysvc.adapter.PackageAdapterApiInterface.invoke(PackageAdapterApiInterface.java:90)

                        at com.vmware.vapi.provider.local.LocalProvider.invokeMethodInt(LocalProvider.java:471)

                        at com.vmware.vapi.provider.local.LocalProvider.invoke(LocalProvider.java:290)

                        at com.vmware.vapi.provider.introspection.ErrorAugmentingFilter.invoke(ErrorAugmentingFilter.java:74)

                        at com.vmware.vapi.security.AuthenticationFilter$1.setResult(AuthenticationFilter.java:180)

                        at com.vmware.vapi.security.AuthenticationFilter$1.setResult(AuthenticationFilter.java:166)

                        at com.vmware.cis.data.service.session.SessionAuthenticationHandler.authenticate(SessionAuthenticationHandler.java:39)

                        at com.vmware.vapi.security.AuthenticationFilter.invoke(AuthenticationFilter.java:165)

                        at com.vmware.vapi.provider.aggregator.ProviderAggregation.invokeMethodImpl(ProviderAggregation.java:244)

                        at com.vmware.vapi.provider.aggregator.ProviderAggregation.invoke(ProviderAggregation.java:269)

                        at com.vmware.vapi.internal.provider.introspection.IntrospectionFilter.invoke(IntrospectionFilter.java:70)

                        at com.vmware.vapi.provider.aggregator.ApiAggregator.invoke(ApiAggregator.java:101)

                        at com.vmware.vapi.protocol.server.msg.json.JsonServerConnection.processApiRequest(JsonServerConnection.java:275)

                        at com.vmware.vapi.protocol.server.msg.json.JsonServerConnection.requestReceived(JsonServerConnection.java:200)

                        at com.vmware.vapi.protocol.server.rpc.http.impl.HttpStreamingServlet.doPostImpl(HttpStreamingServlet.java:124)

                        at com.vmware.vapi.protocol.server.rpc.http.impl.HttpStreamingServlet.doPost(HttpStreamingServlet.java:92)

                        at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)

                        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

                        at com.vmware.cis.data.legacysvc.http.HttpServletAdapter.service(HttpServletAdapter.java:37)

                        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

                        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)

                        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

                        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

                        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

                        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

                        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)

                        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

                        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)

                        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)

                        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)

                        at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:683)

                        at org.eclipse.virgo.web.tomcat.support.ApplicationNameTrackingValve.invoke(ApplicationNameTrackingValve.java:33)

                        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)

                        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)

                        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)

                        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)

                        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)

                        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)

                        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

                        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

                        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

                        at java.lang.Thread.run(Thread.java:748)

                        Caused by: com.vmware.vapi.client.exception.ConnectionException: Read timed out

                        at com.vmware.vapi.internal.protocol.client.rpc.http.HttpClient.send(HttpClient.java:185)

                        at com.vmware.vapi.internal.protocol.client.msg.json.JsonApiProvider.sendRequest(JsonApiProvider.java:126)

                        at com.vmware.vapi.internal.protocol.client.msg.json.JsonApiProvider.invoke(JsonApiProvider.java:307)

                        at com.vmware.cis.data.internal.adapters.util.vapi.VapiInvokeCommand.execute(VapiInvokeCommand.java:44)

                        at com.vmware.cis.data.internal.adapters.util.vapi.SessionAwareApiProvider.invoke(SessionAwareApiProvider.java:60)

                        at com.vmware.vapi.internal.bindings.Stub.invoke(Stub.java:205)

                        at com.vmware.vapi.internal.bindings.Stub.invoke(Stub.java:186)

                        at com.vmware.vapi.internal.bindings.Stub.invokeMethodAsync(Stub.java:150)

                        at com.vmware.vapi.internal.bindings.Stub.invokeMethod(Stub.java:118)

                        ... 65 common frames omitted

                        Caused by: java.net.SocketTimeoutException: Read timed out

                        at java.net.SocketInputStream.socketRead0(Native Method)

                        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)

                        at java.net.SocketInputStream.read(SocketInputStream.java:171)

                        at java.net.SocketInputStream.read(SocketInputStream.java:141)

                        at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)

                        at sun.security.ssl.InputRecord.read(InputRecord.java:503)

                        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)

                        at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930)

                        at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)

                        at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:136)

                        at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:152)

                        at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:270)

                        at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140)

                        at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57)

                        at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:260)

                        at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:161)

                        at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)

                        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                        at java.lang.reflect.Method.invoke(Method.java:498)

                        at org.apache.http.impl.conn.CPoolProxy.invoke(CPoolProxy.java:138)

                        at com.sun.proxy.$Proxy160.receiveResponseHeader(Unknown Source)

                        at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:271)

                        at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)

                        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:254)

                        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)

                        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)

                        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)

                        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)

                        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)

                        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)

                        at com.vmware.vapi.internal.protocol.client.rpc.http.HttpClient.invoke(HttpClient.java:147)

                        at com.vmware.vapi.internal.protocol.client.rpc.http.HttpClient.send(HttpClient.java:166)

                        ... 73 common frames omitted

                         

                        [2017-08-15T13:53:45.831Z] [INFO ] http-bio-9090-exec-1326      70045881 101115 200509 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.

                        • 9. Re: Get-Tag fails with Specified argument was out of the range of valid values
                          chaston Novice

                          Is Get-TagCategory also showing errors? Yes, all tag cmdlets are showing errors...see output below.

                          Is that an embedded VCSA? The PSC is separate from the VCSA

                          Is the Inventory service running ok (without warnings)? Wasn't this service deprecated or renamed? Can't find it in the list of services.

                          Are the tags visible in the Web Client? The tags are present in the Web client and we can manage them in the web client

                          Does the error appear everytime, even after a restart of the VCSA? It happens everytime with all tag commands, even after a restart.

                           

                          To add some further information, a coworker of mine is capable to use the commands and he has installed PowerCLI from the executable and not from the PowerShell Gallery, coincidence or no?

                          • 10. Re: Get-Tag fails with Specified argument was out of the range of valid values
                            stephan87 Novice

                            VMware BCS Support has confirmed this issue and tries to find a solution.

                            1 person found this helpful
                            • 11. Re: Get-Tag fails with Specified argument was out of the range of valid values
                              stephan87 Novice

                              Hi,

                               

                              please check the following folder for files and delete them: C:\ProgramData\VMware\PowerCLI\Usage

                               

                              I had some session and usage files there. And it seems that everytime you do a connect-viserver these session files are used. After deleting them I was able to use "get-tag" and "get-vm -tag <vmname>".

                              So the only things what did not work is "get-tagassignment" if you have a lot of vms and tags

                              Get-TagAssignment

                              Get-TagAssignment : 9/11/2017 12:38:37 PM       Get-TagAssignment               com.vmware.vapi.std.errors.internal_serv

                              er_error

                              {'messages': [com.vmware.vapi.std.localizable_message {'id': vapi.bindings.method.impl.unexpected, 'default_message':

                              Provider method implementation threw unexpected exception: Read timed out, 'args': [Read timed out]}], 'data':}

                              At line:1 char:1

                              + Get-TagAssignment

                              + ~~~~~~~~~~~~~~~~~

                                  + CategoryInfo          : NotSpecified: (:) [Get-TagAssignment], CisException

                                  + FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTagAssi

                                 gnment.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTagAssignment

                               

                              If I run this on one vm it works:

                              Get-TagAssignment -Entity <vmname>

                               

                              I will inform BCS about this.

                               

                              Regards,

                              Stephan

                              • 12. Re: Get-Tag fails with Specified argument was out of the range of valid values
                                chaston Novice

                                stephan87,

                                 

                                I did not have the usage folder but I renamed the PowerCLI_Settings.xml to PowerCLI_Settings.xml.orig and then restarted PowerShell and loaded PowerCLI. I can now do the get-tag in both of my VCSA's running 6.5. Nice find!!

                                • 13. Re: Get-Tag fails with Specified argument was out of the range of valid values
                                  stephan87 Novice

                                  Ok. At the same time I had replaced PowerCLI_Settings.xml with another one from another server where it works. So I was not 100% sure if the session files were the problems. Thanks for that information.

                                  • 14. Re: Get-Tag fails with Specified argument was out of the range of valid values
                                    chaston Novice

                                    I do have the same issues as you stated with get-tagassignment on my production datacenter that has many tags.

                                    1 2 Previous Next