locked
Config Manager 2007 installation stuck at "Transfer Files" RRS feed

  • Question

  • Hi,

    I am in the middle of installing Configuration Manager 2007 SP2 in a virtual test environment.

    The Pre-requisite checker passed all checks and the installation proceeded without any issues but has been stuck at the Transfer Files step for several hours now.

    I have checked the log file and there doesn't appear to be any issues, although the last update was several hours ago now:

    <03-21-2012 11:41:13> Verifying hash for file 'D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\ia64\WindowsUpdateAgent30-ia64.exe'
    <03-21-2012 11:41:13> File hash check failed for D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\ia64\WindowsUpdateAgent30-ia64.exe
    <03-21-2012 11:41:13> Checking alternate path: c:\configmanager\WindowsUpdateAgent30-ia64.exe
    <03-21-2012 11:41:13> Verifying hash for file 'c:\configmanager\WindowsUpdateAgent30-ia64.exe'
    <03-21-2012 11:41:15> Verifying signature for file 'c:\configmanager\WindowsUpdateAgent30-ia64.exe'
    <03-21-2012 11:41:15> Found valid source in folder: 'c:\configmanager\'
    <03-21-2012 11:41:15> Found valid source for external dependency file 'WindowsUpdateAgent30-ia64.exe' at 'c:\configmanager\'
    <03-21-2012 11:41:15> Checking media: D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\i386\msrdcoob_x86.exe
    <03-21-2012 11:41:15> Verifying hash for file 'D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\i386\msrdcoob_x86.exe'
    <03-21-2012 11:41:15> File hash check failed for D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\i386\msrdcoob_x86.exe
    <03-21-2012 11:41:15> Checking alternate path: c:\configmanager\msrdcoob_x86.exe
    <03-21-2012 11:41:15> Verifying hash for file 'c:\configmanager\msrdcoob_x86.exe'
    <03-21-2012 11:41:15> Verifying signature for file 'c:\configmanager\msrdcoob_x86.exe'
    <03-21-2012 11:41:15> Found valid source in folder: 'c:\configmanager\'
    <03-21-2012 11:41:15> Found valid source for external dependency file 'msrdcoob_x86.exe' at 'c:\configmanager\'
    <03-21-2012 11:41:56> Checking media: D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\i386\WindowsUpdateAgent30-x86.exe
    <03-21-2012 11:41:56> Verifying hash for file 'D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\i386\WindowsUpdateAgent30-x86.exe'
    <03-21-2012 11:41:57> File hash check failed for D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\i386\WindowsUpdateAgent30-x86.exe
    <03-21-2012 11:41:57> Checking alternate path: c:\configmanager\WindowsUpdateAgent30-x86.exe
    <03-21-2012 11:41:57> Verifying hash for file 'c:\configmanager\WindowsUpdateAgent30-x86.exe'
    <03-21-2012 11:41:58> Verifying signature for file 'c:\configmanager\WindowsUpdateAgent30-x86.exe'
    <03-21-2012 11:41:58> Found valid source in folder: 'c:\configmanager\'
    <03-21-2012 11:41:58> Found valid source for external dependency file 'WindowsUpdateAgent30-x86.exe' at 'c:\configmanager\'
    <03-21-2012 11:41:58> Checking media: D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\i386\wmirdist.msi
    <03-21-2012 11:41:58> Verifying hash for file 'D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\i386\wmirdist.msi'
    <03-21-2012 11:41:58> File hash check failed for D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\i386\wmirdist.msi
    <03-21-2012 11:41:58> Checking alternate path: c:\configmanager\wmirdist.msi
    <03-21-2012 11:41:58> Verifying hash for file 'c:\configmanager\wmirdist.msi'
    <03-21-2012 11:41:58> Verifying signature for file 'c:\configmanager\wmirdist.msi'
    <03-21-2012 11:42:00> Found valid source in folder: 'c:\configmanager\'
    <03-21-2012 11:42:00> Found valid source for external dependency file 'wmirdist.msi' at 'c:\configmanager\'
    <03-21-2012 11:45:33> Checking media: D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\ccmsetup.cab
    <03-21-2012 11:45:33> Verifying hash for file 'D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\ccmsetup.cab'
    <03-21-2012 11:45:33> File hash check failed for D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\Client\ccmsetup.cab
    <03-21-2012 11:45:33> Checking alternate path: c:\configmanager\ccmsetup.cab
    <03-21-2012 11:45:33> Verifying hash for file 'c:\configmanager\ccmsetup.cab'
    <03-21-2012 11:45:33> Verifying signature for file 'c:\configmanager\ccmsetup.cab'
    <03-21-2012 11:45:33> Found valid source in folder: 'c:\configmanager\'
    <03-21-2012 11:45:33> Found valid source for external dependency file 'ccmsetup.cab' at 'c:\configmanager\'
    <03-21-2012 11:52:53> msvcp60.dll is a system protected file, skip the file copy.
    <03-21-2012 12:06:59> Checking media: D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\osd\bin\i386\wmirdist.msi
    <03-21-2012 12:06:59> Verifying hash for file 'D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\osd\bin\i386\wmirdist.msi'
    <03-21-2012 12:07:00> File hash check failed for D:\CONFIGMGR07SP2EVAL_RTM_ENU\SMSSETUP\osd\bin\i386\wmirdist.msi
    <03-21-2012 12:07:00> Checking alternate path: c:\configmanager\wmirdist.msi
    <03-21-2012 12:07:00> Verifying hash for file 'c:\configmanager\wmirdist.msi'
    <03-21-2012 12:07:00> Verifying signature for file 'c:\configmanager\wmirdist.msi'
    <03-21-2012 12:07:09> Found valid source in folder: 'c:\configmanager\'
    <03-21-2012 12:07:09> Found valid source for external dependency file 'wmirdist.msi' at 'c:\configmanager\'

    Does it normally take this long (4hrs)? Should I cancel the installation and start again or is there anything that I can check?

    many thanks,

    Aoife

    Wednesday, March 21, 2012 2:50 PM

Answers

  • I've seen it take quite a while on slow networks, especially with VMs.  The resulting folder is only 100MB though. 

    I would check the folder you specified for downloading.  Are new files downloading?

    Also, monitor the "Bytes Sent" and "Bytes Received" on the network connection.  Is traffic being generated?

    I make a point of keeping a copy of the download folder that the process creates, and carry it with me for new installs.  I update it when I'm on a fast network, in case I end up on a really slow one...

    Four hours is pretty long.  No harm done to simply cancel (possibly have to kill) the installation and starting over.  If you do, try deleting whatever got downloaded this time, or select an alternate download path.

    Verify that you can go to Microsoft.com and download ANY patch from the server.  You probably have some weirdness in your VM networking.

    • Proposed as answer by UKCats Saturday, April 7, 2012 3:55 AM
    • Marked as answer by Garth JonesMVP Saturday, January 2, 2016 5:56 PM
    Wednesday, March 21, 2012 4:26 PM