Workflow and ServiceDesk Community

 View Only
  • 1.  SD 7.6 Multiple mailbox monitoring error

    Posted Nov 04, 2015 07:32 AM

    Hi

    I recently implemented the multiple mailbox monitoring processes within SD 7.6.

    Now no emails are being processed and I'm getting this error in the log:

     

    Application Name : SD.Email.Monitor
    Process ID : 6312
    Date :2015/11/04 02:16:20 PM
    Log Level :Error
    Log Category :LogicBase.Components.Default.Logging.CreateLogEntryComponent
    Machine Name : xxxxxxxx
    Message :
    Process Name: Email Monitoring
     
    Model: Exception Handling Model
     
    Retrying the following component:
     
    Email Count:1
    Email From: Not Found
    Email Subject: Not Found
    Email Body: Not Found
     
    Component Name: Get List of POP Messages
     
    Component Class Name: LogicBase.Components.Pop3.Pop3ListComponent
     
    Component ID: a9e6c7fc-3a25-4a27-ba14-a8fa84354ab2
     
    Exception Class Name: Quiksoft.EasyMail.POP3.POP3ConnectionException
     
    Message: Error receiving data from socket.
     
    Stack Trace: Quiksoft.EasyMail.POP3.POP3ConnectionException: Error receiving data from socket.  ---> Quiksoft.EasyMail.Internal.᝔: Error receiving data from socket.
       at Quiksoft.EasyMail.Internal.ត.ᜎ(String& A_0, Int32 A_1)
       --- End of inner exception stack trace ---
       at Quiksoft.EasyMail.POP3.POP3.Connect(String POP3Server, Int32 Port)
       at LogicBase.Components.Pop3.Pop3ListComponent.DoRun(String user, String pwd, String server, Int32 port, Boolean useSSL, IData data)
       at LogicBase.Components.Pop3.Pop3AbstractComponent.Run(IData data)
       at LogicBase.Core.ExecutionEngine.MultiPathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context)
       at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunComponent(TLExecutionContext context, IData data, IOrchestrationComponent comp)

     

    Any help would be appreciated!



  • 2.  RE: SD 7.6 Multiple mailbox monitoring error

    Broadcom Employee
    Posted Nov 04, 2015 12:08 PM

    Did you properly configure the port setting to be used for your e-mail server? The error is being thrown because the attempt to access your e-mail server using POP3 is failing.



  • 3.  RE: SD 7.6 Multiple mailbox monitoring error

    Posted Nov 04, 2015 01:47 PM

    There could be many issues that cause a failure to connect to a mail server.   Is POP3 access enabled for your mail server and for the account you are using?  Double-check the server name, account name, and password.  Are there any firewalls or ACLs that could be restricting POP3 access from your Workflow / SD server?



  • 4.  RE: SD 7.6 Multiple mailbox monitoring error

    Posted Nov 05, 2015 08:31 AM

    I tested the account settings and discovered that the password had expired (it is now set to never expire) I was able to open the mailbox successfully with the settings configured in the system but the error in the log still persists



  • 5.  RE: SD 7.6 Multiple mailbox monitoring error
    Best Answer

    Posted Nov 13, 2015 07:41 AM

    Julia from Symantec kindly assisted me to resolve the problem and these were the steps that he took during a remote session to resolve the problem:

    DIAGNOSTIC STEPS:

    Connection to POP was tested via telnet command.
    Also tested via Get Pop List component by entering mail server credentials directly. 
    Found Get Single Message component was using incorrect variables. 


    CAUSE:

    Incorrect variables on Get Single Message component. It was pulling settings from ProfileProperties instead of CurrentMailbox. 


    SOLUTION/WORKAROUND:

    Fixed the following issues with Multi Email Monitor:
    1. Get Single Message component was the one where it kept failing.
    Email server variables in this component were pulled from Profile Properties instead of CurrentMailbox, had those variables updated.
    2. There were 2 versions of Email Monitor (original ad Multi one) running at the same time. Had original removed from IIS, and backed up its folder from Deploy\Release directory to a different location.