Can't install SCCM 2007 Client

Page: 12 > Showing page 1 of 2
Author
mhammes
Expert Member
  • Total Posts : 101
  • Scores: 0
  • Reward points: 29170
  • Joined: 2002/04/18 07:38:00
  • Status: offline
2012/10/31 11:34:03 (permalink)
0

Can't install SCCM 2007 Client

I keep getting the following error when installing the client:
MSI: Setup failed due to unexpected circumstances
The error code is 80004005
MSI (s) (18!14) [10:24:53:119]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances
The error code is 80004005
This is a Windows 7 SP1 64bit machine.
I suspect that the problem is WMI and I have tried many things to get this resolved with no luck at all.  I have ran the SCCM Client Center Repair WMI - That didn't work.
I ran winmgmt /resyncperf,
  • CD %windir%\system32\wbem
  • for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
  • for /f %s in ('dir /b *.mof') do mofcomp %s
  • ?wmidiag
  • ?I ran Chkdsk and SFC /scannow
  • ?Any help would be appreciated!
  • #1

    21 Replies Related Threads

      jsandys
      Expert Member
      • Total Posts : 1438
      • Scores: 131
      • Reward points: 71080
      • Joined: 2005/03/24 01:20:32
      • Location: San Antonio, TX
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/10/31 15:47:46 (permalink)
      0
      Have you reviewed clint.msi.log?
      80004005 is a generic failure message that means you need to dig further to find the root cause. While WMI is certainly a usual suspect, you can't always assume it is in fact the culprit.

      Jason
      Configuration Manager MVP
      My Blog
      Twitter @JasonSandys
      #2
      lroboat
      New Member
      • Total Posts : 11
      • Scores: 2
      • Reward points: 3340
      • Joined: 2012/08/13 10:58:53
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 08:25:47 (permalink)
      0
      Being that sometimes the obvious is what we miss I will ask... Since it the big thing I notice people forget here, is that even though you are logged in as an administrator did you "run as admin"? Your system might be setup different, so you may not have to but sometimes we over look the obvoious... Also did you make sure any AV or Firewall were turned off?
       
      Liesa
      #3
      CAP
      Expert Member
      • Total Posts : 143
      • Scores: 0
      • Reward points: 36530
      • Joined: 2011/12/09 09:28:31
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 08:44:46 (permalink)
      0
      80004005 is usually permissions issue. remove any left over items from a previous attempt and try again. If you can find MSIZAP on the web this may help get rid of orphan items from a bad install.

      Carl Polk
      #4
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 08:45:34 (permalink)
      0
      No Firewall on and UAC turned off and we don't have to run with Admin rights.  When I bring up SCCM client center it brings up an error Invalid Namespace so I'm pretty sure it is WMI.  However if this error comes up for other purposes I don't know.  This error message MSI (s) (38!A8) [04:17:12:447]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances came from the client.msi.log file.
      #5
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 08:52:45 (permalink)
      0
      I have the msizap but what do you suggest for the syntax?
      #6
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 09:03:30 (permalink)
      0
      I tried msizap p, msizap a and msizap g and install still erroring out.
       
      MSI: Setup failed due to unexpected circumstances
      The error code is 80004005
       
      I am also getting this error message in the client.msi.log file Property(S): SmsDetectUpgrade_ErrorMessage = An older version of the SMS Management Point is installed. Please upgrade the Management Point before attempting to upgrade the client.
       
      However there isn't an older MP.
       
      #7
      jsandys
      Expert Member
      • Total Posts : 1438
      • Scores: 131
      • Reward points: 71080
      • Joined: 2005/03/24 01:20:32
      • Location: San Antonio, TX
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 10:09:27 (permalink)
      0
      One correction to this thread, 0x80004005 is not a permissions error. The error code from this HRESULT is 4005 (the first four hex digits -- 8000 -- have a different meaning). If the error code was 0005, this absolutely would be "access denied"; however, 4005 specifically means unknown error.
      As for digging through the MSI verbose log, as the first word of the line above implies, this is just the value of an internal property. All lines near the end that begin with Property(S) are simply dumps of property values and are not in any way indicative of the condition or execution state of the MSI.
      To find errors in a verbose MSI log, search for "return value 3". From there begin scanning the log file above that until you find the issue.

      Jason
      Configuration Manager MVP
      My Blog
      Twitter @JasonSandys
      #8
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 10:40:30 (permalink)
      0
      Well, I'm still not sure of the problem.  This is the log file
      MSI (s) (F0!48) [08:00:28:270]: Closing MSIHANDLE (4979) of type 790531 for thread 4424
      MSI (s) (F0!48) [08:00:28:271]: Closing MSIHANDLE (4974) of type 790540 for thread 4424
      MSI (s) (F0!48) [08:00:28:271]: Creating MSIHANDLE (4980) of type 790531 for thread 4424
      MSI (s) (F0!48) [08:00:28:271]: Creating MSIHANDLE (4981) of type 790531 for thread 4424
      Action start 8:00:28: CcmSetObjectSecurityInit.
      MSI (s) (F0!48) [08:00:28:271]: Closing MSIHANDLE (4981) of type 790531 for thread 4424
      [8:00:28] @@ERR:25001
      MSI (s) (F0!48) [08:00:28:272]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances
      The error code is 80004005
      MSI (s) (F0!48) [08:00:28:272]: Closing MSIHANDLE (4973) of type 790531 for thread 4424
      MSI (s) (F0!48) [08:00:28:272]: Closing MSIHANDLE (4972) of type 790540 for thread 4424
      MSI (s) (F0!48) [08:00:28:273]: Closing MSIHANDLE (4980) of type 790531 for thread 4424
      MSI (s) (F0!48) [08:00:28:273]: Closing MSIHANDLE (4971) of type 790541 for thread 4424
      Error 25001. Setup failed due to unexpected circumstances
      The error code is 80004005
      MSI (s) (F0:EC) [08:00:28:273]: Closing MSIHANDLE (4970) of type 790542 for thread 3856
      CustomAction CcmSetObjectSecurityInit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
      MSI (s) (F0:10) [08:00:28:275]: Machine policy value 'DisableRollback' is 0
      MSI (s) (F0:10) [08:00:28:275]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
      Action ended 8:00:28: CcmSetObjectSecurityInit. Return value 3.
       
      #9
      jsandys
      Expert Member
      • Total Posts : 1438
      • Scores: 131
      • Reward points: 71080
      • Joined: 2005/03/24 01:20:32
      • Location: San Antonio, TX
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 10:51:38 (permalink)
      0
      MSI verbose log reading is an art. You need to keep looking until you find an exact error.

      Jason
      Configuration Manager MVP
      My Blog
      Twitter @JasonSandys
      #10
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 10:56:57 (permalink)
      0
      Well, there is this:
       
      [8:00:27] WARNING: Upgrade Code [{252DA259-82CA-4177-B8D0-49C78937BA3E}] is not a recognized upgrade code
      #11
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 11:06:38 (permalink)
      0
      The line above the error is MSI: Action 10:05:39: CcmSetObjectSecurityInit. Applying security permissions ccmsetup 11/1/2012 10:05:39 AM 4792 (0x12B8)
      What exact permissions do I need to check?
      #12
      jsandys
      Expert Member
      • Total Posts : 1438
      • Scores: 131
      • Reward points: 71080
      • Joined: 2005/03/24 01:20:32
      • Location: San Antonio, TX
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 11:11:14 (permalink)
      0
      Don't know. But that's not any sort of error or causing any issues; it's a normal log line. Keep looking (or post the log so one of us can look).

      Jason
      Configuration Manager MVP
      My Blog
      Twitter @JasonSandys
      #13
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 11:14:01 (permalink)
      0
      I uploaded the file instead.
      post edited by mhammes - 2012/11/02 10:57:15
      #14
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 11:18:48 (permalink)
      0
      This box does have IIS on it. I saw some posts about this but can't find any fix that works.
      #15
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/01 11:37:15 (permalink)
      0
      Here are some errors in the event viewer for WMI:
      Event provider $Core attempted to register query "select * from __ClassOperationEvent" whose target class "__ClassOperationEvent" in //./root/RSOP/User namespace does not exist. The query will be ignored.
       

      Event provider $Core attempted to register query "select * from __ClassOperationEvent" whose target class "__ClassOperationEvent" in //./root/CIMV2/power/ms_409 namespace does not exist. The query will be ignored.
       

        Event provider $Core attempted to register query "select * from __ClassOperationEvent" whose target class "__ClassOperationEvent" in //./root/CIMV2/power namespace does not exist. The query will be ignored.
       



      Event provider $Core attempted to register query "select * from __ClassOperationEvent" whose target class "__ClassOperationEvent" in //./root/Interop namespace does not exist. The query will be ignored.

      #16
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/02 10:15:25 (permalink)
      0
      Did the logs help?
      I still think that it is a WMI issue.  Mainly because when I bring up SCCM Client Center it gives me the error message Invalid Namespace.
      However I have looked at every WMI fix out there and nothing seems to work.
      #17
      jsandys
      Expert Member
      • Total Posts : 1438
      • Scores: 131
      • Reward points: 71080
      • Joined: 2005/03/24 01:20:32
      • Location: San Antonio, TX
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/02 10:42:20 (permalink)
      0
      It brings up invalid namespace because the it has been created yet because the client doesn't successfully install which is what creates the namespace that its looking for.
      Sorry, when I said post the log file, I meant attach it or post it on a file sharing service (like DropBox or SkyDrive) so that it can easily be viewed and searched.

      Jason
      Configuration Manager MVP
      My Blog
      Twitter @JasonSandys
      #18
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/02 10:50:50 (permalink)
      0
      Here is the ccmsetup.log
      #19
      mhammes
      Expert Member
      • Total Posts : 101
      • Scores: 0
      • Reward points: 29170
      • Joined: 2002/04/18 07:38:00
      • Status: offline
      Re:Can't install SCCM 2007 Client 2012/11/02 10:54:22 (permalink)
      0
      And here is the client.msi.log
      #20
      Page: 12 > Showing page 1 of 2
      Jump to:
      © 2018 APG vNext Commercial Version 5.5