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

Volume on Windows Server on VM Server show volume ID, but no data

I've been researching this problem, but haven't found the answer yet. Problem: all volumes on a specific windows server does not show the size of the volume or the space used. Here's what I have done so far:

1. I queried the database using the node ID in the volumes table via SolarWinds Database Manager. It confirms that the volumes are there, but haas only 0 in the table for size, percent used, status (and a few more). There is an N under the Volume is responding column.

2. I have deleted the volumes and readded them. I have deleted the server object and re-added it. No resolution.

3. I ran a manual Database maintenance, no resolution.

4. I used the SNMP community string in IP Network Browser to verify the community string. I used MIB Walk to verify the OID information. The server is responding with the correct numbers, that is: Allocation units X Storage Size /1024/1024/1024 does equal the correct number of GB for the volume. So, this means that SNMP is reporting the correct information.

5. I click the volume from the web console, it gives me this error:

Object reference not set to an instance of an object.

6. I found something about the following on thwack, and had the server admin run it. No resolution.

vicfg-snmp --server {server name} -c {snmp-commuinity} -t {IP/snmp-community}

vicfg-snmp --server {server name} -E

We are running NPM 10.1.3, APM 4.0.2, IP SLAM 3.5.1, NCM 6.1, NTA 3.7, and IVIM 1.1.2 (demo). The database is on a Windows 2003 server with 2 GB RAM. Orion is on a different 2003 server with 3.5 GB RAM.

Any suggestions? Thanks,

Eric

Find more posts tagged with

Accepted answers

Nandish

Eric,

On the point #4,if I am understanding this correctly you were able to see real values(that is instead of zero)when you ran SNMP WALK.Is this close?

Well,understanding from the history of the problem,it looks like something is bad.

I want you to run the configuration Wizard which can very much fix the issue.However if you would like to see where this is coming from,then please open a support ticket.

Also wanted to know if this worked fine before and not working now?If yes please explain what changes were made on the server?

All comments

Nandish

Eric,

On the point #4,if I am understanding this correctly you were able to see real values(that is instead of zero)when you ran SNMP WALK.Is this close?

Well,understanding from the history of the problem,it looks like something is bad.

I want you to run the configuration Wizard which can very much fix the issue.However if you would like to see where this is coming from,then please open a support ticket.

Also wanted to know if this worked fine before and not working now?If yes please explain what changes were made on the server?

ebradford

Point number 4: Yes, the real data is available via SNMP Walk, and when multiplied out and divided, it comes to the correct number of available and total GB volume space.

I'll run the Wizard and report back.

Changes on the server -- this is hard for me to say. I am part of the networking group; the server group also now has admin access to the Orion server. They installed a demo version of VIM on May 3rd at 10:30 pm. I do not know if this problem started in June.

I think the problem may have started in July. There used to be duplicate volume objects for E: and F: (before they were deleted). The duplicates had the same node ID number and same alpha-numeric string following the volume label, but different volume ID number. The old volume objects had an older volume size, different volume name and utilization settings prior to the volume being expanded at some point. The server team doesn't have records of when the volume size was changed. Anyway, in the duplicate volume object has a "next poll" of July 5th 2011, 3:42 pm. Further, they did have volume size and utilization, but they were old and no longer being updated. By the way, the more current of the two duplicate volume objects did not have volume size or utilization.

All previous volumes have been deleted, the new volume objects on the new server object do not have any volume size or utilization data in the database table.

I hope that is all clear, I think there probably was a better way to phrase it... Thanks, Eric

ebradford

I had to run the Config Wizard three times due to errors, but finally did get a successful completion. I logged into the web interface and checked the volume sizes. They are present and correct. Thanks for your help.

Website configuration failed:
• Web Request for /Orion/Login.aspx failed - The operation has timed out

Website configuration failed:
• Failure updating ASP.NET script maps.

• Error starting service "SolarWindsTrapService". Service did not start in a timely manner. Please check the service state in Orion Service Manager.