I had the same problem with GetFullState before. The solution for me was to break the result set up into two parts and ultimately return two blobs back to the calling thread. I could be wrong but I think I had to use the GetChanges\SetChanges methods to put the report back together. I'll have to look at the code to say for sure.
↧