Install BizTalk 2013 R2 + SQL Server on cluster - MSDTC Failure

Question

Hi, Folks.
I'm trying to install BTS 2013 R2 using SQL Server on a cluster. Successfully I've configured SSO (on same BTS server), BRE and Group, perhaps when I try to install Runtime there is an error:
The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service is running and DTC network access is allowed on the BizTalk, SQL and SSO Master servers. For more information, see "MSDTC Configuration
settings required for BizTalk Server" in the BizTalk Server Help.
Internal error: "New transaction cannot enlist in the specified transaction coordinator. "
Well, I get DTCPing and take a test between my BTS server and MSDTC cluster server, which runs fine. I don't have any firewall between those servers. After, I've checked my DTC settings in both sides. They are configured properly, according to MS:
MSDTC Cluster settings
BTS Server settings
After, I've looked to Event Viewer and I found a warning message from SSO every 30 seconds when BTS Config is trying to install BTS Runtime:
Could not access the SSO database. If this condition persists, the SSO service will go offline.
 Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding..
 SQL Error code: 0xFFFFFFFE
I "googled" it and found this issue is generally related to my BizTalk user permission on database server, perhaps, my user have high privileges in all DB servers which compose my cluster.
 All servers (3 from DB cluster and 1 for BTS) runs Windows 2012 R2 64-bit, my SQL Server version is 2014 and BTS user and related groups bellows to my domain. I really don't understand what's going on.

Answer 1

Hi, Shankycheil.
My 3 SQL Cluster nodes share the same CID, so, I've reconfigured two nodes, reboot each server and install MSDTC again. After that, DTCPing stops to show the CID warning.
MSDTC cluster residents on same server with have SQL Server cluster.
After, following Ashwin Prabhu suggestion, I've unconfig and config all BTS itens again, perhaps, at BTS Group I got the same error.
Looking at my BTS MSDTC trace file I see an timeout erro, while BTS Group config is running:
pid=4888       ;tid=3424       ;time=03/02/2015-15:18:16.560   ;seq=11         ;eventid=TRACING_STARTED                          ;;"TM
Identifier='(null)                                            '" ;"MSDTC is resuming the tracing of long - lived transactions"
pid=4888       ;tid=3424       ;time=03/02/2015-15:18:17.145   ;seq=12         ;eventid=TRANSACTION_BEGUN                        ;tx_guid=56b93685-6ada-47bc-8a80-c30ff7ad66ae
    ;"TM Identifier='(null)                                            '" ;"transaction has begun, description :'<NULL>'"
pid=4888       ;tid=3424       ;time=03/02/2015-15:18:17.145   ;seq=13         ;eventid=TRANSACTION_PROPOGATED_TO_CHILD_NODE     ;tx_guid=56b93685-6ada-47bc-8a80-c30ff7ad66ae    
;"TM Identifier='(null)                                            '" ;"transaction propagated to 'xxxxx' as transaction child node
#1"
pid=4888       ;tid=4964       ;time=03/02/2015-15:23:40.801   ;seq=14         ;eventid=ABORT_DUE_TO_TRANSACTION_TIMER_EXPIRED   ;tx_guid=56b93685-6ada-47bc-8a80-c30ff7ad66ae
    ;"TM Identifier='(null)                                            '" ;"transaction timeout expired"
pid=4888       ;tid=4964       ;time=03/02/2015-15:23:40.801   ;seq=15         ;eventid=TRANSACTION_ABORTING                
    ;tx_guid=56b93685-6ada-47bc-8a80-c30ff7ad66ae     ;"TM Identifier='(null)                                            '"
;"transaction is aborting"
pid=4888       ;tid=4964       ;time=03/02/2015-15:23:40.801   ;seq=16         ;eventid=CHILD_NODE_ISSUED_ABORT                  ;tx_guid=56b93685-6ada-47bc-8a80-c30ff7ad66ae
    ;"TM Identifier='(null)                                            '" ;"abort request issued to transaction child node
#1 'xxxxx'"
pid=4888       ;tid=4308       ;time=03/02/2015-15:23:40.801   ;seq=17         ;eventid=CHILD_NODE_ACKNOWLEDGED_ABORT            ;tx_guid=56b93685-6ada-47bc-8a80-c30ff7ad66ae
    ;"TM Identifier='(null)                                            '" ;"received acknowledgement of abort request from
transaction child node #1 'xxxxx'"
pid=4888       ;tid=4308       ;time=03/02/2015-15:23:40.801   ;seq=18         ;eventid=TRANSACTION_ABORTED                      ;tx_guid=56b93685-6ada-47bc-8a80-c30ff7ad66ae
    ;"TM Identifier='(null)                                            '" ;"transaction has been aborted"
pid=4888       ;tid=4308       ;time=03/02/2015-15:23:41.674   ;seq=19         ;eventid=TRANSACTION_PROPAGATION_FAILED_TRANSACTION_NOT_FOUND ;tx_guid=56b93685-6ada-47bc-8a80-c30ff7ad66ae    
;"TM Identifier='(null)                                            '" ;"failed to propagate transaction to child node 'xxxxx' because
the transaction could not be found. Some possible reasons include, client might have already called commit or transaction might have got aborted due to timeout."
pid=4888       ;tid=4308       ;time=03/02/2015-15:23:41.675   ;seq=20         ;eventid=TRANSACTION_PROPAGATION_FAILED_TRANSACTION_NOT_FOUND ;tx_guid=56b93685-6ada-47bc-8a80-c30ff7ad66ae    
;"TM Identifier='(null)                                            '" ;"failed to propagate transaction to child node 'xxxxx' because
the transaction could not be found. Some possible reasons include, client might have already called commit or transaction might have got aborted due to timeout."
My remote MSDTC server has a huge capability and I don't see any high consume process at this time to give me this timeout error.
At least, I've tried run "msdtc -tmMappingSet"
and "msdtc.exe -tmMappingView"
on BTS server, but I got an error message from msdtc.exe:
Error occurred while trying to perform the above operation. Check the trace file for more information
I don't see any error at trace, only at eventvwr showing an error event "Invalid command line arguments.". This configuration must be done at BTS server-side or my MSDTC cluster?