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

SUM not distributing or updating

All,

sorry for the long winded post.
Background: My organization updated the EC on the 12th i believe and since then things have just gone downhill.  The VM that everything is on hated life until I migrated all settings from 15 Software Subscriptions to one general group.  This improved performance until disc space had gotten so low that SUM would time out when ever it tried to contact Sophos.  We have added more disc space enabling SUM to communicate with Sophos.  I have contacted support on 4 occasions and they have been very intelligent and eventually escalated the case.  Oddly enough it took a desperate call to a contact of mine to actually get support to contact me.  I ran the Sophos Diagnostic Utility 3 days ago and have yet to hear anything from support regarding any findings.  I also re-ran the install for SUM as a repair install and still nothing.  Any input is greatly appreciated.

Latest application event error: Synchronize operation failed when synchronizing product release '443DC50B-DFC1-4678-AC88-19965CAEA3B7'. Details: Cannot create stream C:/Documents and Settings/All Users/Application Data/Sophos/Update Manager/Update Manager/Warehouse/123

S2k3 sp2
Ent Con 4

Tried to recreate CIDs and Warehouse folder as described in another kb but no dice.

Update manager status
                                             01/16/2010 9:00:32 AM80040406  Delivery failed for software subscription 'Recommended'. Access to the source update location is denied or the location is otherwise unavailable.
                                             01/16/2010 8:48:41 AM80040401  Software update failed.                 
                                             01/16/2010 8:48:41 AM80040404  Threat detection data update failed

:834


This thread was automatically locked due to age.
Parents
  • Well, in our case it would depend on the share that the group’’’’s updating policy is pointing to.  I can’’’’t say for sure if the SUM will not distribute the software to the shares at all if one fails but I added a share we use along with the default update location and the software delivery failed.  Then, yet another simple detail, I realized that there’’’’s an option to choose a username and pw to use when writing the files to specific shares.  Since we have a network account for updating I configured the distribution shares to use the correct credentials, domain admin so I didn’’’’t have to change permissions on the server’’’’s share, and it was all set. 

    :859
Reply
  • Well, in our case it would depend on the share that the group’’’’s updating policy is pointing to.  I can’’’’t say for sure if the SUM will not distribute the software to the shares at all if one fails but I added a share we use along with the default update location and the software delivery failed.  Then, yet another simple detail, I realized that there’’’’s an option to choose a username and pw to use when writing the files to specific shares.  Since we have a network account for updating I configured the distribution shares to use the correct credentials, domain admin so I didn’’’’t have to change permissions on the server’’’’s share, and it was all set. 

    :859
Children
No Data