An administrator may experience an Import VPG task fail via the Diagnostic Utility due to Journal Hard Size/Warning Threshold attributes.

In the XML example below, it is seen that LimitInMb is set while LimitInPercent is, effectively, not in use:

                <b:VMJournalSettings>
                  <b:HardLimit>
                    <b:LimitInMb>153600</b:LimitInMb>
                    <b:LimitInPercent>4294967285</b:LimitInPercent>
                  </b:HardLimit>
                  <b:WarningThreshold>
                    <b:LimitInMb>115200</b:LimitInMb>
                    <b:LimitInPercent>4294967285</b:LimitInPercent>
                  </b:WarningThreshold>
                </b:VMJournalSettings>

While looking at the XML and comparing to the error output, it is clear that the import is not accurate compared to what is expected in the Storage Profile.

Import VPG fails with similar error below:

Errors: ValuesAreNotCorrespondsServiceProfile: Below fileds Warning Journal Percent[ Profile value 50 , New Value 0 ] , Hard Limit Journal Percent[ Profile value 75 , New Value 0 ] are not corresponds service profile definitions

To resolve the issue, the XML that was exported should be updated so that the LimitInPercent are accurate compared to what is in the alert and effectively disabling LimitInPercent with the large integer seen previously for LimitInPercent field:

                <b:VMJournalSettings>
                    <b:HardLimit>
                      <b:LimitInMb>4294967285</b:LimitInMb>
                      <b:LimitInPercent>75</b:LimitInPercent>
                    </b:HardLimit>
                    <b:WarningThreshold>
                      <b:LimitInMb>4294967285</b:LimitInMb>
                      <b:LimitInPercent>50</b:LimitInPercent>
                    </b:WarningThreshold>
                </b:VMJournalSettings>

Once the edits are made/saved, attempt the Import VPG via Diagnostic Utility once more.