Complete Status

My Captivate v1 lessons work great with my LMS. We are now
testing Captivate v2. I am having some challanges with the
"Completed" status.
If a student launches the lesson and views in its entirety,
the lesson marks Completed. This works fine.
If a student Exits before finishing, the lesson marks In
Progress. This works fine.
When a student relaunches the unfinished lesson the
bookmarking works fine, however the lesson never records the
Completed status. The only way to recieve a Complete status is to
restart the lesson from the beginning.
The Captivate v1 settings (which work fine) are the same on
Captivate v2: Using SCORM v1.2, Report Complete/Incomplete, Report
Score to LMS, and Report interactions and the score. The new v2
setting for Report quiz results only is marked but I've also tried
Report Slide views only and Report user access only with the same
results.
This is not a show stopper since most student will view the
lesson in it entirety but I would like the bookmarking capabilities
to work with the Completed status.

Similar Messages

Complete Status of Purchase Order

HI SRM Gurus,
For SRM 7.0 system, for purchase Order what is the signifance of "Transaction Completed" status ?
I have completed one purchase Order which has open item.
At header level it sets "Transaction Completed" status in SRM PO. but neither it set delete indicator nor delivery complete indicator of open PO items . Hence i wonder what is the signifiance of complete functionality of PO in SRM.
Can you please through light on this topic ?
Regards,
Kalandi

Checks (SRM-SUS)
Before SAP SRM SUS documents are archived, they are processed by a check program to determine if they qualify for archiving. This validation procedure prevents documents that still require processing, erroneous documents, and current documents from being archived and subsequently deleted from the database.
The residence time is a general criterion used to determine when SUS documents are archived. Each document must remain in the system for a certain period of time (the retention period) after it was last changed before it can be archived.
For more information about setting retention periods, see the Supplier Relationship Management Implementation Guide (IMG): Supplier Relationship Management Supplier Self-Services Cross-Application Basic Settings Archiving of Documents Define Residence Times for Documents .
Note
Only SUS documents from completed business processes are considered for archiving. Before you can archive documents, you need to complete the business process to which they belong.
End of the note.
During the check process, the system also checks the relevant follow-on documents. If these documents have been created and completed, the relevant business transactions are assumed to have been completed. In particular, if a SUS purchase order can be archived, then so can the relevant follow-on documents.
*The status Transaction Completed is only applicable to SUS purchase orders and indicates that the document flow has been completed.* This means that all necessary documents in the document flow have been created and that, in the SUS EBP scenario, the confirmations and invoices pertaining to the purchase order have also been approved.
As well as the follow-on documents, the ordered quantity (or the quantity confirmed by the supplier if a purchase order response was requested) and the quantity specified in the follow-on documents must be considered. A purchase order can have one or more follow-on documents for each document type. If the total amount of item values of the follow-on documents does not match the total order value, the process step is not complete. In this case the system does not apply the status Transaction Completed to the original SUS purchase order.
An exception to this process is when a final delivery indicator has been set for an advanced shipping notification or for the invoice. Only the purchaser can set this indicator, which is used to show that no further delivery or invoice is expected and that this particular process step is completed. This information is only available on the purchaser's side in the purchasing system.
Example
A SUS purchase order has one or more advanced shipping notifications (ASN). If the total quantity specified in the ASNs does not match the quantity specified in the purchase order, it implies that some of the goods ordered have not yet been delivered. The delivery process step is therefore not yet completed even though invoices have been created for the existing ASNs.
http://help.sap.com/saphelp_srm70/helpdata/EN/d8/757af9204942aa86735dfefc62e9cd/frameset.htm

Sales order not set to complete status in CRM from R/3

Hi Gurus,
I need some advice. We are working on CRM 2007 and the issue we are facing is....when a sales order is created in CRM it gets successfully copied over to R/3. It is then processed in R/3 and is then set to a Completed status. But this status is never updated across to the original sales order in CRM which hence stays in Incomplete status...
We know this is a config issue and we have also looked at program "CRM_SET_STATUS_COMPLETED" but can anyone point us where exactly we need to change the configuration.
Thanks,
Sushant.

Hi sushant,
When the R/3 Order status is set to 'Completed' then the system status for order in CRM system is automatically changed to 'Completed'.
So firstly check whether the User status ('Completed')in SAP CRM has the Business transaction event set to 'FINI'. So when the system status is set to 'Completed' the user status will also change to 'Completed.'
Secondly even check what are the statuses of item in the Orders.
regards,
Anubhav

Process does not follow the routing ends up in complete status

Installed Adobe LiveCycle server ES 2.5 with SQL Server 2008 as database
And followed the tutorial ‘Create Your First LiveCycle Application’
Deployed it on the server when I test the same
i.e. when the workspace user fills in form details and hits complete button it ends up as status complete
And not assigned to next user in the route
The process does not follow the routing it ends up in complete status
And nothing shows up when trying to record and play back the process
Tried invoking Via workbench too
no errors in the server log
Could this be an installation issue any pointers appreciated
Please advise

Issue with Jboss as it was taking longtime time to start due to low CPU ideally it should not take more than 3 to 5 minutes
Process works now

Completed status on Calibration

Hello Experts,
I'm trying to calibrate apprasal documents (with completed status) through Calibration BSP iview, but the final rating on the Appraisal form is grayed out.
Is that correct, I can not calibrate final Appraisal documents with completed status?
Thanks in advance!
Sivani

Hello Ravi,
the problem is, that the production order has been deleted already.
Regarding the Info-message V2355 - Deletion flag for production order/network &1 cannot be reset:
- if the particular producion order is still available within the system (it has not been deleted) - it is possible to reset the Completed status on the sales order after confirmation this message.
- if the particular producion order has been deleted already, it is not possible to reset the Completed status anymore within the transaction VA02.
It is probably a program error, what do you think?
Thanks a lot

To Reopen the Completed Status Global outline agreements

Hi,
We have got some Global Outline Agreemtns with 'completed' status by the user. We want to reopen it for additional processing,but the change icon in the global outline agreement is greyed out. Could anybody tell me how to reopen the 'completed' status global outline agreement again?
Regards,
Manojkumar.

Hi
i believe system behaves correctly.
to prove you..
note 712367- Deleted and completed contracts can be changed
Symptom
You delete or complete a contract. If you are on the items list of the contract at this time, the change button is still active so that you can change the contract items.
regards
muthu

Few CRs are coimng under "Not Completed" status in CRM_DNO_MONITOR transact

Hi All,
Few (only 3) change requests are coming in "Not Completed" status in CRM_DNO_MONITOR transaction. Ideally all closed change requests should not come under "Not Completed" staus when reporting is done.
Kindly help.

Hi,
Please try to implement this note
1459839 CRM_SOCM_SERVICE_REPORT: no update on CRMD_ORDER wo
if after this still issue persists, then please run
CRM_INDEX_REBUILD to correct the CR's status
Hope this helps.
Cheers
SH

What are the settings under SCORM 2004 to indicate the completion status on LMS

Hi everyone,
I have a captivate file which i have published as scorm 2004 compliant and checked that file on the scorm cloud. It worked well.
SCORM Pacakage does note report partial completion. When a person stops training, we have the progress bar to indicate that they are at 0, 25, 50, 75 or 100%.
Problem: I dont know exactly, what are the settings to enable to indicate the completion status. I tried but it didn't worked.
Please help & suggest the right way to do this..
Regards
Vikas Sharma

anybody there.... pls help

Activity search by Completed status and End Date

Hi All,
When i try searching for an activity based on the date on which the status was set to Completed, the system does not show any results. 'Criteria used are Activity Type, Status = Completed, End Date.'
If i choose an End date = Date on which the status on the Activity was set to Completed, the system does not show correct results. The system only shows those activities where the Activity Status was Open and Completed on the same day. For activities where Open and Completed Status was set on different dates, there are no search results.
However, with the same criteria set, if i change the End Date = Date when Activity Status was Open, i get the results.
Is it not possible to search for activities based on Status and End date combination?
Pls. suggest

Hi Kansal,
There is a possibility that the status profile you maintained for the activities has some issues.Please check the Business transaction (which maps system status) that you have mapped with your completed and open staus.It might be that the user staus is set to be open but in the status profile it is accidently mapped to the completed or finished.
Hope this helps.
Regards
Priyanka

Completion Status Sent Two Times

I am having a problem with my completion status being sent
twice to an LMS. I have 5 questions that are multiple choice (I
give users two attempts at answering each question). Prior to the
Results page, the results are sent to the LMS and the record is
sent twice, not once, like I would like it to be. I have turned off
"reporting interactions", I've turned off the message when an
answer is "correct"...I am not sure what I am doing wrong. Is there
some way to control the submit button or control how the data is
sent to the LMS? Please help...thanks!

chuckguytoronto,
This message seems quite similiar to someone else posting
with the same
issue. Is this AICC or SCORM? What problem is occuring with
the status
being sent more than once?
Regards,
Andrew

SAP 4.6 work processes too often goes to completed status

Hello,
SAP 4.6 C (Oracle 9i / windows NT) system, always work process goes to completed status. This a quality system.
As of now we are only restaring the work processes (SM50->process->restart after error-> yes) manually as a temporary fix.
Could you please suggest any solution to this issue ?
Here is more information about the system :
SAP R/3 Kernel              46D_EXT
Support package number      2283
Thanks,
Prabhakar Reddy.

Thank you for your quick reply. Below is the log
B
B Wed Sep 29 06:15:32 2010
B create_con (con_name=R/3)
B Loading DB library 'E:\usr\sap\ING\SYS\exe\run\dboraslib.dll' ...
B Library 'E:\usr\sap\ING\SYS\exe\run\dboraslib.dll' loaded
B Version of library 'E:\usr\sap\ING\SYS\exe\run\dboraslib.dll' is "46D.00", patchlevel (0.2238)
B New connection 0 created
M relno      4640
M patchlevel 0
M patchno    2283
M intno      0
M pid        8144
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 9 8144) [dpxxdisp.c   976]
I MtxInit: -2 0 0
X EmInit: MmSetImplementation( 2 ).
X <ES> client 9 initializing ....
X Using implementation std
M <ES> Memory Reset enabled
X ES initialized.
M ThSysUsrCheck: clear T9
M calling db_connect ...
C Got NLS_LANG=AMERICAN_AMERICA.US7ASCII from environment
C Logon as OPS$-user to get SAPR3's password
C Connecting as /@ING on connection 0 ...
C *** ERROR => OCI-call 'olog' failed: rc = 12547
[dboci.c      2460]
C *** ERROR => CONNECT failed with sql error '12547'
[dboci.c      7025]
C Try to connect with default password
C Connecting as SAPR3/<pwd>@ING on connection 0 ...
C *** ERROR => OCI-call 'olog' failed: rc = 12547
[dboci.c      2460]
C *** ERROR => CONNECT failed with sql error '12547'
[dboci.c      7025]
C Got NLS_LANG=AMERICAN_AMERICA.US7ASCII from environment
C Logon as OPS$-user to get SAPR3's password
C Connecting as /@ING on connection 0 ...
C *** ERROR => OCI-call 'olog' failed: rc = 12547
[dboci.c      2460]
C *** ERROR => CONNECT failed with sql error '12547'
[dboci.c      7025]
C Try to connect with default password
C Connecting as SAPR3/<pwd>@ING on connection 0 ...
C
C Wed Sep 29 06:15:33 2010
C Now I'm connected to ORACLE using OCI_7 API
C
C Wed Sep 29 06:15:36 2010
C Database instance ing is running on TIRUINT04 with ORACLE version 9.2.0.4.0 since 20100929
B Connection 0 opened
B Wp Hdl ConName              ConCnt ConState     TX PRM RCT Date     Time
B 000 000 R/3                  000000 ACTIVE       NO YES NO 20100929 061532
B ***LOG BY2=> sql error 0      performing CON [dbsh    0707 ]
B ***LOG BY0=> ORA-00000: normal, successful completion
[dbsh    0707 ]
B ***LOG BY2=> sql error 0      performing CON [dblink 0627 ]
B ***LOG BY0=> ORA-00000: normal, successful completion
[dblink 0627 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1188]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3) [thxxhead.c   8468]
Edited by: prabhakaryc on Sep 29, 2010 2:03 PM

Restore completed status 4014 iphone 5s

i try to restore my iphone 5s form 3 PC and change 2 Cabels
every time give me a 4014 and the finall time give me
and this is a log for it status:2005
2014-04-14 06:40:05.147 [15724:4538]: restore library built Feb 12 2014 at 16:27:17
2014-04-14 06:40:05.147 [15724:4538]: iTunes: iTunes 11.1.5.5
2014-04-14 06:40:05.148 [15724:4538]: iTunes: Software payload version: 11D167
2014-04-14 06:40:05.148 [15724:4538]: iTunes: Using MobileRestore state machine
[04:40:49.0144] Changing state from 'Idle' to 'Restoring'
[04:40:49.0147] AppleDevice::GetDeviceID: failed for iBoot
[04:40:49.0148] AppleDevice::GetDeviceID: failed for iBoot
[04:40:49.0151] requested restore behavior: Erase
[04:40:49.0153] requested variant: Erase
[04:40:49.0186] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[04:40:49.0680] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
[04:40:49.0684] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 123A06E8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0686] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 123A5D88 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0688] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 1239F068 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0692] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 123A3160 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0693] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 1239F410 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0695] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 1239FC80 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0697] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 123A18E8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0699] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
[04:40:49.0701] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
[04:40:49.0702] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
[04:40:49.0704] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
[04:40:49.0705] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
[04:40:49.0706] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
[04:40:49.0709] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 123A0418 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0712] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 123A60E8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0714] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 123A02B0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0715] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 123A0B68 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0717] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 123A06A0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0719] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "SEP" Digest = "<CFData 123A26F8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0721] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 1239F6E0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0723] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreSEP" Digest = "<CFData 123A4630 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0724] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 123A4F30 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0726] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 123A0B20 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0728] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 123A35E0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0730] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 123A26B0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0731] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 123A2308 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0733] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 11F7B4D8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:40:49.0735] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
[04:40:49.0736] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per4976.tmp/amai/debug/ts s-request.plist
[04:40:50.0792] amai: tss_submit_job: HttpQueryInfo returned 200
[04:40:51.0005] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
[04:40:51.0007] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per4976.tmp/amai/debug/ts s-response.plist
[04:40:51.0541] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
[04:40:51.0542] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "CFELoader"
[04:40:51.0544] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "RBM"
[04:40:51.0546] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PHLEET"
[04:40:51.0547] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PERTOS"
[04:40:51.0548] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PEHammer"
[04:40:51.0919] <DFU Device 05FDA3F0>: production fused device
[04:40:51.0920] requested restore behavior: Erase
[04:40:51.0924] AppleDevice::GetDeviceID: failed for iBoot
[04:40:51.0925] AppleDevice::GetDeviceID: failed for iBoot
[04:40:51.0936] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#64c33543
[04:40:51.0937] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#64c33543
[04:40:51.0939] <DFU Device 05FDA3F0>: operation 0 progress 1
[04:40:51.0940] <DFU Device 05FDA3F0>: operation 0 progress 2
[04:40:51.0942] <DFU Device 05FDA3F0>: operation 0 progress 4
[04:40:51.0944] <DFU Device 05FDA3F0>: operation 0 progress 5
[04:40:51.0946] <DFU Device 05FDA3F0>: operation 0 progress 7
[04:40:51.0948] <DFU Device 05FDA3F0>: operation 0 progress 8
[04:40:51.0950] <DFU Device 05FDA3F0>: operation 0 progress 9
[04:40:51.0952] <DFU Device 05FDA3F0>: operation 0 progress 11
[04:40:51.0954] <DFU Device 05FDA3F0>: operation 0 progress 12
[04:40:51.0956] <DFU Device 05FDA3F0>: operation 0 progress 14
[04:40:51.0958] <DFU Device 05FDA3F0>: operation 0 progress 15
[04:40:51.0960] <DFU Device 05FDA3F0>: operation 0 progress 17
[04:40:51.0962] <DFU Device 05FDA3F0>: operation 0 progress 18
[04:40:51.0964] <DFU Device 05FDA3F0>: operation 0 progress 19
[04:40:51.0966] <DFU Device 05FDA3F0>: operation 0 progress 21
[04:40:51.0968] <DFU Device 05FDA3F0>: operation 0 progress 22
[04:40:51.0970] <DFU Device 05FDA3F0>: operation 0 progress 24
[04:40:51.0972] <DFU Device 05FDA3F0>: operation 0 progress 25
[04:40:51.0974] <DFU Device 05FDA3F0>: operation 0 progress 26
[04:40:51.0976] <DFU Device 05FDA3F0>: operation 0 progress 28
[04:40:51.0978] <DFU Device 05FDA3F0>: operation 0 progress 29
[04:40:51.0980] <DFU Device 05FDA3F0>: operation 0 progress 31
[04:40:51.0983] <DFU Device 05FDA3F0>: operation 0 progress 32
[04:40:51.0986] <DFU Device 05FDA3F0>: operation 0 progress 34
[04:40:51.0989] <DFU Device 05FDA3F0>: operation 0 progress 35
[04:40:51.0991] <DFU Device 05FDA3F0>: operation 0 progress 36
[04:40:51.0993] <DFU Device 05FDA3F0>: operation 0 progress 38
[04:40:51.0995] <DFU Device 05FDA3F0>: operation 0 progress 39
[04:40:51.0997] <DFU Device 05FDA3F0>: operation 0 progress 41
[04:40:51.0999] <DFU Device 05FDA3F0>: operation 0 progress 42
[04:40:52.0001] <DFU Device 05FDA3F0>: operation 0 progress 43
[04:40:52.0003] <DFU Device 05FDA3F0>: operation 0 progress 45
[04:40:52.0005] <DFU Device 05FDA3F0>: operation 0 progress 46
[04:40:52.0007] <DFU Device 05FDA3F0>: operation 0 progress 48
[04:40:52.0009] <DFU Device 05FDA3F0>: operation 0 progress 49
[04:40:52.0011] <DFU Device 05FDA3F0>: operation 0 progress 51
[04:40:52.0013] <DFU Device 05FDA3F0>: operation 0 progress 52
[04:40:52.0015] <DFU Device 05FDA3F0>: operation 0 progress 53
[04:40:52.0017] <DFU Device 05FDA3F0>: operation 0 progress 55
[04:40:52.0019] <DFU Device 05FDA3F0>: operation 0 progress 56
[04:40:52.0021] <DFU Device 05FDA3F0>: operation 0 progress 58
[04:40:52.0023] <DFU Device 05FDA3F0>: operation 0 progress 59
[04:40:52.0025] <DFU Device 05FDA3F0>: operation 0 progress 60
[04:40:52.0027] <DFU Device 05FDA3F0>: operation 0 progress 62
[04:40:52.0029] <DFU Device 05FDA3F0>: operation 0 progress 63
[04:40:52.0031] <DFU Device 05FDA3F0>: operation 0 progress 65
[04:40:52.0033] <DFU Device 05FDA3F0>: operation 0 progress 66
[04:40:52.0035] <DFU Device 05FDA3F0>: operation 0 progress 68
[04:40:52.0037] <DFU Device 05FDA3F0>: operation 0 progress 69
[04:40:52.0039] <DFU Device 05FDA3F0>: operation 0 progress 70
[04:40:52.0041] <DFU Device 05FDA3F0>: operation 0 progress 72
[04:40:52.0043] <DFU Device 05FDA3F0>: operation 0 progress 73
[04:40:52.0045] <DFU Device 05FDA3F0>: operation 0 progress 75
[04:40:52.0047] <DFU Device 05FDA3F0>: operation 0 progress 76
[04:40:52.0049] <DFU Device 05FDA3F0>: operation 0 progress 77
[04:40:52.0051] <DFU Device 05FDA3F0>: operation 0 progress 79
[04:40:52.0053] <DFU Device 05FDA3F0>: operation 0 progress 80
[04:40:52.0055] <DFU Device 05FDA3F0>: operation 0 progress 82
[04:40:52.0057] <DFU Device 05FDA3F0>: operation 0 progress 83
[04:40:52.0059] <DFU Device 05FDA3F0>: operation 0 progress 85
[04:40:52.0061] <DFU Device 05FDA3F0>: operation 0 progress 86
[04:40:52.0063] <DFU Device 05FDA3F0>: operation 0 progress 87
[04:40:52.0065] <DFU Device 05FDA3F0>: operation 0 progress 89
[04:40:52.0067] <DFU Device 05FDA3F0>: operation 0 progress 90
[04:40:52.0069] <DFU Device 05FDA3F0>: operation 0 progress 92
[04:40:52.0071] <DFU Device 05FDA3F0>: operation 0 progress 93
[04:40:52.0073] <DFU Device 05FDA3F0>: operation 0 progress 95
[04:40:52.0075] <DFU Device 05FDA3F0>: operation 0 progress 96
[04:40:52.0077] <DFU Device 05FDA3F0>: operation 0 progress 97
[04:40:52.0079] <DFU Device 05FDA3F0>: operation 0 progress 99
[04:40:52.0079] WinDFU::UploadData: EOF, cbRead: 1084
[04:40:52.0081] <DFU Device 05FDA3F0>: operation 0 progress 100
[04:40:52.0082] WinDFU::UploadData: ZLP
[04:40:52.0082] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
[04:40:52.0083] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
[04:40:52.0084] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
[04:40:52.0085] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
[04:40:55.0081] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
[04:40:55.0082] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
[04:40:55.0082] WinDFU::ResetDevice: resetting...
[04:40:55.0234] WinDFU::FinalizeDfuUpdate: success
[04:40:55.0237] <DFU Device 05FDA3F0>: DFU succeeded
[04:40:55.0239] Finished DFU Restore Phase: Successful
[04:40:55.0279] DFU mode device disconnected
[04:40:55.0281] Device removed when in state Restoring, moving device to transition state
[04:40:55.0282] Changing state from 'Restoring' to 'Transitioning'
[04:40:55.0283] Creating timer to monitor transition
[04:41:25.0846] DFU mode device connected
[04:41:25.0846] Transitioning device returned, continuing restore.
[04:41:25.0847] Canceling timer
[04:41:25.0848] Changing state from 'Transitioning' to 'Restoring'
[04:41:25.0849] AppleDevice::GetDeviceID: failed for iBoot
[04:41:25.0850] AppleDevice::GetDeviceID: failed for iBoot
[04:41:25.0850] requested restore behavior: Erase
[04:41:25.0851] requested variant: Erase
[04:41:25.0860] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[04:41:26.0594] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[04:41:26.0595] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[04:41:26.0597] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[04:41:26.0598] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[04:41:26.0600] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[04:41:26.0601] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[04:41:26.0602] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBSS"
[04:41:26.0604] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[04:41:26.0605] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
[04:41:26.0607] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
[04:41:26.0608] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
[04:41:26.0609] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
[04:41:26.0610] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
[04:41:26.0612] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
[04:41:26.0613] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[04:41:26.0613] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[04:41:26.0614] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "LLB"
[04:41:26.0615] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[04:41:26.0616] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[04:41:26.0617] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "SEP"
[04:41:26.0618] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[04:41:26.0619] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreSEP"
[04:41:26.0619] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[04:41:26.0620] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[04:41:26.0621] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[04:41:26.0622] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[04:41:26.0623] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[04:41:26.0624] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[04:41:26.0625] <DFU Device 121B7E30>: production fused device
[04:41:26.0625] requested restore behavior: Erase
[04:41:26.0626] AppleDevice::GetDeviceID: failed for iBoot
[04:41:26.0627] AppleDevice::GetDeviceID: failed for iBoot
[04:41:26.0628] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ec6fe4df
[04:41:26.0629] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ec6fe4df
[04:41:26.0630] <DFU Device 121B7E30>: operation 0 progress 0
[04:41:26.0631] <DFU Device 121B7E30>: operation 0 progress 1
[04:41:26.0632] <DFU Device 121B7E30>: operation 0 progress 2
[04:41:26.0633] <DFU Device 121B7E30>: operation 0 progress 3
[04:41:26.0634] <DFU Device 121B7E30>: operation 0 progress 4
[04:41:26.0635] <DFU Device 121B7E30>: operation 0 progress 5
[04:41:26.0639] <DFU Device 121B7E30>: operation 0 progress 6
[04:41:26.0643] <DFU Device 121B7E30>: operation 0 progress 7
[04:41:26.0647] <DFU Device 121B7E30>: operation 0 progress 8
[04:41:26.0653] <DFU Device 121B7E30>: operation 0 progress 9
[04:41:26.0657] <DFU Device 121B7E30>: operation 0 progress 10
[04:41:26.0661] <DFU Device 121B7E30>: operation 0 progress 11
[04:41:26.0665] <DFU Device 121B7E30>: operation 0 progress 12
[04:41:26.0669] <DFU Device 121B7E30>: operation 0 progress 13
[04:41:26.0675] <DFU Device 121B7E30>: operation 0 progress 14
[04:41:26.0679] <DFU Device 121B7E30>: operation 0 progress 15
[04:41:26.0683] <DFU Device 121B7E30>: operation 0 progress 16
[04:41:26.0687] <DFU Device 121B7E30>: operation 0 progress 17
[04:41:26.0694] <DFU Device 121B7E30>: operation 0 progress 18
[04:41:26.0698] <DFU Device 121B7E30>: operation 0 progress 19
[04:41:26.0702] <DFU Device 121B7E30>: operation 0 progress 20
[04:41:26.0706] <DFU Device 121B7E30>: operation 0 progress 21
[04:41:26.0711] <DFU Device 121B7E30>: operation 0 progress 22
[04:41:26.0717] <DFU Device 121B7E30>: operation 0 progress 23
[04:41:26.0721] <DFU Device 121B7E30>: operation 0 progress 24
[04:41:26.0725] <DFU Device 121B7E30>: operation 0 progress 25
[04:41:26.0729] <DFU Device 121B7E30>: operation 0 progress 26
[04:41:26.0735] <DFU Device 121B7E30>: operation 0 progress 27
[04:41:26.0739] <DFU Device 121B7E30>: operation 0 progress 28
[04:41:26.0743] <DFU Device 121B7E30>: operation 0 progress 29
[04:41:26.0747] <DFU Device 121B7E30>: operation 0 progress 30
[04:41:26.0751] <DFU Device 121B7E30>: operation 0 progress 31
[04:41:26.0757] <DFU Device 121B7E30>: operation 0 progress 32
[04:41:26.0761] <DFU Device 121B7E30>: operation 0 progress 33
[04:41:26.0765] <DFU Device 121B7E30>: operation 0 progress 34
[04:41:26.0769] <DFU Device 121B7E30>: operation 0 progress 35
[04:41:26.0775] <DFU Device 121B7E30>: operation 0 progress 36
[04:41:26.0779] <DFU Device 121B7E30>: operation 0 progress 37
[04:41:26.0783] <DFU Device 121B7E30>: operation 0 progress 38
[04:41:26.0787] <DFU Device 121B7E30>: operation 0 progress 39
[04:41:26.0793] <DFU Device 121B7E30>: operation 0 progress 40
[04:41:26.0797] <DFU Device 121B7E30>: operation 0 progress 41
[04:41:26.0801] <DFU Device 121B7E30>: operation 0 progress 42
[04:41:26.0805] <DFU Device 121B7E30>: operation 0 progress 43
[04:41:26.0809] <DFU Device 121B7E30>: operation 0 progress 44
[04:41:26.0815] <DFU Device 121B7E30>: operation 0 progress 45
[04:41:26.0819] <DFU Device 121B7E30>: operation 0 progress 46
[04:41:26.0823] <DFU Device 121B7E30>: operation 0 progress 47
[04:41:26.0827] <DFU Device 121B7E30>: operation 0 progress 48
[04:41:26.0833] <DFU Device 121B7E30>: operation 0 progress 49
[04:41:26.0837] <DFU Device 121B7E30>: operation 0 progress 50
[04:41:26.0841] <DFU Device 121B7E30>: operation 0 progress 51
[04:41:26.0845] <DFU Device 121B7E30>: operation 0 progress 52
[04:41:26.0849] <DFU Device 121B7E30>: operation 0 progress 53
[04:41:26.0855] <DFU Device 121B7E30>: operation 0 progress 54
[04:41:26.0859] <DFU Device 121B7E30>: operation 0 progress 55
[04:41:26.0863] <DFU Device 121B7E30>: operation 0 progress 56
[04:41:26.0867] <DFU Device 121B7E30>: operation 0 progress 57
[04:41:26.0873] <DFU Device 121B7E30>: operation 0 progress 58
[04:41:26.0877] <DFU Device 121B7E30>: operation 0 progress 59
[04:41:26.0881] <DFU Device 121B7E30>: operation 0 progress 60
[04:41:26.0885] <DFU Device 121B7E30>: operation 0 progress 61
[04:41:26.0889] <DFU Device 121B7E30>: operation 0 progress 62
[04:41:26.0895] <DFU Device 121B7E30>: operation 0 progress 63
[04:41:26.0899] <DFU Device 121B7E30>: operation 0 progress 64
[04:41:26.0903] <DFU Device 121B7E30>: operation 0 progress 65
[04:41:26.0907] <DFU Device 121B7E30>: operation 0 progress 66
[04:41:26.0913] <DFU Device 121B7E30>: operation 0 progress 67
[04:41:26.0918] <DFU Device 121B7E30>: operation 0 progress 68
[04:41:26.0922] <DFU Device 121B7E30>: operation 0 progress 69
[04:41:26.0926] <DFU Device 121B7E30>: operation 0 progress 70
[04:41:26.0930] <DFU Device 121B7E30>: operation 0 progress 71
[04:41:26.0936] <DFU Device 121B7E30>: operation 0 progress 72
[04:41:26.0940] <DFU Device 121B7E30>: operation 0 progress 73
[04:41:26.0944] <DFU Device 121B7E30>: operation 0 progress 74
[04:41:26.0948] <DFU Device 121B7E30>: operation 0 progress 75
[04:41:26.0954] <DFU Device 121B7E30>: operation 0 progress 76
[04:41:26.0958] <DFU Device 121B7E30>: operation 0 progress 77
[04:41:26.0962] <DFU Device 121B7E30>: operation 0 progress 78
[04:41:26.0966] <DFU Device 121B7E30>: operation 0 progress 79
[04:41:26.0972] <DFU Device 121B7E30>: operation 0 progress 80
[04:41:26.0976] <DFU Device 121B7E30>: operation 0 progress 81
[04:41:26.0980] <DFU Device 121B7E30>: operation 0 progress 82
[04:41:26.0984] <DFU Device 121B7E30>: operation 0 progress 83
[04:41:26.0988] <DFU Device 121B7E30>: operation 0 progress 84
[04:41:26.0994] <DFU Device 121B7E30>: operation 0 progress 85
[04:41:26.0998] <DFU Device 121B7E30>: operation 0 progress 86
[04:41:27.0002] <DFU Device 121B7E30>: operation 0 progress 87
[04:41:27.0006] <DFU Device 121B7E30>: operation 0 progress 88
[04:41:27.0012] <DFU Device 121B7E30>: operation 0 progress 89
[04:41:27.0016] <DFU Device 121B7E30>: operation 0 progress 90
[04:41:27.0020] <DFU Device 121B7E30>: operation 0 progress 91
[04:41:27.0024] <DFU Device 121B7E30>: operation 0 progress 92
[04:41:27.0028] <DFU Device 121B7E30>: operation 0 progress 93
[04:41:27.0034] <DFU Device 121B7E30>: operation 0 progress 94
[04:41:27.0038] <DFU Device 121B7E30>: operation 0 progress 95
[04:41:27.0042] <DFU Device 121B7E30>: operation 0 progress 96
[04:41:27.0046] <DFU Device 121B7E30>: operation 0 progress 97
[04:41:27.0052] <DFU Device 121B7E30>: operation 0 progress 98
[04:41:27.0057] <DFU Device 121B7E30>: operation 0 progress 99
[04:41:27.0059] WinDFU::UploadData: EOF, cbRead: 1084
[04:41:27.0060] <DFU Device 121B7E30>: operation 0 progress 100
[04:41:27.0061] WinDFU::UploadData: ZLP
[04:41:27.0062] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
[04:41:27.0062] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
[04:41:27.0063] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
[04:41:27.0064] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
[04:41:30.0061] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
[04:41:30.0062] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
[04:41:30.0063] WinDFU::ResetDevice: resetting...
[04:41:30.0127] WinDFU::FinalizeDfuUpdate: success
[04:41:30.0128] <DFU Device 121B7E30>: DFU succeeded
[04:41:30.0130] Finished DFU Restore Phase: Successful
[04:41:30.0174] DFU mode device disconnected
[04:41:30.0175] Device removed when in state Restoring, moving device to transition state
[04:41:30.0176] Changing state from 'Restoring' to 'Transitioning'
[04:41:30.0178] Creating timer to monitor transition
[04:41:41.0291] Recovery mode device connected
[04:41:41.0292] Transitioning device returned, continuing restore.
[04:41:41.0293] Canceling timer
[04:41:41.0293] Changing state from 'Transitioning' to 'Restoring'
[04:41:41.0294] requested restore behavior: Erase
[04:41:41.0295] requested variant: Erase
[04:41:41.0311] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[04:41:41.0927] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[04:41:41.0929] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[04:41:41.0930] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[04:41:41.0932] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[04:41:41.0933] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[04:41:41.0934] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[04:41:41.0936] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBSS"
[04:41:41.0937] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[04:41:41.0938] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
[04:41:41.0940] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
[04:41:41.0941] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
[04:41:41.0943] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
[04:41:41.0944] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
[04:41:41.0946] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
[04:41:41.0947] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[04:41:41.0948] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[04:41:41.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "LLB"
[04:41:41.0951] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[04:41:41.0953] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[04:41:41.0954] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "SEP"
[04:41:41.0955] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[04:41:41.0957] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreSEP"
[04:41:41.0958] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[04:41:41.0960] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[04:41:41.0961] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[04:41:41.0962] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[04:41:41.0964] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[04:41:41.0966] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[04:41:41.0967] iBoot build-version = iBoot-1940.10.58
[04:41:41.0968] iBoot build-style = RELEASE
[04:41:41.0969] requested restore behavior: Erase
[04:41:41.0971] requested restore behavior: Erase
[04:41:41.0972] unable to open device_map.txt: No such file or directory
[04:41:41.0974] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[04:41:41.0975] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[04:41:41.0976] AMDeviceIoControl: GetOverlappedResult failed
[04:41:41.0979] AMDeviceIoControl: pipe stall
[04:41:41.0980] USBControlTransfer: error 31, usbd status c0000004
[04:41:41.0981] command device request for 'getenv radio-error' failed: 2008
[04:41:41.0983] radio-error not set
[04:41:41.0984] unable to open device_map.txt: No such file or directory
[04:41:41.0985] <Recovery Mode Device 12703958>: production fused device
[04:41:41.0987] requested restore behavior: Erase
[04:41:41.0989] requested restore behavior: Erase
[04:41:41.0990] interface has 1 endpoints, file pipe = 1
[04:41:41.0990]
[04:41:41.0991] <Recovery Mode Device 12703958>: operation 4 progress -1
[04:41:41.0992] unable to open device_map.txt: No such file or directory
[04:41:41.0992] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[04:41:41.0993] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[04:41:41.0994] requested restore behavior: Erase
[04:41:41.0995] requested restore behavior: Erase
[04:41:41.0996] <Recovery Mode Device 12703958>: operation 42 progress -1
[04:41:41.0996] requested restore behavior: Erase
[04:41:43.0024] <Recovery Mode Device 12703958>: operation 5 progress -1
[04:41:43.0367] unable to open device_map.txt: No such file or directory
[04:41:43.0369] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[04:41:43.0370] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[04:41:43.0370] AMDeviceIoControl: GetOverlappedResult failed
[04:41:43.0371] AMDeviceIoControl: pipe stall
[04:41:43.0372] USBControlTransfer: error 31, usbd status c0000004
[04:41:43.0373] command device request for 'getenv ramdisk-delay' failed: 2008
[04:41:44.0483] <Recovery Mode Device 12703958>: operation 6 progress -1
[04:41:45.0512] <Recovery Mode Device 12703958>: operation 7 progress -1
[04:41:45.0832] <Recovery Mode Device 12703958>: operation 8 progress -1
[04:41:45.0833] unable to open device_map.txt: No such file or directory
[04:41:45.0833] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[04:41:45.0834] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[04:41:45.0835] <Recovery Mode Device 12703958>: operation 9 progress -1
[04:41:45.0836] <Recovery Mode Device 12703958>: Recovery mode succeeded
[04:41:45.0836] Finished Recovery Restore Phase: Successful
[04:41:46.0607] Recovery mode device disconnected
[04:41:46.0609] Device removed when in state Restoring, moving device to transition state
[04:41:46.0611] Changing state from 'Restoring' to 'Transitioning'
[04:41:46.0612] Creating timer to monitor transition
[04:41:49.0792] Restore completed, status:4014
[04:41:49.0792] Failure Description:
[04:41:49.0792] Depth:0 Error:Unexpected device state 'DFU' expected 'RestoreOS'[
and After one time give me
2014-04-13 14:22:48.639 [3380:18a4]: restore library built Feb 12 2014 at 16:27:17
2014-04-13 14:22:48.639 [3380:18a4]: iTunes: iTunes 11.1.5.5
2014-04-13 14:22:48.639 [3380:18a4]: iTunes: Software payload version: 11D167 (option key)
2014-04-13 14:22:48.639 [3380:18a4]: iTunes: Using MobileRestore state machine
[12:24:20.0679] Changing state from 'Idle' to 'Restoring'
[12:24:20.0713] AppleDevice::GetDeviceID: failed for iBoot
[12:24:20.0714] AppleDevice::GetDeviceID: failed for iBoot
[12:24:20.0719] requested restore behavior: Erase
[12:24:20.0728] requested variant: Erase
[12:24:20.0803] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[12:24:21.0345] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
[12:24:21.0345] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 12C393C0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0346] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 12C38EB0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0347] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 12C39408 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0348] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 12C38E68 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0349] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 12C388C8 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0350] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 12C38A30 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0351] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 12C37EA8 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0352] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
[12:24:21.0352] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
[12:24:21.0353] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
[12:24:21.0354] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
[12:24:21.0354] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
[12:24:21.0355] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
[12:24:21.0356] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 12C38F40 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0357] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 12C394E0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0358] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 12C389A0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0358] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 12C38AC0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0359] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 12C385B0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0360] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "SEP" Digest = "<CFData 12C37D40 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0361] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 12C39768 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0362] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreSEP" Digest = "<CFData 12C38958 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0363] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 12C391C8 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0364] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 12C39888 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0365] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 12C39600 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0366] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 12C39450 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0367] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 12C39840 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0368] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 12BDD478 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[12:24:21.0369] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
[12:24:21.0369] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per9561.tmp/amai/debug/ts s-request.plist
[12:24:23.0320] amai: tss_submit_job: HttpQueryInfo returned 200
[12:24:23.0326] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.0.0)
[12:24:23.0328] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per9561.tmp/amai/debug/ts s-response.plist
[12:24:23.0408] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
[12:24:23.0410] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "CFELoader"
[12:24:23.0412] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "RBM"
[12:24:23.0414] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PHLEET"
[12:24:23.0415] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PERTOS"
[12:24:23.0417] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PEHammer"
[12:24:23.0443] <DFU Device 07B89C58>: production fused device
[12:24:23.0444] requested restore behavior: Erase
[12:24:23.0446] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[12:24:23.0447] AppleDevice::GetDeviceID: failed for iBoot
[12:24:23.0447] AppleDevice::GetDeviceID: failed for iBoot
[12:24:23.0454] amai: AMAuthInstallPlatformCreateDataFromFileURL: can't resolve file
[12:24:23.0455] failed to read dfu file C:\Users\ADMINI~1\AppData\Local\Temp\Per9561.tmp\Firmware\dfu\iBSS.n51ap.RELEAS E.im4p
[12:24:23.0455] WinDFUUpload: dfuData is NULL!
[12:24:23.0456] AMRAuthInstallDeletePersonalizedBundle
[12:24:23.0765] Restore completed, status:2005
[12:24:23.0765] Failure Description:
[12:24:23.0765] Depth:0 Error:Failed to restore device in DFU mode.
i hope some one help me

Put the iPhone in DFU mode. Connect in iTunes. Hit Restore.
(Don't use Shift or Option)

How to re-run the operation that is in complete status?

This sounds funny, but here is my scenario:
I got 10 operations in a process. In the 6th step, it fetches the username to be assigned in the 7th step from the custom DB using JDBC service.
Unfortunately, the username was not maintained properly (with some mistyping in the DB). In the 7th step, I use Assign User service which takes the username got from 6th step. As it cannot find the username (as it was a mis-spelt name), the operation stalls.
If I see the status of the process,
I see
step1 - COMPLETE
step 5 - COMPLETE
step 6 - COMPLETE (fetching record from DB)
step 7 - STALLED (with error - user name doesnot exist)
i realized the error and corrected the Custom DB with right username.
Now my question is, How can I re-execute the whole process from step 6?
I checked it, but adminui doesnot allow to re-run the operations with COMPLETE status. if I rerun the step 7, there's no use as it is still holding the wrong user name.
Only option i see is asking the users to trigger it again from step 1 which doesnt make any sense for user as they think it's a re-work for them again and also there are multiple users in between the process who approves the form and they all have to rework on this.
highly appreciate your help on this.
Thanks,
kc

Hi Nith,
I tried exactly the same way and it worked perfectly in my test system. However in my prod system,
After I added the exception and routed to the stall process, I saw that process got halted this (below screen shot) way. After the invalid principal exception thrown, it should goto the next step which is Stall process that generates the stalled branch error.
As it got stopped here, now its not even allowing me to retry the operation. The process status is still in running state. I'm suing 8.2 ES.
I'm not understanding why the same steps worked in Test system, and not in Prod system.
very much appreciated if you can help me on this:
In PROD:
Retry Terminate
Operation Name
Status
Branch Name
Start Date
Completed Date
Employee Owner Review
EXCEPTION THROWN
main-branch
February 7, 2012 11:15:04 AM EST
Assignments [3]
COMPLETE
main-branch
December 19, 2011 12:14:33 PM EST
December 19, 2011 12:14:33 PM EST
Search E Owner
COMPLETE
main-branch
December 19, 2011 12:14:22 PM EST
December 19, 2011 12:14:32 PM EST
Apply Rights
COMPLETE
main-branch
December 19, 2011 12:14:22 PM EST
December 19, 2011 12:14:22 PM EST
In TEST: (this throws the branch error - execute13 is the stall process)
Retry Terminate
Operation Name
Status
Branch Name
Start Date
Completed Date
execute13
COMPLETE
main-branch
February 8, 2012 12:16:25 PM EST
February 8, 2012 12:16:25 PM EST
Employee Owner Review
EXCEPTION THROWN
main-branch
February 8, 2012 12:16:24 PM EST
Search E Owner
COMPLETE
main-branch
February 8, 2012 12:15:34 PM EST
February 8, 2012 12:15:40 PM EST
Thanks,
kc

Work process in complete status

Hi Gurus ,
wps are going to complete status and restart after error is set to no , tried to retart wps again same problem they going again to complete status .
could some guide on this.
thanks
va

Hi,
please find the trace file info
Network error of client T269, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Client address of T269 is 43.194.61.45(xxxxx.com)
***LOG Q04=> DpRTmPrep, NiBufReceive (1957 AEDIAZP 269 AEPSEDUBWS02) [dpxxdisp.c   8106]
RM-T269, U1957, 400      AEDIAZP, AEPSEDUBWS02, 06:31:06, M0, W11, VA02, 3/1
Thu Aug 14 06:54:08 2008
SoftCancel request for T281 M0 received from REMOTE_TERMINAL
Thu Aug 14 07:33:32 2008
ERROR => W38 (pid 692230) died [dpxxdisp.c   10724]
Thu Aug 14 07:41:12 2008
ERROR => DpCheckTerminals: NiCheck2(rc=-23) failed for tid: 304 -> disconnecting [dpxxdisp.c   8734]
thanks for ur help

SABA LMS Completion Status is always "Successful" -- even if quiz skipped

For a course I'm creating, the SABA LMS Completion Status is always “Successful” even if just 1 slide of the Scorm 1.2 compliant Adobe Presenter course is viewed – doesn’t even need to get into quiz.
A failing grade is also always "Successful". How to get an "Unsuccessful" for skipping the quiz and/or failing the quiz?
Settings:
Reporting - Quiz Manager:
Enable reporting for this project -- checked
Learning Managemenet System (LMS) -- Scorm
Choose Report Data -- Report Quiz results only
Report Pass or Fail -- Report Pass/Fail (should this be Report staus as defined by report data?)
Report Score to LMS as: Percent
Reporting Level -- Report interactions and the score

I have Presenter courses working properly in Saba. Sometimes the issue is your Offering or Content settings in Saba. Could be a combo of having Is Scoring checked and having a Mastery Score set on Course or Offering level.
When you dig down into the Activity History for that transcript completion, what status is listed on the module level? Saba will roll up to a status of Successful/Unsuccessful/Not Evaluated depending on how you have it setup. What Status is your content actually passing back: Completed, Incomplete, Passed, Failed?
Good Luck!

Captivate 4 - LMS Completion Status Updating

Hello,
We recently published Captivate 4 assessments to our LMS (Learn.com LearnCenter) that have a 3 attempt limit and require a score of 80% or greater to pass. We are finding that many will fail the first time, and when they pass the assessment on their second attempt the LMS gains the new higher % score but does not gain the "completed" status. Any ideas on what could be causing this?
Thank you,
Connor

Is the Captivate quiz set for multiple tries? I'd assume so...
If it's sending the updated score, it is likely sending the updated status...
But only way to be sure it to see what the Captivate lesson is actually sending.
If your LMS does not offer any way to 'trace' or otherwise see the actual lesson communication, perhaps try something like 'SCORM Cloud' (websearch) or the Reload Editor. I know the first, and perhaps the second, offer ways to see the actual communication between the lesson and the LMS.
(the official ADL Test Suite also offers this functionality but is more complicated to use, at least last time I tried it).
IF you can validate that the CP lesson is indeed sending the updated status to the LMS, but the LMS is not showing that updated status, then it's something to take up with your LMS vendor.
If CP is not sending that updated status...then it's a CP setting...somewhere...(I don't have any precise things to try, but the setting the quiz to allow retakes would be the first thing to look at).
HTH
Erik

Complete Status

Similar Messages

Maybe you are looking for