I see… in the few times I’ve seen it, it didn’t affect the designer, and everything just kept going along. What your describing definitely doesn’t seem harmless. I’ll try to see if I can track down some lead on why this might be happening, but in the mean time, if it’s happening consistently for you perhaps you could log some details and send them in:
- In the gateway, go to Console>Level and look for “Progress”. Set the level of “Gateway.ProgressManager” to “All”
- In the designer, go to “Help>Diagnostics”
- Next to the tabs, right click, and add “logging levels”.
- Look through the list for the entry that ends with “ClientProgressManager” and set it to all (trace).
- Go through your procedure that locks the designer up.
Now, on the gateway side, just grab the “wrapper.log” file from the install directory. On the gateway side, go back to Help>Diagnostics, and select the “console” tab. Unfortunately I think you’ll have to manually select everything and copy/paste it into note pad. Send those two files to email@example.com, or post them here, and hopefully it will help me track this down more quickly.
After doing all this, you can set those two loggers back to “info”.
If you don’t have time for all this, don’t worry. I’m going to try a variety of things on different machines, but if you can get that I’m sure it will help.