nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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 and Cirrus on Same Box

direland69

Is installing Orion and Cirrus on the same box supported? I currently have Orion and Cirrus on the same server here. Yesterday, I upgraded Cirrus to 3.5 (Orion version was 8.0.1). After upgrading Cirrus, I am no longer able to open Map Maker. Trying to do so produces the following error...'

Run-time error '430':

Class does not support Automation or does not support expected interface

I have tried uninstalling both products and reinstalling just Orion 8.0.2. Still no go. Plus, now when I try to run the Orion install, I get errors referring to OLE2.DLL during the registering components process.

Seems I had a similar issue when I fisrt installed Cirrus on this box (3.0 then). It hosed up my server so bad that I finally had to re-image it. I'm afraid I'm heading down this path again.

Find more posts tagged with

Accepted answers

All comments

FormerMember

Just got this from support

If Cirrus 3.5 has been installed, this is to do with a copy of a dll file being registered in the wrong directory. File name is SWDiscoveryServices8.dll

To fix this go to a DOS prompt and do the following…this will unregister it in the wrong subdirectory and re-register it in the correct subdirectory:
C:\>cd program files
C:\Program Files>cd SolarWinds
C:\Program Files\SolarWinds>cd "Configuration Management"
C:\Program Files\SolarWinds\Configuration Management>regsvr32 /u SWDiscoveryServices8.dll
C:\Program Files\SolarWinds\Configuration Management>cd ..
C:\Program Files\SolarWinds>cd common
C:\Program Files\SolarWinds\Common>regsvr32 SWDiscoveryServices8.dll
C:\Program Files\SolarWinds\Common>

Another way of doing this is:
Start > Run > regsvr32 -u "C:\Program Files\SolarWinds\Configuration Management\SWDiscoveryServices8.dll"
Then
regsvr32 "C:\Program Files\Solarwinds\Common\SWDiscoveryServices8.dll"

worked great for me.

direland69

Yep, worked for me too. Thanks!

mkocsis

I upgraded mine, too and didin't even try Mapmaker yet. When I did I received the same error. This fixed worked for me, too.

Good catch.

Michael Kocsis
Data Communications
City of Tampa

danrog

Just wondering. Have any of you tested editing a node in Cirrus after changing the dll that is registered? After changin the dll that is registered, map maker works but I cannot add/edit a node in Cirrus any longer (hangs and eventually crashes). If I revert back to the Cirrus version of the dll I can add/edit nodes but then I of course lose map maker again.

direland69

danrog,

Yep, having the exact same issue.

FormerMember

not a fix but helps out > Batches for each

www4.solarwinds.net/.../topic.asp

FormerMember

Just had exactly the same issue using Cirrus 3.5 and Orion 8.02. The fix posted by Mike McCartney worked a treat.