LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: egiesen

Hello,

We are trying to upgrade and get our salesforce nodes to work and I see the new Nodes don't look like the old SFDC Login where you have a URL to point to production or the sandboxes (ie. test.salesforce.com or login.salesforce.com) . Im curious how this works for the SFDC Sandboxes if you just have a sfdcUsername and SFDCPAssword (ie the Lavastorm Get for Salesforce node)? We use single sign on and no security tokens, but no matter what I put in even when trying to log into production I get

ERROR: Error occurred during executing request: Invalid username, password, security token; or user locked out.
Error Code: brain.nodes.sfdc.requestError

ive tried just test.admin@org.com and test.admin@org.com.env1

Even though in the same graph same credentials I use the old SFDC LOGIN and it works so I know my credentials are correct, but I must not be filling out the node correctly. Any ideas?

Thanks,
Erica

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

Hi Erica,

The latest release of the Lavastom Analytic Library includes enhancements to the Lavastorm Get for Salesforce node, Lavastorm Metadata for Salesforce node and Lavastorm Update for Salesforce node. These nodes now have a new property that enables you to optionally specify the URL of the Salesforce instance you want to connect to, e.g. a Salesforce sandbox instance. By default, the node uses the URL of the Salesforce login server (https://login.salesforce.com) which redirects the connection to the relevant (production) instance associated with your credentials.

The error you mentioned above is probably related to the security setting configured against your Salesforce instance. On June 25 2016 Salesforce mandated that TLS 1.1 or TLS 1.2 must be used for all sandbox instances and that new production instances would, by default, also only accept TLS 1.1 connections as a minimum (though production instances can be downgraded to use TLS 1.0 if required - for the time being, this will not be supported for production instances in March 2017). The latest version of the above three nodes will negotiate with the server and now supports TLS 1.2 and TLS 1.1.

The latest release of LAL for Lavastorm 6.1.x can be downloaded from the Lavastorm website: http://www.lavastorm.com/lavastorm-installers/

Note, the above link redirects you to the downloads page that is currently hosted on Salesforce here: http://na3.salesforce.com/_ui/selfse...0150000000s09A

(follow the 'Download Lavastorm Analytic Library' link on the page).

Regards,
Adrian

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: egiesen

Thanks Adrian for the reply. I have version 6.1.1, so I will download version 6.1.3 to see the URL parameter.

I figured that this node I currently had was login into production so I used production credentials, but I still get the error. I do get a warning message. Maybe its something else? Its not due to the TLS as production is still at TLS 1.0 but for that matter we had them downgrade their sandboxes to TLS 1.0 until we get the version from Lavastorm that supports the higher TLS.


ERROR: Error occurred during executing request: Invalid username, password, security token; or user locked out.
Error Code: brain.nodes.sfdc.requestError

WARN: Node reported the following messages to stderr:
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)

Error Code: brain.unhandledLogging


NOTE : above it says the credentials are invalid or user locked. again I can login via the SFDC Login node on the same graph same credentials and it works so its not due to login/password/locked user.

I have the SfdcuUsername = test.lavastorm@level3.com
and I have the SFDCPassoword set
I don't have anything else set on the node except the general tab I have it set to Literal and this query
select
Id,
AccountNumber,
Name
from Account

Any ideas why its giving me the above error?

Thanks,

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

Hi Erica,

just one clarification on the new LAL installer. LAL 6.1.47.0 can be used with LAE 6.1.3, LAE 6.1.2 and LAE 6.1.1. So it is not necessary to install LAE 6.1.3 prior to upgrading the LAL component.

I am not familiar with the SOQL Bulk Query node you referred to in your other post (http://community.lavastorm.com/threa...6-1-Salesforce) but in your original post in this thread (above) you mentioned that you are not using security tokens so I assume the external IP address of your LAE server is configured on Salesforce as a trusted host. The issue may be related to the SSL certificate for Salesforce not being installed on the LAE server, see the guide here:

http://community.lavastorm.com/attac...5&d=1447948990

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: egiesen

I upgraded LAL and now have 6.1.47.0 installed which does have the URL parameter. and I still cant connect using any of the LAL nodes to SFDC.

I am able to connect to SFDC using the same graph, same version Lavastorm version , same server. Same everything except not using the LAL nodes. I am using the SFDC nodes that we have with our 4.6 version of Lavastorm, the sfdc library. So I really don't think any of my connection issues has anything to do with certificates, login information etc. I think this warning message I am getting must be the problem, but Im not really sure what to do to resolve it.

WARN: Node reported the following messages to stderr:
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session)

Error Code: brain.unhandledLogging

Has anyone ever seen this message before?

Thanks,
Erica

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

The times that I've seen that error.. the system is trying to send you a "popup" message (like you'd see from a browser), but since you're running on a linux server and you're not running inside a "graphic window".. there's no place to send the message.

There is likely another message buried in there that you are missing.... and is the real cause of trouble.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: egiesen

Shoot, any ideas on how to see what the message really says? I can log into SFDC via the web browser (Not lavastorm) with these credentials and I don't get an error.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: egiesen

Maybe I should double checking Im populating this new ServerURL parameter correctly.

Int eh old SFDC library I would use this
https://login.salesforce.com/services/Soap/u/35.0/ -- connect to production and still works in old SFDC Library
https://test.salesforce.com/services/Soap/u/35.0/ -- connect to fullsand.

Is this how the LAL ServerURL parameter should be populated to? I wasn't sure because I wasn't sure if the Soap in there is correct.

Thanks,

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

In the Lavastorm Get for Salesforce node, Lavastorm Metadata for Salesforce node and Lavastorm Update for Salesforce node the ServerUrl property value should be just the domain without the '/Soap/u/35.0/' elements, e.g.

https://eu5.salesforce.com

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Narenso

Hi team,
Pic.jpg
I'm having this weird error suddenly when i tried to connect the prod using login node for salesforce. This was working until yesterday. Do anybody having the same issue
? Please help on this.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

What error message are you getting?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: gmullin

Originally posted by: Narenso
					

Hi team,

Attachment 1292

 I'm having this weird error suddenly when i tried to connect the prod using login node for salesforce. This was working until yesterday. Do anybody having the same issue

? Please help on this.
			

If you open the Login node you'll see a filter node called Build URL & Headers that looks for a field called serverUrl. It looks like this is gotten from the XML returned from Salesforce. Maybe something changed and the name of it is now slightly different. Have a look at the output from Parse LoginResponse XML node and see if you can identify what the field should be now or if your login response returned was valid.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Narenso

Originally posted by: Narenso
					

Hi team,

Attachment 1292

 I'm having this weird error suddenly when i tried to connect the prod using login node for salesforce. This was working until yesterday. Do anybody having the same issue

? Please help on this.
			

Any idea about the error? This is after June-30 when Salesforce have done something from their end related to TLS update.
We directly trying to connect from Unix server. This was working fine until June-30. Our salesforce account is updated with TLS1.2.Eventhough it was working fine for few days. But suddenly it stopped working.
Using the URl: https://login.salesforce.com/services/Soap/u/25.0/
PFB the error details.
<logEvent level="ERROR" timestamp="1499854550000"><message xsi:type="errorMessage"><code key="lae.brainscript.field.unknownFieldName"/><message xsi:type="rawMessage"><![CDATA[Field 'serverUrl' does not exist on input 'in1'.]]></message></message><detail context="Salmon::NED::Field_Expr::findField()" file="build/linux-x86-64/release/code/source/brain/expert/Field_Expr.cpp" line="159" xsi:type="cppDetail"/><detail xsi:type="dataDetail"><pin channelType="in" name="in1" row="0"><metadata><column name="StatusCode" type="java.lang.Integer"/><column name="StatusMessage" type="java.lang.String"/><column name="Header" type="java.lang.String"/><column name="Call_Response" type="com.lavastorm.lang.UnicodeString"/></metadata></pin><pin channelType="out" name="out1" row="-1"/></detail><detail line="3" operator="'serverUrl'" xsi:type="brainscriptDetail"><fragment><![CDATA[soapOffset = serverUrl.strFindI("soap")]]></fragment></detail><detail xsi:type="expertDetail"><stack><frame line="3" operator="'serverUrl'"/><frame line="3" operator="FindI"/><frame line="3" operator="bs-set"/></stack></detail></logEvent>

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Narenso

@gmullin and @Stony Please assist on this

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: gmullin

I see the error is saying "Field 'serverUrl' does not exist on input 'in1'." On your input pin do you have a field called serverUrl that is being used in the node? Did the field get renamed at some point in the graph?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: gmullin

I just spotted the pic from your post back in March. Today's issue is identical? Are you still using the old sfdc.brg library? It looks like the same issue that a node in there is looking for a field serverUrl that is not in its input pin. The filter node "Build URLs & Headers" uses serverUrl field, check the output of the XML before it.

What version of Lavastorm are you on? Have you ever tried using the newer Salesforce nodes such as Lavastorm Metadata for Salesforce and Lavastorm Query for Salesforce?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Narenso

Originally posted by: gmullin
					

I just spotted the pic from your post back in March. Today's issue is identical? Are you still using the old sfdc.brg library? It looks like the same issue that a node in there is looking for a field serverUrl that is not in its input pin. The filter node "Build URLs & Headers" uses serverUrl field, check the output of the XML before it.


What version of Lavastorm are you on? Have you ever tried using the newer Salesforce nodes such as Lavastorm Metadata for Salesforce and Lavastorm Query for Salesforce?
			

Hi gmullin,
Please ignore all the above posts and i will post a new post with all the details. And thanks a lot for replying to the forum members queries, since we need more help from here. Will update the new post in a while with all details and issue description.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Narenso

Originally posted by: egiesen
					

Maybe I should double checking Im populating this new ServerURL parameter correctly.


Int eh old SFDC library I would use this

https://login.salesforce.com/services/Soap/u/35.0/   -- connect to production and still works in old SFDC Library

https://test.salesforce.com/services/Soap/u/35.0/   -- connect to fullsand.


Is this how the LAL ServerURL parameter should be populated to? I wasn't sure because I wasn't sure if the Soap in there is correct.


Thanks,
			

Hi Erica,
Are you able to solve this issue ? I'm facing the same issue with these nodes.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: gmullin

Originally posted by: Narenso
					

Hi Erica,

Are you able to solve this issue ? I'm facing the same issue with these nodes.
			

You likely need to update your sfloginURL value. Adrian previously suggested just using https://eu5.salesforce.com (for the newer Salesforce nodes) and Erica has posted here that she used https://login.salesforce.com/services/Soap/u/35.0/ successfully.

You have posted that you are using https://login.salesforce.com/services/Soap/u/25.0/ which looks like its out of date. I also see online people posting https://login.salesforce.com/services/Soap/u/40.0 for the latest API. You should try some of these and let us know which ones work for you.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Narenso

Originally posted by: Narenso
					

Hi Erica,

Are you able to solve this issue ? I'm facing the same issue with these nodes.
			

This helped out. Thanks - (Add a token in and it works perfectly)