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

Having trouble polling vCenter

I'm able to successfully assign and test credentials with our vCenter server, but two red exclaimation points remain under Status, and Status Details. Can someone please suggest what may be required to fix this?

Thank you!

vCenter Status - Could Not Poll

vCenter Status Details - Unable to poll - need credentials

vCenter Polling Status - vCenter Polling OK

Find more posts tagged with

Accepted answers

All comments

petrf

Try this scenario:

- Assign the correct credentials

- Click "Poll now" and wait like 10 minutes if vCenter status changes

artb

We're have very similar problems after verifying the correct credentials (including verifying that vSphere client login works with the same credentials).

vCenter Status is "Could Not Poll"

vCenter Status Details is "Error while connecting to VMware device - Cannot complete login due to an incorrect user name or password."

vCenter Polling Status is "vCenter Polling OK"

Also checked the certificate and it's 2048 bits.

Any hints will be very appreciated.

petrf

Please open a support ticket and send us diagnostics.

henriknoerr

Hi,

Have you tried applying the newest hotfix HF3?

I see in the readme that vCenter polling is fixed

Best regards,

Henrik

storn

Have you checked HOW your are polling through the virtualization settings?

You want to make sure if you are polling through vCenter you have that option selected.

If you are polling the ESX servers directly you want to select that option:

lfransen

We have applied this hotfix and it still hasn't fixed the problem. Suffice to say the support and information about this issue coming from Solarwinds has been less than stellar. Originally we were told it was a MS patch problem, even though we have never applied those patches. Now we get a hotfix to fix the problem and it still doesn't work. That fact that NPM works fine with VCenter 4.1 and not with 5.0 tells me it is an NPM problem and has nothing to do with vCenter. In our environment the only thing that was changed was the upgrade from NPM 10.3 to 10.4.

artb

After a few rounds with support, we've gotten a solution. Don't know the actual cause of the problem or why this fixed the issue, but it did work for us:

Remove and reinstall the 10.4 Collector Services and Job Engines 1 & 2, run the Configuration Wizard, and then re-install HF3.

Earlier suggestions to delete and rediscover the vCenter server did not work.

ttl

We have upgraded to NPM 10.4.1 (which includes IVIM 1.5.0) and the problem persists.