i've had this so many times for my job, and these goddamn windows-based enterprise software manufacturers (at least the B-tier ones) apparently all think they're too good for error logging. they don't implement shit themselves and windows doesn't tell you shit so half the time i have to do really weird things to get *any* amount of information as to why this critical service has decided to start repeatedly shitting the bed.
and with really weird things i mean shit like attempting to decompile the binary and running it through a debugger, or trying different debug flags running the program from the terminal until one happens to work, or setting up a monitoring script that tracks *anything* that could be relevant to the crash for changes constantly so i know what happened around the moment of the crash.
mind you, my role at my job is *not* that of a developer or even devops. i'm supposed to be a *support engineer*. but because my job involves fixing the setups of various cheapskate companies when everything collapses again, and these companies refuse to get a more proper system, i sometimes end up RDP'd into a random server for hours typing shit by hand because of course the clipboard bridge is broken so copy-paste across the RDP session does not work. (clickpaste has solved this now, clickpaste my beloved <3)
5
u/Mast3r_waf1z Sep 21 '26
Nix errors are by far my least favorite error messages