locked
923845 BITS Install Fails on XP SP3 RRS feed

  • Question

  • I have some PCs that are running WinXP SP3.  When we try to install the client on those machines, we get the following error in the WindowsXP-KB923845-x86-ENU.log file:

     

    0.844: ================================================================================

    0.844: 2008/09/23 11:06:44.595 (local)

    0.844: c:\40f46413f579d35b82\update\update.exe (version 6.2.29.0)

    0.844: Hotfix started with following command line: /norestart /quiet /log:C:\WINDOWS\system32\ccmsetup\WindowsXP-KB923845-x86-ENU.exe.log

    0.875: CheckSystem: ServicePack version Mismatch

    0.875: DoInstallation: CheckSystem Failed: 0xf06b

    0.891: Setup has detected that the Service Pack version of this system

    is newer than the update you are applying.

    There is no need to install this update.

    0.891: Update.exe extended error code = 0xf06b

    0.891: Update.exe return code was masked to 0x643 for MSI custom action compliance

     

    It seems as if the client install is requiring this installation, but when the installation is called, it finds that SP3 is installed and fails. 

     

    The error message reported back to the ccmsetup.log file is 1603 (general MSI error). 

     

    The CCMSetup log ends with a state ID 309 fallback status point error (Failed to download files through BITS at address).

     

    Any ideas/suggestions?

    Thanks, --Jo

    Tuesday, September 30, 2008 3:36 PM

Answers

  • I checked, and this was tested (deploying Configuration Manager RTM clients to Windows XP SP3) and worked fine in our tests. So the only suggestion was to contact product support so they can look into it for you. Sorry that's all I can offer.

     

    I'll see if I can dig up an RTM site and test it myself, but not sure how soon that will be.

    Thursday, October 9, 2008 7:42 PM

All replies

  • That is the kind of behavior I would expect to see up until it returns the 0x643 (1603) return code.  What version of the client ( RTM / SP1 / R2 ) are you tring to install?  SCCM 2007 RTM probably didn't know about XP SP3 and is probably looking for "BITS_Version = X" rather that "BITS_Version >= X" (or something cool like that)

     

    BH

     

    Tuesday, September 30, 2008 6:38 PM
  • We're installing the RTM version.  We have not yet rolled out SP1 because we were waiting for the ICP2 client (which was just released recently).  If your theory is correct, I should never be able to install the client on any PC that is running XP SP3, right?  I can do that test, but my own PC is XP SP3 and I regularly use my own PC for testing - I know I've uninstalled and reinstalled the client at least twice since SP3 was installed on this PC.  Am I missing something?

     

    Thanks! --Jo

     

    Wednesday, October 1, 2008 12:12 PM
  • I've not tried Windows XP SP3, but a very easy workaround would be to install proper version of BITS 2.5 on the system prior to our client deployment process. We check during our client setup to see if the client already has the minimum BITS version installed - if so, we skip it, if not, we install.

     

    So, if it is already installed, then we'd not have to do so during our setup, and all should be good. Can you try that on one of your systems and let us know?

    Tuesday, October 7, 2008 10:12 PM
  • Thanks for the feedback.  I'm not sure if I understand what you mean when you say "install the proper version of BITS 2.5 on the system".

     

    When I try to install BITS 2.5 on a WinXPSP3 PC, I get a message that the service pack version of the system is newer than the update I am applying.  So... there's no way to install BITS 2.5 on a WinXP SP3 machine.

     

    But... BITS is already installed on the XP SP3 PC.  The BITS service is there and it is set to automatic and it is running.  I'm not sure exactly how to tell what version of BITS is installed on the PC, but the Windows\System32\bits\qmgr.dll file has a file and product version of 6.7.2600.5512. 

     

    What version of BITS would I install to ensure that I have the proper version of BITS on the PC prior to attempting to install the client so that the client installation will detect that BITS is already installed?  Again, just to be clear... right now, it is not correctly detecting the version that is installed and it won't let me install the 2.5 version (which I assume could be correctly detected)...

     

    Thanks so much, --Jo

     

     

     

    Tuesday, October 7, 2008 10:56 PM
  • You are correct, I just downloaded SP3 and am installing it now. I saw the KB that indicated it was included with SP3.  So there is no "proper version" of BITS to install, as it is already included. My client is now in the process of backing up the files prior to upgrade to SP3 (I know, I should have told it not to back up the files). It is virtual environment, so is going slow. So I doubt I'll have an update today on it as I have to head out to a soccer game tonight.

     

    But I'll try it tomorrow morning if I can before my all morning meeting and report back when I have a result from it.

    Tuesday, October 7, 2008 11:02 PM
  • OK, I upgraded my XP SP2 client to SP3 (took a few attempts to a corrupt download :-(, but finally got it working. I then did a push of the client to the XP SP3 box with ConfigMgr SP1. Worked like a charm :-)

     

    The ccmsetup.log said it "Successfully ran BITS check" and the install completed as expected.

     

    Now again, I was running SP1. Given that we didn't start supporting XP SP3 until our SP1 release, it may be that we had to make changes to the setup to accomodate this. Since you are at RTM of Configuration Manager, I'm guessing you are going to have issues, based on what I've seen. But I'm checking with the team that did that testing and will update when I get a response validating whether or not we support XP SP3 with our RTM (it is not listed in the RTM supported configs doc, but is listed in the SP1 version).

    Wednesday, October 8, 2008 7:44 PM
  • I checked, and this was tested (deploying Configuration Manager RTM clients to Windows XP SP3) and worked fine in our tests. So the only suggestion was to contact product support so they can look into it for you. Sorry that's all I can offer.

     

    I'll see if I can dig up an RTM site and test it myself, but not sure how soon that will be.

    Thursday, October 9, 2008 7:42 PM
  • Thanks for looking into it.  I'll call support.

     

    --Jo

     

    Friday, October 10, 2008 12:33 PM
  • And I tested in my RTM site, and my XP SP3 client installed fine also. Same message that it passed BITS check successfully. So must be something in your environment. It is supported and does work.

    Friday, October 10, 2008 5:25 PM
  • I had the same for BITS and the Windows Installer. I used the slipstreamed version of Windows XP with SP3. In this version it had Windows Installer 3.01 and wasn't allowed to upgrade to 3.1.

     

    Exact same error as stated in the first post and also for BITS.

    Tuesday, October 14, 2008 2:14 PM
  • My test was not with a slipstreamed XP SP3, but rather an XP SP2 system upgraded to SP3. Not sure why that would make a difference, but could be.

     

    Did you resolve it Jannes?

     

    Jo, any update from CSS involvement?

    Tuesday, October 14, 2008 5:12 PM
  • It was quicker for me to deploy Windowds XP with SP2 and then run the updates for BITS and Windows Installer. (this was not for a SCCM related issue). Will look into it.

    Tuesday, October 14, 2008 7:48 PM
  • Hi Wally, 

     

    I haven't had time to call support for this issue yet.  We're planning our upgrade our SCCM infrastructure to SP1 on October 24, so I might just wait to see if the problem goes away then before I open that call.

     

    Thanks, --Jo

    Tuesday, October 14, 2008 8:36 PM
  • Well I lookedmore into it . First of all, when we look at the KB article for the update it clearly states that SP2 is a requirement.

    File name

    File version

    File size

    Date

    Time

    Platform

    SP requirement

    Service branch

    Bitsinst.exe

    6.7.2600.3143

    28,672

    24-May-2007

    10:56

    x86

    SP2

    SP2GDR

     Article for BITS:
    http://support.microsoft.com/kb/923845

    Windows XP with slipstreamed SP3
    The BITS version in the default installation is 6.7.2600.5512. Higher than the version stated in the KB article.
    The update fails with the error. The version of the file is higher than the version that comes with the update. This explains the error.

    Windows XP slipstreamed SP2
    The BITS version in the default installation is  6.6.2600.2180. The update succeeds and version after update is 6.7.2600.3143
    After the update I applied SP3, the version after that was 6.7.2600.5512

    So the error is right it is already in the SP3 and so not required. It looks like SCCM is looking for the 6.7.2600.3143 version.

    For Windows installer it is a different story because there is an old version of it in SP3, and updating it is not possible.

     

    Tuesday, October 14, 2008 9:28 PM
  • Hi Jannes,

    Did you manage to find a solution to this problem? I am experiencing the same issue.

    I have a slipstreamed copy of XP Pro SP3 and I get the same error in the ccmsetup.log. Thus gathering from all the above posts, it may be related to the version of BITS -  or not?

    If I do a manual install, the client installs correclty but when I leave it to do a nomal AD push, then I get the errors below in the log


    Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 21/04/2009 08:20:44 AM 3980 (0x0F8C)
    Sending Fallback Status Point message, STATEID='100'. ccmsetup 21/04/2009 08:20:44 AM 3980 (0x0F8C)
    State message with TopicType 800 and TopicId {2638FD4B-F086-4ECC-8762-ED31DF362FBB} has been sent to the FSP FSPStateMessage 21/04/2009 08:20:44 AM 3980 (0x0F8C)
    Running as user "SYSTEM" ccmsetup 21/04/2009 08:20:44 AM 3736 (0x0E98)
    Detected 21565 MB free disk space on system drive. ccmsetup 21/04/2009 08:20:44 AM 3736 (0x0E98)
    DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 21/04/2009 08:20:44 AM 3736 (0x0E98)
    Client OS is not Windows XP Embedded ccmsetup 21/04/2009 08:20:44 AM 3736 (0x0E98)
    Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 21/04/2009 08:20:44 AM 3736 (0x0E98)
    Successfully ran BITS check. ccmsetup 21/04/2009 08:20:45 AM 3736 (0x0E98)
    Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401) ccmsetup 21/04/2009 08:20:45 AM 3736 (0x0E98)
    Sending Fallback Status Point message, STATEID='308'. ccmsetup 21/04/2009 08:20:45 AM 3736 (0x0E98)
    State message with TopicType 800 and TopicId {8382A0D7-9D45-4774-AE1A-E8DBC0BC841A} has been sent to the FSP FSPStateMessage 21/04/2009 08:20:45 AM 3736 (0x0E98)
    Tuesday, April 21, 2009 6:28 AM

  • Successfully ran BITS check. ccmsetup 21/04/2009 08:20:45 AM 3736 (0x0E98)
    Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401) ccmsetup 21/04/2009 08:20:45 AM 3736 (0x0E98)


    This has nothing to do with BITS.

    What client push parameters have you entered? You could also use the search function to get some ideas on how to troubleshoot "StatusCode at WinHttpQueryHeaders: 401"

    Tuesday, April 21, 2009 8:11 PM
  • The client push installation properties are set to:

    smssitecode=ABC FSP=SERVERNAME

    I have one server where everything is installed.
    Thursday, April 23, 2009 6:20 AM
  • See "Troubleshooting Management Point Communication" http://technet.microsoft.com/en-us/library/bb932118.aspx
    Thursday, April 23, 2009 6:51 AM