Re: CcmExec.log
- From: "Fran Vázquez" <fvazquez@xxxxxxxxxxxxxxxx>
- Date: Thu, 6 Mar 2008 08:01:22 +0100
Finally solved!
The blame falls squarely on the firewall's AV solution we use. Somehow the
..cab file ended up mangled just enough so no to work with ScanWrapper, but
not that much it wouldn't even sync. After downloading wsusscn2.cab from
outside our LAN, I noticed the file size was a few KB longer than the .cab
we were using. Swapped them and no more errors.
Thank you for your time and advice, anyway.
.
- Follow-Ups:
- Re: CcmExec.log
- From: "Vicky Hu [MSFT]"
- Re: CcmExec.log
- Prev by Date: Query Works - Collection Based on Query Doesn't
- Next by Date: RE: Support for Vista SP1 and Windows Server 2008
- Previous by thread: Query Works - Collection Based on Query Doesn't
- Next by thread: Re: CcmExec.log
- Index(es):
Relevant Pages
|