The IIS logs are written to a folder other than the one MessageStats is trying to query (4225114)

The folder that MessageStats is using to gather the IIS logs from CAS server either does not exist on the CAS server or the logs are not written to that folder

Confirm which folder MessageStats is trying to gather the IIS logs from:

1. Open the console
2. Expand Exchange Organizations | Your Org Name | Servers
3. Right click a CAS server and select Properties
4. Select the IIS Log Folders tab
5. Note the path that MessageStats had determined from WMI as where the IIS logs exist. (click Refresh if the list is empty)

On the CAS server confirm that the path from Step 5 exists and that the IIS logs are written to the same folder. If the folder from Step 5 is not the same folder that the IIS logs are being written to, use wbemtest to confirm that WMI is returning the same information:

1. Log on to the MessageStats server as the MessageStats service account
2. Open a command prompt
3. Type wbemtest and hit enter
4. Click Connect
5. For the namespace enter \\CASServerName\root\MicrosoftIISV2
6. For Impersonation Level select Impersonate
7. For Authentication level select Packet privacy
8. Click Connect
9. Click Query
10. Type Select Name from IISWebVirtualDirSetting
11. Click Apply
12. Look for the entires that represent the Exchange Virtual Directories in IIS. For example:
     - IIsWebVirtualDirSetting.Name='W3SVC/1/ROOT/owa"
     - IIsWebVirtualDirSetting.Name='W3SVC/1/ROOT/Exchange"
13. The number after 'W3SVC/' is the Site ID that the virtual directories belong to. If this is 1, the folder that MessageStats should be trying to gather from would be W3SVC1.

If the Site ID for the virtual directories matches the folder MessageStats is trying to gather from but the IIS logs are written to a different folder, the issue is environmental as MessageStats is using the data that WMI returned. Microsoft should be consulted to determine why IIS is logging to a different folder.