Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 28798 views
  • Users 0 members are here
Options
Suggested
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

Software Update Failed (error 80040401)

ok_duck

Hi,

I'm new for Sophos Enterprise console and now is testing the software.

This is the error I encounter during update a computer. Below is error and I screenshot it down. Please advice and let me know what else detail I need to provide. Thanks in advance.


SUMTrace20150724T144615 :

2015-07-24 14:47:12 : Dispatcher started...
2015-07-24 14:47:12 : SelfUpdateOperation: Update in progress failed with error: 1603
2015-07-24 14:47:12 : Cmd-Terminal << [R0000] Restart complete.
2015-07-24 14:47:12 : Schedule '__MAINTENANCE_SCHEDULE__' entered new TimeBlock, trigger offset = 645 minutes.
2015-07-24 14:47:12 : Fri Jul 24 14:47:12 2015 - No action
2015-07-24 14:47:12 : EventLog: 3758112806 1 Inserts:> "Payload-SDDM" "56.1" "1603"
2015-07-24 14:47:12 : Cmd-ALL << [E4026][Payload-SDDM][56.1][1603] Failed to self-update from payload 'Payload-SDDM', version 56.1, because the installer returned failure. Error code: 1603
2015-07-24 14:47:12 : Cmd-Terminal <<
2015-07-24 14:47:12 : Fri Jul 24 14:47:12 2015 - No action

:58070


This thread was automatically locked due to age.
  • 0

    Hello ok_duck,

    SUM's self-updating fails. There should be a number of installer logs named MSIxxxxx.LOG with a size of 900+k in %windir%\temp\. Open a recent one, it should mention

    ******* Product: C:\ProgramData\Sophos\Update Manager\Working\Decoded-SDDM\A845A8B5-6532-4EF1-B19E-1DB2B3CB73D1\SUM.msi

     near the top. Search for a line containing Return value 3, the reason for the failure should be in one or more of the lines above. If it's not obvious post the snippet here.

    Christian

    :58073
  • 0

    Hi Christian,

    Thanks for the reply.

    I tried look for what you mentioned but what I found was kinda different, let me show you.



    and I attached the lastest SUMTrace log as well.

    Please advice. Thanks

    :58083
  • 0

    Hello ok_duck,

    normally ...\Update Manager\Logs\ would be the right place to look (and thanks for the log, BTW SUMTrace20150727T094125 is the latest, it shows that your version of SUM is still 1.5.4.11, meanwhile it should be 1.5.6.13).

    The log of the (in this case obviously failed) self-update is written to C:\Windows\Temp\ though, sort by date to get one of the recent MSIxxxxx.LOGs.

    Christian

    :58087
  • 0

    Hi Christian,

    Thanks for the reply.

    Somehow the issue fixed by itself after I didn't go into the Enterprise Console. Seems weird, yet solved. :smileyhappy:


    :58188
Unfiltered HTML