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

            Hi Yinon,

             

            I have upgraded the version to 3.1.4 but still im getting the same error. 

             

            Error executing command.

            11/4/2023 4:08:10 PM : Exceptions:

            11/4/2023 4:08:10 PM : 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:\build\DISCOVERY-DISCOVERYCLOUDRELEASE-BUILD\ProviderClasses\VIMProvider.cs:line 99

            11/4/2023 4:08:10 PM : 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.

             

            11/4/2023 4:08:11 PM : Command:

                  HostSystem

               

            11/4/2023 4:08:11 PM : Result:

            11/4/2023 4:08:11 PM : pattern executed in 41.2835367 seconds

            Ravilal Gunaratne added a comment - Hi Yinon,   I have upgraded the version to 3.1.4 but still im getting the same error.    Error executing command. 11/4/2023 4:08:10 PM : Exceptions: 11/4/2023 4:08:10 PM : 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:\build\DISCOVERY-DISCOVERYCLOUDRELEASE-BUILD\ProviderClasses\VIMProvider.cs:line 99 11/4/2023 4:08:10 PM : 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.   11/4/2023 4:08:11 PM : Command:       HostSystem     11/4/2023 4:08:11 PM : Result: 11/4/2023 4:08:11 PM : pattern executed in 41.2835367 seconds

            Improvements were added in Discovery 3.1.4 and will be added to the next release as well.

            Yinon Negev added a comment - Improvements were added in Discovery 3.1.4 and will be added to the next release as well.

            0d9c6570097f 
            Apologies for the delay in responding.

            We have added some improvements from our end in our recent release - v.3.1.4 and will add one more fix for an edge case; where the Hosting System does not have any VMs on it - to be released in our next Discovery Release.

            If you are still experiencing this issue - once the next release is out, and you've upgraded to the latest version, please create a new ticket with us - and reference this bug.

            In the meantime, we'll proceed to close this report.

            Yinon Negev added a comment - 0d9c6570097f   Apologies for the delay in responding. We have added some improvements from our end in our recent release - v.3.1.4 and will add one more fix for an edge case; where the Hosting System does not have any VMs on it - to be released in our next Discovery Release. If you are still experiencing this issue - once the next release is out, and you've upgraded to the latest version, please create a new ticke t with us - and reference this bug. In the meantime, we'll proceed to close this report.

            Any update receive from VMware ?

            Ravilal Gunaratne added a comment - Any update receive from VMware ?

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

                Created:
                Updated:
                Resolved: