locked
MSI: PERCENTDISKSPACE out of range. A number between 1 and 99 expected. RRS feed

  • Question

  • Hello,

    Getting the error "PERCENTDISKSPACE out of range" in ccmsetup.log. Please help to solve the issue

    MSI: Action 0:51:18: FileCost. Computing space requirements

    MSI: Action 0:51:18: PolicyDefinitionsENUS.50F68C19_42FD_4094_A3C6_DF681B809B3A.

    MSI: Action 0:51:18: PolicyDefinitions.50F68C19_42FD_4094_A3C6_DF681B809B3A. 

    MSI: Action 0:51:18: WBEM.812B0603_EFD0_4199_8B2F_F17F6A0D5261. 

    MSI: Action 0:51:18: CostFinalize. Computing space requirements

    MSI: Action 0:51:18: MigrateFeatureStates. Migrating feature states from related applications

    MSI: Action 0:51:18: SmsSwDistSetCacheDir. This custom action determines if there is an existing cache directory available or not. If not, it creates one and configures it to be used by MSI.

    MSI: PERCENTDISKSPACE out of range. A number between 1 and 99 expected.

    File C:\WINDOWS\ccmsetup\{4D87A80B-6971-43EF-A59F-8088D214378A}\client.msi installation failed. Error text: ExitCode: 1603
    Action: SmsSwDistSetCacheDir.
    ErrorMessages:
    PERCENTDISKSPACE out of range. A number between 1 and 99 expected.

    Regards,

    Boopathi S

    Wednesday, September 30, 2015 4:11 PM

Answers

  • Please provide context when posting log snippets. The above is absolutely meaningless without knowing what you are doing and why. It's clear the log is from ccmsetup during client installation, but how was this client installation triggered?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, September 30, 2015 4:54 PM

All replies

  • Please provide context when posting log snippets. The above is absolutely meaningless without knowing what you are doing and why. It's clear the log is from ccmsetup during client installation, but how was this client installation triggered?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, September 30, 2015 4:54 PM
  • Please provide context when posting log snippets. The above is absolutely meaningless without knowing what you are doing and why.  It's clear the log is from ccmsetup during client installation, but how was this client installation triggered?

    .. plus what parameters have been used.


    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, September 30, 2015 5:01 PM