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

    the error pops up in PDQ Inventory

    ah, then the meaning of this 74 is likely to be found there.

    the primary update location may not contain the selected software subscription

    Usually you get this message when the server part of the UNC path is not the simple NetBIOS name but an FQDN or an alias.

    Christian

    :51064
  • 0

    So for the primary update location i should change to the fully qualified domain name?

    For the first part, I just asked it at the pdq inentory forum. I'll let you know.

    Jo

    :51066
  • 0

    Hello Jo,

    primary update location

    maybe I should have included an example. If the server is named SEC with an FQDN of SEC.servers.acme.com with an alias Sophos.acme.com then the Primary \\SEC\SophosUpdate should not produce a pop-up. \\SEC.servers.acme.com\SophosUpdate and \\Sophos.acme.com\SophosUpdate will.  BTW: In the log the share on Nisos was named SophosUpdates, which is AFAIK not the default name.

    Christian

    :51068
  • 0

    Voila, it's that easy ;)

    I filled the complete path (until SAVSCFXP) but that wasn't necessary apparantly. Will the messages in the Computers with Errors disappear once they correctly update?

    jo

    :51072
  • 0

    Hello Jo,

    I filled the complete path

    yes, it's a little bit confusing. On the endpoint you see the path down to the (OS specific) product folder. SEC constructs the path appending CIDs, the subscription counter (Snnn) and the product folder (the latter was also the case with EM and the legacy SEC). It is important to remember this when you set up a web CID.

    And yes, a successful download will clear these errors.

    Christian

    :51074