I guess part of my problem was that I didn’t know where to look for errors. My web service wasn’t showing errors, but apparently at some point errors *were* being sent back to the EvoStream server, only I didn’t know it.
I ended up installing a network sniffer (WireShark) and could determine that the error was indeed with my web service. I don’t know yet how to fix it, because I thought I already had it set up to receive messages that were Json, but apparently it was expecting Raw. I’m trying to figure that one out now. I belatedly realized that the code I was using to test sending to the my web service wasn’t actually sending it in "application/json" format and that’s why my webservice seemed to be working fine. As soon as I changed it to send to my web service correctly, I started getting the same errors I saw when I sniffed the network with WireShark.
So, sorry everyone … the problem was all at my end! Now, all I gotta do is figure out where I went wrong with my WCF web service.
Thanks everyone, for all your patience and help.
~~Bonnie