none
Exit Code 1639 during client install RRS feed

  • Question

  • Hi Everyone,

     

    Been having issues with a machine, and trying to reinstall the SCCM client to repair it, after a repair failed.

     

    I've uninstalled just fine, but I'm unable to reinstall! Here's what I think is the important part of the log:

    <![LOG[Successfully downloaded client files.]LOG]!><time="15:08:15.503+-60" date="08-15-2012" component="ccmsetup" context="" type="1" thread="6072" file="ccmsetup.cpp:2539">
    <![LOG[Searching for available transform]LOG]!><time="15:08:15.503+-60" date="08-15-2012" component="ccmsetup" context="" type="1" thread="6072" file="ccmsetup.cpp:8873">
    <![LOG[Failed to find resource file 'client.mst']LOG]!><time="15:08:15.503+-60" date="08-15-2012" component="ccmsetup" context="" type="3" thread="6072" file="util.cpp:718">
    <![LOG[No transform available for this locale. Installation will proceed with no transformation.]LOG]!><time="15:08:15.503+-60" date="08-15-2012" component="ccmsetup" context="" type="1" thread="6072" file="ccmsetup.cpp:8912">
    <![LOG[Updated security on object C:\WINNT\system32\ccmsetup\.]LOG]!><time="15:08:15.550+-60" date="08-15-2012" component="ccmsetup" context="" type="0" thread="6072" file="ccmsetup.cpp:8849">
    <![LOG[An MP does not exist on this machine.]LOG]!><time="15:08:15.597+-60" date="08-15-2012" component="ccmsetup" context="" type="1" thread="6072" file="msiutil.cpp:653">
    <![LOG[No client is currently installed.]LOG]!><time="15:08:15.597+-60" date="08-15-2012" component="ccmsetup" context="" type="1" thread="6072" file="msiutil.cpp:667">
    <![LOG[Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931}]LOG]!><time="15:08:16.958+-60" date="08-15-2012" component="ccmsetup" context="" type="1" thread="6072" file="ccmsetup.cpp:7701">
    <![LOG[MSI PROPERTIES are  CCMLOGLEVEL="0" /SOURCE:D:\MICROSOFT CORPORATION\SCCM CLIENT\2007 SP2="/source:D:\Microsoft Corporation\SCCM Client\2007 SP2" CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL]LOG]!><time="15:08:16.958+-60" date="08-15-2012" component="ccmsetup" context="" type="1" thread="6072" file="ccmsetup.cpp:7740">
    <![LOG[IsFileMicrosoftTrusted Verified file 'C:\WINNT\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' is MS signed.]LOG]!><time="15:08:32.443+-60" date="08-15-2012" component="ccmsetup" context="" type="1" thread="6072" file="ccmsetup.cpp:1207">
    <![LOG[Running installation package
      Package:     C:\WINNT\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi
      Log:         C:\WINNT\system32\ccmsetup\client.msi.log
      Properties:   CCMLOGLEVEL="0" /SOURCE:D:\MICROSOFT CORPORATION\SCCM CLIENT\2007 SP2="/source:D:\Microsoft Corporation\SCCM Client\2007 SP2" CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL]LOG]!><time="15:08:32.443+-60" date="08-15-2012" component="ccmsetup" context="" type="1" thread="6072" file="msiutil.cpp:819">
    <![LOG[Installation failed with error code 1639]LOG]!><time="15:08:34.899+-60" date="08-15-2012" component="ccmsetup" context="" type="3" thread="6072" file="msiutil.cpp:889">
    <![LOG[Next retry in 120 minute(s)...]LOG]!><time="15:08:36.025+-60" date="08-15-2012" component="ccmsetup" context="" type="0" thread="6072" file="ccmsetup.cpp:8348">

     

     

    I can provide further info/logs if pointed in the right direction - does anyone know why this would be failing? Been tearing my hair out trying to get it working! :-) Thanks for looking at this!

    Wednesday, August 15, 2012 3:01 PM

Answers

  • To get it to write, if it is not already, kill the ccmsetup.exe, it should dump to the log. Close and reopen the log with notepad and the jibberish should be there.

    As far as not having server side access, that is not a problem for this. It is only a small MSI that can be installed on clients. The contents should be in this folder where ever they saved the SCCM install files. The folder name is "ConfigMgr 2007 Toolkit" and the file you would want is CcmTools.msi. You dont need to know any server specifics for it.

    This can be run on the client (or connected to the hidden share of the PC) and open the log file with it.

    • Marked as answer by Eambo Wednesday, August 15, 2012 5:57 PM
    Wednesday, August 15, 2012 4:47 PM

All replies

  • look in the ccmsetup.log. This looks like the client.msi.log.
    Wednesday, August 15, 2012 3:31 PM
  • Hi.,

    1639 translates to invalid command line argument, what command line arguments did you pass to ccmsetup.exe? It looks like you passed the  /SOURCE:D:\MICROSOFT CORPORATION\SCCM CLIENT\2007 SP2="/source:D:\Microsoft Corporation\SCCM Client\2007 SP2"  If you deploy the client without any command line does it work then?

    /Source:"D:\Microsoft Corporation\SCCM Client\2007 SP2" would be a valid switch.

    regards,

    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Wednesday, August 15, 2012 3:31 PM
    Moderator
  • Thanks for the responses :-) RCCMG, this was indeed the ccmsetup.log I'm afraid Jörgen, think you're absolutely right, I'm going to try again here - been a long day! I may be back with another error as I've tried a few different ways all day, but I'll let you know the outcome/next issue! :-D
    Wednesday, August 15, 2012 3:38 PM
  • My mistake then! ;)
    Wednesday, August 15, 2012 3:40 PM
  • Further query (and yes I'm a total newbie to this I'm afraid!). ccmsetup.exe is running in task manager, the log has written nothing, and it's been running for 45 minutes. Is this normal?
    Wednesday, August 15, 2012 4:14 PM
  • No that is not normal. The ccmsetup.log should have written something though. How are you looking at the log? Using notepad or trace32? Trace32 can be installed from (i think) the ccmtoolkit folder on the disk or where ever you saved the SCCM server install.

    Trace32 will give you realtime logging, basically can have the log file open and it will still write. Notepad locks it so nothing new will show, but it will still be written just need to reopen the log.

    Wednesday, August 15, 2012 4:23 PM
  • No that is not normal. The ccmsetup.log should have written something though. How are you looking at the log? Using notepad or trace32? Trace32 can be installed from (i think) the ccmtoolkit folder on the disk or where ever you saved the SCCM server install.

    Trace32 will give you realtime logging, basically can have the log file open and it will still write. Notepad locks it so nothing new will show, but it will still be written just need to reopen the log.

    I'm using Notepad - I don't actually have any server-side access, just client - can I use something similar to Trace32? Or is there any way to see what's been written so far/been logged so far?

    Thanks again for the help.

    Wednesday, August 15, 2012 4:34 PM
  • To get it to write, if it is not already, kill the ccmsetup.exe, it should dump to the log. Close and reopen the log with notepad and the jibberish should be there.

    As far as not having server side access, that is not a problem for this. It is only a small MSI that can be installed on clients. The contents should be in this folder where ever they saved the SCCM install files. The folder name is "ConfigMgr 2007 Toolkit" and the file you would want is CcmTools.msi. You dont need to know any server specifics for it.

    This can be run on the client (or connected to the hidden share of the PC) and open the log file with it.

    • Marked as answer by Eambo Wednesday, August 15, 2012 5:57 PM
    Wednesday, August 15, 2012 4:47 PM
  • Thank you! Think we're getting somewhere now! :-)

    So, right now it's got to:

    18:07:29: SelfRegModules. Registering modules

    Then after that there's a bunch of "The system is no longer in a low-power state." messages

    It's now 18:15 - is it stuck or should it still be working away? :-)

    Wednesday, August 15, 2012 5:15 PM
  • Just curious, were you able to get trace32? It will help out a lot looking at the logs. It highlights errors and makes looking at the log sooo much easier. Could you post the log up to the start of the continuing of those messeges, I know it will be a bit but will help a bit with errors.

    Also is this a mobile device or a pc? If mobile is it plugged in? I am going to look at my ccmsetup.log and see if it says anything like that. Also since it sounds like you may be using a command line and switches to install the client, what are you entering?

    Wednesday, August 15, 2012 5:22 PM
  • Yup, trace32 is where I pulled the above details from :-)

    Okay so previously I was trying literally just ccmsetup.exe (no parameters). I can see the Config Manager option, but it's entirely empty.

    When I try to run our installation package (prepackaged, so I know 100% it works as it has for all our other machines), I'm getting:

    Error: Failed to retrieve the assigned site. The client is not assigned to any site.

    Can I manually assign the client somehow? I know which site it should belong to =-/

    Edit:

    Okay, now we're rolling!

    Turns out that, rather annoyingly, McAfee HIPS (Host Intrusion Prevention System), was blocking the ccmsetup.exe from registering itself, causing it to hang at that step.

    I disabled HIPS, retried, and now SCCM is installed and looking much healthier! Running the soft/hardware inventory cycles now to try and get it reporting properly :-)

    Edit2: And we have liftoff!

    SCCM is now repaired and looking good, it was all down to that darn McAfee! Due to this machine being off SCCM, it didn't receive the last McAfee update, which I believe actually stops such issues from occuring. Too little too late ;-P

    Thanks to everyone, especially RCCMG, for their help, very much appreciated!

    • Edited by Eambo Wednesday, August 15, 2012 5:58 PM
    Wednesday, August 15, 2012 5:40 PM
  • Good to hear! Yeah antivirus's are a pain. If possible see if you can exclude ccmsetup.exe from the AV protection so McAfee does not stop the process.

    Wednesday, August 15, 2012 5:59 PM