I have Windows XP MCE 2005 SP3 running as a Virtual Machine in Oracle Virtual Box. I have N360 v4 and my backup drive is a samba share on my host Ubuntu server .. Everytime I run a backup I either get a shared component faliure of cltlmh.exe and then after a subsequent reboot Norton will not start, I cannot bring up the gui, there is a red cross on the icon in the icon tray, or just recently it just crashes my system .. I didnt realise thats what wa sgoin on at first, I kept coming back to the XP box and it was at the login prompt, but as my backup is set to automatic it was running backups as and when it felt the need and crashing the system.
Details for the shared component faliure are included in the dr watson upload data ..
---
Manifest.txt
---
Server=watson.microsoft.com UI LCID=1033 Flags=1672016 Brand=WINDOWS TitleName=Symantec Shared Component DigPidRegPath=HKLM\Software\Microsoft\Windows NT\CurrentVersion\DigitalProductId ErrorText=This error occurred on 14/09/2010 at 14:56:46. HeaderText=Symantec Shared Component encountered a problem and needed to close. Stage1URL= Stage1URL=/StageOne/cltlmh_exe/10_6_0_13/cltlmh_exe/10_6_0_13/00064310.htm Stage2URL= Stage2URL=/dw/stagetwo.asp?szAppName=cltlmh.exe&szAppVer=10.6.0.13&szModName=cltlmh.exe&szModVer=10.6.0.13&offset=00064310 DataFiles=C:\DOCUME~1\***\LOCALS~1\Temp\WER3d86.dir00\cltlmh.exe.mdmp|C:\DOCUME~1\***\LOCALS~1\Temp\WER3d86.dir00\appcompat.txt Heap=C:\DOCUME~1\MarkT\LOCALS~1\Temp\WER3d86.dir00\cltlmh.exe.hdmp ErrorSubPath=cltlmh.exe\10.6.0.13\cltlmh.exe\10.6.0.13\00064310 DirectoryDelete=C:\DOCUME~1\***\LOCALS~1\Temp\WER3d86.dir00
---
Event Log
---
Faulting application cltlmh.exe, version 10.6.0.13, faulting module cltlmh.exe, version 10.6.0.13, fault address 0x00064310.
---
I have used the online support, and we have reinstalled a few times using NRT and clearing out the registry etc ... anyone else have this issue ?
It wont let me attach the hdmp and mdmp files that dr watson uploads, not sure how much use they will be tho .. I have attached the manifest and appcompat.txt ..
Any help greatly appreciated ... what other logs should I be looking at ?
I have been chatting to the support guys over this one and they were unable to replicate this issue, they also say that the configuration I am running is not supported (XP VM on Virtualbox) and will not be fixed, they do not however say exactly what is not supported so I have asked for clarification and also, if they cannot replicate then exactly what steps were taken as that could in fact be my resolution by building the virtual machine from scratch.
The issue is still apparent even with the backup disabled, and if I have to reboot the virtual machine for any reason then Norton 360 stops working and I have to shut down and power up, then reboot a few more times and it fires back into life which is a complete pain ..
Early days, but I just seen Virtualbox 4.0 is out of beta, so I installed it with the extension pack (was on 3.2.12) and its looking a bit more stable .. I can force the system down and when it powers back up norton is fine, and again when I do a normal reboot and also when I backup to a shared folder, no crash .. I have just had the shared component faliure again though .. not perfect, but certainly better than before ..
I use virtualbox as a bit of a work around really, I used to have a laptop with MCE2005 and I had all my work stuff on it, I migrated to Ubuntu but still needed some of the windows stuff, so I migrated my laptop to a virtual machine and run it with virtualbox on my Ubuntu server .. its also used for iTunes/iPhone stuff which is all a bit rubbish on Ubuntu at the moment.
N360 basically dies, can't run anything, big red cross in the icon in the system icon tray, cant run live update or access the gui etc .. I have now got rid of n360 in favour of NIS2011, should have got rid of Norton completely because its exactly the same, works for a bit, shared component dies, after any subsequent reboot I get the red cross in the icon and can't access live update or the NIS gui, have to shutdown, power up, then restart again and it kicks into life, then the shared component dies and it all starts again .. proper sodding frustrating ..
Its a problem with "SUN VirtualBox" as it does not support Vectored Exceptions properly ..
Comodo Antivirus carries a caveat ..
"WARNING CIS does not work properly in VirtualBox because of the limitations imposed by this virtual machine Vectored Exceptions fail" So please test it with another VM software.
Am assuming this is the same issue with NIS/Norton 360 etc ..
I have migrated back to VMWare and all is fixed .. not problems whatsoever..