Gotchas for upgrading SolarWinds NTA

Supported Version: SolarWinds NetFlow Traffic Analyzer (NTA) 4.2.3 and earlier.

  • When upgrading to NTA 4.2.3, if you added a site binding to a hostname before you upgrade, you must bind the Orion Web Console to a fully qualified domain name (FQDN). See this article.
  • When upgrading to NTA 4.2.3 with custom menus, you can not see the Performance Dashboard link in the menu. For details, see this article.
  • After NTA 4.2.2, future releases will no longer support Windows OS 2008 and 2008 R2 and Microsoft SQL Server 2008 R2. SolarWinds recommends that you upgrade to Windows Server 2012, 2012 R2, or 2016 at your earliest convenience. For more information, see Deprecation notices.
  • If you have edited resource properties, the All Groups resource may be empty after upgrading to NTA 4.2.
  • When upgrading to NTA 4.2, using the group by feature for custom properties may return no results, and the data loading may hang or not complete. All regular functionality is unaffected by the issue.

General Orion Platform gotchas

  • Orion Platform 2018.4 products are no longer compatible with Windows Server 2012 and 2012 R2.
  • Orion Platform 2018.4 products are no longer compatible with any version of SQL Server 2012.
  • If you wrote your own code, by changing SolarWinds .css files or adding .js files, or were directed to make changes by SolarWinds Support, the code may be overwritten during the upgrade. See Upgrading if you have custom code.
  • Always check that you have enough hard drive space for zipped and unzipped installers. One unzipped installer can consume several GBs of space.
  • During your upgrade, use the Scalability Engine Installer. If you use downloaded installers or the installer bundle, you must install one product and version at a time. The versions must match between the main and additional polling engines or you will receive a Database Configuration Failure Error.
  • If upgrading from a very early or End of Life SolarWinds product version, you may want to install a new product instead of performing an upgrade or migrating data. SolarWinds Support can provide the best advice for these upgrade scenarios.
  • If you enabled SolarWinds High Availability, you must disable High Availability before you can upgrade. You must have the same versions of SolarWinds products on your primary and secondary servers before you can re-enable your HA pools. See Upgrade with HA.