COM+ Error on Orion Install

We are trying to install an evaluation copy of Orion V8.5.1. and are getting errors. We originally installed it with no problems on a seperate server. This new/different server also has Cirrus CM on it and we are trying to take advantage of the integration. The Orion Configuration Wizard gets to a certain point then exits with this message:

"The wizard was unable to register the Solar Winds COM+ Application"

The ConfigurationWizard Log file writes this:

2007-11-21 09:32:36,648 [6] ERROR ConfigurationProgressScene - The wizard was unable to register the SolarWinds COM+ Application. A possible cause is the Distributed Transaction Coordinator service is disabled
2007-11-21 09:32:36,648 [6] ERROR ConfigurationProgressScene - The wizard was unable to register the SolarWinds COM+ Application.

We checked the Distributed Transaction Coordinator service and it is running...

Has anyone seen this before? Any idea what is going on?

Server 2003 Enterprise SP 1, Installing as Local Admin

Thanks!

Find more posts tagged with

Accepted answers

All comments

About2GiveUpNPM

I am getting the same error while trying to upgrade from 8.1 to 8.5.1. The upgrade was recommended by Solarwinds Support to address a Basic Alert problem. The Solarwinds KB is no help. I have a ticket open with them, but since it is afterhours, it will take a while to get help. I will post a follow up if it gets fixed.

Update: Just read through the following posts on similar, if not the same error, and may have a fix for you. See . I have tried some of the suggestions that may apply to my situation, but none worked. I believe my error is that the DTC service is not running even though it show as started in Services. I am going to search the MS KB to address the event log error below. Good luck.

Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4437
Date:  11/27/2007
Time:  10:26:01 PM
User:  N/A
Computer: OKC1APP0002
Description:
The account that the MS DTC service is running under is invalid. This can happen if the service account information has been changed using the Services snap-in in Microsoft Management Console (MMC). MS DTC service will continue to start. Please make sure that the MS DTC service account information is updated using the Component Services Explorer.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Ralphr

Finally got it working, and it looks like you are going down the same troubleshooting path. What I found out was the server was under the domain of a Group Security Policy that was disabling services at designated (unknown to me) times. Make sure your Com+ Application Service is running. Once I ensured all the necessary services were running (not apparent from the documentation, other than IIS), the install completed.

Maybe this will help you...

alanmellerick

When I tried logging into my SolarWinds NPM site this morning, I got lots of the following error

Cannot start SolarWinds Orion NPM Web Engine (OrionNPMWeb.Application).
Error Number -2147467238
006~ASP 0177~Server.CreateObject Failed~8000401a

When I tried running the Orion Configuration Wizard to re-create the website, I kep getting the COM+ error described in all these posts.

More detective work solved the problem. My Windows security log was full of "user must change password upon first logon" messages for my defaultl SolarWinds user account (created when I first installed Orion). When I checked that account I saw that some well-intentioned idiot (me) had marked that account as 'user must change password' having run the MBSA tool some weeks before. My Orion server had not been reboot since, but it had been rebooted a few days ago during a maintenance slot and this was the first time the website had been accessed.

But I had already tried to re-configure the Orion website, and no I had no COM+ application at all. In my local Users, I set the ORION_WEBSITE account straigt by removing the 'user must change password' tick (although I must see if I can get that back up to satisfy Audit). Next I ran the Orion Configuration Wizard again, just re-creating the website on top of the existing settings. This time there were no COM+ errors!

I checked Orion NMP website again - all OK!

My next task - how to satisty the two opposing camps of 'Audit' and 'The Real World' and start working on making Orion NPM work under tighter account limitations.