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

Upgrade from Orion 9.0 SP2 to Orion 9.1 wasn't smooth

Installation procedure failed in Configuration Wizard, message "Failure updating ASP.NET Script Maps". Orion services weren't started.

After that I tried to manually start Configuration Wizard again. It started from scratch and failed in Website configuration with message "Web Request for Orion/login.aspx failed, Error 401 Unauthorized." Orion services were started.

Then I've remembered that I have Windows AD Passthrough Authentication enabled and I've enabled anonymous access in IIS configuration for Orion website. In third attempt with these settings, I was allowed to run only web portion of Configuration Wizard, which failed updating ASP.NET scripts again.

I wasn't discouraged yet ;-> and ran the web portion of Configuration Wizard for the fourth time. It stopped in the step "Validating Website" for about 10 minutes, but finally finished successfully.

Above that I am satisfied with new web performance and I am looking forward to pure ASP.NET version of Orion to see events, web resources etc. in our date/time regional settings.

Any clues about reasons for such behavior? Anyone with similar experiences?

Find more posts tagged with

Accepted answers

All comments

FormerMember

The 'ASP.NET Script Maps' is something I'd need to take a look at a log file for. But, the problem with AD authentication we found and have a fix we're working on for SP1. The workaround you described is how to deal with it. You will need to do this anytime you reconfigure the website until the SP comes out(we're actively working on it).

brad.fletcher

Didn't run into the ASP.NET script map error but AD authenication was an issue for sure.

I'm also now noticing that Dr. Watson (DW20.exe) is going crazy, hogging CPU and as a result the Orion site is painful to use. I'm getting several repeating event log errors from source ".NET Runtime 2.0 Error Reporting" that read as follows:

Faulting application swjobengineworker.exe, version 1.1.1.2048, stamp 48bf7604, faulting module kernel32.dll, version 5.2.3790.4062, stamp 46264680, debug? 0, fault address 0x0000bee7.

Anyone else see this or have any suggestions?

Brad

Gustelj

The 'ASP.NET Script Maps' is something I'd need to take a look at a log file for. But, the problem with AD authentication we found and have a fix we're working on for SP1. The workaround you described is how to deal with it. You will need to do this anytime you reconfigure the website until the SP comes out(we're actively working on it).

Thanks for your reply. Maybe I won't run into the "ASP.NET Script Maps" issue again, but just to be on the safe side, I would like to know the cause and how to deal with it. Which logs should I send and where? Should I open a support ticket? I believe I saw an error message about COM+ authentication problems in my NPM server event log at the time of the "ASP.NET Script Maps" issue.

brad.fletcher

As an update to the CPU utilization problem I'm having post upgrade, I am receiving the error referenced above about every 5 minutes. This corresponds to my volume statistics collection interval if that means anything to anyone.

Brad

FormerMember

Brad,

We need you to open a Support ticket. Dev needs to look at your job engine logs to see why it's misbehaving like this.

brad.fletcher

Opened a case earlier today, case# 63731 Haven't been asked for the job engine logs yet but if you point me to where they are I'll go ahead and get them sent.

Thanks for your help!

Brad