On Sun, Aug 26, 2012 at 2:48 PM, Bob Chapman <rechapman_at_hotmail.com> wrote:
> Windows 7 Professional Service Pack 1 [64 bit]
> I upgraded from TortoiseSVN 1.7.7 [64 bit] to TortoiseSVN 1.7.8 [64 bit] on approx. 8/20/2012 23:11 CDT.
> After the next "restart required" Automatic Live Update to Norton Internet Security 2012 126.96.36.199 [64 bit] (update downloaded on my system 8/23/2012 5:21 AM CDT), NIS would no longer complete either Quick or Full System scans. In addition, the Symantec Security Framework began to experience unexpected terminations (leaving my system unprotected). After uninstalling TortoiseSVN 1.7.8 [64 bit] the problems with NIS 2012 have stopped.
> Since I didn't notice any problems with TortoiseSVN 1.7.8 and NIS 2012 188.8.131.52 until the Norton Automatic Live Update, I believe that this problem was introduced by the Norton update and am reporting the problem here primarily for information.
> I AM CURIOUS why the the Windows Event Log for the the unexpected Norton terminations:
> Faulting application name: ccSvcHst.exe
> indicates that the faulting module was associated with TortoiseSVN!
> Faulting module path: TortoiseSVN32.dll
> [And there is probably a reason why a 64 bit installation of TortoiseSVN 1.7.8 has a TortoiseSVN32.dll ;)]
> There are several threads concerning this problem in Norton Internet Security/Norton Antivirus Forum.
> TortoiseSVN disabling NIS2012 service
> 08-22-2012 06:41 PM
> NIS 2012 WILL NOT COMPLETE Scans After 8/23/2012 5:21 AM Live Update
> 08-23-2012 09:46 AM
> Norton Internet Security 2012 stops working.
> 08-25-2012 03:24 AM
> I hope that Norton (or somebody :) resolves the problem soon because downgrading to TortoiseSVN 1.7.7 is not a long term solution and I hate to go to the trouble of "dumping" NIS. ;)
FWIW, I also had problems with our corporate Symantec antivirus
(ccSvcHst.exe) and Perl's MIME::Lite module on XP 32-bit. A handful of
messages would go through (outbound) just fine, then ccSvcHst.exe
started crashing & wouldn't allow any more messages to go through
until a reboot was performed.
I don't have specific version numbers, as this was a few months ago
and someone else's computer. I replaced the offending parts of the
script with a second script, written in PowerShell; no difficulties
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-08-27 02:08:58 CEST