Re: SMS 2k3 Advanced Client not installing...

From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 03/23/04 

Date: Tue, 23 Mar 2004 14:57:50 -0800

It seems the only issue is that BITS setup is failing.
I am going to try to track down the issue and respond with what I find. You
may try on one client to remove BITS then re-install the advanced client. 

-- 
Thanks
Jeff Harbaugh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Department of Medicine"
<--!-!-33--rfmed--1#41@urmc.--!--rochester--!--.EeDeeYou> wrote in message
news:MPG.1aca6a6f4efef35198968c@news.microsoft.com...
> In article <#VA5fyQEEHA.3784@TK2MSFTNGP10.phx.gbl>,
> jeffharb@online.microsoft.com says...
> > Have you configured your Push Installation account? What OS are your
> > clients? You can ignore the message warnings in the client.msi we log
the
> > custom actions that are part of the MSI but that does not mean all
actions
> > have occurred. It appears that either the BITS installation is failing
or
> > you are getting permission denied. You can search for BITSetup.log this
> > should be in your %windir%
> >
> >
>
> Jeff,
>
> Thank you for the direction.  I realized after I posted that I forgot a
> few vital pieces of information.
>
> The OS seems to be primarily Win2K Pro.  I can't tell you SP level on
> all machines, is there a minimum I might be missing? (There's a
> chicken/egg scenario eh?)
>
> Some of the systems within the same OU, on the same OS level are
> installing the client just fine where others are not.  The problem
> exists similarly on machines across multiple OUs.
>
> The BITS log is attached here, but the account the push is working under
> is a local admin on the machines as defined by the restricted groups
> GPO.  I have also manually checked these machines and the proper groups
> are in the Administrators group on the server.
>
> Thanks for the quick response.  Here's to the next step!
>
> Here is the BITS log:
>
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      Installed
> version of BITS is BITS_v12
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      Detected that
> installation will be an upgrade of the current BITS version
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      Creating
> Uninstall directory
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      Directory C:
> \WINNT\System32\BITS\Uninstall 1.5 Client already exists;
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      Loading inf
> file c:\8b43207b5ed550a83f0e8e7e\bitssetup_clnt.inf, entry point
> Install_w2k...
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      Failed to
> retrieve SfcDllCacheDir policy. Error: 0x2
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      Failed to
> retrieve SfcDllCacheDir key. Defaulting to system32 subdirectory. Error:
> 0x2
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      Dllcache
> directory is C:\WINNT\System32\dllcache
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      >>> Processing
> section [StopBits]...
> 2004-03-23 15:17:04  20:17:04   Success   BITS CLNT      Service
> specified to be stopped: bits
> 2004-03-23 15:17:05  20:17:05   Error     BITS CLNT      Failed to stop
> service bits.. (Error 0x00000005: Access is denied.)
> 2004-03-23 15:17:05  20:17:05   Error     BITS CLNT      Failed to
> install section StopBits. Aborting the entire setup. (Error 0x00000005:
> Access is denied.)
> 2004-03-23 15:17:05  20:17:05   Success   BITS CLNT      =========
> STARTING ROLLBACK ===========
> 2004-03-23 15:17:05  20:17:05   Success   BITS CLNT      ========= END
> ROLLBACK ===========
> 2004-03-23 15:17:05  20:17:05   Success   BITS CLNT      =========
> STARTING VERIFICATION ===========
> 2004-03-23 15:17:05  20:17:05   Success   BITS CLNT      ========= END
> VERIFICATION ===========
> 2004-03-23 15:17:05  20:17:05   Error     BITS CLNT      Setup has
> failed. (Error 0x00000005: Access is denied.)
> 2004-03-23 15:17:05  20:17:05   Success   BITS CLNT      Unloading
> version functions
> 2004-03-23 15:17:05  20:17:05   Success   BITS CLNT      bitssetup has
> finished. Exit code is 5
> 2004-03-23 15:17:05  20:17:05   Success   BITS CLNT
> ************************** BITS Setup has exited
> ************************

Relevant Pages

  • Re: SMS 2k3 Advanced Client not installing...
    ... Can you run a command session as local sytem and try to do a net stop on the ... > may try on one client to remove BITS then re-install the advanced client. ... >>> Have you configured your Push Installation account? ... I can't tell you SP level on>> all machines, is there a minimum I might be missing? ...
    (microsoft.public.sms.setup)
  • Re: XP clients do not appear in Collections
    ... So your XP machines are or are not being discovered? ... installation methods have NOT been enabled. ... Very soon after enabling the discovery methods, ... >>> have any site listed or indicate the client has installed. ...
    (microsoft.public.sms.admin)
  • Re: Adv Client - Causing MSI Installation Issues
    ... machines to go through and we have had to slow down the role out immensely ... SMS client was pushed on the machines using client push installation ... >> Event Source: MsiInstaller ...
    (microsoft.public.sms.setup)
  • Re: SMS Virtual Mouse Problem
    ... Desktop Client on the machines but what we could not understand is that why ... About the Problem of the lose of drivers after the installation of SMS. ...
    (microsoft.public.sms.admin)
  • Re: Client push question - the plot thickens
    ... for clients within the site boundaries of a secondary site are disseminated ... If Client Push is enabled at that site then the ... SMS 2003 and Advanced Client push installation behavior. ... secondary site unless the secondary site has both initiated discovery of the ...
    (microsoft.public.sms.admin)