Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84650members
353990posts

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

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Solved
sbeadle
Janeway Janeway
Janeway
0 Likes
1
449

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

>>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.

 


Accepted Solutions
sbeadle
Janeway Janeway
Janeway
0 Likes
0
448

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

>>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.

See Answer In Context

1 Reply 1
sbeadle
Janeway Janeway
Janeway
0 Likes
0
449

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

>>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.