Hi I'm runing Windows 7 and I've recently upgraded to version 4. I have an error in my Event Log every time I start windows. It's a Kernel-Event Tracing error due to the Norton Installer boot log N360.etl having reached it maximum file size. This informs me that the DINGTraceSession has been stopped.
I have used the Norton uninstaller tool (run it twice with reboots inbetween) and reinstalled three times but the error always reoccurs. I also made sure the Norton Installer file was removed and did a registry clean.
I can't find any reference to this anywhere, can anyone help please?
Let us know whether you get this error when you remove the installation files from your computer. You can try to delete the NortonInstaller folder from C:\ProgramData\NortonInstaller
This only shows, that the log file is too small and the kernel can't save all ETW (Event Tracing for Windows) Events for Norton Installer Boot log. Once the installation is complete without any problem, then there is no need for Norton Installer folder. So, you can ignore this error and the logging of this error will not affect the operation of your computer. This was earlier reported on the beta board:
That thread only have a copy of event log containing this error message.
Description: The maximum file size for session "DINGTraceSession" has been reached. As a result, events might be lost (not logged) to file "C:\ProgramData\NortonInstaller\Logs\05-22-2009-13h52m50s\bootlog.etl". The maximum files size is currently set to 104857600 bytes. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
As the Win 7 Beta board is closed now, you cannot view that information. I just added the thread link as an extra reference.
Having solved the error yesterday with your solution of deleting the NortonInstaller folder from C:\ProgramData\NortonInstaller and rebooted successfully a couple of times, this morning when I turned on my laptop the same error occurred. On investigation I found that the Norton Installer file had re-created itself in Program Data again and caused the problem.