-
Bug
-
Resolution: Fixed
-
Medium
-
3.1.4, 3.1.8, Mindville - Pre Bundled
-
None
-
2
-
Severity 3 - Minor
-
Issue Summary
Run a Discovery scan using the ESXI Patterns & valid credentials
Steps to Reproduce
- 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.