How to ???

Last post 05-13-2008 1:01 AM by Vince Xu - MSFT. 6 replies.

Sort Posts:

  • How to ???

    05-09-2008, 7:34 AM

    Hi,

        In an interview i was asked
        How can u troubleshoot a website ?

        What is the probable answer ??????


     Thanx in advance

  • Re: How to ???

    05-09-2008, 8:29 AM
    Answer

    Many things in troubleshooting .

    1. If website will down or not opening.

    2. If some bugs generated.

    3. If server crashed.

    4. If spam or virus attaching your website.

    there are hundreds of issue can occur with your website And then you will resolve it issue by issue. 

    Regards.
    mimranshafiq
    .NET Web Developer
    http://www.dotnetclassic.com
  • Re: How to ???

    05-09-2008, 8:48 AM
    • Loading...
    • dinesh_sp
    • Joined on 12-03-2007, 12:41 AM
    • Melbourne
    • Posts 366

     I would Troubleshoot a website through IIS Manager. If its stopped, if it needs a different application pool, it it needs to be redirected to some other site, etc etc.

    I dont think troubleshoot means fixing coding errors though.. 

  • Re: How to ???

    05-09-2008, 9:01 AM

    From coding point of view, I will take help of Trace to find the error 

    -----------
    :) MAdHU
    -----------
  • Re: How to ???

    05-09-2008, 12:45 PM
    • Loading...
    • tracer
    • Joined on 02-08-2008, 12:39 PM
    • Cochin , India
    • Posts 40

    well incase your website s relying heavily on databases, then surely checking concurrency issues, simultaneous access become part of troubleshooting.

    tracer


    tracer

  • Re: How to ???

    05-09-2008, 1:49 PM
    • Loading...
    • 5prime
    • Joined on 01-30-2008, 1:40 PM
    • Posts 21

    There are all kinds of things you can do to troubleshoot a web site. Generally, I end up doing some of these things when troubleshooting web sites:

    Go to the site myself to recreate any error messages - or at least try to get a screenshot from the user getting the error

    Rule out any network related issues by doing pings, nslookups, traceroutes and stuff like that

    Check the Event Viewer on the server to see if there have been any errors associated with the web site

    Check the IIS logs for HTTP errors (logparser is great for this)

    Put traces in the code files for debugging purposes

    Also when I make a web site, I usually include a function that emails me when any errors are generated - so I usually know about any errors before the users inform me of them (assuming that the site is still functional enough to send out an email)

  • Re: How to ???

    05-13-2008, 1:01 AM
    Answer
    ================================================
    Sincerely,
    Vince Xu
    Microsoft Online Community Support

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as
    Answer” if a marked post does not actually answer your question. This can be beneficial to other
    community members reading the thread.
Page 1 of 1 (7 items)