Single Client not receiving policy...
I have a machine that happens to be a VIP's machine (of course) that simply will not download policy. I think the issue may be related to a BITS corruption of some kind and I'm hoping someone here can point me in the right direction. Getting this individual to reboot his machine is nearly impossible, as is getting a window to fix it, so I'm hoping I only have to do it once. There aren't too many things to go on in the error logs, but I did find these lines in the DataTransferService.log: DTS::AddTransportSecurityOptionsToBITSJob - Failed to QueryInterface for IBackgroundCopyJobHttpOptions. BITS 2.5+ may not be installed properly. It does this several times mixed with notifications that it is trying to download policy and throws ERROR (0x80004002) as well. Other than that, there really isn't much to go on, but I would think that if it can't download because BITS is corrputed, it would prevent policy from being downloaded. I do see that 0x80004002 error elsewhere in the logs as well such as in the mtrmgr.log: CSWMtrClientConfig::Load - Failed to get an instance of CCM_SoftwareMeteringClientConfig, error 80004002 and the SmsClientMethodProvider.log: Failed to retrieve the requested schedule (80041002) Failed to send schedule (80041002) Method TriggerSchedule failed with error code 80041002 I have rebooted, verified the certificates and reinstalled the agent several times. Thanks in advance...
December 30th, 2009 10:07pm

Check if the BITS service is up and running on the client. The other errors *could* indicate a possible WMI issue.
Free Windows Admin Tool Kit Click here and download it now
December 30th, 2009 11:57pm

BITS is running and I've restarted the service several times.
December 31st, 2009 5:25pm

help? any way to "repair" BITS?
Free Windows Admin Tool Kit Click here and download it now
January 6th, 2010 1:03am

Since you only have a single window to repair everything, this is what I would do...Uninstall the SCCM clientStop WMIKill the repositoryRebuild the repository (Ref: http://windowsxp.mvps.org/repairwmi.htm)Remove the CCM, CCMSetup & SMS entries under HKLM\Software\MicrosoftDelete the C:\Windows\System32\ccm & ccmsetup foldersReinstall BITS manually (ver 2.5) (Link: http://www.microsoft.com/downloads/details.aspx?FamilyId=A064BF14-E54C-4E8C-85E7-1E3BE1628B2D&displaylang=en)Reinstall the SCCM clientI know, it's probably overkill but this is a nearly guaranteed way to fix EVERYTHING that could be broken. Also, I've done all of this (except install BITS) without ever logging into the box using PSExec. Just FYI, I'm sure BITS could be installed through PSExec too, I just haven't done it before. Scott GillSCCM Consultant
January 6th, 2010 3:08am

Sounds great - and I'm very familiar with PSExec, so I'll give it a shot. Thanks very much. Does any of this require a reboot?
Free Windows Admin Tool Kit Click here and download it now
January 6th, 2010 5:37pm

Nope no reboots necessary (usually), however there are occassionally outstanding circumstances in which a reboot is sometimes necessary. This is generally so rare it's not worth worrying about. If you can get the client uninstalled and ccm/ccmsetup folders deleted without a reboot you should be OK.Scott Gill SCCM Consultant
January 6th, 2010 8:08pm

Scott, I tried this and had no luck. What exactly did you mean by "Reinstall BITS manually"? I tried running it with the /quiet /norestart /overwriteoem switches but it doesn't look like it actually reinstalled BITS.
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2010 5:24pm

That's all I meant, just install the EXE over what's existing. Do you get any errors? Perhaps a newer version was already installed on the machine? You may just want to try reinstalling the client (it checks for BITS during install anyway), and see if it works again.Scott Gill SCCM Consultant
January 7th, 2010 7:44pm

yea, when I actually run it by hand (not command line remotely), it says "Setup has detected that a service pack version of this system is newer than the update you are applying. There is no need to install this update." I don't want to upgrade - I want to repair... if it helps at all, the BITS service is running and will restart without any problem. I did everything you said to and it is giving me the same errors.
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2010 8:35pm

What OS is on this machine?Scott Gill SCCM Consultant
January 7th, 2010 9:06pm

XP 32-bit
Free Windows Admin Tool Kit Click here and download it now
January 8th, 2010 12:07am

Any idea what version of BITS is installed? I have two options left.. "uninstall" bits (remove the windows update associated with BITS) and then go back and install that version again (it's probably version 3).Or, you could try this BITS repair "tool" that I found... I've never tried it before but it seems to fix some users issues with BITS. http://www.philmorgan.net/techie-tools/windows-update-bits-background-intelligent-transfer-service-fix-batch-file-for-windows-xpScott Gill SCCM Consultant
January 8th, 2010 1:55am

Well, when I run bitsadmin /util /version, it says its running 2.0, but when i check the file versions, they're even higher than the ones listed on the BITS 2.5 download page you provided above. I saw the Phil Morgan thing, but I was more than a little hesitant to run a random batch file found on the internet on a VIP machine. As for uninstalling BITS, I couldn't find KB923845 in either the Add/Remove Programs list or the HKLM\Software\Microsoft\Windows NT\CurrentVersion\HotFix key. This is Windows XP SP3, so maybe its not listed if it was installed along with that?
Free Windows Admin Tool Kit Click here and download it now
January 8th, 2010 9:32pm

Yeah I was a little concerned about the batch file idea too, but it was just an idea... I found this site regarding the version of bits and how to determine what version it is.. http://msdn.microsoft.com/en-us/library/aa362837(VS.85).aspxI checked on my machine which is XP SP3 and it has version 2.5 installed.Oh, I just found this command which should repair bits.. give this a shot:Bitsadmin /util /repairservice /forceScott Gill SCCM Consultant
January 8th, 2010 10:49pm

I tried the bitsadmin /util /repairservice /force command several times. It says it is successful but nothing changes. His qmgr.dll is 6.7.2600.5512 so it looks like its 2.5, but I don't know how to use the second part of that article... I'm not familiar with symbolic class identifiers or how to use them. Where on your machine did you find that 2.5 is installed? Was the KB in the Add/Remove list or did bitsadmin report the correct version? Thanks
Free Windows Admin Tool Kit Click here and download it now
January 11th, 2010 6:43pm

Kill the repositoryRebuild the repository (Ref: http://windowsxp.mvps.org/repairwmi.htm) Just a side note: rebuilding the repository is not recommended: http://blogs.technet.com/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx
January 11th, 2010 6:59pm

Kill the repositoryRebuild the repository (Ref: http://windowsxp.mvps.org/repairwmi.htm) Just a side note: rebuilding the repository is not recommended: http://blogs.technet.com/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx Yes I've heard this many times, but I've also repaired WMI using this method hundreds of times with no noticable side effects. "Data loss" in this instance really means that if you have done some custom additions to WMI, you could loose that data unless you re-load it (or if custom applications made changes to WMI). However, most of the apps I've seen do not use WMI. All of the HW and Registry data (99% of WMI) is reloaded automatically so the issue is negligable.However, Microsoft did a much better job with the WMI in Vista/Win7 and in the 2 years I have been supporting those OS's, I have never needed to rebuild a WMI on either OS. I believe the WMI in XP is just much more fragile than Vista/Win7 and there really isn't a fix for the issue (yes I did try the WMI update to XP, which doesn't seem to do much of anything).Scott Gill SCCM Consultant
Free Windows Admin Tool Kit Click here and download it now
January 11th, 2010 8:00pm

I tried the bitsadmin /util /repairservice /force command several times. It says it is successful but nothing changes.His qmgr.dll is 6.7.2600.5512 so it looks like its 2.5, but I don't know how to use the second part of that article... I'm not familiar with symbolic class identifiers or how to use them.Where on your machine did you find that 2.5 is installed? Was the KB in the Add/Remove list or did bitsadmin report the correct version?Thanks I just used the qmgr.dll version to identify version 2.5. Anyway, if this was an exec at my place, I would try one last thing, and that would be installing BITS 3.0 which, if installed successfully *Should* fix everything BITS related.If that doesn't fix the issue, IMO it would be time to re-image. However, seeing as it's a VIP, I'd have one of the techs build out a new machine and do a replace instead of a re-image. I don't consider this giving up, I consider it too much of a time investment to repair, and your time is valuable too, there's no reason to spend any more time on the subject.Scott Gill SCCM Consultant
January 11th, 2010 8:04pm

Thanks for your help Scott. I'll try the 3.0 installation... where can I download the installer?
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2010 12:58am

Check the system %path% variable on the machine where the problem is. If it contain the following: "%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem" then it is the root cause of the issue you have with SCCM client. %path% variable MUST contain "C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem" instead of above format. If this is the case just replace "%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem" by "C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem" You may do this remotely in the following registry hive: "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\Path" and reboot machine. Good luck.
January 17th, 2011 4:22am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics