Printable View
All our SQL 7 and 2000 servers here run SQLMail for alerting and notifications (via jobs and DTS packages) and we are increasingly having the issue where MAPI32 goes to 100% CPU utilisation and the server needs rebooting.
We are getting the response from Microsoft that "this happens" - hmmm
Anyone else having this problem come up with a solution or workaround at all?
Regards
Jason
smtp mail.
Had this problem on a Win2K workstation. However it was not in conjunction with SQL mail. The process mapisp32 was consuming up to 100% CPU resouces. Killing that process sorted the problem. The next mail session will start a new instance of Mmapisp32. Which -at least- works around a reboot...
BTW the problems disappeared on my workstation after I had applied SP3 for WIN2K and the latest security patches.