Unfortunately, this is a known issue. It is unclear whether the number of objects or the size of the image is the problem. I have the problem. However, in my experience, when you save Moose images of more than 300Mb on a Windows Server, they get corrupted. However, on a Windows7, it seems I can work with larger images. Cheers, Doru On Sat, Nov 17, 2012 at 11:53 AM, Fabrizio Perin <fabrizio.perin(a)gmail.com>wrote;wrote: -- www.tudorgirba.com "Every thing has its own flow"

The problem is the Windows VM, not the image. So, as long as you build the image on Windows, there isn't much you can do. But, the good news is that the image does not crash while it is created actually. So, you can still run the exporter to Hudson. So, what I do is to export the XML report, and when I need to take a look at the live image, I load the MSE file again. Ideally, I want to do it via FuelMoose, but this is broken these days, too. Cheers, Doru On Mon, Nov 19, 2012 at 12:47 PM, Fabrizio Perin <fabrizio.perin(a)gmail.com>wrote;wrote: -- www.tudorgirba.com "Every thing has its own flow"