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

Unknown Error (Unbalanced composite package source name)

kej

Hi,

 I've just upgraded from Enterprise Console 3  to 4 and am having problems getting a secondary site update working.

 The site itself appears to be working fine from a Web browser and the passwords all seem to work. The CID seems to be generating the right folders under the virtual directory (ie http://my.website.tld/virtualdirectory/CIDs/S000/SAVSCFXP/). The URL seems to have been correctly updated on the clients (ie you enter http://my.website.tld/virtualdirectory and the clients get the above).

 ..but all I get in the auto-update logs is;

 Time: 25/02/2010 21:12:20
Message: ERROR:   the operation failed due to an unknown error: Unbalanced composite package source name {auto|http://my.website.tld/virtualdirectory/CIDs/S000/SAVSCFXP/|username: password}{mapped|C:\Program Files\Sophos\AutoUpdate\data\warehouse|}
Module: ALUpdate
Process ID: 2796
Thread ID: 2172

 Bug?

  The "}{" looks very suspect and there's nothing quite like unbalanced brackets/braces to ruin a programmer's day!

 If anyone has run into this let me know please!

Keith

:1522


This thread was automatically locked due to age.
Parents
  • 0

    You're welcome, Keith

    I tend to shut out thoughts about IIS ...

    While the catch-all is definitely a good idea it might not be enough. Webserver Extensions and "application" settings sometimes map certain extensions to active content (and this is not overridden by the catch-all). And in such cases it's not a simple 404 which is reported back but some "smart" content which could confuse Sophos.

    Yes, it's a good idea to also check the IIS logs ...

    Christian

    :1567
Reply
  • 0

    You're welcome, Keith

    I tend to shut out thoughts about IIS ...

    While the catch-all is definitely a good idea it might not be enough. Webserver Extensions and "application" settings sometimes map certain extensions to active content (and this is not overridden by the catch-all). And in such cases it's not a simple 404 which is reported back but some "smart" content which could confuse Sophos.

    Yes, it's a good idea to also check the IIS logs ...

    Christian

    :1567
Children
No Data