vCenter Storage Monitoring Service fails with the error: Service initialization failed
search cancel

vCenter Storage Monitoring Service fails with the error: Service initialization failed

book

Article ID: 336134

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:

When upgrading to vCenter Server 5.5 and when you are running the VMware VirtualCenter Server service and the VMware VirtualCenter Management Webservices service with a service account, you experience these symptoms:

  • vCenter Sever Service Status page reports that the vCenter Sever Storage Monitoring Service has failed.
  • You see error similar to:

    Service initialization failed
  • The Storage View tab reports the error:

    An internal error has occurred

  • In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vws.log file, you see entries similar to:

    <time>,634 tomcat-http--40 ERROR com.vmware.vim.health.VcAuthorize]</time> VC session has expired and could not be authenticated
    com.vmware.vim.binding.vim.fault.NotAuthenticated: inherited from com.vmware.vim.binding.vim.fault.NoPermission: object =
    com.vmware.vim.binding.vmodl.ManagedObjectReference@c1f8a09,privilegeId = System.Read inherited from com.vmware.vim.binding.vmodl.fault.SecurityError:inherited from com.vmware.vim.binding.vim.fault.NotAuthenticated: The session is not authenticated.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at java.lang.Class.newInstance0(Unknown Source)
    at java.lang.Class.newInstance(Unknown Source)
    at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:171)
    at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:26)
    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:33)
    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:135)
    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:98)
    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:84)
    at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:37)
    at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:97)
    at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:245)
    at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:203)
    at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:126)
    at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:98)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:533)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:514)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:302)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:272)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:169)
    at com.sun.proxy.$Proxy131.hasPrivilegeOnEntity(Unknown Source)
    at com.vmware.vim.health.VcAuthorize.hasHealthPrivilege(VcAuthorize.java:50)
    at com.vmware.vim.health.servlets.HealthServlet.isAuthenticated(HealthServlet.java:111)
    at com.vmware.vim.health.servlets.HealthServlet.processRequest(HealthServlet.java:65)
    at com.vmware.vim.health.servlets.HealthServlet.doPost(HealthServlet.java:158)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

  • In the C:\ProgramData\VMware\Infrastructure\Profile-Driven Storage\Logs\sps.log file, you see entries similar to:

    YYYY-MM-DD <time> [pool-22-thread-1] WARN opId= com.vmware.vim.storage.common.util.VpxdConnection - Ignoring exception while verifying vpxd connection
    com.vmware.vim.binding.vim.fault.NotAuthenticated: inherited from com.vmware.vim.binding.vim.fault.NoPermission: object =
    </time>    com.vmware.vim.binding.vmodl.ManagedObjectReference@c1f8a09     , privilegeId = Sessions.ValidateSession inherited from
    com.vmware.vim.binding.vmodl.fault.SecurityError: inherited from com.vmware.vim.binding.vim.fault.NotAuthenticated: The session is not authenticated.
    at sun.reflect.GeneratedConstructorAccessor85.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at java.lang.Class.newInstance0(Unknown Source)
    at java.lang.Class.newInstance(Unknown Source)
    at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:171)
    at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:26)
    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:33)
    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:135)
    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:98)
    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:84)
    at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:37)
    at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:97)
    at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:245)
    at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:203)
    at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:126)
    at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:98)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:533)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:514)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:302)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:272)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:169)
    at com.sun.proxy.$Proxy33.sessionIsActive(Unknown Source)
    at com.vmware.vim.storage.common.util.VpxdConnection.verifyConnection(VpxdConnection.java:227)
    at com.vmware.vim.storage.common.util.VpxdConnectionFactory.getAdminConnection(VpxdConnectionFactory.java:94)
    at com.vmware.vim.sms.security.ActivationValidatorImpl.updatePrivilegeMap(ActivationValidatorImpl.java:104)
    at com.vmware.vim.sms.security.ActivationValidatorImpl.validateSession(ActivationValidatorImpl.java:322)
    at com.vmware.vim.sms.security.ActivationValidatorImpl.validate(ActivationValidatorImpl.java:457)
    at com.vmware.vim.vmomi.server.impl.ValidationStartTask.run(ValidationStartTask.java:67)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

    ...

    <YYYY-MM-DD>T<time> [Thread-5] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STARTED: Query get_vpx_datacenter
    <YYYY-MM-DD>T<time> [Thread-5] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STOPPED: Query get_vpx_datacenter
    <YYYY-MM-DD>T<time> [Thread-5] DEBUG opId= com.vmware.vim.storage.common.util.SimpleTimeCounter - TIME TAKEN: Query get_vpx_datacenter: 0.025
    <YYYY-MM-DD>T<time> [Thread-5] ERROR opId= com.vmware.vim.sms.provider.vc.VcProviderImpl - Failed populating service cache


    </time></time></time></time>    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

  • The database backing vCenter Server fails to log in every 30 minutes with this query:

    SELECT DATACENTER.ID AS ENTITY_ID, ENTITY.NAME
    FROM VPX_DATACENTER DATACENTER, VPX_ENTITY ENTITY
    WHERE (DATACENTER.ID = ENTITY.ID)


Environment

VMware vCenter Server 5.5.x

Resolution

This is a known issue affecting VMware vCenter Server 5.5. Currently, there is no resolution.

To work around this issue, add the service account credentials to the VMware vSphere Profile-Driven Storage Service used to start the VMware VirtualCenter Server service and the VMware VirtualCenter Management Webservices service. By default, the account used is Local System.

To change the service account for the vSphere Profile-Driven Storage Service:
  1. Log in to the vCenter Server machine.
  2. Click Start > Run, type services.msc, and click OK. The Services window opens.
  3. Locate the VMware VirtualCenter Server service. Make note of the Log On As user account.
  4. Locate the VMware vSphere Profile-Driven Storage Service service. The status should be Started / Automatic.
  5. Right-click the VMware vSphere Profile-Driven Storage Service.
  6. Click Properties > Log On tab and select This Account. Change it to use the same account used to run the vCenter Server service found in Step 3 and click OK.
  7. Restart the VMware vSphere Profile-Driven Storage Service and VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box.. How to stop, start, or restart vCenter Server services
次のエラーが表示されて、vCenter Storage Monitoring Service が失敗する: サービスの初期化が失敗しました(Service initialization failed)
vCenter 存储监控服务失败，报错：服务初始化失败

Powered by Wolken Software