NCO 3.0 doesn't work with .NET Version 4.6 RC

[Former Member]

Hi folks,

after installing VS2015 RC for evaluation on one of our dev machines, some of our unit tests stopped working there (they continued working on other machines with exactly the same config, user, SAP-System, etc..)

On the machine with VS2015 RC installed, NCO threw an RfcSerializationException with message End mark RFCID.Header (0x0101) expected, but RFCID.FunctionName (0x0102) received when trying to connect (detailed stacktrace at the end of this post).

After some investigation it turned out to be the new .NET Framework-Version 4.6 RC which automatically was installed with VS2015 RC. After removal of both, the test worked again, so it seems there's a problem with NCO and the .NET Framework 4.6 RC

Will this be fixed in the next patch-release?

Thanks,

Tobias

**** Log file opened by process 396 at 2015-06-18 15:08:14 (UTC+02:00 Mitteleuropäische Sommerzeit)

SAP .NET Connector 3.0 with file version 3.0.15.0 running on 64-bit .NET Framework 4.0.30319.0

Program: C:\Program Files (x86)\JetBrains\ReSharper\v8.2\Bin\JetBrains.ReSharper.TaskRunner.CLR4.x64.exe

Working directory: <removed>

Operating system: Windows 7 Enterprise 64-bit Service Pack 1

Processor: 8x AMD64 (or x64)

SAP release: 721, Kernel release: 721, Kernel patch level: 418

Hostname: <removed>, IP address: <removed>, IP_v6 address:

Default trace level: None

>> Error entry 2015-06-18 15:08:14.624 [Thread 7 (xUnit.net STA Test Execution Thread)]

SAP.Middleware.Connector.RfcCommunicationException

   bei SAP.Middleware.Connector.CpicConnection.ThrowCpicErrorMsg(Int32 length, Int32 dataReceived)

   bei SAP.Middleware.Connector.CpicConnection.CpicReceive(Int32 timeout)

   bei SAP.Middleware.Connector.CpicConnection.Read(Byte* buffer, Int32 offset, Int32 count)

   bei SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)

>> Error entry 2015-06-18 15:08:14.638 [Thread 7 (xUnit.net STA Test Execution Thread)]

Failure to create pool for destination default (ORIGINAL) [USE_SAPGUI=0 SNC_LIB=<removed> CLIENT=100 LANG=DE POOL_SIZE=2 MAX_POOL_SIZE=5 IDLE_TIMEOUT=1 MAX_POOL_WAIT_TIME=100 POOL_IDLE_TIMEOUT=1 IDLE_CHECK_TIME=1 SNC_MODE=1 GROUP=<removed> MSHOST=<removed> SYSID=<removed> NAME=default]

SAP.Middleware.Connector.RfcSerializationException: End mark RFCID.Header (0x0101) expected, but RFCID.FunctionName (0x0102) received

   bei SAP.Middleware.Connector.RfcConnection.ReadRfcIDEnd(RFCID expectedRid, RfcParameter& param, RfcTable& table)

   bei SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)

   bei SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)

   bei SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length)

   bei SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)

   bei SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)

   bei SAP.Middleware.Connector.RfcConnection.ConnectAsClient(RfcDestination destination, Boolean forRepository)

   bei SAP.Middleware.Connector.RfcConnectionPool..ctor(RfcDestination destination, Boolean forRepositoryCalls)

[othulke]

We had the same issue with .net 4.6 RC, too.

Using .net 4.6 RTM (4.6.00081) the NCo library appears to work as expected.

[Former Member]

I've experienced the same issue, but for some reason I only receive the same error when utilizing a asp.net application, but if I create the same application in a windows form application it works without error.

[MarkusTolksdorf]

Hello Tobias,

so far NCo 3.0 is only supported up to .NET 4.0. As long as a .NET runtime is not supported officially, you can use it at own risk, but there is no guarantee that it works and you won't get support in case of issues. You can regularly check note 856863 whether there have been changes with regards to supported OS versions and .NET runtimes in case you need to know the state of a certain combination.

Best regards,

Markus