Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 2026 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

Unable to configure secondary update manager

oreo81

Hi,

I installed Enterprise Console 4.0 a while ago, and ever since have been unable to configure a secondary update manager at one of our branch offices. Adding the primary update manager as a source works fine and I can add a subscription, but when I click on OK to come out of that dialogue box, I get the following error:

"The distribution share SelfUpdate is in use by the server [server name here]."

Has anyone else seen this? I've been back and forth with Sophos support for a couple of months now, but they seem unable to work out what's going on. I've reinstalled SUM on the branch office server, checked the permissions on SophosUpdate at share-level and filesystem-level, but no luck. I have no idea what "SelfUpdate" refers to; it's only mentioned once on the entire Sophos website, in the release notification for the newest version of SUM.

:877


This thread was automatically locked due to age.
  • 0
    oreo81 wrote:

    Has anyone else seen this? I've been back and forth with Sophos support for a couple of months now, but they seem unable to work out what's going on. I've reinstalled SUM on the branch office server, ....

    A couple of months? That's not good - adding a SUM shouldn't be something esoteric. Unfortunately for you and fortunately for me - no, haven't seen anything like that. But I don't want to leave you out in the cold.

    Happen to have still the former beta installation around and just installed SUM on an XP SP3. Deliberately misconfiguring the secondary SUM I got "The distribution share \\primaryserver\SophosUpdate is in use by the server primaryserver" - close but not what you have got. On the other hand - \\servername\SophosUpdate is the default share you can't remove and it might run under the name SelfUpdate. In fact SelfUpdate can be found in table SDDMLocations and refers to C:\Documents and Settings\All Users\Application Data\Sophos\Sophos Endpoint Management\4.0\Updates\Secure. Somehow something's messed up here.

    BTW: you did install the secondary SUM from \\primaryserver\SumInstallset, didn't you?

    Probably doesn't help but it sure beats sudoku when I have nothing better to do :smileywink:

    Christian

    :904
  • 0

    Christian,

    I'd forgotten that I'd posted this and only just saw your reply! Thanks for taking some time out to help me.

    When you say you deliberately misconfigured SUM in order to get that error message, what exactly did you do?

    And yes, I did install from the SUMInstallSet share :)

    :1056
  • 0

    Sorry - have been off-net the last days :smileyvery-happy:

    When you say you deliberately misconfigured SUM
    - well, I just tried to add \\primaryserver\SophosUpdate as a distribution share for the secondary. That's when I got the message mentioned (which contained the share's name, not SelfUpdate).

    Christian

    :1172
Unfiltered HTML