Good Morning,

it would be important to know the version of Exchange and the OS version it run on.

But my first recommandation for you is to upgrade SIFMSMSE to the latest build 6.0.10.295 via fileconnect.

Before you start your upgrade, uninstall the current build and reboot your machine (It´s not really necessary, as you can install new versions just over the old one, but I think it´s better in your situation to start from the scratch). Do not forget to save (export) your settings, for re-imorting it at the end!

Kind regards,

Rolf

Hi Sathyan,

Once you have 6.0.10 installed, make sure that SMSMSE is using enough threads and scan processes to handle the mail.  Details can be found in the Admin guide or in the following article: Calculating the Number of Scan Processes in Symantec Mail Security for Microsoft Exchange 5.x and 6.x

Thanks and best regards,

Mick

Dear Mick,

Thanks for the info.But we would be needing the below information to convince the customer to upgrade the SMSE version.

1) Is the issue reported,a bug in the existing version 6.0.7.253
2) All these days,this was working fine and suddenly we had this issue twice,once during last week and then second which has occurred now.We would be needing the RCA for this.

We have also logged a case in the support portal.Case # 411-463-923

If possible,can you have someone take ownership of this case immediately and send us the relevant information through mail.

Regards,
Sathyan

Hi, we also observe a similar issue: (6.0.10)
2 exchange 2003 server about 1'000 mailboxes,
previous installed SMSMSE version 5

upgrade was ok, (don't forgot to add the 2 additionnal exclusions)
we also take care during upgrade
https://www-secure.symantec.com/connect/forums/upgrade-mail-security-exchange-6010-or-65-win-server-2003-running-exchange-2003#comment-3875771

and we also take care the VSAPI was 9 (servers are 4 CPU), try reduce to 5, same problem.

What we see to reduce the impact.
As we use SEP11 client to protect the Exchange server, the Vdef are shared, so each SEP update run the update on SMSMSE... With high CPU impact all the same we do not activate the "force rescan" !!!

We force the Vdef only 3h in the morning, to lower the impact. But all the same: Outlook client disconnect, etc... we do not have this problem when installing SMSMSE version 5. we reinstall one of the 2 exchange server, with v5, and all is OK this one. !!!

We have open 2 cases at Symantec.