PENDING ConfigMgr TS failed with error code 80004005

[Nthabiseng]

Hello,

Please help, I am Upgrading machines to windows 10 1909, I'm facing challenge where task sequence fail with error code 80004005. any ideas how i can resolve this issue?.

Thanks,

 

[Gokul]

Hi There ,

80004005 is a generic issue , This error codes pops something broken. So you need to dig smsts.log . And have you checked the content distribution status of package ? .

 

[Nthabiseng]

Hi There ,

80004005 is a generic issue , This error codes pops something broken. So you need to dig smsts.log . And have you checked the content distribution status of package ? .

Hi,

I just checked my Distribution Configuration Manager, First distribution point, there is an error " Distribution manger failed to connect to distribution point, and on my second DP there is an error " distribution manager failed to access the source directory " and "Distribution Manager failed to instruct Scheduler to send package"

normally I distribute to both DP's . Task sequence distributed successful only on First distribution point. and failed to distribute to second DP.

How do i fix this error?

Thanks,

 

[Gokul]

So we have arrived on conclusion that this is due to package distribution

1.make sure your DP is online to get the package .
2.Port /Admin$ access check
3. For more info i would recommend to check the distmgr.log in your primary site
4.Try to redistribute the package
5. Go to the Monitoring Node > Distribution Status > DP Configuration status. Select the DP > at the bottom click on Details and verify all the content has been distributed successfully.
6.Try restart SMS agent host (Try last)

 

[Nthabiseng]

So we have arrived on conclusion that this is due to package distribution

1.make sure your DP is online to get the package .
2.Port /Admin$ access check
3. For more info i would recommend to check the distmgr.log in your primary site
4.Try to redistribute the package
5. Go to the Monitoring Node > Distribution Status > DP Configuration status. Select the DP > at the bottom click on Details and verify all the content has been distributed successfully.
6.Try restart SMS agent host (Try last)

The content has been distributed successfully to DP 1 and failed to distribute to DP 2.

on distmgr.log "Failed to process package HO10002A after 47 retries, will retry 53 more times $$<SMS_DISTRIBUTION_MANAGER><03-11-2020 15:14:20.941-120><thread=12464 (0x30B0)>".

 

[Gokul]

attach the full log file and check any queue is there or not (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER )

 

[Nthabiseng]

attach the full log file and check any queue is there or not (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER )

 

[Gokul]

• check the retry history folder (above), maybe you could see packages in queue if any
• redistribute the content again
• attach distmgr.log too

 

[Nthabiseng]

• check the retry history folder (above), maybe you could see packages in queue if any
• redistribute the content again
• attach distmgr.log too

Please see the attached distmgr.log .

 

[Gokul]

i can see that Package HO10002B is process queue . It smells like some space issue/AV . You can check you drive space . i would prefer configuring the DP other than in root drive (c drive).

 

[Prajwal Desai]

@Nthabiseng - Error creating package bundle to send copy of package HO10002B to site HO2 - You need to check why the packages are not sent to the DP. It could be a firewall / AV / security device blocking the content transfer. Can you also attach smsts.log file ?.

 

[Nthabiseng]

i can see that Package HO10002B is process queue . It smells like some space issue/AV . You can check you drive space . i would prefer configuring the DP other than in root drive (c drive).

Thank you, It was space issue

 

[Gokul]

Cool marking the thread solved