This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

0x80041f09 Error on Setup

I have one workstation that will not install Sophos.  It is Windows XP Pro 32bit, all current patches, and we JUST uninstalled Sunbelt VIPRE security.  

I start the install, and part way through, it backs off the install and throws error 0x80041f09 - contact network admin (me).

I have tried all the KB articles from sophos, including checking registry permissions, rebooting, re-registering MSInstaller (per sophos AND microsoft instructions), checked credentials, logged on a network AND local admin to run the install - all to no avail.

I have scoured the registry and deleted any keys the reference sophos.  I've rebooted many times, tried as multiple users (with admin rights) to install this.  Checked the system and application logs in windows and all I get are "inspecific installer errors" that lead nowhere.

Any help?

:1083


This thread was automatically locked due to age.
Parents
  • HI,

    Have you identified the package that has failed to install?  From that we can check the relevant install log.

    Presumably it's the Anti-Virus package as opposed to AutoUpdate, the Firewall or RMS?

    If it's the Anti-Virus package (the most likely): what does the MSI log and custom action log say for the SAV install?

    If AutoUpdate attempted to install SAV (as it would typically on a managed install) it will create the logs in:

    %windir%\temp\

    They will be called:

    Sophos Anti-Virus Install Log_<timestamp>.txt

    Sophos Anti-Virus CustomActions Log_<matchingtimestamptothatabove>.txt

    It keep a history of 4 so I tend to sort by "Date modified" to quickly find the latest.

    N.B. If you have run the install of SAV as the logged on user, as would be the case if you ran the standalone installer of SAV or just ran the MSI, they would be in:

    %temp%

    I would start by opening up the log file:

    Sophos Anti-Virus Install Log_<timestamp>.txt

    If it says that it failed at the bottom of the file, then search up for:

    return value 3

    This will help identify what the installer was trying to do and what might have failed.  Maybe you could post the lines around the failure line and check the customer action log around the same time.

    Finding the line in the install log file that details the problem is the first step.

    Hope this helps,

    Jak

    :7929
Reply
  • HI,

    Have you identified the package that has failed to install?  From that we can check the relevant install log.

    Presumably it's the Anti-Virus package as opposed to AutoUpdate, the Firewall or RMS?

    If it's the Anti-Virus package (the most likely): what does the MSI log and custom action log say for the SAV install?

    If AutoUpdate attempted to install SAV (as it would typically on a managed install) it will create the logs in:

    %windir%\temp\

    They will be called:

    Sophos Anti-Virus Install Log_<timestamp>.txt

    Sophos Anti-Virus CustomActions Log_<matchingtimestamptothatabove>.txt

    It keep a history of 4 so I tend to sort by "Date modified" to quickly find the latest.

    N.B. If you have run the install of SAV as the logged on user, as would be the case if you ran the standalone installer of SAV or just ran the MSI, they would be in:

    %temp%

    I would start by opening up the log file:

    Sophos Anti-Virus Install Log_<timestamp>.txt

    If it says that it failed at the bottom of the file, then search up for:

    return value 3

    This will help identify what the installer was trying to do and what might have failed.  Maybe you could post the lines around the failure line and check the customer action log around the same time.

    Finding the line in the install log file that details the problem is the first step.

    Hope this helps,

    Jak

    :7929
Children
No Data