Search the VMware Knowledge Base (KB)
View by Article ID

Installing Profile-Driven Storage via vCenter Server 5.1 fails with an error code 1603 (2047080)

  • 14 Ratings

Symptoms

When performing an in-place vCenter Server upgrade from 5.0 to 5.1a or 5.1b, you experience these symptoms:
  • You are unable to install Profile-Driven Storage via vCenter Server.
  • Installing Profile-Driven Storage via vCenter Server fails with an error code 1603.
  • In the vim-sps-msi.log file, you see entries similar to:

    MSI (s) (80:E4) [12:58:26:977]: Note: 1: 1708
    MSI (s) (80:E4) [12:58:26:977]: Product: VMware vSphere Profile-Driven Storage -- Installation operation failed.
    MSI (s) (80:E4) [12:58:26:977]: Windows Installer installed the product. Product Name: VMware vSphere Profile-Driven Storage. Product Version: 5.1.0.34460. Product Language: 1033. Manufacturer: VMware, Inc.. Installation success or error status: 1603.
    MSI (s) (80:E4) [12:58:27:087]: Deferring clean up of packages/files, if any exist
    MSI (s) (80:E4) [12:58:27:087]: MainEngineThread is returning 1603
    MSI (s) (80:B0) [12:58:27:087]: No System Restore sequence number for this installation.
    === Logging stopped: 2/12/2013 12:58:26 ===
    MSI (s) (80:B0) [12:58:27:087]: User policy value 'DisableRollback' is 0
    MSI (s) (80:B0) [12:58:27:087]: Machine policy value 'DisableRollback' is 0
    MSI (s) (80:B0) [12:58:27:087]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (80:B0) [12:58:27:087]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (80:B0) [12:58:27:087]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (80:B0) [12:58:27:087]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (s) (80:B0) [12:58:27:087]: Post-install cleanup: removing installer file 'C:\Windows\Installer\5c71d.mst'
    MSI (s) (80:B0) [12:58:27:087]: Restoring environment variables
    MSI (s) (80:B0) [12:58:27:087]: Destroying RemoteAPI object.
    MSI (s) (80:D8) [12:58:27:087]: Custom Action Manager thread ending.
    MSI (c) (10:74) [12:58:27:087]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (c) (10:74) [12:58:27:087]: MainEngineThread is returning 1603


    Note: The vim-sps-mis.log is located in the %temp% directory during installation of the Profile-Driven Storage service. The log will be located in temp/1 or temp/2.

  • If the Look Up service URL has an sts string, installing the Profile-Driven Storage using the vCenter Server installer fails with a message similar to:

    The wizard was interrupted before Profile-Driven Storage could be completely installed
    .

  • The vpxd service is unable to start because the sts URL in the vpxd.cfg file is incorrect.
  • The vpxd.log (located at C:\ProgramData\VMware\VMware VirtualCenter\Logs) contains entries similar to:
     
    :57:51.290-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [CheckTokenValidity] Refreshing SSO token ...

    :57:51.290-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [RefreshSsoToken]
    :57:51.322-05:00 [04276 error '[SSO][SsoAdminFacadeImpl]'] [RefreshSsoToken] AcquireToken exception: Unexpected SOAP fault: ServerFaultCode; request failed.
    :57:51.322-05:00 [04276 error '[SSO]'] [UserDirectorySso] GetDefaultPrincipal NormalizationException: RemoteGetDomainNames RuntimeServiceFault exception: sso.fault.RuntimeServiceFault
    12:57:51.322-05:00 [04276 info '[SSO]'] [UserDirectorySso] GetDefaultPrincipal(, true)
    12:57:51.322-05:00 [04276 info '[SSO]'] [UserDirectorySso] GetUserInfo(, true)
    T12:57:51.322-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [GetDomains]
    T12:57:51.322-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [LazyInitAdmin] Initializing
    T12:57:51.322-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [InitSsoAdminServices]
    T12:57:51.322-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [CreateAdminSsoServiceContent] Try to connect to SSO Admin server.
    T12:57:51.369-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [InitSsoAdminServices] successful.
    T12:57:51.369-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [LoginToAdmin]
    T12:57:51.369-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [CheckTokenValidity]
    T12:57:51.369-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [CheckTokenValidity] Refreshing SSO token ...
    T12:57:51.369-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [RefreshSsoToken]
    T12:57:51.400-05:00 [04276 error '[SSO][SsoAdminFacadeImpl]'] [RefreshSsoToken] AcquireToken exception: Unexpected SOAP fault: ServerFaultCode; request failed.
    T12:57:51.400-05:00 [04276 info '[SSO]'] [UserDirectorySso] GetUserInfo NormalizationException: RemoteGetDomainNames RuntimeServiceFault exception: sso.fault.RuntimeServiceFault
    T12:57:51.400-05:00 [04276 error '[SSO]'] [UserDirectorySso] NormalizeUserName AuthException: Authorize Exception
    T12:57:51.400-05:00 [04276 info '[SSO]'] [UserDirectorySso] GetUserInfo(, true)
    T12:57:51.400-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [GetDomains]
    T12:57:51.400-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [LazyInitAdmin] Initializing
    T12:57:51.400-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [InitSsoAdminServices]
    T12:57:51.400-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [CreateAdminSsoServiceContent] Try to connect to SSO Admin server.
    T12:57:51.415-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [InitSsoAdminServices] successful.
    T12:57:51.415-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [LoginToAdmin]
    T12:57:51.415-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [CheckTokenValidity]
    T12:57:51.415-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [CheckTokenValidity] Refreshing SSO token ...
    T12:57:51.415-05:00 [04276 info '[SSO][SsoAdminFacadeImpl]'] [RefreshSsoToken]
    T12:57:51.447-05:00 [04276 error '[SSO][SsoAdminFacadeImpl]'] [RefreshSsoToken] AcquireToken exception: Unexpected SOAP fault: ServerFaultCode; request failed.
    T12:57:51.447-05:00 [04276 info '[SSO]'] [UserDirectorySso] GetUserInfo NormalizationException: RemoteGetDomainNames RuntimeServiceFault exception: sso.fault.RuntimeServiceFault
    T12:57:51.447-05:00 [04276 error 'Default'] Failed to add default permission: user not found
    T12:57:51.447-05:00 [04276 error 'Default'] Cannot start authorize - system has no access rules
    T12:57:51.447-05:00 [04276 error 'Default'] [Auth] Failed to initialize: <class Vmacore::Authorize::AuthException(Authorize Exception)>
    T12:57:51.447-05:00 [04276 error 'authvpxdAuthorize'] Failed to initialize security
    T12:57:51.447-05:00 [04276 info 'Default'] Shutting down VMware VirtualCenter...
    T12:57:51.447-05:00 [04276 info 'vpxdvpxdSupportManager'] Wrote uptime information
    T12:57:57.634-05:00 [05036 warning 'VpxProfiler' opID=SWI-52fed480] VpxUtil_InvokeWithOpId [TotalTime] took 12000 ms
    T12:58:01.009-05:00 [03600 info 'commonvpxLro' opID=task-internal-1-1e703d8e] [VpxLRO] -- FINISH task-internal-1 -- -- VpxdDrmMainLoop --
    T12:58:09.634-05:00 [05112 warning 'VpxProfiler' opID=SWI-d8770920] VpxUtil_InvokeWithOpId [TotalTime] took 12000 m

  • The ssoLocations.txt file contains a message similar to:

    sts=https://lookup_service-ip:7444/ims/STSService?wsdl

  • The vpxd.cfg file contains an incorrect sts URL similar to:

    <sts>
    <uri>https://lookup_service-ip:7444/sso-adminserver/sdk</uri>
    </sts>

Cause

This issue occurs due to an error in the sts URL in the vpxd.cfg file.

Resolution

This is a known issue in VMware vCenter Server 5.1.0a and 5.1.0b.
 
This issue is resolved in vCenter Server 5.5, available at VMware Downloads. For more information, see the VMware vSphere 5.5 Release Notes.
 
To work around this issue when you do not want to upgrade, update the sts URL in the vpxd.cfg file.

Note: The vpxd.cfg file is located at C:\ProgramData\VMware\VMware VirtualCenter.
To update the sts URL in the vpxd.cfg file:
  1. Open the SsoData/ssoLocations.txt file using a text editor.
  2. This file may be located in the temporary ( %tmp%) folder, if it is not use the lookup service to get the URL:

    1. Open a command prompt as administrator, change the directory to:

      C:\Program Files\VMware\Infrastructure\VirtualCenter Server\ssoregtool

      Note
      : Adjust the commands depending on where you have installed vCenter Server.

    2. Run the commands:

      SET JAVA_HOME=C:\Program Files\VMware\Infrastructure\jre

      regtool.cmd storeSsoData -d https://SSO_Server_FQDN:7444/lookupservice/sdk -f output_path

    3. Open the location you specified in step 2.b in the regtool command and find the sts URL in the ssoLocations.txt file.

  3. Locate the sts URL within the SsoData/ssoLocations.txt file.

    For example:

    groupcheck = https://<lookup service-ip>:7444/sso-adminserver/sdk
    admin = https://<lookup service-ip>:7444/sso-adminserver/sdk

    sts = https://<lookup service-ip>:7444/sso-adminserver/sdk


  4. Copy the sts URL from the ssoLocations.txt file and update the sts URL in the vpxd.cfg, for example:

    <sts>
    <uri>https://<lookup service-ip>:7444/sso-adminserver/sdk</uri>

    </sts>

Note: Run the vCenter Server installer to install Profile-Driven Service.

Additional Information

See Also

Update History

04/09/2013 - Added Step 4 to run vCenter Server installer.

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

  • 14 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)




Please enter the Captcha code before clicking Submit.
  • 14 Ratings
Actions
KB: