topic Re: Qlikview can't communicate with R (SSE Plugin) in Integration, Extension & APIs

Qlikview can't communicate with R (SSE Plugin)

fredericobarrac — Sat, 16 Nov 2024 08:41:58 GMT

Hi everyone,

I'm having problems installing the R plugin (Link: sse-r-plugin/GetStarted.md at master · qlik-oss/sse-r-plugin · GitHub) in the client machine.

I've installed R, Rstudio, the Rserve library and I downloaded the plugin.

I've launched everything manually (first the Rserve and then the SSE), I updated the settings.ini in the AppData Folder, also in the Qlikview Server as well, I stoped and started the services, and nothing, there is no single line passing through the SSE.

The client has another machine (built for the purpose of testings with the data science team) and the settings are the same, everything looks the same, but in that machine it runs.

I've also done the installation in my local machine (for the purpose of testing) and everything runs perfectly.

Can anyone point me towards problems I could have ?

Thank you!

Best regards!

Re: Qlikview can't communicate with R (SSE Plugin)

maksim_senin — Tue, 20 Feb 2018 23:04:05 GMT

Hi,

I have the same issue, R.* function does not work in a QlikVeiw chart (Nov. 2017 SR2), Rserve and SSE starts normal. Rserve_d says the following when starting:

Loading config file Rserv.cfg

Failed to find config file Rserv.cfg

Rserve: Ok, ready to answer queries.

But SSE finally says "gRPC listening on port 50051".

What can go wrong?

Thanks.

Re: Qlikview can't communicate with R (SSE Plugin)

fredericobarrac — Wed, 21 Feb 2018 09:46:52 GMT

Hi Maxim,

I actually get the same message when I run the Debug mode but it still works.

I also saw the same in a clients configuration and no problems were found, so... nothing can go wrong.

Re: Qlikview can't communicate with R (SSE Plugin)

fredericobarrac — Wed, 21 Feb 2018 09:52:38 GMT

I'm sorry Maxim, only read the last part of the message.

Tell me something:

You're using qlikview desktop? did you changed the settings.ini?

does the R code appear in red like you're having a sintaxe error??

Re: Qlikview can't communicate with R (SSE Plugin)

maksim_senin — Wed, 21 Feb 2018 11:35:52 GMT

Hi Frederico,

Yes I use QV Desktop (but am going to use the R with QVS) and I've changed the settings.ini file.

The R code in the chart's expression is underlined with red waves...

Re: Qlikview can't communicate with R (SSE Plugin)

fredericobarrac — Wed, 21 Feb 2018 11:41:20 GMT

Ok we can configure both if you have them.

Did you changed the settings.ini on both Qlikview and Qliksense?

Qliksense location file -> C:\Users\XXX\Documents\Qlik\Sense\settings.ini

Qlikview location file -> C:\Users\XXX\AppData\Roaming\QlikTech\QlikView\settings.ini

Here, you place the following:

[Settings 7] (this is already there)

SSEPlugin=R,localhost:50051

since you're not using Qlikview Server, close the Qlikview app, run Rserve, Run SSEToRserve and then Qlikview.

Tell me if it worked.

Re: Qlikview can't communicate with R (SSE Plugin)

maksim_senin — Thu, 22 Feb 2018 11:23:35 GMT

Hi Frederico,

Wow! Wow! Wow! That works!

Thank you very much, I must be missed the settings.ini in the profile folder.

Have a good day.

Re: Qlikview can't communicate with R (SSE Plugin)

fredericobarrac — Thu, 22 Feb 2018 12:12:28 GMT

No problem !

Glad I could help.

Best regards!

Re: Qlikview can't communicate with R (SSE Plugin)

fredericobarrac — Thu, 22 Feb 2018 12:13:50 GMT

To who follows the get started , although a bit confusing, that get started explains everything.

In this case, and probably it won't affect any users, WATCH OUT for your Qlikview version.

In this case, it was the 12.10 and the plugin doesn't work with that version. Upgraded to the November 2017 version and it works. Simple solution!

Re: Qlikview can't communicate with R (SSE Plugin)

wallaceacn — Tue, 09 Apr 2019 06:31:35 GMT

Hi Everyone,

I have configured :

1) Rserve 2) SSEtoRserve 3) put right path in loadscript in qliksense but got parsing errors as follows :

May I ask what is issue causing this to be fixed ? thanks