locked
Getting this error on some Client upgrades RRS feed

  • Question

  • MSI: Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\PresentationMode.   Verify that you have sufficient access to that key, or contact your support personnel.

    Anybody have thoughts. CCMclean does not clean up this registry and we can't manually remove it.

    Wednesday, January 2, 2013 7:11 PM

Answers

  • Had to take Ownership of the whole SMS Key.  The in PresentationMode then individually add full rights to the SIDs to delete them and after that was able to delete the key. Push out the client and install without issue.
    • Marked as answer by Paul024 Friday, January 4, 2013 6:58 PM
    Friday, January 4, 2013 6:58 PM

All replies

  • I doubt that is a terminating error. Where are you seeing this error? Is the client install truly not completing?

    Can you post the ccmsetup.log and client.msi.log from the clients on a file sharing service and post the links in this thread?


    Jason | http://blog.configmgrftw.com

    Wednesday, January 2, 2013 9:00 PM
  • here is the log when it fails:

    MSI: Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\PresentationMode.   Verify that you have sufficient access to that key, or contact your support personnel.  ccmsetup 1/2/2013 8:46:34 PM 14032 (0x36D0)
    MSI: Action 20:46:35: Rollback. Rolling back action: ccmsetup 1/2/2013 8:46:35 PM 14032 (0x36D0)
    File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
    Action: WriteRegistryValues.
    ErrorMessages:
    Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\PresentationMode.   Verify that you have sufficient access to that key, or contact your support personnel.
     ccmsetup 1/2/2013 8:46:46 PM 14032 (0x36D0)
    Client installation has failed too many times. Ccmsetup will now abort. ccmsetup 1/2/2013 8:46:46 PM 14032 (0x36D0)
    Sending Fallback Status Point message to 'SeverName', STATEID='313'. ccmsetup 1/2/2013 8:46:46 PM 14032 (0x36D0)
    Params to send FSP message '5.0.7804.1000 Deployment ExitCode: 1603 Action: WriteRegistryValues. ErrorMessages: Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\PresentationMode.   Verify that you have sufficient access to that key, or contact your support personnel.  ' ccmsetup 1/2/2013 8:46:46 PM 14032 (0x36D0)
    Request failed: 404 Not Found
     FSPStateMessage 1/2/2013 8:46:46 PM 14032 (0x36D0)
    InstallFromManifest failed 0x80070643 ccmsetup 1/2/2013 8:46:46 PM 14032 (0x36D0)
    Deleted file C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 1/2/2013 8:46:46 PM 14032 (0x36D0)
    CcmSetup failed with error code 0x80070643 ccmsetup 1/2/2013 8:46:46 PM 14032 (0x36D0)
    Thursday, January 3, 2013 2:07 PM
  • Have you reviewed that registry key and its permissions on one of these clients?

    Have you reviewed client.msi.log for any additional info?

    How are you initialing client install?


    Jason | http://blog.configmgrftw.com


    Thursday, January 3, 2013 4:18 PM
  • try the push install and than manual.

    Property(S): CompleteDialog_Info = The Configuration Manager Client setup was successful.
    Property(S): UserExitDialog_Title = Setup Aborted
    Property(S): UserExitDialog_SubTitle = Setup was cancelled
    Property(S): UserExitDialog_Info = The Configuration Manager Client setup was cancelled.
    Property(S): InstallErrorDialog_Title = Setup Aborted
    Property(S): InstallErrorDialog_SubTitle = Setup failed
    Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue.
    Property(S): UATData.9180931B_6ABA_475F_8007_1211E0D725BA = C:\Windows\CCM\UATData\
    Property(S): CcmDefaultPolicyAuthority = SMS:Client:Default:{D6804B3A-BFEC-4AB4-BFA5-FD9BECC80630}
    Property(S): D9F8C395_CAB8_491d_B8AC_179A1FE1BE77.9180931B_6ABA_475F_8007_1211E0D725BA = C:\Windows\CCM\UATData\D9F8C395-CAB8-491d-B8AC-179A1FE1BE77\
    Property(S): SMSSITECODE = 100
    Property(S): SystemFolder = C:\Windows\SysWOW64\
    Property(S): CcmInstallUtil = C:\Windows\CCM\
    Microsoft.ConfigurationManager.WinRTProvider.dll|Microsoft.ConfigurationManager.AssetProvider.dll|

    and

    MSI (s) (0C:A4) [10:55:37:840]: Note: 1: 1708
    MSI (s) (0C:A4) [10:55:37:841]: Product: Configuration Manager Client -- Installation operation failed.
    MSI (s) (0C:A4) [10:55:37:843]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.7804.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
    MSI (s) (0C:A4) [10:55:37:844]: Closing MSIHANDLE (33) of type 790542 for thread 4004
    MSI (s) (0C:A4) [10:55:37:935]: Deferring clean up of packages/files, if any exist
    MSI (s) (0C:A4) [10:55:37:935]: MainEngineThread is returning 1603
    MSI (s) (0C:F8) [10:55:37:944]: RESTART MANAGER: Session closed.
    MSI (s) (0C:F8) [10:55:37:944]: No System Restore sequence number for this installation.
    MSI (s) (0C:F8) [10:55:38:026]: User policy value 'DisableRollback' is 0
    MSI (s) (0C:F8) [10:55:38:026]: Machine policy value 'DisableRollback' is 0
    MSI (s) (0C:F8) [10:55:38:026]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (0C:F8) [10:55:38:027]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (0C:F8) [10:55:38:027]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (0C:F8) [10:55:38:028]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (0C:F8) [10:55:38:029]: Destroying RemoteAPI object.
    MSI (s) (0C:10) [10:55:38:029]: Custom Action Manager thread ending.
    MSI (c) (F0:40) [10:55:38:103]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (F0:40) [10:55:38:104]: MainEngineThread is returning 1603
    === Verbose logging stopped: 1/3/2013  10:55:38 ===

    Thursday, January 3, 2013 4:56 PM
  • Those log snippets have nothing of value: http://blogs.msdn.com/b/astebner/archive/2005/08/01/446328.aspx

    What about the registry key permissions? Have you reviewed them?


    Jason | http://blog.configmgrftw.com

    Thursday, January 3, 2013 5:16 PM
  • check permissions, seem good but can't change them anyway.

    The install fails trying to open HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\PresentationMode.  Wouldn't care if we could get rid of it when we uninstall old client and do a clean install.  Anybody know a way to remove this registry?

    Thursday, January 3, 2013 7:56 PM
  • But if you're going to troubleshoot an issue involving permissions of a registry key, the place to start is to examine those permissions and compare them to determine if they are "off" somehow or if something else is actually causing the failure like maybe the key not being properly created in the first place. To my knowledge, this is a new key for 2012 so knowing these things could help. Troubleshooting is about gathering facts and retracting what happened, what was supposed to happen, bad assumptions, etc. Without knowing all of the relevant facts and details, you can never figure out what's going wrong.

    Jason | http://blog.configmgrftw.com


    Thursday, January 3, 2013 8:01 PM
  • ok, the fact is we did compare and nothing is different with permissions to the 1800 other successful upgrades, except for these two computers. Even if these where different we can not change permission on this registry key. So we can not fully uninstall or fully install.  The failure happens trying to change this registry key, so the logs snips I pasted shows enough of what is happening. So what more is there to do? What mastery do you have to tell how this registry got corrupted during the upgrade and how to correct it?  What other logs or tools to find these answers?

    Thank you for your help, but I already know "issue involving permissions of a registry key" and it got corrupted.  So after days of trouble shooting, looking at logs, event viewers, comparing and  trying many different possible solutions.  I posted here to seek advice with someone that might have run into the same issue and found a solution.

    Friday, January 4, 2013 12:56 PM
  • Why can't you change permissions on the registry key?

    Jason | http://blog.configmgrftw.com

    Friday, January 4, 2013 3:36 PM
  • to have the rights. using either local or domain admin.
    That is the issue, that I can not find the cause of the corruption. That will not allow the install of the client to complete.  Can not find anything in the logs or event viewer to point to when or how it got corrupted.
    • Edited by Paul024 Friday, January 4, 2013 5:45 PM
    Friday, January 4, 2013 5:39 PM
  • Can you take ownership of the keys and then change rights?

    How about launching regedit using the System account (using psexec)?


    Jason | http://blog.configmgrftw.com

    • Proposed as answer by Derek Gary Wednesday, January 22, 2014 8:51 PM
    Friday, January 4, 2013 6:04 PM
  • Had to take Ownership of the whole SMS Key.  The in PresentationMode then individually add full rights to the SIDs to delete them and after that was able to delete the key. Push out the client and install without issue.
    • Marked as answer by Paul024 Friday, January 4, 2013 6:58 PM
    Friday, January 4, 2013 6:58 PM
  • I have been beating my head against the wall for weeks trying to SCCM client to install on two of my machines. I have tried everything I could find and this WORKED!!! Thank you
    Thursday, September 22, 2016 8:16 PM