LAE

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

Originally posted by: ANTARA MALLIK

Hello,
I am using lavastorm 6.1.3 version. When trying to make a connection to Salesforce using the 'Lavastorm metadata for Salesforce' node or other Salesforce nodes present in this version, I am getting an error as below:
'RSA premaster secret error.
Error code: brain.nodes.sfdc.requestError'

Please could you help me understand why am I getting this error and what needs to be taken care of?
Also please note that I am giving the required SF parameters and security token.

Looking forward to your suggestions.

Thanks and Regards,
Antara Mallik

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

Originally posted by: khopkins

Hello

I am also getting this same error on the same node but also an additional one which i think is related.

ERROR: Error occurred during executing request: Connect to na3.salesforce.com:443 [na3.salesforce.com/, na3.salesforce.com/, na3.salesforce.com/] failed: Connection timed out
Error Code: brain.nodes.sfdc.requestError

Any help for us both would be appreciated as we are both working on the same upgrade

Regards,

Keith

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

Originally posted by: khopkins

Hello,

After turning on the full debug error logging i get the below error now if thats any help

DEBUG: Node class = com.lavastorm.brain.nodes.sfdc.SalesForceQueryNode Impl
DEBUG: Done processing java properties
DEBUG: Initializing CleanOutputs with ls.brain.node.java.brdCleanup
DEBUG: Initialized CleanOutputs withfalse
DEBUG: : Sending output message for Records
DEBUG: : Sending output message for sessionData
DEBUG: finish open took 0 called 0 times
DEBUG: Creating node
DEBUG: Node created. Duration: (15)
DEBUG: Setting up node
INFO: An error occured while converting ServerUrl: no protocol: (https://na13.salesforce.com
Error Code: brain.node.evaluation.property.conversionError
INFO: Evaluation of parameter ServerUrl failed.
Error Code: brain.node.parameter.evaluationFailed
ERROR: Evaluation of parameter ServerUrl failed.
DEBUG: Destroying node
DEBUG: Node destroyed. duration (2)
INFO: Node failed.
Error Code: brain.nodeFailed

Regards,

Keith

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

Originally posted by: prasmussen

Is this a test or a production environment? Please try with the following URL: https://login.salesforce.com

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

Originally posted by: khopkins

Hello,

this is a production environment and i have tried various URL`s in an attempt to rectify this but the below is the error log from https://login.salesforce.com

DEBUG: Node class = com.lavastorm.brain.nodes.sfdc.SalesForceQueryNode Impl
DEBUG: Done processing java properties
DEBUG: Initializing CleanOutputs with ls.brain.node.java.brdCleanup
DEBUG: Initialized CleanOutputs withfalse
DEBUG: : Sending output message for Records
DEBUG: : Sending output message for sessionData
DEBUG: finish open took 0 called 0 times
DEBUG: Creating node
DEBUG: Node created. Duration: (17)
DEBUG: Setting up node
INFO: An error occured while converting ServerUrl: no protocol: (https://login..salesforce.com
Error Code: brain.node.evaluation.property.conversionError
INFO: Evaluation of parameter ServerUrl failed.
Error Code: brain.node.parameter.evaluationFailed
ERROR: Evaluation of parameter ServerUrl failed.
DEBUG: Destroying node
DEBUG: Node destroyed. duration (2)
INFO: Node failed.
Error Code: brain.nodeFailed

Regards,

Keith

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

Originally posted by: ANTARA MALLIK

Hello,

Please can you provide your suggestions and extend help in this case? We are stuck at this point and unable to proceed any further for the upgrade activity.

Looking forward to hear from you!

Thanks and Regards,
Antara Mallik

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

Originally posted by: prasmussen

Which version of LAL are you using? You can check by selecting in the toolbar (View->Dependent Libraries)

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

Originally posted by: khopkins

Hello,

We are using 6.1.48.0.19 both on the client and the server

Regards,

Keith

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

Originally posted by: ANTARA MALLIK

Hi Team,

Is there an update on this please? We need your suggestions and help.

Thanks and Regards,
Antara Mallik

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

Originally posted by: ejones

Hi Antara,

I am working with someone that is now receiving this error too. It is exactly the same one you are. One thing interesting is that a different version of Lavastorm installed on the same Linux server is working. Have you been able to solve this?

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

Originally posted by: khopkins

Hello,

What version of Linux is this running on and what versions of Lavastorm as we are having to upgrade our Linux version as it doesnt support TLS1.0 and this is what is causing us this issue.

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

Originally posted by: ejones

The version of Lavastorm that is failing is 6.1.4. Exactly the same as originally reported in this thread.
But on the same Linux server version 5.1 is working. Since 5.1 does not support TLS 1.0 we need the customer to upgrade before support for TLS 1.0 is shut off completely.
I was mistaken, so thanks for asking about the version of Linux, I checked and it is actually Solaris.

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

Originally posted by: khopkins

OK you may need to look at the java setup also as we had issues with that as i have been told that 6.1 now utilises java directly as previous versions did not

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

Originally posted by: ejones

We just solved this.

It turned out that in the new environment we had copied the files in the ./lib/java/ext directory from another Lavastorm install. Because of our research and Internet searches we began to suspect that sunjce_provider.jar might be involved with the error. When we deleted it from the ./lib/java/ext directory and retried, it worked.