We have encountered various MFBSI errors: 209 211 228. We have had performance issues, system slows down, transactions stop responding, jobs are running very slow and are stuck in the JES Input queue, and jobs are taking more time to send a spool file to the printer using the printer exit module.
After examining log and diagnostic files from different customers and hearing back from their IT departments, we have found a variety of problems pointing back to the Symantec Endpoint Protection (SEP) antivirus software. There may be other antivirus software also causing such errors but at this time since it is very popular, our reports were for Symantec Endpoint Protection. Customers have given us the following descriptions and steps they took in trying to isolate the problems.
After disabling our Symantec Endpoint Protection (SEP) antivirus software, the intermittent but frequent Micro Focus related problems we were experiencing for many months seem to have disappeared. SEP does cause problems for us on non-Micro Focus servers but it also gives our Wintel team grief at times. SEP is installed and is doing its job on over 500 of our servers. SEP was installed on our production Micro Focus ES server before we went live last year. We ran for just over six months and then we started experiencing various MFBSI errors at different times: '209 Job submission failed', '211 Job Ended' and '228 Server crashed/killed when job was running'. We also saw communications errors in our Log.Html file. They were Windows socket errors: 'CCITC32-0015E A CCITCP transport failure has occurred. (CCI 15, Ext 10054) Conversation closed by client or failed due to broken network connection' and 'CCITC32-0015E A CCITCP transport failure has occurred. (CCI 15, Ext 10053) Conversation closed by client or failed due to broken network connection'. All of these errors pointed to timeouts and communication failures. We also experienced what many users perceived to be 'system hangs'. We now believe and have believed for some time that there was a common thread responsible for the problems just described. It is our feeling that this common thread is some sort of communication problem that caused the 209 timeouts and also prevented new work from entering the system via web services (i.e. the perceived 'hang' problem). When we checked the Microsoft event viewer, we would see events for SEP but they very often did not match up with our Micro Focus related errors. The events we did see did not lead us to believe SEP was the culprit as most of the events that SEP logged seemed to be quite innocuous (e.g., a simple signature file download). It seems that many times SEP would perform some task like a product update download but because nothing was 'updated', SEP did not log an event. After we removed Symantec Endpoint Protection from all of our Micro Focus ED and ES servers and from our SQL servers that Micro Focus communicates with, it seems that disabling SEP has caused our problems to disappear and it has now been the better part of two weeks since we have seen any MFBSI 209 errors or 'hangs'.
#EnterpriseDeveloper
#MFDS
