OIM: Request completed status

Guys,
OIM 9.1.0.2
I need to confirm one thing:
For manual approval process(standard approval process):
Request should be completed after provisioning process completes.
1-When it is approved:
Request Status:Object Approval Complete - When the resource level Approval is complete and 'Approved' the status changes to 'Object Approval Complete'
2-When it is provisioned:
Request Status:Request Complete - When the resource is approved and provisioned, the request status changes to 'Request Complete'
For Pre Approval process:
Request should be completed before provisioning process completes.
1- Pre-approval process complete the request. Request Status:Request Complete
2- For some reason the provisioning could not be completed it is not intervene with the request status.
Is this true or not? If not, what should be the behavior(request status) of pre-approval process after approval process finish?
[]'s
Thiago Leoncio
Edited by: Leôncio on Apr 27, 2011 5:39 AM

The request status in OIM is not consistent. For the answer in your situation, you need to go through each step and record what your status is to know what the outcome is going to be. You will get different status's if you do more than auto complete and have actual approval tasks involved.
-Kevin

Similar Messages

Submitting Customized Report Request, Completed with Error Status

Dear All ,
Good Day ,,
1- I am using Oracle Application 11.5.0
2- Application And Data Base Server Unix AI
3- created Oracle Report file (i testes all sql statmets using toad , successfly)
5- Tested the report , passed parameters , it is running successfully .
6- Cpied the reports to the next path (E:\oracle\testappl\per\11.5.0\reports\US)
7- Created Executable file (has the same name of the rdf file)
8- Created Concurrent program contains the same Executable file and the output format is 'PDF', Style = 'Landscape' , printer = 'noprint' , the added the parameters (the same named in the rdf file)
9- Added the Concurrent program to the HRMS 'Reports & Process'
10- From the HRMS Manager Responsibility , i submitted the request , passed the parameters .
11- Refresh , Pending , Runing , phase 'Completed' , Status 'Error'
12-View Log .. :
Human Resources: Version : 11.5.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
KU_PAYSLIB module: KU_PAYSLIB
Current system time is 31-MAR-2010 23:29:55
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
TIME_PERIOD_ID='442'
ORGANIZATION_ID='1424'
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.AR8MSWIN1256
stat_low = 84
stat_high = 0
emsg:was terminated by signal 4
Start of log messages from FND_FILE
End of log messages from FND_FILE
Program was terminated by signal 4
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 3192426.
Review your concurrent request log and/or report output file for more detailed information.
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
Current system time is 31-MAR-2010 23:29:56
12-When i change the output format to XML it completes with 'Normal Status' but , the next Log is appearing :
Human Resources: Version : 11.5.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
KU_PAYSLIB module: KU_PAYSLIB
Current system time is 31-MAR-2010 23:36:19
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
TIME_PERIOD_ID='442'
ORGANIZATION_ID='1424'
Environment will now switch to UTF-8 code-set.
Parts of this log file may not display correctly
as a result. This is an expected behavior.
XML_REPORTS_XENVIRONMENT is :
/apps/oracle/testora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
XENVIRONMENT is set to /apps/oracle/testora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8
REP-3000: Internal error starting Oracle Toolkit.
Report Builder: Release 6.0.8.28.0 - Production on Wed Mar 31 23:36:20 2010
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Enter Username:
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PRINT   -------------
Printing output file.
Request ID : 3192428
Number of copies : 0
Printer : noprint
Finished executing request completion options.
Concurrent request completed successfully
Current system time is 31-MAR-2010 23:36:21
Thanks A lot

>
emsg:was terminated by signal 4
>
For this issue , pl see the solutions in this related thread - Re: The Concurrent Manager and Programs is failing random
>
REP-3000: Internal error starting Oracle Toolkit.
>
This typically indicates that an X server is not running on the Unix server. Pl see these MOS Docs
200474.1 - Comprehensive REP-3000 Troubleshooting and Overview Guide
207532.1 - Troubleshooting Tips for REP-3000 Error when Running PDF/POSTSCRIPT/HTML Reports
Searching on this topic in these forums will also retrieve many hits.
HTH
Srini

Need sql query to get OIM request pending approval details for one user

HI OIM Guru,
It would be great help if someone can provide me sql query by which i can find out how many requests are pending for approval for one user ?

1. Below query will give you status of all the request.
SELECT REQ.REQUEST_ID , REQ.REQUEST_STATUS FROM REQUEST REQ
2. You can have following status
Obtaining Operation Approval
Obtaining Template Approval
Operation Approval Approved
Operation Approval Rejected
Post Operation Processing Initiated
Request Approval Rejected
Request Closed
Request Completed
Request Created
Request Failed
Request Withdrawn
Template Approval Rejected
3. Now prepare the query from above sapmle, the requset status string should not contains foloowing values.
Rejected
Failed
Closed
Withdrawn
Completed
The builded query will give you the desired result for 11g
for 10 G
Get the OST_STATUS from Req table, and do you logic above stated
-Kuldeep
Edited by: Kuldeep on May 22, 2012 1:04 AM

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

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

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)

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

You cannot cancel a change request with status New.

We're just starting to dive into SCSM. We created a test Change Request and now want to delete / cancel it. When we try, we get a message
"You cannot cancel a change request with status New."
Is there an easy way to remove this?
Orange County District Attorney

Hi, a Little late but..
This is a problema from your 3 scsm services, maybe in your principal or secundary server. You must to restart services in an special order and delete application cache.
Please review
http://www.systemcentercentral.com/scsm-2012-tip-all-workflows-stuck-in-new-status-and-never-completing-issue-and-workaround/
it Works!
If you have principal and secondary do it in both servers.
I think this problem is for bad performance in databases and application, so review your hardware design, and logical, so review workflow performance too.
For items when state new, you must change it to inprogress with smlets

"completed" status tasks in UWL giving Exception...

Hi All,
Once the Request is approved successfully at all the Levels, the status of the Request in UWL shows as "completed" and the request is moving to "Tracking Tab". But, if we click on this completed status Request, it is giving "500 Internal Server Error/Null Pointer Exception". If anyone has idea, how to fix this issue, Please advise me.....
Thanks in Advance..
Thanks & Regards||
Ashok Kumar M.

Hi Ashok,
                 Navigate to SystemAdministration -> System configuration -> Universal Worklist ->Workflow -> Universal Worklist Administrationand then select the link: "Click to Manage Item Types and View Definitions" and then download the uwl.gp.config configuration files.
Then u can add this following tag to there (uwl.gp.config.xml)
    <ItemType name="uwl.completedtask.gp" connector="GuidedProceduresConnector" defaultView="uwlTaskGPView" defaultAction="launchGP" executionMode="default">
          <Actions>
            <Action name="launchGP" groupAction="no" handler="IViewLauncher" referenceBundle="launch_sap" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowName="GPWindow" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
              <Properties>
                <Property name="DynamicParameter" value="app.processId=${item.processID}&app.taskId=${item.activityID}&"/>
                <Property name="page" value="pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance"/>
                <Property name="System" value="SAP_LocalSystem"/>
              </Properties>
            </Action>
          </Actions>
    </ItemType>
Then overwrite the same file
Regards,
Vinoth

Request completed with error

the Concurrent request "Billing and Receipt History" is completing with following error message:
Enter Password:
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP--1870639101: MSG-00101: Consolidated Billing Profile: Y
REP-0081: Error during file I/O operation.
REP-0124: Unable to write to the temporary file.
scafa 3
REP-0002: Unable to retrieve a string from the Report Builder message file.
REP--1870639101:
following is the filesystem status:
df -gFilesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 0.50 0.46 8% 2461 3% /
/dev/hd2 2.00 0.17 92% 45635 52% /usr
/dev/hd9var 1.00 0.92 9% 2661 2% /var
/dev/hd3 3.50 0.65 82% 10424 7% /tmp
/dev/fwdump 0.50 0.50 1% 4 1% /var/adm/ras/platform
/dev/hd1 0.50 0.47 6% 252 1% /home
/proc - - - - - /proc
/dev/hd10opt 0.50 0.37 27% 2079 3% /opt
/dev/testdblv 20.00 11.14 45% 41930 2% /testdb
/dev/testdatalv 120.00 56.96 53% 78 1% /testdata
/dev/testappslv 56.00 15.48 73% 575441 14% /testapps
Please suggest any help.
Regards,
M.U.N.A

Try to delete the files from the /tmp directory and see if this helps.$ df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 0.50 0.46 8% 2461 3% /
/dev/hd2 2.00 0.17 92% 45635 52% /usr
/dev/hd9var 1.00 0.92 9% 2661 2% /var
/dev/hd3 3.50 3.39 4% 2541 1% /tmp
/dev/fwdump 0.50 0.50 1% 4 1% /var/adm/ras/platform
/dev/hd1 0.50 0.47 6% 252 1% /home
/proc - - - - - /proc
/dev/hd10opt 0.50 0.37 27% 2079 3% /opt
/dev/testdblv 20.00 11.14 45% 41934 2% /testdb
/dev/testdatalv 120.00 56.93 53% 78 1% /testdata
/dev/testappslv 56.00 15.47 73% 575448 14% /testapps
/dev/stagelv 51.00 7.22 86% 112970 7% /stage
/dev/visapp 40.00 9.56 77% 625906 22% /visapp
/dev/visdb 160.00 19.87 88% 42126 1% /visdb
$
Also, try to submit the concurrent program with smaller ranges of data (if application -- not sure what parameters you pass to this concurrent program).Request completed Normal with 100 records
If none of the above helps, log a SRShould I log SR if issue remains for huge number of records?

Send email notification when a concurrent request completes with Error

{color:#0000ff}I need to setup the system such that when a concurrent request completes with the status "Error", generate/send email notification to an application user. Please advice if you know how to configure the system to accomplish this.
Note: If the concurrent request completes with status "Normal" or "Warning", do not send/generate email notification to the application user.
Thanks.
{color}

We do what amOx does. I made a concurrent program that calls a sql script, and emails me of errored jobs. It is more convenient than logging in each day. I ran this twice daily, and the sql checks for the previous 12 hour time slice (ie - twice a day run).
..colin

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

The Customer has requested complete delivery

Hello all,
I am unable to create a delivery, and I am getting the following message log in the delivery creation Log.
The Customer has requested complete delivery
But my problem is, I dont know which item this is related to?
How can i find out which item it is?
I have seen the delivery log, it gives details, but doesnt say which one has the error.
I have seen the Long text details.
Also, my other point is, is the complete delivery againbst a customer or is it against a material?
Many thanks

Hi saping SAP
In VD02 go to sales area data -> shipping tab ->uncheck the box for complete delivery.
But make sure you have opted for partial deliveries in VD02
Another option is in when you create a sales order VA01- go to header data->shipping tab->uncheck the box complete delivery and then proceed by saving the order
If you have the shortage of material and you have checked the complete delivery, then system will not allow you to save order
Regards
Srinath

OIM: Request completed status

Similar Messages

Maybe you are looking for