Has anyone upgraded to 2023.4.1 or 2023.4.2? Only seeing two posts in the catalog. If you have upgraded has it been smooth? Trying to skip over the job engine issues that plagued releases until 2023.3.x.
Upgrade process was fairly smooth. We had an issue with database maintenance but not a major one
We have upgraded 3 of our environments to 2023.4.2 now and all went smoothly with no obvious issues and certainly nothing that we've spotted or had reported to us. two small, single server deployments and one multi server, multi APEs and HA.I will add if you are on 2023.2.x or .3.x then make the jump. It fixes loads of bugs and made our systems stable again.
Hi @stuartd
I am currently on 2020.2.6 and planning to upgrade to 2023.4.2, I know i can directly upgrade to the 2023.4.2
I was going through a few threads:
1. Backup any Unmanage utility tasks
2. Make sure there are no custom queries used in syslogs/traps rules
3. Is there anything else that you can think of that is deprecated or needs to be recreated ?
Direct from 2020 I don't think you need any specific steps outside of the usual 'backup your database' - but your extras are always a good shout to check or backup.
We had no issues with it
I just made our third attempt to get off of 2020.2.6, this time to 2023.4.2. Again, received a failure during the Configuration Wizard stage that was yet again different from previous attempts to previous versions:
"Database configuration failed: Error while executing script- Column already has a DEFAULT bound to it. Could not create constraint or index. See previous errors."
I'm finally opening a case as we need to get this thing upgraded as I can't find anything on this error. I don't know why these recent upgrades are so problematic for us, we aren't doing anything particularly custom. Also annoying since we completely rebuilt our cluster from scratch a few years ago. I've easily got 120 hours into trying to get past 2020.2.6 and it's become annoying.
In the CW logs they usually post exactly the SQL they are trying to run at each step, so if I run into something weird like that I usually just dig into the SQL and reverse engineer the change that it's attempting to make and see what hoops I need to clear to make it happen. In the past I've had to do various fixes for customers that didn't seem like they would have been needed, but things like dropping existing tables just for the CW to recreate them, or removing indexes, other bits. Can't say why some environments run into things like that when most don't but it seems to happen maybe one out of 20-30 upgrades that I've performed for clients.
My issue is that I'm a network guy, not a SQL whiz. I know my way around servers well enough that I'm the defacto "server guy" on our team, but issues like this are precisely why we pay $$$ for support.
I was able to get past this issue by deleting one of the constraints in SQL. It sounds like support was super familiar with this issue as I didn't even provide logs or diagnostics. They were able to give me a working procedure just from the error message. We are finally off 2020.2.6, so I'm happy.
Starting with 2023.2, new alert actions that require executing an external program or VB script require an approval by a system administrator.
I had some alerts that used scripts to create trouble tickets in our ticketing system. After the upgrade the scripts stopped working.
Approve alert actions executing a script (solarwinds.com)
documentation.solarwinds.com/.../core-approve-execute-alert-action.htm
still issues with the database maintenance on upgrade ? DB auth issues ?
It was down as Fixed in the previous patch, but was only 1/2 fixed, the other half is down as Fixed in the current patch, but I wont have that installed till Wednesday to confirm
@revco . Curious if you successfully upgraded to 2023.4.2? Either way, if you opened any tickets, could you post them here so I can review them? Thanks!
Thanks for the replies! Upgraded today from 2022.4.x to 2023.4.2 and so far so good.
Good to know. We have a lot of alerts that execute programs. The link above is either dead or somewhere I don't have access to get to.
Was is this -> Article Detail (solarwinds.com) or something else, what error was it ?
My exp was a little different, we have managed to fix most of the issues but I still need to look into a few things.
I upgraded from 2020.2.6 to 2023.4.2 and broke a few things on NCM.
Upgrade was smooth but then I faced a few issues though broke the NCM Views, had to change few custom templates, custom creds and other settings, faced an issue with Cisco CDP Inventory updates (still looking into it).
We were suffering with NCM inventory related issues following our move to 2023.4.2. Admittedly it took us quite a bit longer to spot than I'd have liked - but the inventory jobs in place did initially suggest it was CDP related, from the SQL related errors returned in the job logs. Although if you removed CDP from the inventory job, the job log noted failure with a different SQL PrimaryKey error. With the help of SolarWinds support, we were up and running again following the running of a lengthy set of prepared SQL statements, that are noted in case 01544402. My SQL knowledge is rubbish - so please don't go and do anything in the database on the back of this comment alone - but I interpreted the script as truncating the NCM_InventoryDatabaseMapping and rebuilding it (across 1500+ lines of SQL). This got our inventory jobs back in working order as soon as it was executed - so if the errors sound familiar, it could be worth asking support to check out that case.
https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-approve-execute-alert-action.htm
Not sure why the other link quit working.
Thanks for posting the working link! I used it and it did fix a couple alert actions that I had created recently that had not yet triggered. Also I upgraded to 2024.1 in my Test environment and had no issues with the upgrade. Have two Production environments scheduled for next month.
We are evaluating a jump from 2023.3.1 to 2024.1. It is still cooking, but seems solid. No major issues at this time. I will post updates. My co-worker likes the the blue roll over main menu, and the solid SolarWinds icon.
All went good on my environment.
@solarflare2033 I’m planning to upgrade 2022.4.1 to 2023.4.2 but before that upgrade, I just want to know whether the upgrade make any schema / data changes to the databases?
Our process could not be going more poorly. We have decided we must skip to 2024.1 from 2023.2.0 but it's not going better. We've been attempting, rolling back, and upgrading over the last 3 months with Solarwinds Premier Support and we still haven't (after 6 attempts) managed a successful upgrade with functional, reporting agents.
Hi, can you post your number of your support case?
01559630 & 00814594
