locked
Reinstalling client on web server RRS feed

  • Question

  • I am having currently having a baffling time trying to get this client reinstalled.  We had it installed but it was pointed at our old site.  When we tried to change the site code it complained that the installation was corrupt or something.  I have been doing my best to get the client removed.  At this point ccmsetup.exe /unistall says that it is removed.  The control panel icons are gone, and the services have been removed. 

    I am not trying to reinstall the client and it is consistently failing.  Any help would be great.  I am fairly stuck on this one.

    Full log files can be found here: http://cid-1baf411c0b2a713d.office.live.com/feed.aspx/.Public/ccmsetup

    Here are snippets of my log files:

    -----------------  ccmsetup.log  -----------------

    MSI: Action 9:50:46: RegisterUser. Registering user ccmsetup 6/21/2010 9:50:46 AM 7716 (0x1E24)
    MSI: Action 9:50:46: CcmFixupServiceConfigInit.  ccmsetup 6/21/2010 9:50:46 AM 7716 (0x1E24)
    MSI: Action 9:50:47: CcmSetObjectSecurityInit. Applying security permissions ccmsetup 6/21/2010 9:50:47 AM 7716 (0x1E24)
    MSI: Setup failed due to unexpected circumstances
    The error code is 80070534 ccmsetup 6/21/2010 9:50:47 AM 7716 (0x1E24)
    Installation failed with error code 1603 ccmsetup 6/21/2010 9:50:47 AM 7716 (0x1E24)

    -----------------  client.msi.log  -----------------

    [9:50:47] @@ERR:25001
    MSI (s) (68!10) [09:50:47:296]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances
    The error code is 80070534

    MSI (s) (68!10) [09:50:47:312]: Closing MSIHANDLE (5018) of type 790531 for thread 5136
    MSI (s) (68!10) [09:50:47:312]: Closing MSIHANDLE (5017) of type 790540 for thread 5136
    MSI (s) (68!10) [09:50:47:312]: Closing MSIHANDLE (5025) of type 790531 for thread 5136
    MSI (s) (68!10) [09:50:47:312]: Closing MSIHANDLE (5016) of type 790541 for thread 5136
    MSI (s) (68:54) [09:50:47:312]: Closing MSIHANDLE (5015) of type 790542 for thread 7496
    Error 25001. Setup failed due to unexpected circumstances
    The error code is 80070534
    ...

    Property(S): SmsDeinstallDesktopClient_ActionText = Deinstalling the SMS Legacy Client or SMS 2.0 Client
    Property(S): SmsDeinstallDesktopClient_StoppingComponents_ActionText = Stopping SMS Legacy Client or SMS 2.0 Client Components
    Property(S): SmsDeinstallDesktopClient_DeinstallingComponents_ActionText = Deinstalling SMS Legacy Client or SMS 2.0 Client Components
    Property(S): SmsDetectDowngrade_ErrorMessage = A newer version of the Configuration Manager Client is already installed
    Property(S): SmsDetectColocationDowngrade_ErrorMessage = A newer version of the SMS Management Point is installed. Cannot continue installing this version of the client.
    Property(S): SmsMigrateQuarantineUpdateSchema_ActionText = Migrating content download schema.
    Property(S): SmsDetectUpgrade_ErrorMessage = An older version of the SMS Management Point is installed. Please upgrade the Management Point before attempting to upgrade the client.
    Property(S): SmsManagementPointName = Configuration Manager Client
    ...

    Property(S): CompleteDialog_Title = Setup Complete
    Property(S): CompleteDialog_SubTitle = Setup has finished updating your system.
    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.

    Monday, June 21, 2010 2:38 PM

Answers

  • Have you tried to search for "value 3" in the client.msi.log?  The error is usually around that area.  It might help to troubleshoot.

    Thanks,

    Minh.


    Minh
    Tuesday, June 22, 2010 8:20 PM

All replies

  • I will give you a totally unsupported step you can "try" at your own risk....

    I've had something like this happen before and I ran ccmclean from the SMS 2003 toolkit and then rebooted and installed the client with no issue at all.

    AGAIN, this is unsupported so take it for what's it's worth. Also if this server is a MP it will be broken if you run ccmclean with the wrong switches.

     

     


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
    Monday, June 21, 2010 7:12 PM
  • Hi,

    just found a related Blogpost with a solution.

    http://ms31337.spaces.live.com/blog/cns!41326BF7507BE401!113.entry


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, June 22, 2010 8:47 AM
  • I have run ccmclean, but without the reboot.  This is a production server that I have been working on for someone else, so I haven't exactly been able to be too heavy handed with is.
    Tuesday, June 22, 2010 1:50 PM
  • I have seen this blog post.  There are a number of reasons why this may not be related.  As far as I know, this server has never been syspreped or imaged.  Also, the errors I am getting don't seem to be related to BITS. 

    Thanks for the suggestion however.  This is the only lead that I have right now.  I will probably recommend we try this but it has to be scheduled during a maintenance and all that.

    Matt

    Tuesday, June 22, 2010 1:52 PM
  • I have run ccmclean, but without the reboot. 

    In all honesty the reboot is probably me being overly cautious. Did it still fail after running ccmclean?

     

     

     


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
    Tuesday, June 22, 2010 2:18 PM
  • Correct John, these log files where collected after ccmclean had been run.

    Matt

    Tuesday, June 22, 2010 2:54 PM
  • Sorry, I am out of ideas then.

     

     


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
    Tuesday, June 22, 2010 3:07 PM
  • Have you tried to search for "value 3" in the client.msi.log?  The error is usually around that area.  It might help to troubleshoot.

    Thanks,

    Minh.


    Minh
    Tuesday, June 22, 2010 8:20 PM