Found this good article here:
http://nikifoster.blogspot.com/2009/12/troubleshooting-packages-that-just-wont.html
These are the steps:
1. First delete the package from that DP using the console.
2. Wait for the package deletion message to arrive at the DP (keep monitoring the distmgr.log file).
3. Wait for this message to reach the central site (in the console, it should show version number as 0). This is important.
4. Run this query on the sccm database. If there is a child primary site, then run it on both:
update pkgstatus set sourceversion = 0, status = 2 where id = 'packageid' and sitecode = 'xxx'
5. Now, reassign the package to the DP. This will cause the whole package to be resent and the package will be installed successfully at the DP.
http://nikifoster.blogspot.com/2009/12/troubleshooting-packages-that-just-wont.html
These are the steps:
1. First delete the package from that DP using the console.
2. Wait for the package deletion message to arrive at the DP (keep monitoring the distmgr.log file).
3. Wait for this message to reach the central site (in the console, it should show version number as 0). This is important.
4. Run this query on the sccm database. If there is a child primary site, then run it on both:
update pkgstatus set sourceversion = 0, status = 2 where id = 'packageid' and sitecode = 'xxx'
5. Now, reassign the package to the DP. This will cause the whole package to be resent and the package will be installed successfully at the DP.
No comments:
Post a Comment