Just thought it would be useful to post this one, it's something I first saw last year and escalated throught EV support and also to Microsoft. This only applies if you're using OL2003 on the EV server
If you check the temp directory on your EV server you may well find 1000's of these exchangeperflog files. You'll need to check the temp folder for the account that runs the EV services (normally in C:/documents and settings/...../local settings/temp) unless you've changed it. I wouldn't say there's major impact but it may have a knock on performance effect because you could end up with 10,000's of these files - it's just not good house keeping and is plain annoying.
These files contain performance information which is useful for troubleshooting OL2003 on a normal client. They're generated because when a temp MAPI profile is created (as with EV) the associated MAPI DLLs will create a perflog file. Normally OL cleans them up when it exits but I'm affraid that EV doesn't do the same so they are just left.
I've attached the Microsoft response at the end of this post but their recomended action doesn't help and the response from Veritas (at the time) was that they're working on it. I still think it's there cause we still have them and it can run into 1000's per day. Deleting them is the only option which you can do with a nice little script schedule to run each day.
The MS response followsACTION:
Running KVS archiving with Outlook 2003 to create temporarily Mapi Profiles
RESULT:
ExchangePerfLog*.dat files are created and not cleaned op in the Temp folder
CAUSE:
The ExchangePerfLog*.dat files are created and used by Outlook 2003 for sending RPC performance data to Exchange. There is one file for each profile + security context. Perf records that are to be sent to the server are staged in and out of this file so that we minimize the amount of data that we keep in memory at any given time.
Basically what happens when you use Enterprise Vault from KVS (Veritas) and the Temp Mapi profile is deleted leaves an orphaned ExchangePerflog_*.dat behind, which is not used anymore as its associated Mapi profile does not exists anymore. (KVS removes the Created Mapi profile when it is ready with archiving with the user's mailbox.
RESOLUTION:
Installing the Exchange System Manager not only puts on the necessary MAPI files, but also installs CDO. So only installing the Exchange System Manager of Exchange 2003 should be enough for KVS. You might want to install Exchange service packs and the latest CDO update in order to get the most recent files.
