Re: ccmclean fails!

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

Date: Wed, 21 Jul 2004 08:58:26 -0700

I would seriously look at the hardware at this point. If you are running as
a local admin instead of using %temp% just use c:\

So again msiexec /i client.msi /L*v c:\cliinst.log

The logging is basic msi functionality and if it is truly not creating a log
file I am thinking you may have a disk problem. 

-- 
Thanks,
Jeff Harbaugh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"nickmo" <nickmo@discussions.microsoft.com> wrote in message 
news:7D386559-3706-4FE4-B5AA-1873A2FD437C@microsoft.com...
> My first attempt to run client.msi did not generate a log file, but rolled 
> back its actions and appears to have left most of the original log files 
> in place.
>
> Then I ran your msiexec suggestion.  I am not sure if the install failed 
> or what happened, but the system logged off the local admin.  (This has 
> also been occuring on a disk defrag)  There may be a deeper problem. 
> Cliinst.log was never generated.
>
> For grins and giggles I ran the msiexec again and received the following 
> error, "There is a problem with this Windows Installer package.  A DLL 
> required for this install to complete could not be run.  Contact your 
> support personnel or package vendor".
>
> So I recopied the instalation files to the local PC and ran msiexec again, 
> only to have the PC log off in the midst of the 
> installation....Cliinst.log was never generated.
>
> "Jeff Harbaugh [MSFT]" wrote:
>
>> So you kind of have a half installed/de-installed client? Do you see the 
>> SMS
>> Agent Host running on the machine?
>> When you ran client.msi did you create a log file?
>>
>> If not you can run msiexec /i (path to client.msi) /L*v 
>> %temp%\cliinst.log
>>
>> This will create a log file which we can then troubleshoot or atleast see
>> the error.
>>
>> -- 
>> Thanks,
>> Jeff Harbaugh [MSFT]
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>>
>>
>> "nickmo" <nickmo@discussions.microsoft.com> wrote in message
>> news:C1341C66-4F72-43EF-ACEC-AD44FE309D03@microsoft.com...
>> > Thanks for the super quick reply.
>> >
>> > The CCMRepair log file say the repair was successfull at the time I ran
>> > it, but I can gurantee it wasn't.
>> >
>> > A force push cannot happen because I got ahead of myself and already
>> > deleted the PC from the database.  When I attempt to rediscover and\or
>> > reenter the site code, I get errors.
>> >
>> > "Jeff Harbaugh [MSFT]" wrote:
>> >
>> >> 1. It is trying to remove the root\ccm namespace from WMI.
>> >> 2. You should ahve a repair log under %widnir%\system32\ccm\logs. This
>> >> would
>> >> indicate what if anything is happening.
>> >> 3. Have you tried to push the client out to that specific machine? You
>> >> would
>> >> have to use the "Forced always install setting". from the wizard.
>> >> You can also look at the client.msi.log for specific error during the
>> >> re-installation.
>> >>
>> >> -- 
>> >> Thanks,
>> >> Jeff Harbaugh [MSFT]
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >> "nickmo" <nickmo@discussions.microsoft.com> wrote in message
>> >> news:EC07B9CB-3A1F-4851-9A01-4459259C0B02@microsoft.com...
>> >> > Here is a brainbuster for MS (at least it has been for me!).  I am
>> >> > running
>> >> > SMS2003.
>> >> >
>> >> > I have an Adv. Client that is generating errors in my logs and the
>> >> > advertisements are failing.  My thought is just to uninstall the
>> >> > client,
>> >> > delete the pc from the database, then reinstall the client.  But 
>> >> > when I
>> >> > attempt to run ccmclean.exe, I receive about 2 dozen errors that say
>> >> > (in
>> >> > bad english) "Failed to connected to namespace root\ ... 
>> >> > (80041001)",
>> >> > where the .... is the failed file.
>> >> >
>> >> > So then I thought I would try to just reinstall the client.  The
>> >> > "Repair"
>> >> > function in Systems Management never processes anything and just 
>> >> > sits
>> >> > around like dead weight.
>> >> >
>> >> > So I try to run the initial msi - Client.msi - and it fails with 
>> >> > error
>> >> > "Setup failed due to unexpected circumstances.  The error code is
>> >> > 80004005".
>> >> >
>> >> > Yikes.  Any help would be more than greatly appreciated.
>> >>
>> >>
>> >>
>>
>>
>>

Relevant Pages

  • Re: Adv client install fails when Local Admin
    ... IIRC, what is needed permissions wise is Local admin, which you already ... the Advanced Client network access account. ... Have you configured an Advanced Client Network Access Account? ... > the user is a Local admin and attempting to install. ...
    (microsoft.public.sms.setup)
  • Client Installation Issues: SMS 2.0 SP5
    ... Domain admin installs the client, ... Domain user who sets himself up as local admin on a PC works fine. ... Where we run into issues w/ the client install is if we use the local admin ... site (within SMS), but no site info gets put on the client and none of the ...
    (microsoft.public.sms.setup)
  • Re: Deny Interactive Logon but Allow Runas
    ... that occasionally an install can become 'corrupt' and needs re-installing. ... client has version 6 of the software, with fix pack 2, so they need to get ... We've tried virtualisation, running VMware, and giving the users local admin ...
    (microsoft.public.windowsxp.security_admin)
  • Re: TrendMicro Client-Server Security Questions
    ... When I have run into this it is asking for the local admin name and password ... for the PC, not the domain creds. ... As other have stated it is far easier to install this from the client side. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS has no computers
    ... Did you also check the log file "WindowsUpdate.log"? ... all my policy settings looked correct as well, but when I went into the log ... - If it asks you to install the latest version of the Windows Updater ... I also found a program to run on the client side called ...
    (microsoft.public.windows.server.general)
Loading