Skip to Content

Can I configure my NCO server to be non-unicode?

I'm using NCO 3.0.19.0 and have created a server that initially threw the RfcUnsupportedPartnerException when the SAP system tries to connect. (Non-ABAP RFC client (partner type ) not supported)

When we change the unicode setting on SM59 to "Unicode", the connection succeeds as expected.

Is there some setting that I've missed on the NCO server configuration that forces all incoming connections to be unicode? I'd like to avoid forcing changes on the SAP side when I update all our PC services, and we've always used non-unicode connections with versions of the NCO prior to 3.0.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers