Workflow Soluiton

If i run my workflow in debug mode it works correctly, but when I publish it, I get the error below:

System.Exception: Execution Exception ---> System.Exception: exception component created:  ---> LogicBase.Framework.BusinessRuleException: The critical error failed execution on component Pop3 List : -ERR Server Unavailable. 21
 :    at Quiksoft.EasyMail.POP3.POP3.Login(String Account, String Password, AuthMode AuthMode)
   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)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.ExceptionComponentDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunEngine(List`1 executionQueue)

Which App Pool is the project published under?

Which Identity is the App Pool running as?

Pop3 List

Class: LogicBase.Components.Pop3.Pop3ListComponent
Library: LogicBase.Components.Email.dll
Publisher: Symantec Corporation

• https://www.symantec.com/connect/articles/pop3-list
• https://www.symantec.com/connect/content-external/workflow-id_LogicBase.Components.Pop3.Pop3ListComponent/workflow

It is running under it's own app pool and it is running with a domain service account.

-ERR Server Unavailable.

I take it the server is available since it's working in Debug.

The account hasn't locked out you are using in the component?

Alternative, if you can use IMAP instead.

From: SD.Email.Monitor

IMAP4 Get
Class: LogicBase.Components.IMAP4.IMAP4GetComponent
Library: LogicBase.Components.Email.dll
Publisher: Symantec Corporation

The Unavailable: 21 is the main error here... could it be network/firewall related?

The server is up, the service account is not locked.

I could try iMap, but that would involve me reworking the workflow.

It currently works fine in debug mode, so I don't see a reason that I should have to rework this. It's got to be a setting somewhere that is just off.

Any more ideas?

The Debug runs under the account you're logged in as, the App Pool likely runs under the Service Account so there could be permissions issues with that account.

Is the WF Service running as your service account?

You could either Telnet to the server or PortQuery or PortQueryUI to test you can connect to your Email Server.

You coul call Support too.

I did try running the App Pool as my account, I thought it might have been a permissions issue. However, my account failed in the App Pool too.

My WF service is running as the same service account as the App Pool.

Yes, I wanted to exhaust this forum first before I contacted support, usually I can get answers faster here.

Called support and got a solution to the problem.

When you change a project property to a project that has been published before, you have to select "use project value" during the publishing to get it to update on the published version.

Our mail server was updated in the version I was debugging, but the published version still had the old value.

Thank you Tyler with support!

Might be worth moving to Application Properties stored in Process Manager, makes it easier to manage and then you can easily change them for different environments