Browsing Solutions For Email Agent

  • Does Email Agent support many custom fields when calling APIs?

    How many custom fields can be processed in a single email? Does Email Agent support many custom fields when calling APIs? Email Agent mode: API Invoke keywords: SEC.NET SuperEmailClerk

  • How do I enable logging of windows installer failures?

    Problems can crop up with windows installers. If you do not have permissions or a required subsystem is missing you can get weird errors. When you open a case with us regarding installation issues we will likely ask that you send us an installer log. Below are instructions on how to get a log of the results of an failure to install one of our MSI installers.

  • Error running Email Agent in ApiInvoke mode - Could not load type

    Using Email Agent in apiinvoke mode can produce an error: Could not load type 'FChoice.Foundation.Clarify.Compatibility.Toolkits.FCCS' from assembly 'fcSDK'. keywords: SEC.Net

  • Email Agent Error - Unable to delete credential handle. InvalidHandle

    When running Email Agent on a 64-bit operating system with the POP3 or SMTP authentication type set to NTLM, GSSAPI, or UseStrongest. You may receive this error: ERROR Dovetail.Sec.Core.SecDaemonManager - Could not connect to POP3 server. The error was: Unable to delete credential handle. InvalidHandle This is happening because a library that Email Agent uses for handling email attempts to do Windows authentication (e.g. NTLM) by invoking 32-bit Windows API calls. When Email Agent attempts to authenticate against the email server it is crashing because windows does not allow 32-bit APIs to be called from within a 64-bit program. These 32-bit API calls are allowed when running under WOW64 32-bit emulation. Email Agent is a .Net application which can be run under both 32 and 64-bit environments. It is possible to force .Net applications to run as 32-bit for these types of situations.

  • How to clear a string field using EmailAgent in API invoke mode

    How do I clear a string field using EmailAgent in API invoke mode? KEYWORDS: SEC, SEC.NET, SuperEmailClerk

  • Custom API Invocations crash Email Agent with a BadImageFormatException

    When using Email Agent's API Invoke mode an attempt to invoke a custom API that resides in a .Net 2.0 assembly (e.g. built using Visual Studio 2005 or above) on Email Agent versions prior to 1.1 will result in Email Agent stopping unexpectedly. An administrative email is sent containing exception details regarding the exception type: System.BadImageFormatException with a message saying "The format of the file 'AssemblyName' is invalid." This situation occurs when the Email Agent service is using the .Net 1.1 runtime and you attempt to invoke a custom API written for the .Net 2.0 framework. It is not possible to load .Net 2.0 assemblies in an application running on the .Net 1.1 runtime.

  • Font size of attached emails is too small to read

    If you use Dovetail Email Agent to automatically save incoming emails as a .mht attachment to a case, the font, when opened in Internet Explorer, of the .mht file may appear to be too small to read.

  • Connection refused error when sending an email via SMTP

    The Rulemanager service will not start. The log file indicates a socket error sending email. When Rulemanager starts up, it sends a test email. The log file indicates a connection refused error when talking to the SMTP server. Also tried connecting directly to the mail server using telnet: CmdPrompt>telnet MyMailServer 25 connection refused

  • This service has been marked for deletion

    If you uninstall a Windows service (such as SEC.NET or Rulemanager) , it may still show in the Services console (services.msc) If you try to start it, stop it or uninstall it again (using sc.exe /delete) you get an error: "This service has been marked for deletion".

  • unable to uninstall sec.net

    Unable to uninstall sec.net. Running the uninstaller or running secsetup.bat program indicates that an error has occured and that the program cannot be uninstalled. SEC.NET uses the Windows Installer for installation and un-installation. Although the Windows Installer is designed to be very robust, it is possible for Windows Installer to become damaged if: - Your computer's registry becomes corrupt - You or someone else inadvertantly changes a registry setting used by the Windows Installer, resulting in a problem - The installation of a program that uses Windows Installer is interrupted - There are multiple instances of Setup running simultaneously, or an instance of Setup is "blocked" - etc.