Ohh, didn't think that anyone was reading this. However I have fixed the problem and am no longer getting the no buffer space "WSAENOBUFS" error. I have created an alias which is formatted much like that of /dde and $dde that caches the dde results (in varibles) for up to 8 hours on certain things and 16 hours on others. I have yet to see the error and the bots and system seem to be running better than ever. As I may have explained in other posts about my problem the system overall seemed to be out of buffer space, the no buffer space available just seemed to be one of many things errors that occured due to lack of system resources. I was unable to run programs or even remotely login via RDP.
Since our hub bot doesn't directly do dde nearly as much as it used to and the same system is operating much much better I must assume that the insane amounts of DDE calls and commands between our hub and the 10 other bots was causing the system to crap out.
