VMware Cloud Community
cheng77
Contributor
Contributor

Error encountered while exporting PBM Properties

Facing the error during the upgrading. Any Idea?

Thanks

2015-04-14T10:06:06.177Z INFO wf.wf_processor State Export com.vmware.vmsyslogcollector has succeeded.

2015-04-14T10:06:06.178Z INFO wf.wf_processor Start executing State Export com.vmware.sps

2015-04-14T10:06:06.191Z INFO upgrade.states.component_states sps:Export: Built context {'destinationVcPlatform': 'Windows', 'resourceDir': 'Y:\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\upgrade_working_directory', 'infrastructureUsername': u'administrator@vsphere.local', 'sourceSsoPassword': 'CENSORED', 'exportDir': u'C:\\ProgramData\\VMware\\vCenterServer\\export\\sps', 'locale': 'en', 'destinationPlatform': 'Windows', 'destinationVcVersion': '6.0', 'cmUrl': u'https://127.0.0.1:443/cm/sdk/', 'systemExportDir': u'C:\\ProgramData\\VMware\\vCenterServer\\export\\system-data', 'infrastructureHttpsPort': u'443', 'sourcePlatform': 'Windows', 'sourceVcVersion': u'5.5', 'sourceSsoVersion': u'5.5', 'infrastructureHost': u'127.0.0.1', 'destinationSsoVersion': '6.0', 'sourceVcPlatform': 'Windows', 'infrastructurePassword': 'CENSORED', 'sourceSsoUsername': None}

2015-04-14T10:06:06.207Z INFO upgrade.states.component_states sps:Export: Start executing component phase ['Y:\\PFiles\\VMware\\CIS\\python\\python.exe', 'Y:\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\payload\\componentPhaseLauncher.py', '--compdir', 'Y:\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\payload\\component-scripts', '--compName', u'com.vmware.sps', '--dynamicContextFile', u'Y:\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\upgrade_working_directory\\com.vmware.sps\\dynamic-context-2015_04_14_18_06_06', '--logFileName', u'Export_com.vmware.sps_2015_04_14_18_06.log', '--logDir', 'C:\\Users\\ADMINI~1.EBC\\AppData\\Local\\Temp\\vcsUpgrade', '--pythonPath', 'Y:\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\libs\\pyVim.zip,Y:\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\libs\\pyVmomi.zip,Y:\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\libs\\sdk,Y:\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\libs\\status-reporting-sdk', '--silent', 'False', u'sps', u'Export']

2015-04-14T10:06:06.226Z INFO upgrade.states.component_states sps:Export: didn't have progress. Next report will come after 60 seconds

2015-04-14T10:06:07.253Z INFO upgrade.states.component_states sps:Export: 2015-04-14T10:06:06.312Z INFO __main__ Set root upgrade folder to: Y:\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts

2015-04-14T10:06:07.257Z INFO upgrade.states.component_states sps:Export: 2015-04-14T10:06:06.545Z INFO __main__ Context file C:\ProgramData\VMware\vCenterServer\export\system-data\upgrade-com.vmware.sps-upgradeContext does not exist. Use default context

2015-04-14T10:06:07.259Z INFO upgrade.states.component_states sps:Export: 2015-04-14T10:06:06.546Z INFO extensions Found upgrade phase <module 'sps' from 'Y:\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\sps\__init__.pyc'>:Export'

2015-04-14T10:06:07.259Z INFO upgrade.states.component_states sps:Export: 2015-04-14T10:06:06.546Z INFO extensions Executing upgrade phase '<module 'sps' from 'Y:\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\sps\__init__.pyc'>:Export' with context {u'destinationVcPlatform': u'Windows', u'resourceDir': u'Y:\\PFiles\\VMware\\CIS\\cis_upgrade_runner\\upgrade_working_directory', u'infrastructureUsername': u'administrator@vsphere.local', u'sourceSsoPassword': 'CENSORED', u'exportDir': u'C:\\ProgramData\\VMware\\vCenterServer\\export\\sps', u'locale': u'en', u'destinationPlatform': u'Windows', u'destinationVcVersion': u'6.0', u'cmUrl': u'https://127.0.0.1:443/cm/sdk/', u'systemExportDir': u'C:\\ProgramData\\VMware\\vCenterServer\\export\\system-data', u'sourcePlatform': u'Windows', 'logDir': 'C:\\Users\\ADMINI~1.EBC\\AppData\\Local\\Temp\\vcsUpgrade', u'sourceVcVersion': u'5.5', u'sourceSsoVersion': u'5.5', u'infrastructureHost': u'127.0.0.1', u'infrastructureHttpsPort': u'443', u'sourceVcPlatform': u'Windows', u'infrastructurePassword': 'CENSORED', u'sourceSsoUsername': None, u'destinationSsoVersion': u'6.0'}.

2015-04-14T10:06:07.260Z INFO upgrade.states.component_states sps:Export: 2015-04-14T10:06:06.546Z INFO sps Executing SPS Export phase...

2015-04-14T10:06:07.262Z INFO upgrade.states.component_states sps:Export: 2015-04-14T10:06:06.548Z ERROR transport.local NOT FOUND: Cannot read registry. Error: [Error 2] The system cannot find the file specified

2015-04-14T10:06:07.263Z INFO upgrade.states.component_states sps:Export: 2015-04-14T10:06:06.548Z ERROR sps Exception  while exporting PBM Properties

2015-04-14T10:06:07.263Z INFO upgrade.states.component_states sps:Export: 2015-04-14T10:06:06.549Z ERROR __main__ Upgrade Phase 'sps:Export' failed. Exception: Error encountered while exporting PBM Properties

2015-04-14T10:06:07.263Z INFO upgrade.states.component_states sps:Export: Traceback (most recent call last):

2015-04-14T10:06:07.265Z INFO upgrade.states.component_states sps:Export:   File "Y:\PFiles\VMware\CIS\cis_upgrade_runner\payload\componentPhaseLauncher.py", line 379, in main

2015-04-14T10:06:07.266Z INFO upgrade.states.component_states sps:Export:     executionResult = systemExtension(exeContext)

2015-04-14T10:06:07.266Z INFO upgrade.states.component_states sps:Export:   File "Y:\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\extensions.py", line 94, in __call__

2015-04-14T10:06:07.266Z INFO upgrade.states.component_states sps:Export:     result = self.extension(*args)

2015-04-14T10:06:07.267Z INFO upgrade.states.component_states sps:Export:   File "Y:\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\extensions.py", line 110, in _func

2015-04-14T10:06:07.269Z INFO upgrade.states.component_states sps:Export:     return func(*args)

2015-04-14T10:06:07.270Z INFO upgrade.states.component_states sps:Export:   File "Y:\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\sps\__init__.py", line 115, in exportData

2015-04-14T10:06:07.272Z INFO upgrade.states.component_states sps:Export:     raise raiseUpgradeFailed("exporting PBM Properties")

2015-04-14T10:06:07.273Z INFO upgrade.states.component_states sps:Export:   File "Y:\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\sps\__init__.py", line 42, in raiseUpgradeFailed

2015-04-14T10:06:07.273Z INFO upgrade.states.component_states sps:Export:     raise PermanentError(cause=errStr, resolution=resStr)

2015-04-14T10:06:07.275Z INFO upgrade.states.component_states sps:Export: PermanentError: Error encountered while exporting PBM Properties

2015-04-14T10:06:07.276Z INFO upgrade.states.component_states sps:Export: Script completed for 1.02300000191 secs with return-code='1', and executionId=5a30cc52-5404-45a3-964a-06c6915e9e67

2015-04-14T10:06:07.279Z ERROR upgrade.states.component_states sps:Export: Remote script failed with an error [PermanentError()]

2015-04-14T10:06:07.280Z ERROR upgrade.states.component_states sps:Export: failed with permanent error. For details take a look at Export_com.vmware.sps_2015_04_14_18_06.log.

2015-04-14T10:06:07.315Z WARNING wf.wf_processor State Export com.vmware.sps has failed.

2015-04-14T10:06:07.316Z WARNING root stopping status aggregation...

2015-04-14T10:06:07.346Z INFO utils.logs_collector Start collecting logs in C:\Users\ADMINI~1.EBC\AppData\Local\Temp\vcsUpgrade\export-logs_2015-04-14-18-06.zip

2015-04-14T10:06:07.348Z INFO deployer.migration_env_deployer Cleaning-up migration environment...

2015-04-14T10:06:07.348Z INFO deployer.migration_env_deployer Cleaning up target: Windows target with address=127.0.0.1

2015-04-14T10:06:07.348Z INFO deployer.migration_env_deployer The target Windows target with address=127.0.0.1 is already cleaned up

2015-04-14T10:06:07.352Z ERROR __main__ Upgrade mode export failed

4 Replies
maxim315
Enthusiast
Enthusiast

having a same error. anyone, help?

0 Kudos
Murali_M0han
Contributor
Contributor

pbm.properties file is part of Profile Driven Storage

Check "C:\Program Files\VMware\Infrastructure\Profile-Driven Storage\conf" folder

If the pbm.properties file is missing, You will have to re-install previous version of vCenter

If Profile Driven Storage is missing, Just run previous version of vCenter installer. It will install it.

Then try running 6.0 installation again.

Good luck Smiley Happy

rhinbourgeois
Contributor
Contributor

I had this same issue today. The last poster pointed me in the right direction, but not without some stumbling on my part. So here is a for dummies (me), way to do it inside of Windows:

From the Run command type: appwiz.cpl

Navigate to VMware vCenter Server and select Change

Let the installer run, and it should install the missing components

Proceed with the upgrade.

0 Kudos
future2000
Enthusiast
Enthusiast

Had exactly the same issue with a vCenter 6.0 Update 1 upgrade from vCenter 5.5U2e today. The comments are correct. The profile driven storage service was missing from vCenter. From AppWiz.cpl running the vCenter installer (change) option then installed the Profile Driven storage service silently. The service was then running.

The installation of vCenter 6.0 Update 1 then continued successfully.

0 Kudos