I to have encountered this, but with an earlier release. The BASIS and ABA components on this system are still 6.40. However i have another 640 system that has no issues. The User account and password I'm using is valid as i can log into the SAP GUI with them. To add to this, i can get a successful RfcOpenEx() call via the srfctest binary packaged with the SDK. But both a JCo(2.1.6) and a custom C binary that use RfcOpenEx() both fail with this error, all 3 using the same userid and password and other connection params. Seems to be the RFCPING that is failing when i examine the Trace file, but in both successful RFC trace from srfctest.exe and the failed RFC Traces from the JCo app and C app both have the same connection parameters. Could this be due to the new case insensitivity introduced not working correctly? However setting the TOUPPER connection param does not seem to make any difference. One difference between the 2 systems is that the one that is failing is unicode, and the one that is successful is non-unicode. Could this be a factor? Although there is code in srfctest.c which sets a param based on unicode/non-unicode, this param is not being sent on the successful connection.
Has anyone encountered anything like this? Any assistance here would be greatly appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.