1) Deployment of BW 6.x application fails with below error while deploying from TEA UI:

2019-06-13 13:49:22.560 DEBUG [main] c.t.b.t.m.d.u.ApplicationLifecycleCommand - TIBCO-BW-ADMIN-500402: Failed to deploy application [PublishSplitFileDetails:1.0], <CausedBy> {2}
2019-06-13 13:49:22.575 INFO  [main] bw.external.script - No script configured or script not found
2019-06-13 13:49:22.575 INFO  [main] bw.audit - application operation [create] with arguments { profileName=null appSpaceName=PublishSplitFileDetailsFT profileFile=E:/00.Deploy/Profiles//PublishSplitFileDetails/Deployment.substvar domainName=daydevbw6 replace=true description= earFileName=PublishSplitFileDetails.ear autoStart=true earFilePath= } failed with [TIBCO-BW-ADMIN-500402: Failed to deploy application [PublishSplitFileDetails:1.0], <CausedBy> TIBCO-BW-ADMIN-500011: Remote command execution failed, <CausedBy> {0}]
2019-06-13 13:49:22.575 DEBUG [main] c.m.s.j.internals.SQLServerStatement - SQLServerPreparedStatement:1310 created by (ConnectionID:1 ClientConnectionId: ed39c786-c349-4d0b-b024-5fa18de98a40)

2) Deploying the application from bwadmin console is also failing with the  same error message:

E:\tibco\bw\6.3\bin>.\bwadmin deploy -d daydevbw6 -a PublishSplitFileDetailsFT -pf E:\\00.Deploy\\Profiles\\PublishSplitFileDetails\\Deployment.substvar.PublishSplitFileDetailsFTNode1 -r -as PublishSplitFileDetails.ear
TIBCO ActiveMatrix BusinessWorks version 6.3.2, hotfix 3, build V42, 2016-09-08
TIBCO-BW-ADMIN-CLI-500402: Failed to deploy application from the archive [PublishSplitFileDetails.ear], TIBCO-BW-ADMIN-500402: Failed to deploy application [PublishSplitFileDetails:1.0], <CausedBy> TIBCO-BW-ADMIN-500011: Remote command execution failed, <CausedBy> {0}

The issue could be caused by the bwagent timed out before deployment was completed and succeeded. 
a) Tune below two bwagent properties in bwagent.ini file:

    bw.agent.technology.requestTimeout
    bw.agent.technology.remote.status.requestTimeout
    
    In case above values are already configured then please double the existing values.

b) If these values are not configured in your environment, you can add below properties in bwagent.ini to begin with.

bw.agent.technology.requestTimeout=120000
bw.agent.technology.remote.status.requestTimeout=6000

c) Please note that you need to restart the bwagent in order to make those changes effective.