SpecialK Posted April 17, 2014 Report post Posted April 17, 2014 Hello, I have installed a new DP on a remote location. There is still the old DP on site. So I activated the Pull DP feature for speeding up the package replication. It works like expected for round about the half of the packages. But suddenly, it stopped. So I looked up the pending packages in the console and removed the assignment from the new DP to have a "clean view". Now it looks like this in the console: So I tried to assign just one new package to the DP. This is what I get in the PkgXferMgr.log: Checking for sending capacity. Used 4 out of 9. COutbox::TakeNextToSend(pszSiteCode) Retrieved the snapshot for priority 2, there are 1 files in the snapshot. Found send request. ID: 21992EME, Destination: server1.mydomain.com Checking for sitesystem-specific sending capacity. Used 3 out of 3.Abandoning send request because no sitesystem specific sending capacity. Sitesystem server1.mydomain.com added to list of busy sites. Reset the send request to a pending state. I ask myself, why there is no sitesystem-specific sending capacity available (used 3 of 3). I would say there is no active sending to the specific DP according to the console. Is there some kind of possibility to reset the sending capacity for the DP? It's not possible for me at the moment to send any new package to the DP because of the error. Thanks and best regards SpecialK Quote Share this post Link to post Share on other sites More sharing options...