Salesforce

Salesforce Troubleshooting (Magic xpi 4.13)

Printable View
« Go Back

Information

 
Created BySalesforce Service User
Approval Process StatusPublished
Objective
Description

Salesforce Troubleshooting (Magic xpi 4.13)

Q

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?

A

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)

Q

Why isn't the Salesforce connector working?

A

  • When you are required to work behind a proxy server, the proxy settings need to be defined in the Magic.ini file to enable the validation of your Salesforce resource. You do this by creating the following entry in the [MAGIC_ENV] section of the Magic.ini file: HTTPProxyAddress = <ProxyAddress>:<Port>

    For example: 10.9.3.16:8080

  • To be able to work with Linux and TLS 1.2, you need to add the following to the JVM_ARGS parameter in the MAGICXPI.INI file: -Dhttps.protocols=TLSv1.1,TLSv1.2

Q

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

A

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 recommended to test this change before deploying it to your production servers.

Q

Why am I not able to connect to the Salesforce's Sandbox environment through OAuth?

A

To connect to the Salesforce's Sandbox environment through OAuth, try doing the following steps:

  1. Open the Registry Editor (regedit)

  2. Go to the entry HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION

  3. Add new DWORD (32-bit) entries with names MgxpiStudio.exe and EnvironmentSettings.exe with value as 11000 for both the entries below:

"MgxpiStudio.exe"=11000

"EnvironmentSettings.exe"=11000

Reference
Attachment 
Attachment