Give me a lesson in reading IIS log files and interpreting problems. I have a situation where an external call to my server from another server failed. I want to learn what log file(s) to look at and how to find what happened. This is a specific situation, but I want to learn an overview of how to make the best use of log files in troubleshooting.
We can use TeamViewer to look at the actual files on my server.
I will want a document when we are finished outlining the process so I can add to my knowledgebase for future reference.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
Windows Server 2008/IIS