“The World Wide Web Publishing Service (WWW Service) did not configure logging for site X. The data field contains the error number.”

This warning will show up in your System event logs and you custom IIS logging to a SQL database won’t work. Obviously the message is fairly cryptic, however in a facepalm sort of moment I worked out what wasn’t working.

Two words. Custom Logging.

Although I had enabled the ODBC logging feature for IIS, I hadn’t enabled custom Logging. Once you enable the custom logging feature your SQL DB will start to fill with log entries. I’ve included the full warning message for those of you unsure.

“The World Wide Web Publishing Service (WWW Service) did not configure logging for site X. The data field contains the error number.”

This warning will show up in your System event logs and you custom IIS logging to a SQL database won’t work. Obviously the message is fairly cryptic, however in a facepalm sort of moment I worked out what wasn’t working.

Two words. Custom Logging.

Although I had enabled the ODBC logging feature for IIS, I hadn’t enabled custom Logging. Once you enable the custom logging feature your SQL DB will start to fill with log entries. I’ve included the full warning message for those of you unsure.

<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event>
<System>
<Provider Name=”Microsoft-Windows-IIS-W3SVC Guid=”{05448E22-93DE-4A7A-BBA5-92E27486A8BE} EventSourceName=”W3SVC />
<EventID Qualifiers=”32768>1016</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0×80000000000000</Keywords>
<TimeCreated SystemTime=”2009-04-15T23:55:39.000Z />
<EventRecordID>46323</EventRecordID>
<Correlation />
<Execution ProcessID=”0 ThreadID=”0 />
<Channel>System</Channel>
<Computer>SERVER01</Computer>
<Security />
</System>
- <EventData>
<Data Name=”SiteID>3</Data>
<Binary>57000780</Binary>
</EventData>
</Event>
 
Matt Shadbolt