We have several machines failed to run TS: SAP GUI 720 EN x64
Here's the smsts.log
Failed to run the action: TaskSequence Failed.
The operation completed successfully. (Error: 00000000; Source: Windows) TSManager 12/9/2013 12:33:50 PM 5020 (0x139C)
Sending status message . . . TSManager 12/9/2013 12:33:50 PM 5020 (0x139C)
Send a task execution status message SMS_TSExecution_ActionFailError TSManager 12/9/2013 12:33:50 PM 5020 (0x139C)
Formatted header: TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:5f93786e-447b-4ba1-baad-da6a065d09d0</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2013-12-09T17:33:51Z</SentTime><Protocol>http</Protocol><Body
Type="ByteRange" Offset="0" Length="2674"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Clear local default environment TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Let the parent group (If INI not exist) decides whether to continue execution TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Let the parent group (SAP GUI 7.20Bit64 EN) decide whether to continue execution TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
The execution of the group (SAP GUI 7.20Bit64 EN) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Failed to run the last action: TaskSequence Failed. Execution of task sequence failed.
The operation completed successfully. (Error: 00000000; Source: Windows) TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Sending status message . . . TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Send a task execution status message SMS_TSExecution_TaskSequenceFailError TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Formatted header: TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:5f93786e-447b-4ba1-baad-da6a065d09d0</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2013-12-09T17:33:51Z</SentTime><Protocol>http</Protocol><Body
Type="ByteRange" Offset="0" Length="2094"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSManager 12/9/2013 12:33:51 PM 5020 (0x139C)
Task Sequence Engine failed! Code: enExecutionFail TSManager 12/9/2013 12:34:19 PM 5020 (0x139C)
**************************************************************************** TSManager 12/9/2013 12:34:19 PM 5020 (0x139C)
Task sequence execution failed with error code 80004005 TSManager 12/9/2013 12:34:19 PM 5020 (0x139C)
Cleaning Up. Removing Authenticator TSManager 12/9/2013 12:34:19 PM 5020 (0x139C)
Cleaning up task sequence folder TSManager 12/9/2013 12:34:19 PM 5020 (0x139C)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 12/9/2013 12:34:19 PM 5020 (0x139C)
Executing command line: "C:\Windows\SysWOW64\CCM\TsProgressUI.exe" /Unregister TSManager 12/9/2013 12:34:19 PM 5020 (0x139C)
Don't see useful information in execmgr.log, etc.
Anyone can tell what's the problem? Anyother information, you need?