I have seen sometimes where that setting has caused this.
What version is your Core?
What version are your agents?
Specifically what version of sdclient.exe and lddwnld.dll are on your agents?
We are supposed to be on SP2a on both our core and clients. I looked at one machine I'm testing with. The version of sdclient.exe is 220.127.116.11 and the version of lddwnld.dll is 18.104.22.168
The SDClient.exe is the correct SP2 version
The LDDwnld.dll file is newer, must have come from a Post SP2 patch.
Sounds like a bug in lddwnld.dll or maybe in the TMC service where the client is trying to get a file from a peer but for some reason it is crashing.
Do you have a support ticket on this? This might have to come to support.
I do have a ticket opened. They let me know today that SP3 has been released a couple days ago and applying this to our core and clients would be the first step into troubleshooting this issue. I think that is a lot of work to just find out after the fact it didn't solve the issue. Our server admin is out until 5/18 and I was hoping there would be another solution to try.
That is not normally the default procedure. We don't just blatantly say that for all issues.
I think that in this instance there is some significant development work in SP3 around improving behinds the scenes peer download technology. So they are not giving you a quick answer to close your case or anything, in your case with your issue, it really is something that has a high probability of resolving the situation.
But again, despite the work, you are correct in that there is a chance the issue may still exist after installing SP3.
Buy the way, I did a pilot on SP3 with a customer in Chicago and it went really smooth for us. Took 30 minutes from when we clicked Setup.exe until it was done.
So lets look at your options:
1. Troubleshoot at the current version and root cause the issue in 8.8 SP2. You could turn on xtrace of sdclient, lddwnld, and tmcclient and tmcservice and try to get more debugging. Issues like this can be time consuming and some of the more difficult to find the issue as so many pieces are involved: Core, Client and their processes such sdclient, lddwnld, tmc, peers and their processes and many steps happen on the network and on different machines.
- If you find it is a configuraton issue, you make whatever change and go on.
- However, you may find that it is a bug you are encountering that most environments don't see, and in order to submit a CR, it would need to duplicate in SP3. So you have to install SP3 to move on. If SP3 fixes the issue, then the troubleshooting would feel like a wast of time.
2. You could go ahead and install SP3.
- However, if you install SP3 and it doesn't fix it, you may feel like the time to install SP3 was a waste (though at least you got your box patched out of it) and then you will have to start troubleshooting with xtrace until you figure it out.
- If it is not a configuration issue, you submit a bug and wait for a patch, that will require SP3 be installed.
3. Or you can live with the issue for now.
- So Limit remote downloads to one device at a time is a key feature but not exactly required. You can simulate this using two tasks by deploying a task to a single machine per subnet and once finished, deploy a task with a peer download only delivery method afterwards.
You should discuss these options with your support engineer.