Tibco Scribe Insight fails to connect to a Dynamics 365 Target when launching a DTS Integration Map. The message box that appears makes it seem like the entity no longer exists in the target CRM but of course it’s there still.
This could start happening suddenly for integrations that you previously had working without issues.
If you enabled tracing then you would see an out of memory exception in the workbench logs.
The fix that Tibco has on their website is mentioned here and it does work but it’s missing a few additional items which I’ve noted below.
The Tibco article only mentions the highlighted item below, but adding these other items is really necessary if you have any of the marketing or portal solutions installed. Now, don’t add any of these entries until you’ve confirmed that you’re not targeting any entities which contain these prefixes because that will break those integrations.
<BusinessEntityTableMetadata TableName="msdyn_*" omit="true"/>
<BusinessEntityTableMetadata TableName="msfp_*" omit="true"/>
<BusinessEntityTableMetadata TableName="msevtmgt_*" omit="true"/>
<BusinessEntityTableMetadata TableName="msdynmkt_*" omit="true"/>
<BusinessEntityTableMetadata TableName="msdyncrm_*" omit="true"/>
<BusinessEntityTableMetadata TableName="msdynci_*" omit="true"/>
<BusinessEntityTableMetadata TableName="adx_*" omit="true"/>
Additionally, the article only mentions one file to add these to, but you should add them to any files in your runtime directory which hold these properties for the Dynamics CRM Metadata, on my install those files are pictured below:
This issue can come on suddenly anytime you install a new solution because it may include new entities which adds to the overhead during the DTS startup when it is retrieving the metadata for everything that hasn’t been excluded with the above referenced tags.
Click the link below for AppHost's Tibco Scribe integration package: