You receive the following warning during an OWA gathering:
Error occurred while trying to normalize the user account name USERNAME. This account will not be normalized to the DOMAIN\User format.
Time Component HResult EventID
2009-07-30T10:38:48.1158555Z OWA Processor {5173fb8e-92d7-4f24-9f0a-c8fa45c253ac}
Most likely it is not a valid username (i.e. there is no account in the domain with that username). The gathering code takes the username in the IIS log file and tries to normalize it into the DOMAIN\User format. This is done for two reasons:
1. OWA allows you to log on using different username formats (e.g. username, test\username or username@test.com). Different users typically log on using different formats. This looks very messy in the report. By putting all of the usernames into a single format, the report looks a lot cleaner.
2. One of the reports provides the number of logons for each user. In version 1.0 of the report pack, if a user were to log on three times, each time using a different usename format, the report would end up with three different entries (showing the three formats that the user logged on with) with a single logon for each. This is not correct. What is desired is a single entry in the report showing 3 logons. The only way to do this is to normalize the username so that the three different logons with three different usernames becomes three logons with a single user name.
If someone tries to logon, but accidentally types in the wrong username this will result as an entry in the log file for a failed logon. The code that tries to normalize that username will fail to do so because the username is not valid. When this happens Messagestats logs a warning and moves on.
You can ignore this warning.
