Title explains the issue pretty well. When the service is started, it immediately begins using 100% CPU and eats all available memory until service is stopped and process is killed. Haven't been able to find any good reason why this might happen and searching on Google has not yielded much of use.
I'm evaluating a product that utilizes the Exchange Transport Logs to populate reports desired by senior management, if anyone is wondering why I care about this service.
Exchange 2010 SP2 (virtualized on VMware platform)
60 mailboxes
1vCPU
4GB RAM
Any other questions, just ask. Thanks in advance for the help.
I'm evaluating a product that utilizes the Exchange Transport Logs to populate reports desired by senior management, if anyone is wondering why I care about this service.
Exchange 2010 SP2 (virtualized on VMware platform)
60 mailboxes
1vCPU
4GB RAM
Any other questions, just ask. Thanks in advance for the help.