I'm unsure exactly what is causing my issue at the moment as I've tried a multitude of different settings and none have yet to work right. This may have nothing to do with Ftprush, though if not, Ftprush is not handling the issue at all. Currently I have narrowed the client setup to 10 per tab, 5 per site, 2 sites in use. I am using the mircrush.dll to initiate the transfers which had no problem before the upgrade. I've tried changing the "per tab" settings which seems to have no effect on the issue.

When I have a list of transfers queued and mircrush queues another transfer, it opens another tab. That's cool.. I don't mind the multiple tabs open as long as it will reuse empty tabs once the queue in that tab has completed. The issue is sometime after the second tab is opened, the transfers on the first tab stop - usually in the middle of a transfer. This continues on as I don't think the new tab's connections actually ever get to login due to the total logins per site going over the max allowed logins that we USED to be able to set! (where did that setting go!?) The combination of the above cause more tabs to be opened with unsent queues. The only way I've found to fix the issue is to close Ftprush and reopen the queues one at a time into the first tab and restart transfers. So much for automation.

In any case, I'm unsure as to whether or not I am configuring something wrong or whether this is (unfortunately) the intended behavior. Any help is greatly appreciated as this has been aggravating me since the upgrade.

This is unusable. I've had to switch back to single connection mode to be able to even use the application. Please let me know if there is anything I can try to make things work. Until then, I'm going to try single connection mode and hope that I don't have too many issues without being able to limit connections per site. Sadly, I might have to revert back to v1 as it seems v2 is too buggy at the moment to use in a production environment.

I have the same issue (already posted as a reply to the sticky thread above) The difference is that my connections "Time out" and do not move onto the next queue. There doesn't seem to be a constant timing to this. 10 Connections can transfer OK for an hour then suddenly 1 or 2 will die off. Over time they all shutdown with many more files in the queue to keep transferring. I have to shutdown FTPRush and restart it. Simply cancelling the transfers and reconnecting only restarts the connections that haven't died.

exoduz wrote:I'm unsure exactly what is causing my issue at the moment as I've tried a multitude of different settings and none have yet to work right. This may have nothing to do with Ftprush, though if not, Ftprush is not handling the issue at all. Currently I have narrowed the client setup to 10 per tab, 5 per site, 2 sites in use. I am using the mircrush.dll to initiate the transfers which had no problem before the upgrade. I've tried changing the "per tab" settings which seems to have no effect on the issue.

When I have a list of transfers queued and mircrush queues another transfer, it opens another tab. That's cool.. I don't mind the multiple tabs open as long as it will reuse empty tabs once the queue in that tab has completed. The issue is sometime after the second tab is opened, the transfers on the first tab stop - usually in the middle of a transfer. This continues on as I don't think the new tab's connections actually ever get to login due to the total logins per site going over the max allowed logins that we USED to be able to set! (where did that setting go!?) The combination of the above cause more tabs to be opened with unsent queues. The only way I've found to fix the issue is to close Ftprush and reopen the queues one at a time into the first tab and restart transfers. So much for automation.

In any case, I'm unsure as to whether or not I am configuring something wrong or whether this is (unfortunately) the intended behavior. Any help is greatly appreciated as this has been aggravating me since the upgrade.

Thanks in advance

If you need to use mircrush.dll, we suggest you use version 1.x.Version 2.x support mircrush.dll not very well because of simultaneous transfer.

Any chance the .dll will be updated to provide support? I would like to use the version that's receiving updates if at all possible. They say "If it's not broke, don't fix it." but I don't really want to use dead software.