VMware Cloud Community
ganbidada
Contributor
Contributor
‎04-18-2013 12:44 AM

Storage service is not initialized

vCenter5.1 and all esxi5.1 servers - no upgrades, all fresh installs.

I get a "Storage service is not initialized, please try again later" when i click on the storage views tab. The sms logs are full of "incorrect username or password" but i cant figure out which ones since what i am using do have full access. The plugin is also enabled, tried restarting the inventory service and profile service along with a few other things but none seem to help.

What am i missing?

2013-04-17 23:40:53,274 [Thread-16] INFO  com.vmware.vim.clientutil.InventoryClientUtil  - Using key: 65c0adc2-c211-43cf-ad44-bb81e8ab1c67/VIMWEBSVC
2013-04-17 23:40:55,380 [Thread-16] ERROR com.vmware.vim.storage.common.qs.QsProxyStrategy  - Initialize QS connection failed
java.util.concurrent.ExecutionException: com.vmware.vim.binding.vim.fault.InvalidLogin:

inherited from com.vmware.vim.binding.vim.fault.VimFault:

inherited from com.vmware.vim.binding.vim.fault.InvalidLogin: Cannot complete login due to an incorrect user name or password.
    at com.vmware.vim.vmomi.core.impl.BlockingFuture.get(BlockingFuture.java:70)
    at com.vmware.vim.clientutil.InventoryClientUtil.acquireSessionTicket(InventoryClientUtil.java:124)
    at com.vmware.vim.clientutil.InventoryClientUtil.getAuthDataForDataService(InventoryClientUtil.java:92)
    at com.vmware.vim.storage.common.qs.QsAuthenticationProvider.getAuthDataForQueryService(QsAuthenticationProvider.java:25)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy$1.execute(QsProxyStrategy.java:73)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy$1.execute(QsProxyStrategy.java:70)
    at com.vmware.vim.storage.common.util.RetryTaskExecutor.execute(RetryTaskExecutor.java:24)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy.createClient(QsProxyStrategy.java:88)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy.<init>(QsProxyStrategy.java:50)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy.getInstance(QsProxyStrategy.java:57)
    at com.vmware.vim.storage.common.qs.QsClientImpl.<init>(QsClientImpl.java:35)
    at com.vmware.vim.sms.qs.QueryMapper.<init>(QueryMapper.java:95)
    at com.vmware.vim.sms.qs.QueryMapper.getInstance(QueryMapper.java:103)
    at com.vmware.vim.sms.provider.ProviderFactory.loadVasaProviders(ProviderFactory.java:294)
    at com.vmware.vim.sms.StorageManagerImpl$ProviderLoader.run(StorageManagerImpl.java:103)
Caused by: com.vmware.vim.binding.vim.fault.InvalidLogin:

inherited from com.vmware.vim.binding.vim.fault.VimFault:

inherited from com.vmware.vim.binding.vim.fault.InvalidLogin: Cannot complete login due to an incorrect user name or password.
    at sun.reflect.GeneratedConstructorAccessor231.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at java.lang.Class.newInstance0(Class.java:355)
    at java.lang.Class.newInstance(Class.java:308)
    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 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)
ware.vim.binding.vim.fault.InvalidLogin: Cannot complete login due to an incorrect user name or password.
    at com.vmware.vim.vmomi.core.impl.BlockingFuture.get(BlockingFuture.java:70)
    at com.vmware.vim.clientutil.InventoryClientUtil.acquireSessionTicket(InventoryClientUtil.java:124)
    at com.vmware.vim.clientutil.InventoryClientUtil.getAuthDataForDataService(InventoryClientUtil.java:92)
    at com.vmware.vim.storage.common.qs.QsAuthenticationProvider.getAuthDataForQueryService(QsAuthenticationProvider.java:25)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy$1.execute(QsProxyStrategy.java:73)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy$1.execute(QsProxyStrategy.java:70)
    at com.vmware.vim.storage.common.util.RetryTaskExecutor.execute(RetryTaskExecutor.java:24)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy.createClient(QsProxyStrategy.java:88)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy.<init>(QsProxyStrategy.java:50)
    at com.vmware.vim.storage.common.qs.QsProxyStrategy.getInstance(QsProxyStrategy.java:57)

Reply
0 Kudos
3 Replies
ganbidada
Contributor
Contributor
‎04-25-2013 02:34 AM

Any ideas from the experts?

Reply
0 Kudos
kpelt
Contributor
Contributor
‎11-18-2013 07:51 AM

Change profile-driven storage service account to run as the same account you are running vCenter Server.

Reply
0 Kudos
admin
Immortal
Immortal
‎11-21-2013 08:22 AM

Symptoms

  • The performance overview in vCenter Server fails. 
  • You see the error:

    Perf-charts experienced an internal error. Report application initialization is not completed successfully. Re-try in 60 seconds

     
  • The Storage view in vCenter Server fails  .
  • You see the error:

    The storage service is not initialized, try again later

     
  • In the Jakarta log located at C:\j2sdk1.4.2_13\jre\lib\zi\Asia, you see the error:

    The module path requested, null, is not in the same web application as this servlet, /vws

     
  • In the SMS log located at C:\ProgramData\VMware\VMware VirtualCenter\Logs, you see the error:

    Error creating vcdbClient com.vmware.vim.common.vdb.VdbException: Invalid DSN <DSN Name> 

Resolution

This issue occurs due to a trailing or leading space in your DSN name.

Note: Ensure that the vCenter ODBC driver is a supported SQL Native Client. For more information, see Upgrading vCenter Server fails with the error: DSN is pointing to an unsupported ODBC driver (101580....

To resolve this issue:

  1. Stop the VirtualCenter Server and VirtualCenter Management Webservices services. For more information, see Stopping, starting, or restarting vCenter services (1003895).
  2. Open ODBC and click the System DSN tab.
  3. Click Configure.
  4. Remove the trailing or leading space from the VirtualCenter DSN Windows registry key:
    1. Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\VMWare, Inc\VMware VirtualCenter\DB.
    3. Click the DSN name and remove the leading or trailing space from it.
  5. Start the VirtualCenter Server and VirtualCenter Management Webservices services. For more information, see Stopping, starting, or restarting vCenter services (1003895).  
Reply
0 Kudos