Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Orion migration from 2015.1.3 to 2016.1 failed while configuring Message Bus

We are migrating: Orion from 2015.1.3 to 2016.1 and while the Config Wizard is configuring Message Bus it stops with this error:

• Exception while configuring plugin Orion Core Services component Message Bus. The data to be decrypted exceeds the maximum for this modulus of 128 bytes.

We have done repairs from "Programs and Features" to no avail. Database appears fine.

Has anyone experienced this? What is the workaround/fix?

TIA

Find more posts tagged with

Accepted answers

All comments

jburklow

Hello, Have you gotten any resolution on this error? I am running into the same issue and would be interested in finding the fix. Thanks!

jousterde1

We ended up uninstalling everything, and then reinstalling everything from scratch and sitting thru the config wizard each time (didnt even click "optimize web site"), following reboots etc. If this does not work for you call their support, but ask to be escalated as soon as you hear "low confidence" and "beating up around the bushes" by the tech speaking with you. We had unrelated NCM issue after upgrade and after the escalation it was quickly fixed. Unfortunately lvl1 Solarwinds support is just bad.

smartd

I've got an open ticket on a similar issue. Can't get RabbitMQ to load and run. Working a ticket on the problem with Sterling Elliott

techsyslonghorn

I've had the same issue. We've uninstalled/reinstalled/ told that the VM image was bad. Just rebuilt the server from scratch, still getting the exact same answer. Is there anyone else that's gotten this fixed?