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

Cannot create stream (pulling my hair out now)

Bluetooth

Hey Guys

First post here but long time sophos user. I look after 5 primary schools in west yorkshire and our anti virus is provided by sophos. We have our own update location that we pull updates from rather than from sophos (dont ask me for the reason why, i just get told where to get updates :-/)

Anyway, we have finally been given sophos enterprise console 4.7 to play with and i have upgraded two of my servers across the 5 schools. Ive been having some severe problems getting EC to update, upon checking the logs i see "cannot create stream" and a bunch of hex code.

Ive followed the stuff on sophos' website on deleting the working-sub and sub0 directories or whatever and this unfortunately doesnt resolve the problem.

Ive been waiting over a week for our in house support desk to resolve the issues but ive not heard a peep and some of my servers havent updated in that time.

Can anyone offer some advice? unfortunately i cant contact sophos direct as because our license is a local education one sophos cannot actually support us we are expected to speak to our in house team for all support (even as useless as hey are)

Any help is much appreciated. Thanks

:13845


This thread was automatically locked due to age.
  • 0

    Hi Guys

    Right i think i have narrowed this down with nearly 2 hours of solid research on the issue. Upon checking several of the servers they are all trying to download the 87ad1772e9a9fee660a7c06be588a5bex000.xml from our update store (http://sophos.yhgfl.net/libraryv4 & http://sophos2.yhgfl.net/libraryv4). After checking those sources manually, and checking their backups i cannot find that file ANYWHERE. Makes sense why sophos is now failing to update.

    Is there any way to get around this issue? i of course will be passing these details onto yhgfl although ive been asking for help for 2 weeks and havent received any as of yet.

    Thanks again guys

    :13853
  • 0

    Hello Bluetooth,

    much guesswork but looking at the update stores I'd say they are providing only SAV9.7 but not SAV9.5 - and it seems that you are requesting the latter.

    Christian

    :13891
  • 0

    Indeed you are correct there QC.

    After much messing about again yesterday morning i found that we had to switch to 9.7 recommended in our subscriptions to continue getting updates. Something YHGFL had not told us until recently.

    Im still waiting for them to get back to me on the subject hehe.. something so simple that could have been solved in 2 minutes has taken countless hours of work and wasted my time.

    Got to love YHGFL.

    :13959
  • 0

    Can't say why YHGfL set up their re-distribution warehouse this way.

    Don't know how widely "dependent autonomous" SUMs (as opposed to a SUM hierarchy) are used. You might for example have several locations with their "own" IT but you don't want to give them the license credentials. Like with YHGfL they'd have to use your central SUM (instead of Sophos) as their source. This is a valid setup. So why did Bluetooth encounter this error when using the 9 Recommended (I assume it was this one - but it could have been 9.5 Recommended) subscription?

    When a SUM accesses its source warehouse it downloads 

    • all Metadata (i.e. a description and content list of the available products)
    • the Update Manager software
    • the files for the products/product versions selected in the Software Subscriptions

    to its own warehouse. A "dependent" SUM will thus have the same software list to select from but if it tries to download a product not selected by the redistributing SUM it will encounter an error like the one in the subject as the required files are not in this warehouse. Another point to note is "generic" version name used. At the moment you'll see 9 Recommended, 9.5 Recommended and 9.7 Recommended with 9.5 as recommended for 9. After a few months 9.7 will become the recommended version for the base version 9. Thus if the central SUM has subscribed to 9 Recommended but the dependent to 9.5 Recommended it will work right now but eventually fail.   

    @Bluetooth: I'd like to send you some more comments but not publicly . If you are interested please send me a PM (and turn on PM so I can reply).

    Christian

    :14011