Microsoft .NET Application Crashes Over Network - Part 2

Here is a second way to set the security permissions of a .NET program file that will work locally but not over the network. Once again, if the program works locally but not over the network there is a good chance it has something to do with Windows security. After the release of Windows XP, Microsoft has really tightened up on there application security and sometimes it is more of a headache than it is worth.

Now, you may have something programmed incorrectly like a path to a database or something. But before pulling your hair out trying to figure out what you did wrong in the programming one thing you may want to check first is the security policy of the .NET framework. Without the correct permissions, .NET applications may give you a very hard time when running over the network.

Here is Part 2 of the article. Click here for Part 1 of the article

Here is how to check it:
1. Go to "Start" -> "Settings" -> "Control Panel" -> "Administrative Tools"

2. Next Double-Click on ".NET Framework Wizard x.x" where x is the version #



2. A screen like the following will display. From here you want to click on "Trust an Assembly"



3. A wizard screen will display asking you if you would like to make a change to the computer or user. From here, you select "Make changes to this computer." and click "Next". This will bring you to the following screen:



4. From here, you want to browse for the application file (EXE File) over the network that is giving you problems, and then choose "Next"



5. Make sure you change this security setting on the server and all workstations that you plan on using the application. Move the scroll bar all the way to the top to full trust.



Finally click "Next" ant then "Finish"

Hopefully this fixed the problem! If not and you were unable to complete these steps or some of these options were grayed out, please refer to Microsoft .NET Application Crashes Over Network - Part 3 to circumvent these user security privileges

This type of problem can be found on Windows XP, Windows Vista, Windows 7 or Windows 2003, Windows 2008 Server (32 or 64 bit versions).