Internet Information Server Transaction Log

Since Connection Point Services relies on WWW and FTP services, the IIS transaction log can be used to monitor service activity. For example, using the WWW transaction log you can determine when query variables were received by Phone Book Service and when data was downloaded to the client. The following table shows sample information the server transaction log can record.

Log information	Sample

Client IP address	138.57.7.27
Returned client information	-
Connect date	5/6/97
Connect time	9:57:47
Service name (multiple services can log to same file)	W3SVC
Server computer name	Hostname
Server IP address (services can support multiple IP addresses)	138.57.7.27
Processing time in milliseconds	2360
Bytes received	205
Bytes sent	1290
Service-specific or protocol-specific status or error code	200
Win32®-specific status or error code	0
Name of the operational service-specific fields	GET
First of three optional service-specific fields (containing query)	/PBServer/PBServer.dll, OSArch=0&OSType=2&LCID=1033&OSVer=4.0.1381&CMVer=6.0.10.0&PBVer=6&PB=ByteComp
Second of three optional service-specific fields	N/A
Third of three optional service-specific fields	N/A

To determine the location of the transaction log files

Click Start, point to Programs, point to Windows NT 4.0 Option Pack, point to Microsoft Internet Information Server, and then click Internet Service Manager.
1. Click the IIS folder to expand the tree, and click the server name.
2. Right-click Default Web Site, and click Properties.
3. Click Properties in the Active log format box. The log file directory is listed. You may need to stop and restart the Default Web Site service to update this log.

The example shown in the previous table appears as follows in the transaction log:

138.57.7.27, -, 5/6/97, 9:57:47, W3SVC, PointSrv, 138.57.7.27, 2360, 205, 129, 200, 0, GET, /pbserver/PBServer.dll, OSArch=0&OSType=2&LCID=1033&OSVer=4.0.1381&CMVer=6.0.10.0 &PBVer=6&PB=ByteComp