[Imported] CS2017R2 August Update .NET Exception on incoming email

[sbeadle]

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: du5tin, originally posted: 2018-10-24 04:07:01 Id:183
Just upgraded a client's server tonight to CS2017R2 August Update and ran into issues. I think we have it sorted now by disabling the incoming email, just staying up to monitor the server. I already emailed support and am waiting to talk to them in the AM (really wanting 24/7 support right now!). I was wondering if anyone has seen this with 2017R2 July update or newer.

In the CS Logs:
'Exception 0xE0434352 at 00007FFF5E7E8EAC occurred'

Some internet searching says this is a general .NET exception. Could be for anything.

In Windows Application Events I found this nugget:
~~~~
Application: DBServer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentNullException
at .msclr.interop.marshal_as,class std::allocator ,class System::String ^(std.basic_string,std::allocator *, System.String*)
at .CEmailWrapper.GetEmails(CEmailWrapper*, std.vector *, Int32, std.vector,std::allocator ,std::allocator,std::allocator *, Boolean)
~~~~

Hopefully support will have something useful in the AM.

[sbeadle · Accepted solution]

>>Responses imported from previous forum

Reply From User: sbeadle, posted: 2018-10-24 09:51:13
Please can you confirm you are running 2017R2 August - 77.6807.1 ?

Reply From User: du5tin, posted: 2018-10-24 13:48:15
Just logging on to confirm. Looks like 6.79.6809.1 from the ISO file.

Reply From User: du5tin, posted: 2018-10-24 13:51:06
[at]sbeadle said:
Please can you confirm you are running 2017R2 August - 77.6807.1 ?

Steve, we are running 6.79.6809.1. Thanks!

Reply From User: du5tin, posted: 2018-10-24 19:57:19
Fixed! This problem was fixed in the September update.

Reply From User: du5tin, posted: 2018-11-15 18:05:52
Update: there were still some bugs in the CS2017R2 September update. So far these appear to be fixed in the October update.