<p>I have a recollection that this can also happen if the account Mercury is running under doesn't have access, as a result of folder permissions, to all the folders Mercury needs.</p><p> Chris </p>

<p>Hello</p><p>this is my first post from a new user of mercury 32 which has just been licensed.</p><p>Have been trialing it for a few weeks and my customer decided to go with it and buy it.</p><p>Unfortunately  the server it is running on (HP proliant, W2003 Server) has started to generate errors within the mercury application.</p><p> </p><p>Mercury.exe - application error</p><p>The instruction at 0x0046a7ad referenced memory at 0x00000010. the memory could not be written</p><p> </p><p> </p><p>I have logged this with support but would appreciate some feedback from the forum if anyone can shine a light on the problem.</p><p>The proliant does very little, has lots of memory, RAID 1 and gives no ther issues apart from mercury.</p><p> </p><p>Any advice would be grateful</p><p>thanks</p><p> Alan</p><p>email: alan@hallam-it.co.uk </p>

<p>Is there some process on the server that might interfere with Mercury's network access or disk access, for instance some kind of anti-virus software?</p><p>/Rolf </p>