I had the same problem and same messages comming back... It turned out to be that my web service was usign the WORNG ASP.NET Version, I changed it to use the
correct one, 2.0, and all works fine now. You can do via the IIS management console
Cheers
Guillermo