search

SAP / node-rfc

Asynchronous, non-blocking SAP NW RFC SDK bindings for Node.js
Apache License 2.0
251 stars 73 forks source link

GUID returned by RFC has garbled characters #187

Closed MichelFernandes1997 closed 3 years ago

MichelFernandes1997 commented 3 years ago

I make a call to RFC and the returned data have a GUID === L^=V�c� Whats happened here? Someone can help me?

bsrdjan commented 3 years ago

Need more info on platform, could you please post the output of:

$ node -p "require('node-rfc').environment"
MichelFernandes1997 commented 3 years ago

Retuned undefined

MichelFernandes1997 commented 3 years ago

node-rfc: "0.1.10" and node: 6.9.4. These are the versions

bsrdjan commented 3 years ago

You need the latest node-rfc and supported node LTS version: https://github.com/SAP/node-rfc#supported-platforms

MichelFernandes1997 commented 3 years ago

For node-rfc it is version 2.3.1 and for node it is 12. * correct?

MichelFernandes1997 commented 3 years ago

I'll updated node-rfc and node libs but the error continue. You have idea?

bsrdjan commented 3 years ago

Could you please post the output of:

$ node -p "require('node-rfc').environment"
PaulWieland commented 3 years ago

Are you using docker by chance?

I found that if I had node-rfc installed on a volume, and I swap the container image out to a new version of nodejs but use the old version of node-rfc from the volume that I get garbage characters returned from RFCs.

My situation is unique, but in my case I had to make sure the volume was built from scratch so that the latest versions of my npm libraries were installed by the version of node in the docker image.

bsrdjan commented 3 years ago

Please re-open if support still needed