Log file entries to confirm the Erase Data and Disable Handheld command
Posted 07-18-2009 at 05:00 AM by hdawg
Tags polc log, wipe handheld
I've taken this content directly from KB10970; which shows you the log lines created during a success use of the Erase Data and Disable Handheld command.
You'll find this information in the BlackBerry Policy Service (POLC) log:
[40000] (07/17 17:50:27):{0xB80} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}SCS::PollDBQueueNewRequests - Queuing KILL_DEVICE_REQUEST request
[30000] (07/17 17:50:51):{0xB78} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler::SendQueuedITAdminCommandToDevice Sending data to device, contentType=ITADMIN, size=52, RefId=0, TransactionId=-984458983, Tag=5
[40000] (07/17 17:50:51):{0xB78} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler::SendToRelay - SubmitToRelaySendQ, Tag=5
[30000] (07/17 17:50:51):{0xB7C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler:: DoDeviceSentProcessing - Message has been delivered to device, Tag=5
[40000] (07/17 17:50:51):{0xB7C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler:: DoITPolicyDeviceSentProcessing - ITPolicy GME Receive Ack for the command KILL_HANDHELD_COMMAND - Processing packet, Tag=5
[40000] (07/17 17:50:52):{0xB6C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler:: DoGMEReceiveProcessing - Receiving packet from device, size=46, TransactionId=-2078283753, Tag=5618075, content type=ITADMIN, cmd=0x3
[40000] (07/17 17:50:52):{0xB6C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler::HandleITADMINDataCommand - ITPolicy Success Ack for the command KILL_HANDHELD_COMMAND - Processing packet, Tag=5618075
[40000] (07/17 17:50:53):{0xB6C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler::SendToRelay - SubmitToRelaySendQ, Tag=5618075
Queuing KILL_DEVICE_REQUEST request - The Erase Data and Disable Handheld command has been queued from the BlackBerry Manager (or BRK / API)
SendQueuedITAdminCommandToDevice Sending data to device - The Policy service is sending the wipe command for the router service to deliver
SendToRelay - SubmitToRelaySendQ - The command has been sent to the BlackBerry relay (RIM NOC) to be delivered to the handheld
DoDeviceSentProcessing - Message has been delivered to device - The handheld has confirmed receipt of the wipe command
DoITPolicyDeviceSentProcessing - ITPolicy GME Receive Ack for the command KILL_HANDHELD_COMMAND - The handheld has confirmed that it is processing the received command
HandleITADMINDataCommand - ITPolicy Success Ack for the command KILL_HANDHELD_COMMAND - The handheld has confirmed execution of the command. We won't get a confirmation that it has completed successfully, but rather that the handheld started execution ... once the command is completed the device will be wiped to a base OS / configuration.
So, if you're trying to track successful wipes, look for HandleITADMINDataCommand - ITPolicy Success Ack for the command KILL_HANDHELD_COMMAND
You'll find this information in the BlackBerry Policy Service (POLC) log:
[40000] (07/17 17:50:27):{0xB80} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}SCS::PollDBQueueNewRequests - Queuing KILL_DEVICE_REQUEST request
[30000] (07/17 17:50:51):{0xB78} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler::SendQueuedITAdminCommandToDevice Sending data to device, contentType=ITADMIN, size=52, RefId=0, TransactionId=-984458983, Tag=5
[40000] (07/17 17:50:51):{0xB78} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler::SendToRelay - SubmitToRelaySendQ, Tag=5
[30000] (07/17 17:50:51):{0xB7C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler:: DoDeviceSentProcessing - Message has been delivered to device, Tag=5
[40000] (07/17 17:50:51):{0xB7C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler:: DoITPolicyDeviceSentProcessing - ITPolicy GME Receive Ack for the command KILL_HANDHELD_COMMAND - Processing packet, Tag=5
[40000] (07/17 17:50:52):{0xB6C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler:: DoGMEReceiveProcessing - Receiving packet from device, size=46, TransactionId=-2078283753, Tag=5618075, content type=ITADMIN, cmd=0x3
[40000] (07/17 17:50:52):{0xB6C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler::HandleITADMINDataCommand - ITPolicy Success Ack for the command KILL_HANDHELD_COMMAND - Processing packet, Tag=5618075
[40000] (07/17 17:50:53):{0xB6C} {testuser1@port3101.org, PIN=FFFFFFFF, UserId=1}RequestHandler::SendToRelay - SubmitToRelaySendQ, Tag=5618075
Queuing KILL_DEVICE_REQUEST request - The Erase Data and Disable Handheld command has been queued from the BlackBerry Manager (or BRK / API)
SendQueuedITAdminCommandToDevice Sending data to device - The Policy service is sending the wipe command for the router service to deliver
SendToRelay - SubmitToRelaySendQ - The command has been sent to the BlackBerry relay (RIM NOC) to be delivered to the handheld
DoDeviceSentProcessing - Message has been delivered to device - The handheld has confirmed receipt of the wipe command
DoITPolicyDeviceSentProcessing - ITPolicy GME Receive Ack for the command KILL_HANDHELD_COMMAND - The handheld has confirmed that it is processing the received command
HandleITADMINDataCommand - ITPolicy Success Ack for the command KILL_HANDHELD_COMMAND - The handheld has confirmed execution of the command. We won't get a confirmation that it has completed successfully, but rather that the handheld started execution ... once the command is completed the device will be wiped to a base OS / configuration.
So, if you're trying to track successful wipes, look for HandleITADMINDataCommand - ITPolicy Success Ack for the command KILL_HANDHELD_COMMAND
Total Comments 0











