Interesting observation. Is this working for others too? I just tried the same on one of the problem servers and was unable to use this to install avast on a server where it was failing to install.
What was the size of the original setiface.dll and after that procedure did you have a new setiface.dll in that directory and what size?
To fill people in on some background that file is the Alwil software supplied setup dll that surgemail calls into to run the actual installer. If it is missing surgemail should re-download a copy from netwinsite.com and use that instead. In my testing just now the failing to install system started with:
03/04/2012 01:58 p.m. 81,968 setiface.dll
Removing that did not seem to have surgemail redownloading the file (which I expected it to do), but downloading it manually from:
resulted in the newer (and smaller) version of this file:
14/04/2012 10:37 a.m. 79,706 setiface.dll
But even with that running the installer from the surgemail admin interface was still failing. This is on a system we have done a fair bit of messing with to try and get it to work so there may be other reasons now for it failing :-(
So it does look like the surgemail distributions still have the older setup dll in them which is something we can fix. Let us know if anyone else has better luck getting avast to install using the above procedure!
On Saturday 14/04/2012 at 8:01 am, surgemailHIDDEN@etwinsite.com wrote:
This is a tip for those with issues installing AVAST virus scanner on Windows Server.
On two separate Windows Server machines AVAST would not install. We were using server 2003 and server 2008 with SurgeMail Version 6.0a4-4.
The solution was to remove "C:\surgemail\avast\setup\setiface.dll" and then retry the AVAST installation through the web gui.
In both cases this installed AVAST anti-virus correctly.