Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 15 replies
  • Subscribers 1 subscriber
  • Views 27083 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

Return code: 74

Jvuz

Hi, 

I'm installing a lot of our machines for sophos remotely (via a command), which works very good. But for one pc, I'm getting the return code: 74 error. Does anybody has an idea what this means? I followed this page http://www.sophos.com/en-us/support/knowledgebase/12570.aspx, but this code isn't listed.

Jo

:50994


This thread was automatically locked due to age.
  • 0

    Hello Jo,

    no idea what 74 could be (it's 0x00000074, isn't it?). Guess only the logs on the endpoint can tell ...

    Christian

    :51002
  • 0

    And which log would that be and where should I look for it?

    :51006
  • 0

     %ProgramData%\Sophos\AutoUpdate\Logs\, the latest ALUpdate log (guess AU is relaying the error via RMS so you might be able to identify the failing component/step and the approximate time) and %windir%\temp, whichever Sophos log has been created around the time of the error.

    Christian

    :51010
  • 0

    Could you give me a hint for what I'm looking for?

    :51012
  • 0

    :smileyvery-happy: that would make it too easy :smileytongue:

    Seriously - this is a rare error, if I ever encountered it I can't remember. Take the ALUpdate log, search for ALUpdate started: - it should be in the first line with ALUpdate started: -Bootstrap  -NoGUI .... Search for the next  ALUpdate started:. If there is one it should be ALUpdate started: -ScheduledUpdate  -NoGUI ... (unless the installer has been called again). Go up from there (or from the end of the log), look for obvious errors and lines ending with returns 0 or returned 0.

    Christian

    P.S.: feel free to attach the log if you can't make out any error

    :51014
  • 0

    Feel free ;)

    I launched the command twice on the 12th of june.

    Jo

    :51034
  • 0

    Hello Jo,

    where do you get this 74 error? Which command do you run, how, and why? Asking because there's no apparent error in the log (no wonder you didn't find one) and there are two conspicuous data: The CID is on Nisos both in the old and new part and all the updates are scheduled ones.

    Chriistian 

    :51040
  • 0

    This is the command being launched via PDQ Inventory:

    \\sv20-57\SophosUpdate\CIDs\S000\SAVSCFXP\setup.exe -mng yes -crt R -updp \\sv20-57\SophosUpdate\CIDs\S000\SAVSCFXP  -user OurDomain\DomainAdmin -pwd Password -G "\SV20-57\RBINS" -s

    The CID shouldn't be on nisos but on the server itself. Strange.

    I also noticed I have a lot  of errors (download of sophos autoupdate from server \\sv2057... (0X0000006b)), but when I look under the Protection part, that there isn't any outdated computer.

    Jo

    :51046
  • 0

    Hello Jo,

    CID shouldn't be on nisos

    there is no indication that this setup command has been run on the endpoint which the log you've posted is from. And you still didn't say where the 74 error pops up :smileyhappy:

    download of sophos autoupdate failed from server \\sv2057

    The missing dash in the server name is probably a typo. Don't tell me it's the same problem as in the recent succession of errors 0000006b and 00000000 thread. But anyway, up to date refers solely to the AV component (software and data, including IDEs, the same as in the CID) and what is more doesn't reflect update errors.

    Christian

    :51050
  • 0

    Sorry, the error pops up in PDQ Inventory, where I launched the command.

    What can help, maybe, is the following. I see now that, when I edit the updating policy (in fact I don't do anything) and I close, I'm getting the message: the primary update location may not contain the selected software supscription recommended. But when I check the bootsrap locations it's the same. What am I missing?

    Jo

    :51058