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

Unmanage Scheduler Utility - Error

I'm getting the following error (in the log) with the Unmanage Scheduling Utility:

12/12/2010 6:58:55 AM - Login successful (ServerName/UserName): XXXXXXXXXX

12/12/2010 6:58:55 AM - Unable to read from database.
The given key was not present in the dictionary.
12/12/2010 6:59:02 AM - Error while connecting to the NPM DB or while reading from the DB. Unmanage Task Editor exits.
12/12/2010 6:59:02 AM - Unmanage Editor closed.

And the Utility closes - running 10.1

Find more posts tagged with

Accepted answers

brandon.godby78

With the aid of Toks at Solarwinds we were able to reproduce the issue, and it is a known bug. The resolution is to create a custom property for interfaces. The utility worked fine after that.

All comments

aLTeReGo

Does the device you're attempting to unmanage happen to be a NetFlow source? Also, have you ensured that the system clock on the Orion server is in sync with the system clock on the MSSQL server?

bshopp

When you upgraded to 10.1, did you use the one you installed from 10.0 or the one in the Program Files -> SolarWinds Orion menu?

jbaulsir

I don't get that far, it errors out on invocation of the utility itself.

Orion and database are on the same server.

jbaulsir

The one from Program Files -> SolarWinds Orion menu

I did have the old one installed, but removed it.

brandon.godby78

Bump....I have the exact same problem. Does anyone have a resolution yet?

bshopp

Not sure what is going on then, I would recommend a support ticket to investigate further.

MarieB

Brandon et al--

When you open a support ticket, could you:

--Reference this thread to Support.
--Post back here with a case number.
--Post any solutions you get from Support.

Many thx,

brandon.godby78

Case #243321

Nothing we tried yesterday resolved the issue. I will update here Monday when we start again.

gibjim01

Hi! I got a similar error, but I don't know where to find the log you are talking about. Can you tell me where it is so I will push my investigation?