“Error encountered while exporting PBM Properties” after upgrade
Article ID: 301208
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Restarting the profile driven service resolves the issue.
Symptoms:
Symptoms:
- Unable to export SPS service after upgrading from vCenter Service 5.5 to 6.0.
- In the %TEMP%\vminst.log file, you see entry similar to:
2016-11-07 13:39:52.456-07:00| vcsInstUtil-3634789| I: Entering function: ParseStatusFile
2016-11-07 13:39:52.456-07:00| vcsInstUtil-3634789| I: ParseStatusFile: curr error msg: "Error encountered while exporting PBM Properties"
2016-11-07 13:39:52.456-07:00| vcsInstUtil-3634789| E: ParseStatusFile: Displaying error message for " ": "Error encountered while exporting PBM Properties
- In the vc-support-bundle\vcsUpgrade\upgradeRunner.log file, you see entries similar to:
2016-11-07T20:39:52.437Z INFO upgrade.states.component_states sps:Export: 2016-11-07T20:39:51.539Z INFO sps Executing SPS Export phase...
2016-11-07T20:39:52.437Z INFO upgrade.states.component_states sps:Export: 2016-11-07T20:39:51.539Z ERROR transport.local NOT FOUND: Cannot read registry. Error: [Error 2] The system cannot find the file specified
2016-11-07T20:39:52.437Z INFO upgrade.states.component_states sps:Export: 2016-11-07T20:39:51.539Z ERROR sps Exception while exporting PBM Properties
2016-11-07T20:39:52.438Z INFO upgrade.states.component_states sps:Export: 2016-11-07T20:39:51.539Z ERROR __main__ Upgrade Phase 'sps:Export' failed. Exception: Error encountered while exporting PBM Properties
2016-11-07T20:39:52.444Z ERROR upgrade.states.component_states sps:Export: Remote script failed with an error [PermanentError()]
2016-11-07T20:39:52.444Z ERROR upgrade.states.component_states sps:Export: failed with permanent error. For details take a look at Export_com.vmware.sps_2016_11_07_13_39.log.
2016-11-07T20:39:52.448Z WARNING wf.wf_processor State Export com.vmware.sps has failed.
2016-11-07T20:39:52.450Z WARNING root stopping status aggregation...
- In the Export_com.vmware.sps_2016_11_07_13_39.log file, you see entries similar to:
2016-11-07T20:39:51.539Z INFO sps Executing SPS Export phase...
2016-11-07T20:39:51.539Z ERROR transport.local NOT FOUND: Cannot read registry. Error: [Error 2] The system cannot find the file specified
2016-11-07T20:39:51.539Z ERROR sps Exception while exporting PBM Properties
- The profile driven storage service is not listed as a service under WIndow's Services (services.msc).
- Folder for profile driven storage is missing under C:\Program Files\VMware\Infrastructure .
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
Environment
VMware vCenter Server 5.5.x
Cause
This issue occurs if the VMware vSphere Profile-driven storage component is not installed correctly or is corrupted.
Resolution
To resolve this issue, use one of these options:
- If the profile driven storage service is listed under Windows Services, try restarting the service.
- If the profile driven storage service is not listed under Windows Services, repair the vCenter Server installation:
- Navigate to Control Panel > Program and Features.
- Right click on vCenter Server.
- Select Change.
- If requested for installation media, browse vCenter 5.5 ISO and point to vCenter-server.msi.
- The installation automatically installs the missing VMware vSphere Profile Driven Storage component and completes the installation.
- After installation, ensure profile driven storage service is listed in windows services before attempting to run the upgrade again
Additional Information
Feedback
Yes
No
Powered by
