From eScan Wiki
Revision as of 09:46, 19 June 2009 WikiSysop (Talk | contribs) ← Previous diff |
Revision as of 09:47, 19 June 2009 WikiSysop (Talk | contribs) Next diff → |
||
Line 1: | Line 1: | ||
- | |||
{| class="wikitable" border="0" | {| class="wikitable" border="0" | ||
|- | |- | ||
Line 27: | Line 26: | ||
|} | |} | ||
- | Backup failing on Windows 2003 server SP2 with eScan. | + | Backup failing on Windows 2003 server with Service Pack 2 with eScan installed. |
Revision as of 09:47, 19 June 2009
|
General |
Knowledgebase |
Support |
Backup failing on Windows 2003 server with Service Pack 2 with eScan installed.
Solution: Windows 2003 uses the back-ground process of savefs.exe to start the backup task. This process, though excluded for binding from eScan's Transport Service Provider (MWTSP), was causing an issue with the task. This issue was happening because MWTSP will try to mark all socket operations as Over-Lapped sockets. Though this marking shouldn't generally affect any operation, the backup task itself was failing with this setting.
With the new hotfix, whenever the backup task runs, the sockets it creates wont be marked as Over-Lapped sockets.
Furthermore, a setting in MAILSCAN.INI (mailscan.ini file will be in \Program files\eScan folder), [general] section(, ChangeFlags = 1, has also been provided in order to exclude OverLapped sockets settings for all tasks. Default value is 1. Set this to 0 in order to avoid marking all socket operations as Over-Lapped Sockets.
Email us your feedback to solutions@mwti.net