Need help with a failed Task Sequence (SCCM 2007 R2 - 4.00.6487.2000)
I have three stubborn workstations (among over three thousand) that are not completing an advertised Task Sequence. Each one is reporting a "Last Execution Result" of 261 in the SCCM report. xcerpt for SMSTS.log Getting assignments from local WMI. TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found non-active policy: WPG20781-WPG00228-B7FF86B5 TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: WPG20586-WPG001DB-76A64A05 TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found non-active policy: {68f7c923-bdc4-48cd-9dfc-4a7225b9bdbe} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {8ab914f4-d338-4784-8550-15dda3a9c6d1} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {2c6b45e4-9fb1-44b3-8d63-1a4d47b964fd} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {2486de55-691e-41b5-9eec-45ad1f02931e} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {3a700958-a291-4ab3-86b7-361d74d7da66} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {4c397093-68b3-4846-8d34-52dd25247228} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {ca204589-f478-4ded-b2ab-84cb73115878} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {0e85baf4-46d4-4fd0-8000-0cafcbcbbf73} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found non-active policy: {68f7c923-bdc4-48cd-9dfc-4a7225b9bdbe} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: WPG2034C-WPG0013A-E8721773 TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {2c019afc-048a-4b9e-ab1d-947741907c12} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: WPG20E37-WPG00473-A1E321D1 TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: WPG20551-WPG001C1-486BAF91 TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: WPG20782-WPG00228-BAB6C06C TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {7f01adca-02fb-46d6-9ead-56f7744e7d5a} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {dea7ca6a-cd84-4723-a3e5-a38c1de3729c} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {28387c66-0c93-46c0-bee3-73e8e6ac60df} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {eea39c32-67c3-4edb-9354-a054a68ee15b} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: WPG20BAB-WPG000B0-A30D9498 TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {d814a322-e9a6-4ed5-b2ea-aea9ebb839b9} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) found empty policy xml: {bba28492-1f60-4f2e-b533-da43e42d6a1b} TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) Successfully read 106 policy assignments. TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) Downloading policy body {72b0d437-2965-49f6-877a-66fbd4f547da}. TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) Found NetworkAccessUsername/NetworkAccessPassword from NAAConfig CCM_NetworkAccessAccount TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) Network Access Account has a non-empty value TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) Cannot find ClientConfig CCM_ClientAgentConfig TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) Error initializing policy environment variables. Code 0x80040105 TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) Error initializing TS environment. Code 0x80040105 TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) Task sequence launcher advertisement failed!. Code 0x80040105 TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs TSLauncher 2/24/2010 10:05:02 AM 2896 (0x0B50) In researching the error 0x8004105, I found this on the MS Technet site: http://technet.microsoft.com/en-us/library/bb735886.aspx Troubleshooting Operating System Deployment Using Custom Error Codes 0x80040105 Could not find CCM_ClientAgentConfig raw policy Make sure policy is downloaded locally. Check policy agent log for details. The PolicyAgent.log doesn't tell me much. It seems rather cryptic. I have tried to refresh the policies in the SCCM Configuration Manager on one of the workstations to no avail as well as repairing the SCCM client. So, is there anything else I can try? I can't seem to find anything on that 261 exit code and the Technet site is not very helpful.
February 24th, 2010 11:16pm

Hello Gilles,My experience with these policy errors is that I have to recreate the wbem repository on the clients. That's a full uninstall of the CCM client, stopping WMI (and dependent services), renaming the Respository folder in windows\system32\wbem, restarting WMI (and the other services), deleting the ccmsetup and ccm folders, and then re-installing the CCM client. After all that, everything always works. If I try to shortcut anything, say just re-install the client, or don't delete the ccm-related folders, then I have limited results (maybe 50% work), so I don't bother and just rip the whole thing out the first time. I also find that there are other advertised programs and software updates that didn't run properly on these clients, so they take off, too. It's weird , because some advertisements work, some fail and some never run, so running down the "No Status" clients can help ID these bad boys.Seems like I have to rebuild 1% - 2% a month...Russell
Free Windows Admin Tool Kit Click here and download it now
February 25th, 2010 1:43am

On you 'Computer Client Agent Settings' on the site (Site Settings, Client Agents, Computer Client Agent), try modifying a property (e.g., State message reporting cycle). This will force the site to generate a new ClientConfig policy.
February 25th, 2010 2:59am

On you 'Computer Client Agent Settings' on the site (Site Settings, Client Agents, Computer Client Agent), try modifying a property (e.g., State message reporting cycle). This will force the site to generate a new ClientConfig policy. I tried changing the "State message reporting cycle" from15 minutes to 20 minutes and then back to 15 after a few hours. It seems to have helped two of three workstations. I am now left with only one stubborn machine.I may have to try the brute force method and completely remove the SCCM client and re-installing it.
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2010 8:37pm

On you 'Computer Client Agent Settings' on the site (Site Settings, Client Agents, Computer Client Agent), try modifying a property (e.g., State message reporting cycle). This will force the site to generate a new ClientConfig policy. I tried changing the "State message reporting cycle" from15 minutes to 20 minutes and then back to 15 after a few hours. It seems to have helped two of three workstations. I am now left with only one stubborn machine.I may have to try the brute force method and completely remove the SCCM client and re-installing it. I didn't need to completely remove the SCCM client. I deleted the CCM branch in the WMI repository which initiated a repair of the SCCM client and thus repopulated the repository after a reboot of the workstation. Just doing a repair of the client in the Configuration Manager was not enough to clear the WMI cache. I was able to do this by using the "SCCM Client Center" by Roger Zander. This tool is available on Sourceforge.net. Great tool!The first two workstations, although working now, probably still have some WMI corruption in the CCM branch and would probably benefit from have a WMI repair initiated. If such a problem does happen again on those two, I will try that. In the meantime, I will leave them alone. Kerwin's initial suggestion had a smiliar effect on the first 2 workstations by forcing a ClientConfig policy to be generated, but I would like to avoid making changes that affect the whole site every time a couple of workstations run into trouble.
February 26th, 2010 11:06pm

Gilles, Thanks for the reference to SCCM Client Center. Roger Zander has done a remarkable job with this tool, and I look forward to testing out all the buttons and menu items to see what they do. The WMI repair section appears to handle what I've been doing manually, so that alone will save tons of effort. You are in Canada, yes? Congratulations on one of the best Olympics ever! The Games were not only executed excellently, Canadian athletes were absolutely splendid (IMHO). I think the whole world, including the US, was happy and grateful for your country's achievements. I'm in Oregon, and we often travel up to B.C. for truly wonderful vacations. Magnifique! Russell
Free Windows Admin Tool Kit Click here and download it now
March 1st, 2010 7:47pm

Hi all, i have the same trouble, like the subj, but simple changes in Computer Client Agent doesn't help. Part of smsts.log: Preparing Policy Assignment Request. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Setting transport. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Setting site code = A1L. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Setting client ID = GUID:8BDE89F6-C835-4B32-B0FC-396C851CCEFB. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Getting assignments from local WMI. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {1903dcc2-9573-4ea8-abfb-69e6b5768e42} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {6c40a544-3b4e-4549-9471-8566280ff303} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {1a191032-8a12-49ac-821b-9f1baa12b9e8} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found non-active policy: {b5e0957c-94b1-4785-86f8-fbe553d4f567} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {c151efc5-d79e-4d91-b014-72ec9670d192} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {251e22b4-f049-445e-8fd2-bacf8021a42d} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {9421bb5e-b99f-408a-99b8-7be0ad1ebc0a} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {1a9e806d-1726-4577-adf8-7951444c8efc} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {b8444e80-510d-4104-a1cf-592a1b06f297} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {3f6e55a9-ca73-4de2-b476-23ed3f2fa4db} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {e77ec7b1-97fb-4629-9fe7-016d15757487} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {7835254e-23d8-4934-a1e8-79d428aa2ba7} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {55c26562-ef69-4edd-8c6c-6da4c4fc70f0} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) found empty policy xml: {bdbc9c74-2261-4230-aae1-75338b71c53d} TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Retrieving Policy Assignments: TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Processing Policy Assignment {8090ce05-46ce-4ef3-a7e4-94f3784e5719}. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Processing Policy Assignment {998b114e-75af-41d3-8f8a-33b145a259d5}. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Processing Policy Assignment {e2ad2504-117b-4d91-84d3-151b0dfb03f5}. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Processing Policy Assignment {28c30b76-f387-46f2-8e25-b6f9fd8bb86d}. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Processing Policy Assignment DEP-A1L20196-A1L0010B-0A2DC1C3. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Processing Policy Assignment {2bc6e2c4-a1f2-486d-848b-409de1f9ba26}. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Processing Policy Assignment A1L20196-A1L0010C-DBBBC9D6. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Processing Policy Assignment {3b884c54-c215-4c65-86b1-adcd0e900f3b}. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Successfully read 8 policy assignments. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Downloading policy body {e2ad2504-117b-4d91-84d3-151b0dfb03f5}. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Preparing Policy Body Request. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Setting transport. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Setting policy location = http://<mp>/SMS_MP/.sms_pol?{e2ad2504-117b-4d91-84d3-151b0dfb03f5}.4_00. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Executing Policy Body Request locally. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) ::DecompressBuffer(65536) TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Decompression (zlib) succeeded: original size 773, uncompressed size 2864. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Reading Policy Body. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Parsing Policy Body. TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Found NetworkAccessUsername/NetworkAccessPassword from NAAConfig CCM_NetworkAccessAccount TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Network Access Account has a non-empty value TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) !aTSPolicyObjectArray.empty(), HRESULT=80040105 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1462) TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Cannot find ClientConfig CCM_ClientAgentConfig TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) PolicyMgr.TSPolicyManager::GetBrandingTitle(sBrandingTitle), HRESULT=80040105 (e:\nts_sms_fre\sms\client\tasksequence\launcher\tslauncher.cpp,128) TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Error initializing policy environment variables. Code 0x80040105 TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) LoadPolicyBasedEnvVars(), HRESULT=80040105 (e:\nts_sms_fre\sms\client\tasksequence\launcher\tslauncher.cpp,778) TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Error initializing TS environment. Code 0x80040105 TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) InitializeEnvironment(), HRESULT=80040105 (e:\nts_sms_fre\sms\client\tasksequence\launcher\tslauncher.cpp,962) TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Task sequence launcher advertisement failed!. Code 0x80040105 TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) **Please cleanup TSM directory before you rerun the advert** TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Finalizing logging from process 4004 TSLauncher 07.07.2011 14:23:51 3136 (0x0C40) Any search on "Error initializing policy environment variables. Code 0x80040105" have no working result. Do someone have any ideas? Thanks in advance.
July 7th, 2011 8:49am

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

Other recent topics Other recent topics