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

Runtime error '70' for Invenory tab in NCM

byrona

In the NCM I recently setup one of my first users with full Admin access to the NCM. When that user clicks on the Inventory tab for a node they receive a Runtime Error '70' and then the application crashes out.

What is the cause of this?

P.S. This works just fine for me so the problem seems specific to this user. Also, this is in the console on the system, not in the web console.

Find more posts tagged with

Accepted answers

ShamChauthani

I was about to ask you this specific question. Looks like NCM is depending on Windows Admin priviledges when accessing the Inventory tab which is likely causing this issue. I will open a bug for this.

All comments

chris.lapoint

Are you both viewing the inventory tab in NCM desktop client for the same node with different results (yours works, other user doesn't)? If so, we haven't seen this one before. You might need to submit a support case on this one.

byrona

Yes, we are both viewing the inventory tab for the same node in the NCM client that resides on the server that NCM runs from. When I do this it works fine, when my Network Admin does it, she receives the error I noted.

byrona

The only difference between our accounts that I am aware of is that I have admin permissions on the Windows 2008 system itself while she only has user access. Both of our accounts in NCM are at the Admin level.

ShamChauthani

byrona

After doing some investigation and speaking with our Windows System Engineer, it seems that the Runtime 70 error has historically been associated with DCOM permission issues. Also, it was suggested that granting proper access to the application file structure may help resolve this problem as well.

Based on this information it sounds like a combination of resolving a DCOM permission problem and granting proper access to the application file structure may be a work around until the bug can be resolved.

Can you please let me know if a workaround is possible and what it may be? That is other than granting Administrator level access to the Windows 2008 server to every user that needs NCM access as that isn't a workable solution for us and our security requirements.

Thanks!

Derek

We have been trying to localize and replicate the issue and was wondering if you could quickly answer the following questions.

1. Is NCM installed to default location?

2. What are the exact Windows permissions for the user?

3. Is UAC enabled on the system with NCM installed?

byrona

I should also point out that we are also running Solarwinds NPM and APM on this same box; however, the DB for all of these applications is on separate system.

Derek

Just want to update you that our Dev team is still looking into the issue.

byrona

Just as an FYI, this bug was in the critical path of us moving forward with a project so I had to play with account permissions for the user experiencing the problem and what I found was Power User access did not resolve the problem, it required full Administrator access.

Now I am sure that if me or one of our Windows engineers had the time we could isolate it to specific files or folders, unfortunately time is a much lacking resource at the moment so this is the only additional information I can offer you at this time.

Hope it helps.

Derek

Orion NCM (since v4) has required an Windows Administrator account when accessing the Windows console application.

Unfortunately it will not work for a user from users group due to permissions issue.

The NCM application needs to have:

a. read/write permissions to file system NCM folder

b. Read/write permissions to system registry

c. Permissions to access to Windows Task Scheduler

I believe we have this documented, but will double check for you.

byrona

I don't recall reading anything about those being necessary permissions when I went through the Administrators guide but I may have missed it. Please let me know if this is documented and if so where, thanks!

mark_wiggans

Yes, this needs to be added to the documentation.