kacperm ✭✭✭✭✭

Your problem is caused by something different, fortunately it should be easy to solve. On the main server locate the installer exe file and run it. When the page with list of product appear - you can close it. Then you should be able to proceed with update. Technical note - that information (missing installer metadata) is…

I've never seen APE installer to fail like that too, interesting case. What you can check for now is: 1) Whether SolarWinds Administration service is up and running on the main server, if it is you can give him a reboot, 2) Check whether system clock on main server and APE are synced - if they show different time then…

Installer on mains server and APE needs to be in the same version to avoid any miscommunications. In case the one used on APE is in lower version - it should get auto-updated automatically, opposite scenario should trigger a big yellow message with option to redownload correct installer from the main server. If neither of…

That should not be a problem. It's just NAM would provide you unlimited number of "regular" APEs in this case, while SAM would offer unlimited number of "SAM only" APEs. In the end - if you have both licenses then probably it does not make sense to deploy those SAM-only APEs (all depends on the environment though).

Version 0.0.0.1 indicates that this is old Scalability Engine Installer. New unified installer is available and it would be marked as version 1.3.0.484. The best you could do is to download online installer for SRM from Customer Portal (check that this is 1.3 version, but it should be available by now), then run it on Main…

Actually - first version of Centralized Upgrade is available from 2018.2, and 2018.4 version should be able to properly upgrade automatically all scalability engines

If I understand correctly - upgrade and configuration passed and now you are stuck at this screen whenever you access Orion web console, right? Other thing that you could do is to check Orion DB, find table SWA_InstallationSession. There will be at least one row with field isActive set to true. Make it false, reboot…

So I found that Configuration Wizard was not able to properly finish its job, because OpenJDK could not be updated. Apparently its files are held by another process. You can check whether there is no activity on that component and try to kill any attached process before running CW again.

Hi, Sorry for my late answer - short vacation time Your registry is missing installer related entry - it is required for SE installer correct behavior. To fix that download any online installer from the Customer Portal and run it on the primary server - after that you should have 'Path' field present in Installer key. Then…

Hi John, It seems that the problem manifests during the primary server installation and then your case is just one of the consequences. Do you think it would be possible to get us logs from primary server installation? Also regarding registry - slightly below what's on your screenshot there is also key 'Installer' with…

When you write 'similar' - does that mean same "The write operation failed" issue or different one but with the same result that you were blocked with installation?

Just to clarify - with new SAM license - it's not completely true that it means unlimited free APEs, as those "free" APEs would not be able to, for example, poll NPM data. Those free APEs are limited to new SAM, SRM, VMAN and Log Analyzer.

Hi, The answer for your question is simple (unfortunately) - composite metrics cannot be nested. To achieve currently what you need would require creation of the composite metric like this: sum([scale( divide([ zero_fill(sum(s("trace.service.transaction.errors", {"service": "truevue-prod-enterprise01"}, {"period":"60"}))),…

The check that you mentioned is verifying the products and components versions, that are installed on main server and APE and compares whether they are the same prior to the upgrade. The best you can do to find the culprit would be to: 1) On the main server check logs from Administration service located here -…

Hi. Without access to the CW log there is no way to tell what exactly went wrong in your case. Do you have maybe support ticket created already with attached diagnostics? That would make it easier to troubleshoot. Thanks!

Is HTTPS for your website configured on IIS directly or used as an option in Configuration Wizard? In the first case - you can try to rerun CW and on website configuration panel select HTTPS option. Also - restart Solarwinds Administration service - that is the one responsible for Health Page hosting.

Easiest way to overcome this particular error is to go to DB and look for table SWA_InstallationSession. There will be at least one row with field isActive set to true - make it false and maybe give SolarWindsAdministration service a reboot.

Following Serena's comment: In DB there is table SWA_InstallationSession, and if any row has IsActive field set to true - this means Centralized Upgrades are running. You can change that entry to unblock yourself. You wrote: I look at the available updates section on the Orion, there is nothing displayed and no option to…

Hi, New installer in version 1.3.0.484 (available on Customer portal) is using different download approach and should solve your problem. Make sure to use online installer on your Main Server first and then run it on APE.

From the Customer Portal you can download offline installer for any product that you own - it should contain latest HotFixes for that version. Then run it on the Main server first, then on the HA backup and any Additional Pollers/Websites that you have. Regarding downtime - HF installation is usually faster than regular…

Your problem seems similar to the case described here - After migration of a poller Configuration Wizard loops the popup Multiple polling Engines Detected - SolarWinds Worldwid… . Have you tried maybe to apply mentioned workaround?

Was that HF installation? What you can do now is to try to close that window and open the classic Orion web console, navigate to 'My Orion Deployment' and check what status would be displayed there. Maybe there was some miscommunication between UI and DB and UI was never updated correctly.

I am not sure if this was solved already, but the way I solve this case is always the same: 1) Error like that pops out, 2) I uninstall current SolarWinds RabbitMQ, 3) Retry the installation. Rabbit will get installed anyway during the upgrade flow.