Alarms -"deploy ovf" "A general system error occurred: PBM error occurred during PreCreateCheckCallback:invalid state" "delete file DatastoreX"
search cancel

Alarms -"deploy ovf" "A general system error occurred: PBM error occurred during PreCreateCheckCallback:invalid state" "delete file DatastoreX"

book

Article ID: 411964

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

In the vSphere client, we are seeing PBM call error messages every second:

  • Alarms -"deploy ovf" "A general system error occurred: PBM error occurred during PreCreateCheckCallback: invalid state" "delete file DatastoreX"

The following are seen in the var/log/vmware/sps.log file:

  • YYYY-MM-DDT10:08:21.307-07:00 [pool-4-thread-19] ERROR opId=45c24e50-01-01-01 com.vmware.vim.storage.common.VmodlErrorStrings - Login to PBM failed com.vmware.vim.storage.common.fault.LoginException: com.vmware.vim.sso.client.exception.MalformedTokenException: Error parsing SAML token. at com.vmware.vim.storage.common.security.CommonSessionManager.loginByToken(CommonSessionManager.java:176) ~[storage-commons-1.0.jar:?]
  • YYYY-MM-DDT10:08:21.307-07:00 [pool-4-thread-19] ERROR opId=45c24e50-01-01-01 com.vmware.vim.storage.common.security.CommonSessionManager - Login by token failed com.vmware.vim.sso.client.exception.MalformedTokenException: Error parsing SAML token. at com.vmware.identity.token.impl.SamlTokenImpl.parseTokenXmlToDom(SamlTokenImpl.java:759) ~[samltoken-1.0.jar:?]

 

Environment

VMware vCenter Server 7.x

Cause

Incorrect Service Registrations are causing PBM login fails.

Resolution

 

  • Take a snapshot of the vCenter Server VM
  • Download the lsdoctor script from the following KB: https://knowledge.broadcom.com/external/article/320837/using-the-lsdoctor-tool.html
  • Downloaded the lsdoctor script and uploaded it into the root of the vcenter server using WINSCP
  • SHH into the affected vCenter Server with root credentials
  • Navigate to the directory where the lsdoctor file was uploaded
  • Extracted the zip file
  • Navigated into the lsdoctor directory and ran lsdoctor -u
  • Acknowledge the disclaimer and choose option 2 to update the service registrations

Restarted the vcenter server services by running

  • service-control –stop –all && service-control –start –all

Additional Information