Clients may encounter/report an issue when attempting to deploy a new BW project in an new environment making use of a DQ which fails with following error

2018 Jan 18 16:25:03:625 GMT +0100 BW.Sis-Process_Sis Error [BW-Core] BWENGINE-100001 Arguments conflict
TibrvException[error=5,message=Arguments conflict]
        at com.tibco.tibrv.TibrvImplCmTPortC.natCmdCreate(Native Method)

TibrvException[error=5,message=Arguments conflict]

This exception indicates that the transport creation call failed, and the reason for it could be the daemon, service, network parameters of the transport conflicts with that of an existing transport on the same rvd.  More specifically you should not specify the same service number for transports that use different network specifications and connect to the same daemon.

As originally reported it's best to check for existing RVD daemons running and their transport settings to ensure there is no expected clash.

Another cause for this error was found to be when client wrongly set the heartbeat interval to be greater than the activation interva;

tibco.clientVar.Common/CmqSettings/SchedulerHeartbeatInSec=10
tibco.clientVar.Common/CmqSettings/SchedulerActivationInSec=3

By setting a heartbeat value larger than the activation interval can also introduce this error