Network Management
Discovery: An error while processing the results has occurred. See discovery log for more details
Discovery: An error while processing the results has occurred. See discovery log for more details
First published date
10/26/2018 7:34 PM
Last published date
7/20/2022 7:00 PM
Overview
The following error occurs during Manual Network Discovery after an upgrade from NPM
An error while processing the results has occurred.
See discovery log for more details.
Product section
Network Performance Monitor
Cause
There are missing XML sections in the web.config file after the upgrade.
Resolution
Check that these 2 XML sections were included in the web.config file after an upgrade.
1. Find the web.config file. By default, it is in c:\inetpub\SolarWinds.
2. Open the web.config file using a text file editor and check that these 2 XML sections are in the file.
<extensions>
<bindingelementextensions>
<add name="gzipMessageEncoding" type="SolarWinds.Orion.Core.Common.Bindings.GZipMessageEncodingElement, SolarWinds.Orion.Core.Common">
</add></bindingelementextensions>
</extensions>
<binding name="Core.NetTcpStreamedBinding" sendtimeout="00:20:00" receivetimeout="00:20:00">
<gzipmessageencoding innermessageencoding="binaryMessageEncoding">
<transactionflow>
<security authenticationmode="SecureConversation" requiresecuritycontextcancellation="false">
<secureconversationbootstrap authenticationmode="UserNameOverTransport">
</secureconversationbootstrap>
</security>
<sslstreamsecurity requireclientcertificate="false">
<tcptransport maxreceivedmessagesize="2147483647" portsharingenabled="true" maxbuffersize="2147483647" transfermode="Streamed">
</tcptransport></sslstreamsecurity> </transactionflow> </gzipmessageencoding></binding>
3. If these 2 sections are not in the file, add them accordingly.
4. If the mentioned XML files are in the web.config, ensure that the client is not using proxy settings.
5. Try to use a different browser. If you don't encounter any error while running the job discovery, try clearing the browsing history, cache, and cookies in the problematic browser.
6. Re-run the discovery job.
1. Find the web.config file. By default, it is in c:\inetpub\SolarWinds.
2. Open the web.config file using a text file editor and check that these 2 XML sections are in the file.
<extensions>
<bindingelementextensions>
<add name="gzipMessageEncoding" type="SolarWinds.Orion.Core.Common.Bindings.GZipMessageEncodingElement, SolarWinds.Orion.Core.Common">
</add></bindingelementextensions>
</extensions>
<binding name="Core.NetTcpStreamedBinding" sendtimeout="00:20:00" receivetimeout="00:20:00">
<gzipmessageencoding innermessageencoding="binaryMessageEncoding">
<transactionflow>
<security authenticationmode="SecureConversation" requiresecuritycontextcancellation="false">
<secureconversationbootstrap authenticationmode="UserNameOverTransport">
</secureconversationbootstrap>
</security>
<sslstreamsecurity requireclientcertificate="false">
<tcptransport maxreceivedmessagesize="2147483647" portsharingenabled="true" maxbuffersize="2147483647" transfermode="Streamed">
</tcptransport></sslstreamsecurity> </transactionflow> </gzipmessageencoding></binding>
3. If these 2 sections are not in the file, add them accordingly.
4. If the mentioned XML files are in the web.config, ensure that the client is not using proxy settings.
5. Try to use a different browser. If you don't encounter any error while running the job discovery, try clearing the browsing history, cache, and cookies in the problematic browser.
6. Re-run the discovery job.