Showing posts with label SCCM/SMS Client. Show all posts
Showing posts with label SCCM/SMS Client. Show all posts

Solution: OnSearchComplete - Failed to end search job. Error = 0x80072efe

Errror in WUAHandler.log:
OnSearchComplete - Failed to end search job. Error = 0x80072efe.
Scan failed with error = 0x80072efe.

Step 1: Check background programs.
=======================
Disable firewalls or other Internet browser programs that can affect the Internet connection. The following programs can affect the connection to the Windows Update site and I suggest you remove or disable them:

McAfee firewall
Norton Internet Security
Zone Alarm Firewall
Panda firewall


Step 2: Delete the CatRoot2 folder
=======================
A: Stop Cryptographic Services:

1. Click Start, click Run, type in "SERVICES.MSC" and press Enter.
2. Double click Cryptographic Services, and then click Stop (if it has been started).

B: After stopping Cryptographic Service, please delete the "Catroot2" folder:

1. Locate the "C:\Windows\System32\" folder.
2. Delete the Catroot2 subfolder in System32.

Note: I am assuming your Windows Vista is installed in C:\Windows.

C: Re-start Cryptographic Services:

1. Click Start, click Run, type in "SERVICES.MSC" and press Enter.
2. Double click Cryptographic Services, and then click Start.

Hardware Inventory not being processed by SMS/ConfigMgr servers | Hardware Inventory not working

I noticed some systems mostly Windows 2000 Servers hardware inventory did not report back to SMS and their hardware inventory MIF files were being moved to \inboxes\dataldr.box\BADMIFS\ directory. This problem seem to get resolved by uninstalling and re-installing the SMS/ConfigMgr client, but this will reappear again after few days.
 In the DataLDR.log the following error will be report for the effected clients.

File size exceeds defined maximum.

SMS creates a BadMifs directory only if a bad IDMIF or NOIDMIF is detected at your site server by the Inventory data loader. By default, the MIF file size is set to 5,000,000 bytes (4.7MB) that SMS collects from a client during its normal hardware inventory. If a MIF file exceeds the limit the MIF is rejected and placed into BADMIFs folder.
 You can increase the maximum MIF file size value from the registry on your SMS/ConfigMgr Site Server by modifying the following registry key:

On a 32-bit server:
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size

 On a 64-bit server:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\SMS_INVENTORY_DATA_LOADER\Max MIF Size

However if you increase this value your disk space on the site server may grow considerably because of the larger the MIF file size and your resources may diminish because it takes longer for the Inventory Data Loader to parse and process them.


http://support.microsoft.com/kb/319167
http://support.microsoft.com/kb/198766
http://social.technet.microsoft.com/Forums/en-US/configmgrinventory/thread/fc9f5405-a476-4ee4-af71-4e74717c5fdd

Where can we find SCCM/SMS client logs

Client logs location:
  • On 32-bit system, the client logs are located in the %WINDIR%\System32\CCM\Logs folder. 
  • On 64-bit system, the client logs are located in the %WINDIR%\SysWOW64\CCM\Logs
  • On SMS/SCCM servers the client logs are located in the <INSTALLDRIVE>\SMS_CCM , here <INSTALLDRIVE>  is the drive where sms/sccm servers is installed.
Client installation logs location(ccmsetup.log,client.msi.log etc):
  • On 32-bit system, the client installation log(ccmsetup.log,client.msi.log etc) are located in the %WINDIR%\System32\ccmsetup\ folder.
  • On 64-bit system, the client installation logs(ccmsetup.log,client.msi.log etc) are located in the %WINDIR%


MSI: Setup failed due to unexpected circumstances The error code is 80041002

Problem:

 
When trying to install the new SCCM client 4.0.6487.2000  everything seems to start and go fine.....   but at the end of it you get the last two lines and it just stops.

 ----------------Start CCMSETUP.LOG----------------
Version: 4.0.6487.2000
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.
"Command line: ""C:\WINDOWS\system32\ccmsetup\ccmsetup.exe"" /runservice /config:MobileClient.tcf"
CCMHTTPPORT: 80
CCMHTTPSPORT: 443
CCMHTTPSSTATE: 0
CCMHTTPSCERTNAME:
FSP:
CCMFIRSTCERT: 0
Config file: C:\WINDOWS\system32\ccmsetup\MobileClient.tcf
Retry time: 10 minute(s)
MSI log file:
"MSI properties: INSTALL=""ALL"" SMSSITECODE=""HS1"" SMSCACHESIZE=""2048"" CCMHTTPPORT=""80"" CCMHTTPSPORT=""443"" CCMHTTPSSTATE=""0"" CCMFIRSTCERT=""0"""
Source List
file://sccmserver.somedomain.biz/SMSClient
file://sccmserver/SMSClient
MPs:
SCCMSERVER.SOMEDOMAIN.BIZ
Updated security on object C:\WINDOWS\system32\ccmsetup\.
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent.
"Running as user ""SYSTEM"""
Detected 36580 MB free disk space on system drive.
DetectWindowsEmbeddedFBWF() Detecting OS Version
"Client OS Version is 5.1, Service Pack Version 2"
Client OS is not a supported Windows Embedded Platform
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.
Deleted file C:\WINDOWS\system32\ccmsetup\client.msi
Successfully ran BITS check.
IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed.
Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab.
Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml
Successfully loaded ccmsetup manifest file.
"Adding file 'http://SCCMSERVER.SOMEDOMAIN.BIZ:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\client.msi'."
Starting BITS download for client deployment files.
Download Update: 76883 out of 17847296 bytes transferred.
Successfully completed BITS download for client deployment files.
Successfully downloaded client files via BITS.
Updated security on object C:\WINDOWS\system32\ccmsetup\.
An MP does not exist on this machine.
No client is currently installed.
Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
"MSI PROPERTIES are INSTALL=""ALL"" SMSSITECODE=""HS1"" SMSCACHESIZE=""2048"" CCMHTTPPORT=""80"" CCMHTTPSPORT=""443"" CCMHTTPSSTATE=""0"" CCMFIRSTCERT=""0"" SMSPUBLICROOTKEY=0602000000A40000525341310004000001000100E3FE16910549BC7E5EE664FED18FA09085E3BA678C50BB2018D0E525A1295C2FFE7611C7B23EF1A0974744C9785CAC840CA5C1C12FD14B9D37BF62BD70A109F1537B8F1D66D979996FE9007EC8F6DD2E121182C55FC7B9E2E49DBFE3F56E6CFAEF3FF0C1EE6837D95A04ED8A45AD5B198687C372B43AA3D83316A655AB0EF4B8 INSTALL=ALL"
IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' is MS signed.
Running installation package
Package: C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi
Log: C:\WINDOWS\system32\ccmsetup\client.msi.log
" Properties: INSTALL=""ALL"" SMSSITECODE=""HS1"" SMSCACHESIZE=""2048"" CCMHTTPPORT=""80"" CCMHTTPSPORT=""443"" CCMHTTPSSTATE=""0"" CCMFIRSTCERT=""0"" SMSPUBLICROOTKEY=0602000000A40000525341310004000001000100E3FE16910549BC7E5EE664FED18FA09085E3BA678C50BB2018D0E525A1295C2FFE7611C7B23EF1A0974744C9785CAC840CA5C1C12FD14B9D37BF62BD70A109F1537B8F1D66D979996FE9007EC8F6DD2E121182C55FC7B9E2E49DBFE3F56E6CFAEF3FF0C1EE6837D95A04ED8A45AD5B198687C372B43AA3D83316A655AB0EF4B8 INSTALL=ALL"
MSI: Action 15:21:14: INSTALL.
MSI: Setup failed due to unexpected circumstances The error code is 80041002
MSI: Action 14:54:01: Rollback. Rolling back action:


Installation failed with error code 1603
-------------------END LOG ----------------


Resolution:


Rebuild the WMI Repository by following the steps outlined in the following post
http://www.madanmohan.com/2010/10/rebuilding-wmi-repository.html

Rebuilding and reinstalling the WMI Repository

If you experience behavior when using WMI, such as application errors or scripts that used to work are no longer working, you may have a corrupted WMI repository. To fix a corrupted WMI repository, use these steps:

Windows XP and Windows Vista

Click Start -> Run and type CMD.EXE
Note: In Windows Vista, you need to open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

Type this command and press Enter:

net stop winmgmt

Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad). %windir% represents the path to the Windows directory, which is typically C:\Windows.

Switch to Command Prompt window, and type the following and press ENTER after each line:
net start winmgmt
EXIT

For Windows XP Service Pack 2 and Service Pack 3

Click Start, Run and type the following command:
rundll32 wbemupgd, UpgradeRepository

This command is used to detect and repair a corrupted WMI Repository. The results are stored in the setup.log (%windir%\system32\wbem\logs\setup.log) file.

For Windows Vista

Open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type the following command:

winmgmt /salvagerepository

The above command Performs a consistency check on the WMI repository, and if an inconsistency is detected, rebuilds the repository. The content of the inconsistent repository is merged into the rebuilt repository, if it can be read.

For Windows Server 2003

Use the following command to detect and repair a corrupted WMI Repository:

rundll32 wbemupgd, RepairWMISetup

Re-registering the WMI components

The .DLL and .EXE files used by WMI are located in %windir%\system32\wbem. You might need to re-register all the .DLL and .EXE files in this directory. If you are running a 64-bit system you might also need to check for .DLLs and .EXE files in %windir%\sysWOW64\wbem.

To re-register the WMI components, run the following commands at the command prompt:
  • 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 
Registering WMI Service itself

Open the command console, type "net stop winmgmt". When you get the warning that other services need to be stopped type 'Y' and continue.

Open 'My Computer' and then go to the folder '%SystemRoot%\System32\WBEM\Repository' and delete that folder.

Reboot your system.

After you login, open the command console, and type the following commands in order: 

winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf
Note: If this doesn't fix the problem, you need to try reinstalling Comprehensive rebuild method.

Comprehensive rebuild method

Important note: If you've installed a Service Pack, you need to insert your Windows XP CD with Service Pack integration (called as the Slipstreamed Windows XP CD). If you don't have one, you may point to the %Windir%\ServicePackFiles\i386 folder for a recent version of the system files required during WMI repair. Or you may create a slipstreamed Windows XP CD and insert it when prompted.


Click Start, Run and type the following command, and press ENTER:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

Insert your Windows XP CD into the drive when prompted. Repair process should take few minutes to complete. Then restart Windows for the changes to take effect.

Note that none of the above two methods restore the missing files related to Windows Management Instrumentation (WMI). So, below is a comprehensive repair procedure that restores all the missing WMI modules. In case of missing WMI modules, you may use the following method.

Repair WMI using BAT File:

Most of the WMI problems can be solved by rebuilding the WMI Repository, re-registering the WMI components. To automate this, you could create a BAT file. Copy the following lines to a text file and save it with .BAT extension and run it to fix common WMI issues.
net stop winmgmt /y
%SYSTEMDRIVE%
CD %windir%\system32\wbem
rd /S /Q repository
net start winmgmt
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s