Setting wizard error: An error occurred while retrieving policy for this computer  (0x80004005)
I'm unable to build a PC through Task Sequence by booting from media. I'm running SCCM 2007 SP2 This just started to occurring. From the smsts.log I see the following entries: dwBodyLength <= m_nMaxReplySize, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2201) reply message body length is too long (4405510, 4194304) DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2754) oPolicyAssignments.RequestAssignments(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,883) Failed to request policy assignments (Code 0x80004005) I'm not sure what's changed or what body length is too long. I don't believe it's a certificate issue as non are blocked.
October 17th, 2011 9:12am

It Could be the problem with your PXE Certificate issue. Are you running your SCCM Site mode in Native mode ? If so then you need to create a certificate for PXE Server and assign it. You can check this link for creation of PXE Certificate http://www.opsvault.com/how-to-create-a-certificate-for-a-pxe-service-point-in-sccm-2007/ If the site is runining in Mixed mode make sure the PXE self certificate is not blocked . Also look this discussion http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/3b88f926-8565-4e71-9fcb-551490c08745 Thanks, This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2011 9:40am

Thanks Paddy, We're running in Mixed Mode and we're not using PXE. We build with WinPE media and the certificates are not blocked. I don't know what this means: reply message body length is too long (4405510, 4194304)
October 17th, 2011 11:11am

Did you also checked your PXE certificate expiry date, Make sure that the certificate should not expire and it should valid. This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2011 11:47am

I did, and we don't have any PXE certificates only Boot Media
October 17th, 2011 11:52am

While Boot Media creating PXE certificate will be injected in the media.... so i thought to verify the expire date of PXE certificate in your SCCM Console (I had same error in the Native mode site.. so requested the same steps to check the settings).This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2011 11:59am

Yeah I double checked. Now, is it necessary to import the cert into the certificate store?
October 17th, 2011 3:26pm

I might have answered my own question... We're running mixed mode with self signed certificates.
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2011 3:40pm

Hi, In the log: dwBodyLength <= m_nMaxReplySize, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2201) reply message body length is too long (4405510, 4194304) There is a hard limit in the product which indicates that there is a 4MB limit for policy body download when processing task sequences. 4405510=4.20142M > 4M See Task Sequence Fails Because the File Size Exceeds the 4-Megabyte (MB) Limit Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
October 19th, 2011 2:48am

Hi, In the log: dwBodyLength <= m_nMaxReplySize, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2201) reply message body length is too long (4405510, 4194304) There is a hard limit in the product which indicates that there is a 4MB limit for policy body download when processing task sequences. 4405510=4.20142M > 4M See Task Sequence Fails Because the File Size Exceeds the 4-Megabyte (MB) Limit Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2011 9:47am

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

Other recent topics Other recent topics