bykhansen01-12-201207:23 AM - edited 01-12-201207:26 AM
When you’re dealing with any sort of web-related issue – be it the Web Client, problems with SData, or (in the future) things like SSAA – checking the IIS logs can sometimes be a helpful step. However, they can sometimes be a bit troublesome to read. Here’s how to make the formatting a little easier:
1. Locate the IIS log for the appropriate site
. • By default, this will be located at C:\Windows\System32\Logfiles\W3SVCX (Windows 2003 and IIS 6) or C:\inetpub\logs\LogFiles\W3SVCX (Windows 2008 and IIS 7/7.5)
2. Copy the log file to a workstation with Excel. Log file name syntax by default is u_exYYMMDD.
3. Open the log file and delete the following lines: #Software: Microsoft Internet Information Services 7.0 #Version: 1.0 #Date: 2011-11-16 00:09:56 #Fields: Note: This may be appear multiple times throughout the file. Deleting this allows headers to appear properly in Excel.
4. Save the edited log file.
5. Open Excel.
6. On the Excel File menu, click Open.
7. From the File Types drop-down, select All files (*.*).
8. Browse to and select the edited log file.
9. Click Open.
10. On the Text Import Wizard window, click the Delimited radio button.
11. Click Next.
12. In the Delimiters section, deselect the Tab checkbox.
13. In the Delimiters section, select the Space checkbox.
14. Click Finish.
15. The imported log file should now be separated into columns with appropriate column headers (date, time, s-ip, etc.). The columns we are most interested in for troubleshooting are sc-status and sc- substatus.
16. To easily filter out successful status entries, from the Excel toolbar, click Data.
17. Click Filter.
18. The column headers should now show arrow buttons indicating they are now drop-down menus. Click the arrow button on the sc-status column.
19. In the sc-status filter drop-down, click the Select All checkbox to deselect all entries.
20. In the sc-status filter drop-down, click the entries for any statuses 4XX or 5XX.
An IIS log file can often have entries to multiple websites. You can use the cs-uri-stem column to determine the entries that apply to the site in question. For instance, if you are troubleshooting an issue with the SalesLogix Client, then most often the cs-uri-stem column can be filtered to show only entries beginning with /SLXClient/.
There may also be erroneous errors in the IIS logs. One common error that you’ll see will be for a cs-uri-stem including /favicon.ico with an HTTP status of 404.
Once you’ve located any errors that might apply to your specific issue, then proceed to do a Google search using the cs-status and cs-substatus codes. For instance, if the status is 401 and the substatus is 3, do a search for HTTP 401.3; this will give you the verbiage of the actual message the error code is indicating, and from there you may be able to decipher how this applies to SalesLogix or do further searches within the SalesLogix knowledgebase on the verbal error.
If you have any questions, please don’t hesitate to contact the Support Desk at 1-800-643-6400.