Thanks. It seems that it was a versioning issue, as I recompiled my service with the 3.3 components and it's now working correctly...

Michael