Just a question...
Has anybody created an API manager for WinCC OA 3.19 using the .NET API?
I have noticed that when updating to Patch 11 or 12 and recompiling my API managers to use the ETM.WINCCOA.Manager package of P11 or P12 result in the API manager crashing with a System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt'
When running the API manager under the Visual Studio debugger the manager always seems to crash in the Dispose() method of the ActionInt (ETM.WINCCOA.Internal) class. When the debugger can actually catch the crash it breaks on the line:
CSharpBridgePINVOKE.delete_ActionInt(swigCPtr);
The managers run just fine when using ETM.WINCCOA.Manager of Patch 10 or below.
Has anybody else ran into this issue?
P.S. I am aware that this is not the place to post bugs and expect support. I'm just curious if others have this issue in their .NET API managers...
Regards,
Jan
.NET API 3.19
Search
Re: .NET API 3.19
Just created a new empty API manager using the supplied templates (WinCC OA 3.19 P12). Running that manager exhibits the same behavior. The output of that manager is:
WCCOAWCCOAmanager1(6), 2024.06.24 14:41:54.947, IMPL, INFO, 0, , Microsoft.Hosting.Lifetime, Application started. Press Ctrl+C to shut down.
WCCOAWCCOAmanager1(6), 2024.06.24 14:41:54.957, IMPL, INFO, 0, , Microsoft.Hosting.Lifetime, Hosting environment: Production
WCCOAWCCOAmanager1(6), 2024.06.24 14:41:54.963, IMPL, INFO, 0, , Microsoft.Hosting.Lifetime, Content root path: C:\Users\adm_jcbaar\Desktop\WCCOAmanager1\WCCOAmanager1\bin\x64\Debug\net6.0
WCCOAWCCOAmanager1(6), 2024.06.24 14:41:54.971, IMPL, INFO, 0, , WCCOAmanager1.Services.HelloWorldService, 'Hello World' successfully written on DP 'ExampleDP_SumAlert.'
WCCILdata (0), 2024.06.24 14:42:00.733, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Api -num 6 CONN: 1), Status code: Itc_Tp_Read_Call_Failed, errno: Connection reset by peer (10054)
WCCILevent (0), 2024.06.24 14:42:00.734, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Api -num 6 CONN: 1), Status code: Itc_Tp_Read_Call_Failed, errno: Connection reset by peer (10054)
WCCOAWCCOAmanager1(6), 2024.06.24 14:41:54.947, IMPL, INFO, 0, , Microsoft.Hosting.Lifetime, Application started. Press Ctrl+C to shut down.
WCCOAWCCOAmanager1(6), 2024.06.24 14:41:54.957, IMPL, INFO, 0, , Microsoft.Hosting.Lifetime, Hosting environment: Production
WCCOAWCCOAmanager1(6), 2024.06.24 14:41:54.963, IMPL, INFO, 0, , Microsoft.Hosting.Lifetime, Content root path: C:\Users\adm_jcbaar\Desktop\WCCOAmanager1\WCCOAmanager1\bin\x64\Debug\net6.0
WCCOAWCCOAmanager1(6), 2024.06.24 14:41:54.971, IMPL, INFO, 0, , WCCOAmanager1.Services.HelloWorldService, 'Hello World' successfully written on DP 'ExampleDP_SumAlert.'
WCCILdata (0), 2024.06.24 14:42:00.733, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Api -num 6 CONN: 1), Status code: Itc_Tp_Read_Call_Failed, errno: Connection reset by peer (10054)
WCCILevent (0), 2024.06.24 14:42:00.734, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Api -num 6 CONN: 1), Status code: Itc_Tp_Read_Call_Failed, errno: Connection reset by peer (10054)
Re: .NET API 3.19
Sorry. Missed your post.
Yes, we are running a big C# API manager on 3.19. I am not sure about the patch number but we do not have any issues. if you want, I could verify our patch number for you.
Yes, we are running a big C# API manager on 3.19. I am not sure about the patch number but we do not have any issues. if you want, I could verify our patch number for you.
Re: .NET API 3.19
If you could then yes please. If you are running P10 or lower then maybe be careful updating to the later patches. If you are running P11 or higher then I will have to take a look at my environment.
Regards,
Jan
Regards,
Jan
Re: .NET API 3.19
Jan
Just saw that ETM has fixed a bug. Should make you happy. If this doesn't fix then we can check our patch level.
(but i'm sure we're not using the latest patch)
190814/1-7493284094, 1-7522817984: The custom API manager (C#) crashes
when used in WinCC OA 3.19 P012.
Just saw that ETM has fixed a bug. Should make you happy. If this doesn't fix then we can check our patch level.
(but i'm sure we're not using the latest patch)
190814/1-7493284094, 1-7522817984: The custom API manager (C#) crashes
when used in WinCC OA 3.19 P012.
Re: .NET API 3.19
I saw this in the readme for the P13 patch
Re: .NET API 3.19
Just downloaded P13 and it seems to be working again. Thanks for the heads up!