Danforth Posted November 27, 2011 Report Share Posted November 27, 2011 Our Win2003 Standard SP2 installation was working fine for weeks (no other checkers active) until I upgraded to 3.0.5 last Friday. Since then, I noticed a popup over the tray icon saying an Immunet service had not started properly, and suggesting a reboot. The popup did not stick around long enough to read the service name properly, and there was no logged error in Event Viewer or that I could find in the Immunet program folder. However, the Immunet Service WAS running when I looked in Service Manager (and could be stopped ok when I tested that point later). Subsequently, I noticed that apps accessing files on the server were experiencing hangs. Uninstalling Immunet and rebooting was the only way to resolve them. I did a full/clean reinstall of 3.0.5 twice more, getting the same result each time. I even rebooted a second time after a successful reinstall, as the popup suggested, in case that really fixed it - it didn't. Local hangs were also occurring so I could not run the diagnostic tool. It's a show stopper - 3.0.5 has broken something that was fine under 3.0.4 and your installation process doesn't provide an obvious way to install the older version so I can use it again. Suggestions very welcome. Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.