Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. Generic old Troubleshooting tips

Generic old Troubleshooting tips

Scheduled Pinned Locked Moved IT & Infrastructure
helpcsharpsysadmintutorialquestion
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    Sue H
    wrote on last edited by
    #1

    Hey, developer community! I would like to know if anyone knows of good "tips" out there - things you can "always" try to help diagnose problems of various natures. For example: -- Web sites mysteriously shutting down -- Services frozen -- Application permissions For instance, some generic things one might like to do regardless of the technology, is to check: -- Application Event log -- Server Event log -- Application-specific logging directories -- W3C logs Does anyone else have a list of tips and tricks as to some "basic" things to "always" look for? I am a .NET developer, but all of the problems I have troubleshooting come from when it's more of a "server-related" type of problem - but it always seems to start with the developer: Why can't I log in to your application today? Why did the server shut down between X and Y times? Thanks in advance for any tips anyone can provide. Sue :-D

    P 1 Reply Last reply
    0
    • S Sue H

      Hey, developer community! I would like to know if anyone knows of good "tips" out there - things you can "always" try to help diagnose problems of various natures. For example: -- Web sites mysteriously shutting down -- Services frozen -- Application permissions For instance, some generic things one might like to do regardless of the technology, is to check: -- Application Event log -- Server Event log -- Application-specific logging directories -- W3C logs Does anyone else have a list of tips and tricks as to some "basic" things to "always" look for? I am a .NET developer, but all of the problems I have troubleshooting come from when it's more of a "server-related" type of problem - but it always seems to start with the developer: Why can't I log in to your application today? Why did the server shut down between X and Y times? Thanks in advance for any tips anyone can provide. Sue :-D

      P Offline
      P Offline
      Paul Conrad
      wrote on last edited by
      #2

      Alot of these things you mention have a multitude of ways of happening. Only tip I have is to start by looking at the server first...

      "The clue train passed his station without stopping." - John Simmons / outlaw programmer

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups