Upgrade Issues With The November 8, 2016 Release Of The Scribe Online Connector For Salesforce

Upgrade Issues With The November 8, 2016 Release Of The Scribe Online Connector For Salesforce

book

Article ID: KB0078877

calendar_today

Updated On:

Products Versions
TIBCO Cloud Integration - Connect ( Scribe ) -

Description

With the recent upgrade of the TIBCO Scribe® Online Connector for Salesforce to support the Salesforce API v37, a few of our users reported the following two issues:
  • When using the Connector for Salesforce in a Replication Solution, Execution History displayed 0 records processed and 0 records failed.
  • Some integrations failing with a fatal error similar to the following:
A fatal error has occurred in the Salesforce Connector: There is an error in XML document (87, 4641). | Details:    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle) at  System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

Issue/Introduction

Workaround for fatal error in Salesforce Integrations or 0 records processed.

Resolution

Initial analysis by our Engineering Team indicates that there may be some backward incompatibilities of our upgraded Connector with the prior versions of the Salesforce API (v33 and below). As such, the recommended workaround is as follows:

IMPORTANT: Follow these steps for each and every Salesforce Connection in all of your Organizations:
  1. Open the TIBCO Scribe® Online Salesforce Connection dialog.
  2. Change the Salesforce URL to use the V37 API instead of v33.0 and below by entering the following URL:
https://login.salesforce.com/services/Soap/u/37.0
  1. Test and save the Connection.
  2. From the Connections page, reset the metadata for each Salesforce Connection either by right-clicking the Connection and selecting Reset Metadata or by selecting the Connection and clicking the Reset Metadata button at the top of the Connection page.
  3. Wait a few minutes for metadata to be reset and run the Map or Solution again.
Note: In some cases, users needed to remove the .0 from the end of the URL to connect successfully.

We will continue to work to determine the root cause of this issue and address it accordingly.
 
Powered by Wolken Software