I chose to use the offline installer while updating from 2020.2.1 HF1 to 2020.2.1 HF2. The configuration wizard is stuck at 47.2% and has been for some time. Anybody have any suggestions? How bad is it to kill the task and try to start over again?
the hf1 to hf2 jump only took a few minutes in my environment, but the install for hf1 when i did that a couple months back took a LONG time for me, about 4 hours. To keep eyes on what the wizard is doing i run a powershell tail on the config wizard log file while it runs
get-content "C:\ProgramData\Solarwinds\Logs\Orion\ConfigurationWizard.log" -tail 10 -wait
I also ran queries similar to this one to see if the wizard was still making calls to my DB
USE masterGOSET TRANSACTION ISOLATION LEVEL READ UNCOMMITTEDSELECTer.session_Id AS [Spid], sp.ecid, er.start_time, DATEDIFF(SS,er.start_time,GETDATE()) as [Age Seconds], sp.nt_username, er.status, er.wait_type, SUBSTRING (qt.text, (er.statement_start_offset/2) + 1,((CASE WHEN er.statement_end_offset = -1THEN LEN(CONVERT(NVARCHAR(MAX), qt.text)) * 2ELSE er.statement_end_offsetEND - er.statement_start_offset)/2) + 1) AS [Individual Query], qt.text AS [Parent Query], sp.program_name, sp.Hostname, sp.nt_domainFROM sys.dm_exec_requests erINNER JOIN sys.sysprocesses sp ON er.session_id = sp.spidCROSS APPLY sys.dm_exec_sql_text(er.sql_handle)as qtWHERE session_Id > 50@SPID)ORDER BY session_Id, ecid
In my case the delay was caused because the upgrader was running some kind of update against all my SAM templates, we had 1,500 templates so it took a long time to work through them but i saw it moving one by one so i knew not to mess with anything.
This is helpful. After it was stuck for about an hour and a half, i decided to revert to my snapshots and restore my database. After attempting to do it in the web application using the update tool, I received an error while the configuration was running that just said 'Configuration Failed'
at this point, I would open a ticket with support.
@MasonLan i think this issue is not only specific to 2020.2.1.HF2. I have experienced this problem few times in past, mainly when i was upgrading full version. Best solution is to wait it to give error message(will take some time). Analyze installation logs, it will give you clear picture, what causing the issue.
You can start over again and it will complete the wizard. However If the issue is still there in 1-2 attempts, better to raise a case with support. Thanks
Open a ticket. if you have a large environment with lots of data, the config wiz can take hours. And more hours. Check the config wiz log file and look for at this document:
https://support.solarwinds.com/SuccessCenter/s/article/CWActiveInstanceChecker-Extending-expiration-for-active-instance-of-ConfigWizard-on-machine?language=en_US
As long as it is updating the log file - let it run. But still call support. You may need to have another issue going on.
I had the same issue when trying to install HF1 Monday morning. I have yet to have any tech take my high and critical tickets from that day. You can not reach anyone on the phone and the phone que hangs up automatically after 1 hour; using the call back feature results in no call backs.
Solarwinds support has gone down hill over the past few years as it takes weeks to get anyone to take a ticket and actually look into an issue.
you can try and temporarily disable your Anti-virus and re-install the update to make sure your Antivirus software package is not preventing you from installing or causing your environment to perform slowly or unresponsive.
Another thing that sometimes jams me up during CW is if i have APE's and web servers that are still running their solarwinds admin services they tend to keep writing to the DB and it can sometimes cause locks and contention that slows the CW bigtime.
This is the same experience I have had. They are understandably busy after everything that has happened this week, but I have waited in the phone queue for an hour until it times out multiple times this week. I guess at this point it's just a waiting game.
