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
Home
Products
Network Configuration Manager (NCM)
Error Launching Cirrus (v3)
clanger
I was curious if anyone has seen this error and what resolved it for you if so- Cirrus stopped launching for me a couple weeks ago with the following error (I pulled this from the logs when it backs up the DB but it's the same when you run config managment):
3/26/2007 11:00:02 PM : Cannot start ConfigMgmtEngine8.dll
6 : Overflow
You may need to reinstall this application.
I've tried a reinstall but I get the same error. I opened a ticket with support but figured I'd ask here as well.
Find more posts tagged with
Accepted answers
All comments
clanger
Issue resolved:
According to SW support, cirrus can (rarely) import a device config into the registry of all places. Typically this results in a garbage entry in the hive key and prevents cirrus from launching.
From Support: Here is what you need to do. Go to Start > Run > Regedit, then HKEY_LOCAL_MACHINE > Software > Solarwinds.Net and find the Configuration Management folder. Open this folder and go into the settings. Delete the last entry (typically the corrupt data) and close the registry, then launch Cirrus.
Mine was not this issue however removing the entire hive key after reinstalling worked. It gets recreated when you run cirrus again. My database also corrupted and I was able to recover to a backed up database file.
Deleting the hive key will only lose your settings from the settings portion of the File>settings menu (like hiding passwords etc. so you have to redo those)
After restoring the database i reran config downloads for all my devices and reset baselines for them to the current date and all is well again. Hope this helps someone...
Haley
The issue mentioned above has been resolved with Cirrus 3.5.
Quick Links
All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of