0x1204 - Installation of BizEd on a virtualized server: update issues

Discussion in 'ESET NOD32 Antivirus' started by rickub, Oct 7, 2009.

Thread Status:
Not open for further replies.
  1. rickub

    rickub Registered Member

    Joined:
    Oct 7, 2009
    Posts:
    2
    RESOLVED - 0x1204 - Installation of BizEd on a virtualized server: update issues

    Our environment is the kind of "2 servers on a single box". For a bit more clarity, it is a physical server (running Win2k3 R2), running a virtualized one inside (Win2k3 via VMWare). Both are to be protected, thus we bought Business Edition and a suitable license coverage.

    Installation on both machines was a breeze, updates - so far - not.

    Main issue is that automatic updates are working smoothly on the virtualized server (inside), and refusing to start on the main machine, croaking a "Updater: retval = 0x1204, failures: 38 NT AUTHORITY\SYSTEM" over log files.

    No proxy or other security-related issues. A search on 0x1204 on this forum led to little result, so far.

    Any pointer to a suitable manual or, better yet, to a solution?

    Many thanks in advance
    rick
     
    Last edited: Oct 7, 2009
  2. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    Hello rickub,

    Sometimes the error you see can be caused by a corrupt installation. I would try reinstalling the software and see if you get the same error when trying to update.
     
  3. rickub

    rickub Registered Member

    Joined:
    Oct 7, 2009
    Posts:
    2
    RESOLVED: 0x1204 - Installation of BizEd on a virtualized server: update issues

    Thanks WayneP,

    installation was fine - we found after some scanning that our issue was determined by an infection on the physical server (some sort of trojan on different .exe and .dll's).

    Removed the above via some malware cleaner, reboot... and voilà, outside box updated at boot time!

    Btw, your suggestion would have been my next move, in case.

    Thx again
    rick
     
Thread Status:
Not open for further replies.