How to clear or expand the event log in Ghost 9?
Under Tools->Options->Notificati
The problem is that I got an unable to write to the event log because it was full? I don't see anyway to clear the event log or expand it. I have loads of disk space.
I actually found the manual pdf... It mentions the log file in the agent folder where Ghost is installed. I found that and below are the last few entries. ...It's logging that it can't log to the event log? When I get the error it gives the reason as event log full.
2/3/2008 17:43:05 PM Medium Priority Notice: Norton Ghost service started successfully. 0x00 (Norton Ghost 9.0)
2/3/2008 17:53:19 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Norton Ghost 9.0)
2/3/2008 17:53:19 PM Medium Priority Notice: Norton Ghost service started successfully. 0x00 (Norton Ghost 9.0)
2/3/2008 18:27:29 PM High Priority Warning: Unable to open the event log. 0x800706B5 (Norton Ghost 9.0)
2/3/2008 18:27:29 PM Medium Priority Notice: Norton Ghost service stopped. 0x00 (Norton Ghost 9.0)
2/3/2008 18:30:46 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Norton Ghost 9.0)
2/3/2008 18:30:46 PM Medium Priority Notice: Norton Ghost service started successfully. 0x00 (Norton Ghost 9.0)
2/3/2008 19:26:31 PM High Priority Warning: Unable to open the event log. 0x800706B5 (Norton Ghost 9.0)
2/3/2008 19:26:31 PM Medium Priority Notice: Norton Ghost service stopped. 0x00 (Norton Ghost 9.0)
2/3/2008 19:30:29 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Norton Ghost 9.0)
2/3/2008 19:30:29 PM Medium Priority Notice: Norton Ghost service started successfully. 0x00 (Norton Ghost 9.0)
2/3/2008 19:31:52 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Norton Ghost 9.0)
2/3/2008 19:31:52 PM High Priority Error: Unable to successfully reconcile changes since last session. Unable to enumerate the current drives on this system.
Cannot initialize the Storage Management Engine.
Error E0020002: Device \\.\PhysicalDrive0 cannot be opened. Error 00000020: The process cannot access the file because it is being used by another process. 0xE0020002 (Norton Ghost 9.0)
2/3/2008 21:00:03 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Management Console)
2/3/2008 21:00:03 PM High Priority Notice: Notification System Test 0x00 (Management Console)
2/4/2008 12:08:12 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Management Console)
2/4/2008 12:08:12 PM High Priority Notice: Notification System Test 0x00 (Management Console)
The problem is that I got an unable to write to the event log because it was full? I don't see anyway to clear the event log or expand it. I have loads of disk space.
I actually found the manual pdf... It mentions the log file in the agent folder where Ghost is installed. I found that and below are the last few entries. ...It's logging that it can't log to the event log? When I get the error it gives the reason as event log full.
2/3/2008 17:43:05 PM Medium Priority Notice: Norton Ghost service started successfully. 0x00 (Norton Ghost 9.0)
2/3/2008 17:53:19 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Norton Ghost 9.0)
2/3/2008 17:53:19 PM Medium Priority Notice: Norton Ghost service started successfully. 0x00 (Norton Ghost 9.0)
2/3/2008 18:27:29 PM High Priority Warning: Unable to open the event log. 0x800706B5 (Norton Ghost 9.0)
2/3/2008 18:27:29 PM Medium Priority Notice: Norton Ghost service stopped. 0x00 (Norton Ghost 9.0)
2/3/2008 18:30:46 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Norton Ghost 9.0)
2/3/2008 18:30:46 PM Medium Priority Notice: Norton Ghost service started successfully. 0x00 (Norton Ghost 9.0)
2/3/2008 19:26:31 PM High Priority Warning: Unable to open the event log. 0x800706B5 (Norton Ghost 9.0)
2/3/2008 19:26:31 PM Medium Priority Notice: Norton Ghost service stopped. 0x00 (Norton Ghost 9.0)
2/3/2008 19:30:29 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Norton Ghost 9.0)
2/3/2008 19:30:29 PM Medium Priority Notice: Norton Ghost service started successfully. 0x00 (Norton Ghost 9.0)
2/3/2008 19:31:52 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Norton Ghost 9.0)
2/3/2008 19:31:52 PM High Priority Error: Unable to successfully reconcile changes since last session. Unable to enumerate the current drives on this system.
Cannot initialize the Storage Management Engine.
Error E0020002: Device \\.\PhysicalDrive0 cannot be opened. Error 00000020: The process cannot access the file because it is being used by another process. 0xE0020002 (Norton Ghost 9.0)
2/3/2008 21:00:03 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Management Console)
2/3/2008 21:00:03 PM High Priority Notice: Notification System Test 0x00 (Management Console)
2/4/2008 12:08:12 PM High Priority Warning: Unable to write to the event log. 0x800705DE (Management Console)
2/4/2008 12:08:12 PM High Priority Notice: Notification System Test 0x00 (Management Console)
Norush
You can try openeing the event viewer and rightclick on the nodes and selecting [clear all events]
ASKER
I ran the Ghost console, selected advanced view, and selected the Events tab. Events are listed. Clicking on/selecting an event displays some event details in the lower pane. Right clicking on an event does not produce a drop down menu at all (right clicking on a line item in the Backup History does produce a drop down). Is there another event viewer you are referring to?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes. That did it.
Odd, I had the system event log set to 512KB and to overwrite events more than 7 days old.
Also odd that it appears Ghost 9 does not write to it's own log if the write to the system log fails.
Oh well, that solved that problem. thanks
Odd, I had the system event log set to 512KB and to overwrite events more than 7 days old.
Also odd that it appears Ghost 9 does not write to it's own log if the write to the system log fails.
Oh well, that solved that problem. thanks
ASKER
Thanks.
Thank you and good luck.