Salesforce

Salesforce Troubleshooting (Magic xpi 4.5)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Salesforce Troubleshooting (Magic xpi 4.5)

Q1

Why do I keep getting the "Login error (RemoteException): nested exception is: org.xml.sax.SAXException: Invalid element in com.sforce.soap.partner.GetUserInfoResult – orgDisallowHtmlAttachments" error when trying to connect to Salesforce's Sandbox?

A1

This error indicates that you are trying to use the wrong API version.

3.2 SP1 or higher uses API 18 to connect to Salesforce (previous versions used API 10 or 12). Make sure that the number at the end of the Sandbox URL matches the relevant version:

https://test.salesforce.com/services/Soap/c/18.0 (enterprise WSDL)

or

https://test.salesforce.com/services/Soap/u/18.0 (partner WSDL)

Q2

Why isn't the Salesforce connector working?

A2

To be able to use the Salesforce connector, you have to install the Magic xpi app that is available from the Salesforce AppExchange. For information about installing the app, click here. (Since version: V4.5a)

The Salesforce connector does not work if it is behind a proxy that requires only basic authentication.

Q3

Why am I getting an error message when I try to configure the OAuth with my Salesforce resource?

A3

Make sure that your .NET framework is configured to support TLS 1.2.

.NET 4.0 does not enable TLS 1.2 by default. To enable TLS 1.2 by default:

In the following two registry keys, set the SchUseStrongCrypto DWORD value to 1:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319.

If these keys do not exist, create them. These changes can be made by using the following import file: https://help.salesforce.com/apex/HTViewSolution?id=000221207.

Note that these registry keys will enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on your system. These registry values will not have an affect on .NET applications that set the System.Net.ServicePointManager.SecurityProtocol value.

It is recommend to test this change before deploying it to your production servers.

Reference
Attachment 
Attachment