If it was me I would firstly see if I could re-create the issue locally
and completely eliminate the network. Its all about building up clues that
will hopefully lead you closer to the solution. Other things that maybe
worth thinking about are:
- 32bit vs 64bit, What was the target for your compilation?
- Is there any funky scripts running on the server?
- Does it behave in the same manner on a different server?
- Maybe try removing the .NET framework from the server and then
- Make sure that there are not any other errors in the event log from
other parts of the system
- Is there any firewall or anti-virus on the server that maybe
interfering with the application
- I would also run a memory tester on the server and possibly also
chkdsk but this is just a general thing to eliminate that wouldn't hurt to
do as a matter of course
- I would even swap out the network lead (extremely unlikely its
- Try putting the application on a different UNC share and see if you
can re-create it from there
Process of elimination is the name of the game, even the most unlikely
candidates shouldn't be overlooked.