Hardware Status tab reports the message: No new host data available. Data will be updated in 5 minutes. vCenter Inventory search fails
search cancel

Hardware Status tab reports the message: No new host data available. Data will be updated in 5 minutes. vCenter Inventory search fails

book

Article ID: 340920

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • The Hardware Status Tab displays and hangs with the message Updating hardware data and then reports:

    No new host data available. Data will be updated in 5 minutes
  • Clicking Update in the Hardware Status tab reports the error:

    Host Sensor data is not updated. The Query Service is not available or was restarted, please retry.
  • When searching the Inventory in vCenter Server, you see the error:

    Login to the query service failed The server could not interpret the communication from the client. (The remote server returned an error: (403) Forbidden.)."

  • When searching the Inventory in vCenter Server, you see the error:

    Login to query service failed. A connection failure occurred (Unable to connect to the remote server)

  • In the vws.log file, you see entries similar to:

    [<YYYY-MM-DD><time> Thread-67 ERROR com.vmware.vim.cimmonitor.qs.provider.impl.QsHelperImpl] Failed to query
    com.vmware.vim.query.client.exception.UnauthenticatedException: Got status code: 401 reason: Unauthorized
    at com.vmware.vim.query.client.impl.ValidationHelper.validateResponseCode(ValidationHelper.java:35)
    at com.vmware.vim.query.client.impl.QueryDispatcherImpl$QueryResponseImpl.<init>(QueryDispatcherImpl.java:332)
    at com.vmware.vim.query.client.impl.QueryDispatcherImpl$QueryResponseImpl.<init>(QueryDispatcherImpl.java:323)
    at com.vmware.vim.query.client.impl.QueryDispatcherImpl.query(QueryDispatcherImpl.java:189)
    at com.vmware.vim.cimmonitor.qs.provider.impl.QsHelperImpl.executeQuery(QsHelperImpl.java:268)
    at com.vmware.vim.cimmonitor.inventory.InventoryPoller$1.run(InventoryPoller.java:118)
    at java.lang.Thread.run(Thread.java:662)</time>

  • You see the error:

    401 reason: Unauthorized
  • While editing the virtual machine, you see the error:

    The server fault invalid argument had no message

  • In the C:\ProgramData\VMware\Infrastructure\Inventory Service\Logs\ds.log file, you see entries similar to:

    [<YYYY-MM-DD><time> pool-14-thread-1 ERROR com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl] Error parsing atom feed:
    com.vmware.vim.query.server.store.exception.AtomFeedParserException: </time>    Feed id: D6DE7CCF-F7AE-4094-9858-BFC020A235DD does not match provider id: 904C32DA-DC48-4DD0-946D-E396376B2C71
    at com.vmware.vim.query.server.store.impl.VmomiAtomFeedImpl.parse(VmomiAtomFeedImpl.java:98)
    at com.vmware.vim.query.server.provider.VmomiAtomPullFeedImpl.getFeed(VmomiAtomPullFeedImpl.java:135)
    at com.vmware.vim.query.server.provider.AbstractAtomPullProviderBase.checkFeed(AbstractAtomPullProviderBase.java:99)
    at com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl$FeedPump.run(ProviderManagerServiceImpl.java:542)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

  • In the ds.log file located at C:\ProgramData\VMware\Infrastructure\Inventory Service\Logs, you see entries similar to:

    [<YYYY-MM-DD><time> pool-20-thread-238 INFO com.vmware.vim.vcauthorization.impl.AuthorizationManagerImpl] Computing permissions for DOMAIN\USERID
    [<YYYY-MM-DD><time> pool-20-thread-238 INFO com.vmware.vim.vcauthorization.impl.AuthorizationManagerImpl] ParentChain map:ParentChain:
    [<YYYY-MM-DD><time> pool-20-thread-238 FATAL com.vmware.vim.vcauthorization.impl.provider.InMemoryAuthCache] VC provider not registered: could not find a provider of type 'vpx'
    [<YYYY-MM-DD><time> pool-20-thread-238 ERROR com.vmware.vim.vcauthorization.impl.provider.InMemoryAuthCache] Error updating cache
    com.vmware.vim.query.server.store.exception.StoreException: No VC providers registered: unable to do permission checks
    at com.vmware.vim.vcauthorization.impl.provider.InMemoryAuthCache.fetchRootObject(InMemoryAuthCache.java:634)
    at com.vmware.vim.vcauthorization.impl.provider.InMemoryAuthCache.getRootObject(InMemoryAuthCache.java:604)
    at com.vmware.vim.vcauthorization.impl.provider.AuthorizationProvider.getRootObjectId(AuthorizationProvider.java:313)
    at com.vmware.vim.vcauthorization.impl.AuthorizationManagerImpl.getRootObjectId(AuthorizationManagerImpl.java:789)
    at com.vmware.vim.vcauthorization.impl.AuthorizationManagerImpl.isAllowedOnRoot(AuthorizationManagerImpl.java:271)
    at com.vmware.vim.vcauthorization.impl.AuthorizationManagerImpl.isLoginAllowed(AuthorizationManagerImpl.java:379)
    at com.vmware.vim.vcauthorization.impl.UserSessionManagerImpl.addConnection(UserSessionManagerImpl.java:53)
    at com.vmware.vim.vcauthenticate.servlets.AuthenticationHelper.addConnection(AuthenticationHelper.java:644)
    at com.vmware.vim.vcauthenticate.servlets.AuthenticationHelper.addConnectionForSSPISession(AuthenticationHelper.java:600)
    at com.vmware.vim.vcauthenticate.servlets.AuthenticationHelper.loginBySSPI(AuthenticationHelper.java:180)
    at com.vmware.vim.vcauthenticate.servlets.AuthenticationServlet.loginBySSPI(AuthenticationServlet.java:230)
    at com.vmware.vim.vcauthenticate.servlets.AuthenticationServlet.processRequest(AuthenticationServlet.java:120)
    at com.vmware.vim.vcauthenticate.servlets.AuthenticationServlet.doGet(AuthenticationServlet.java:93)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
    [<YYYY-MM-DD><time> pool-20-thread-238 ERROR com.vmware.vim.vcauthorization.impl.AuthorizationManagerImpl] Root object not found - unable to check privilege on root
    [<YYYY-MM-DD><time> pool-20-thread-238 INFO com.vmware.vim.vcauthenticate.servlets.AuthenticationHelper] User has no privileges


    </time></time></time></time></time></time>
  • The ds.log file located at C:\ProgramData\VMware\Infrastructure\Inventory Service\Logs\ may also report an error similar to:

    Error connecting to peer:https://vCenter.domain.local:10443 reason: org.apache.http.conn.HttpHostConnectException: Connection to https://vCenter.domain.local:10443 refused


Environment

VMware vCenter Server 5.0.x
VMware vCenter Server 5.5.x
VMware vCenter Server 5.1.x

Cause

The Hardware Status tab client communicates with the Inventory Service to validate whether the user has sufficient permissions.
This issue occurs if there are problems with user permissions.

Resolution

To resolve this issue, reset the Inventory Service database. For information on resetting the Inventory Database, see
Resetting the VMware vCenter Server 5.x Inventory Service database (2042200)

Warning: Resetting the Inventory Service database can lead to data loss. Perform this procedure only under the guidance of VMware Technical Support.

Note: For more information on a similar issue in vCenter Server Appliance, see vCenter Inventory Service fails to start in vCenter Server Appliance 5.x (2037952).


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box



Logging in to the vCenter Server 5.0 Web Client fails with the error: unable to connect to vCenter Inventory Service
How to repoint and re-register vCenter Server 5.1 / 5.5 and components
[ハードウェア ステータス] タブに次のメッセージが報告される：利用可能な新規ホスト データがありません。データは5分以内に更新されます。vCenter Inventory の検索に失敗します
vCenter Inventory Service fails to start in vCenter Server Appliance 5.x
Resetting the VMware vCenter Server 5.x Inventory Service database
“硬件状态”选项卡报告消息：无可用新主机数据。系统将在 5 分钟后更新数据。vCenter Inventory 搜索失败

Powered by Wolken Software