Your obstacle is that the target computer is in a remote disconnected network from your own, which makes it useless to use the Visual Studio Remote Debugger tool (if you cannot open the firewall ports on the target machine or set up some kind of VPN).
Try a remote debugger, install the VPN client on your computer and it ( Hamachi is a good example), then the remote debugger should work ( docs on MSDN ).
I would start normal diagnostic measures
- What is special about this machine compared to others that can interact with a normal function.
- Can you replicate the target environment.
- Is stack trace available, does it contain any useful values.
- Can you deploy the version to a target that has additional logging wrapped around a broken function (log all the values โโbefore clicking on the code that might cause the crash).
- Visit the site with the target environment and launch the remote debugger from your network.
- Install Visual Studio (and all source code) on this target machine and debug from there (extreme view).
source share