SEHException from applications on the associated share

Question

Background

We run all of our Windows form applications from a Windows share (UNC) localized locally to the user drive W. We have been having problems connecting for the last few days, and we get a System.Runtime.InteropServices.SEHException from several random places in our programs after they have been running from a few minutes to several hours.

These exceptions are thrown even after reconnecting. They seem to appear when showing a dialogue or other form. None of the programs do I / O on the disk / network in the user code.

Questions

Do Windows write applications to download applications from an exe file?

If so, to get them to boot earlier? or reload them after their failure?

Any ideas or suggestions for launching windows form applications from a network resource? Except for the boss’s obvious “copy files to the local machine”, this idea is not to be liked.

Answer 1

I have no convincing evidence of this, but standard MSFT practice uses memory mapped files. There are many calls to CreateFileMapping () in the rotor. Very effective for read-only files such as assemblies, memory pages should not be backed up by a swap file.

But, it gets into the fan when the Windows memory manager needs paging back, and the file becomes inaccessible. It suits your observation very well. There is no workaround for this, except for your boss, who prefers and acquires more reliable network equipment. MTBF hours are pretty bad.

Answer 2

If you have access to client computers, you can open Administrative Tools and go to the Microsoft.NET Framework Configuration to define a custom set of permissions for your application. For more information, see this article in ID Automation.

In theory, you should be able to use group policy or similar for this change throughout the network, if necessary, but I have not tried it myself.

Another option is to open the security zone settings in Internet Explorer and add the path to the share to the Local Intranet folder: // add the file: // server_name / file_name to the local intranet zone.