Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-8667

Discovery Tool scan generates an Error when executing an ESXI pattern

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • Discovery 3.1.11
    • 3.1.4, 3.1.8, Mindville - Pre Bundled
    • Assets Discovery
    • None

      Issue Summary

      Run a Discovery scan using the ESXI Patterns & valid credentials

      Steps to Reproduce

      1. No specific steps - run a Discovery Scan for ESXI Hosts

      Expected Results

      Scan completes successfully, no errors and all VMs are scanned and saved

      Actual Results

      The below exception is thrown in the discovery.log file:

      18/5/2021 10:30:27 AM : Using pattern: ESXi_HostSystems.pat (v1.3.4) 18/5/2021 10:30:52 AM : Error executing command. 18/5/2021 10:30:52 AM : Exceptions: 18/5/2021 10:30:52 AM : The maximum message size quota for incoming messages (1073741824) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. Server stack trace: at System.ServiceModel.Channels.MessageEncoder.BufferMessageStream(Stream stream, BufferManager bufferManager, Int32 maxBufferSize) at System.ServiceModel.Channels.MessageEncoder.ReadMessage(Stream stream, BufferManager bufferManager, Int32 maxBufferSize, String contentType) at System.ServiceModel.Channels.HttpInput.ReadChunkedBufferedMessage(Stream inputStream) at System.ServiceModel.Channels.HttpInput.ParseIncomingMessage(HttpRequestMessage httpRequestMessage, Exception& requestException) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at VimApi_67.VimPortType.RetrieveProperties(RetrievePropertiesRequest request) at VMware.Vim.PropertyCollector.RetrieveProperties(PropertyFilterSpec[] specSet) at VMware.Vim.VimClientImpl.GetViewsByMorefs(IEnumerable`1 moRefs, String[] properties) at VMware.Vim.VimClientImpl.FindEntityViews(Type viewType, ManagedObjectReference beginEntity, NameValueCollection filter, String[] properties) at Insight.Discovery.ProviderClasses.VIMProvider.ExecuteCommand(String command, Boolean useCache) in C:\SourceCode\discovery_repo\ProviderClasses\VIMProvider.cs:line 98 18/5/2021 10:30:52 AM : The maximum message size quota for incoming messages (1073741824) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. 18/5/2021 10:30:53 AM : Command: HostSystem
       
      

      Workaround

      Note:
      The ServiceModel is a library used by VMWare's VIM Client that Discovery uses.

      We are not in control of that dependency.

      We will try to raise this issue with VMWare, but logging it here for followup reasons.

          Form Name

            [JSDSERVER-8667] Discovery Tool scan generates an Error when executing an ESXI pattern

            Zakhar Listiev made changes -
            Assignee Original: vgedzhev [ 8a797fe2b442 ] New: Volodymyr Batrukh [ 56f064e7d59c ]
            Zakhar Listiev made changes -
            Fix Version/s New: Discovery 3.1.11 [ 105714 ]
            Zakhar Listiev made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Short Term Backlog [ 12074 ] New: Closed [ 6 ]
            Bartosz Ornatowski made changes -
            Priority Original: Low [ 4 ] New: Medium [ 3 ]
            Zakhar Listiev made changes -
            Status Original: Needs Triage [ 10030 ] New: Short Term Backlog [ 12074 ]
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            Pablo Bartolome made changes -
            Fix Version/s Original: 3.1.8 [ 61995 ]
            Pablo Bartolome made changes -
            Description Original: h3. Issue Summary

            Run a Discovery (2.27.1 and 3.0.4) scan using the ESXI Patterns & valid credentials
            h3. Steps to Reproduce
             # No specific steps - run a Discovery Scan for ESXI Hosts

            h3. Expected Results

            Scan completes successfully, no errors and all VMs are scanned and saved
            h3. Actual Results

            The below exception is thrown in the discovery.log file:
            {code}
            18/5/2021 10:30:27 AM : Using pattern: ESXi_HostSystems.pat (v1.3.4) 18/5/2021 10:30:52 AM : Error executing command. 18/5/2021 10:30:52 AM : Exceptions: 18/5/2021 10:30:52 AM : The maximum message size quota for incoming messages (1073741824) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. Server stack trace: at System.ServiceModel.Channels.MessageEncoder.BufferMessageStream(Stream stream, BufferManager bufferManager, Int32 maxBufferSize) at System.ServiceModel.Channels.MessageEncoder.ReadMessage(Stream stream, BufferManager bufferManager, Int32 maxBufferSize, String contentType) at System.ServiceModel.Channels.HttpInput.ReadChunkedBufferedMessage(Stream inputStream) at System.ServiceModel.Channels.HttpInput.ParseIncomingMessage(HttpRequestMessage httpRequestMessage, Exception& requestException) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at VimApi_67.VimPortType.RetrieveProperties(RetrievePropertiesRequest request) at VMware.Vim.PropertyCollector.RetrieveProperties(PropertyFilterSpec[] specSet) at VMware.Vim.VimClientImpl.GetViewsByMorefs(IEnumerable`1 moRefs, String[] properties) at VMware.Vim.VimClientImpl.FindEntityViews(Type viewType, ManagedObjectReference beginEntity, NameValueCollection filter, String[] properties) at Insight.Discovery.ProviderClasses.VIMProvider.ExecuteCommand(String command, Boolean useCache) in C:\SourceCode\discovery_repo\ProviderClasses\VIMProvider.cs:line 98 18/5/2021 10:30:52 AM : The maximum message size quota for incoming messages (1073741824) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. 18/5/2021 10:30:53 AM : Command: HostSystem
             
            {code}
            h3. Workaround

            Note:

            The ServiceModel is a library used by VMWare's VIM Client that Discovery uses.

            We are not in control of that dependency.

            We will try to raise this issue with VMWare, but logging it here for followup reasons.
            New: h3. Issue Summary

            Run a Discovery scan using the ESXI Patterns & valid credentials

            h3. Steps to Reproduce
             # No specific steps - run a Discovery Scan for ESXI Hosts

            h3. Expected Results

            Scan completes successfully, no errors and all VMs are scanned and saved

            h3. Actual Results

            The below exception is thrown in the discovery.log file:
            {code}
            18/5/2021 10:30:27 AM : Using pattern: ESXi_HostSystems.pat (v1.3.4) 18/5/2021 10:30:52 AM : Error executing command. 18/5/2021 10:30:52 AM : Exceptions: 18/5/2021 10:30:52 AM : The maximum message size quota for incoming messages (1073741824) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. Server stack trace: at System.ServiceModel.Channels.MessageEncoder.BufferMessageStream(Stream stream, BufferManager bufferManager, Int32 maxBufferSize) at System.ServiceModel.Channels.MessageEncoder.ReadMessage(Stream stream, BufferManager bufferManager, Int32 maxBufferSize, String contentType) at System.ServiceModel.Channels.HttpInput.ReadChunkedBufferedMessage(Stream inputStream) at System.ServiceModel.Channels.HttpInput.ParseIncomingMessage(HttpRequestMessage httpRequestMessage, Exception& requestException) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at VimApi_67.VimPortType.RetrieveProperties(RetrievePropertiesRequest request) at VMware.Vim.PropertyCollector.RetrieveProperties(PropertyFilterSpec[] specSet) at VMware.Vim.VimClientImpl.GetViewsByMorefs(IEnumerable`1 moRefs, String[] properties) at VMware.Vim.VimClientImpl.FindEntityViews(Type viewType, ManagedObjectReference beginEntity, NameValueCollection filter, String[] properties) at Insight.Discovery.ProviderClasses.VIMProvider.ExecuteCommand(String command, Boolean useCache) in C:\SourceCode\discovery_repo\ProviderClasses\VIMProvider.cs:line 98 18/5/2021 10:30:52 AM : The maximum message size quota for incoming messages (1073741824) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. 18/5/2021 10:30:53 AM : Command: HostSystem
             
            {code}

            h3. Workaround

            Note:
            The ServiceModel is a library used by VMWare's VIM Client that Discovery uses.

            We are not in control of that dependency.

            We will try to raise this issue with VMWare, but logging it here for followup reasons.
            Pablo Bartolome made changes -
            Affects Version/s New: 3.1.4 [ 61510 ]
            Affects Version/s New: 3.1.8 [ 61995 ]
            Pablo Bartolome made changes -
            Resolution Original: Done [ 17 ]
            Status Original: Closed [ 6 ] New: Needs Triage [ 10030 ]

              56f064e7d59c Volodymyr Batrukh
              8cdc82c96fd5 Yinon Negev
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: