Simple Trouble Shooting Application Now Fixes Everything

September 12, 2008

With Joe Cooney's help, we've constructed a simple checklist for trouble-shooting regular problems.

Have you got any further items you regularly find yourself checking off?

Please add more!

check the event log google it reboot run iisreset empty the recycle bin hit ctrl+break kill the aspnet worker process clear temporary internet files touch the config file degauss the monitor remove everything from the startup folder "get latest" and rebuild login as admin run ipconfig /renew check if capslock is on. run a virus scan download the latest CTP disable and then re-enable the network interface restart services (some/most/all) change your password unplug your router, and leave it unplugged for 10 seconds before plugging it back in clear your cookies add current site to your trusted zone disable javascript try to ping the server press 'clean solution' from the context menu in the solution explorer repair the installation run large magnets over all hard drives check the network cable defrag the hard drive try it in a different browser run a spyware scan minimize all windows and check for a modal dialog ensure configuration is correct see what has changed recently run process monitor run chkdsk /v revert all checkins from anyone named 'Gazza' run the windows update service remove and then recreate all Bluetooth partnerships do a hardware reset on your mobile device decompile + monkey punch + duck slap + donkey whack what would jesus do? look for suitable workarounds re-calibrate your Geiger counter check for packet storms best to rule out toxicological contamination early on describe the problem in terms even a child can understand apply duct tape increase the timeout duration increase the maximum threadpool size write to your local minister or government representative try using the Microsoft Online Crash Analysis to submit your crash dump bucket-id disable the customer experience improvement program eat liver of sacred monkey import the decryption certificate to the local client certificate store ensure sql server is setup for mixed mode authentication bypass proxy server for local addresses check the hosts file and the routing tables use filemon to locate any other log files being accessed check the bios update the device drivers for all peripherals attach a debugger, get a memory dump, look at it in a hex reader and post it to a forum cleanse all user inputs put a try catch around it replace the batteries in your wireless mouse and keyboard recompile all dll's uninstall the old version, re- install the new version, apply hot fixes patches and upgrades remove the case from your computer, and aim a fan at it check that you haven't been blacklisted run diagnostic checks on surge protection units add an index remove an index recalculate indexes ensure ftp uses passive mode recalculate statistics reboot in safe mode check kerberos delegation review query plan if 'automatically detect settings' is checked/unchecked, then uncheck/check it kill rogue processes in task manager run memtest.exe boot from your emergency repair disks follow standard knoppix data recovery procedures tweak-UI uninstall adobe pdf reader insert "Debug.WriteLine("up to line 53");" where appropriate set tracelevel to verbose flush buffers % truss -t \!all -t open a.out use cdb or windbg. add in SOS for clr issues. field test any lightning protection devices use a temperature gauge on all hardware components, and compare against safe operating limits from manufacturer run it inside a VM check the DPI. search the knowledge base enable javascript debugging turn off friendly http error messages in IE set the current culture to en-US attach a multi-meter roll back to your most recent backup check for GC pressure empty the MSI cache temporarily allow popups look in your spam folder recompile. wait. recompile. turn off windows firewall run caspol and give everything full trust put yourself in the shoes of the program itself. if you were the program, what would you do? ask hanselman try wireshark. failing that, try fiddler. what does tracert show? check the blueprints and read over the uml. implement the retry pattern. rtfm delete the bios attach anti-static wrist strap on every appendage sit inside a faraday cage insert "alert('here');" where appropriate overwrite every byte in memory the standard five times as pre-scribed by nsa guidelines reinstall the operating system from the original media provided by the supplier add a lock statement blame Irwin the intern blame the guy who left last week blame the ESL guy blame DNS add a sleep statement apply a fudge factor. run a spell checker over your code light some candles. sacrifice chicken. set all DWORD's to 0 in the registry. Then delete the registry drop all databases. unregister and re-register all dlls reboot 3 times drink own urine run prime95 overnight recompile the kernel do the packets hop subdomains, and if so does NAS require a NAS forwarding service -- how about VLAN? track down the original programmers who wrote the system, apply percussive trauma therapy. uninstall java underclock it ignore it post a request for comment on theDailyWTF ask for correlating evidence that the problem even exists sharpen your wooden stakes before proceeding any further melt silver crucifixes onto tips of all bullets fill your water bottle with holy water call tech support check when daylight savings begins simmer ground rhino horn on a bed of whale pancreas plan and enact your fire evacuation plan bathe in holy water increase dosage on all medications. check for interactions. bury heart of an ox at midnight under crossroads on fullmoon clean up your desk check that pump's suction pipe is elevated above bottom of pond. (Float the inlet 18 to 24 inches below the water surface) wear shoes with six inch cork soles wear raincoat, goggles, breathing apparatus climb into an anti static bag always use a condom check pressure reading on gauges number 1 and 2 run it through an oscilloscope check your immunization schedule is up to date check for seismic/tectonic activity, solar flares, tsunami, meteor showers. go and get a coffee. come back and look at it with a fresh set of eyes.

My book "Choose Your First Product" is available now.

It gives you 4 easy steps to find and validate a humble product idea.

Learn more.