Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Installing Single Sign On fails with the error 20010: Failed to Configure LookupService (2038086)

Symptoms

  • Cannot install Single Sign On (SSO)
  • Installing SSO fails
  • Single Sign On Installer fails with the error:

    error: 20010: Failed to Configure LookupService
  • The imsTrace.log file shows the year 2555
  • In the vminst.log file, you see entries similar to:

    VMware Single Sign On-build-797273: 10/16/12 16:30:50 Process returned 4294967295
    VMware Single Sign On-build-797273: 10/16/12 16:30:50 ERROR: Failed to run the command
    VMware Single Sign On-build-797273: 10/16/12 16:30:50 Posting error message 20010

  • In the discover-is.log file, you see entries similar to:

    2012-10-16 16:30:15,457 - center.vmware.local,,,,ERROR: Identity source discovery failed: Invalid input data. Validation failed
    Field: 'GssApiSupported', message: 'Test failed. Invalid user name or password specified'
    com.rsa.tools.common.action.exception.CLUExitException: Identity source discovery failed: Invalid input data. Validation failed
    Field: 'GssApiSupported', message: 'Test failed. Invalid user name or password specified'
    at com.rsa.riat.tools.is.DiscoverIdentitySources.execute(DiscoverIdentitySources.java:155)
  • In the vm_vim_ls.log file, you see entries similar to:

    [2012-10-16 16:30:50,035 main INFO com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor] Request message has expired. Server message: ns0:MessageExpired: Request has expired
    [2012-10-16 16:30:50,037 main INFO com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor] Server returned 'request expired' less than 0 seconds after request was issued, but it shouldn't have expired for at least 600 seconds.

  • The imsTrace.log file indicates that the STS request has expired:

    2555-10-16 16:30:49,981, [castle-exec-2], (AuthnProcessorChain.java:77), trace.com.rsa.riat.ws.security.AuthnProcessorChain, DEBUG, center.vmware.local,,,,Invoking authentication handlers
    2555-10-16 16:30:49,983, [castle-exec-2], (ValidationHandler.java:66), trace.com.rsa.riat.ws.security.AuthnHandler, DEBUG, center.vmware.local,,,,Current time: Tue Oct 16 16:30:49 ICT 2012
    2555-10-16 16:30:49,985, [castle-exec-2], (ValidationHandler.java:83), trace.com.rsa.riat.ws.security.AuthnHandler, ERROR, center.vmware.local,,,,Request has expired
    2555-10-16 16:30:49,986, [castle-exec-2], (SecurityTokenServiceImpl.java:102), trace.com.rsa.riat.sts.impl.SecurityTokenServiceImpl, ERROR, center.vmware.local,,,,com.rsa.riat.core.WSSESecurityException: Request has expired

    Note: In the log timestamp, the current year is set to 2555.

Cause

This issue occurs due to an incorrect system date and occurs because the local user's locale is set to Thailand time when executing the installer.

Resolution

This issue is resolved in vCenter Server 5.1 Update 1. To download vCenter Server 5.1 Update 1, see the VMware Download Center.
 
If you are unable to upgrade, see the workaround below:
  1. Navigate to Control Panel > Region & Language  > Location.
  2. Change the system local time to United States.

    This sets the system clock to the Gregorian calendar.
 
Note: The preceding link was correct as of December 04, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.

Update History

04/30/2013 - Added resolved vCenter Server 5.1 Update 1

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 5 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 5 Ratings
Actions
KB: