Problems sending Emails With K2 BlackPearl and MS Exchange

  • 15 February 2010
  • 2 replies
  • 8 views
M
Badge +1

Hi Everyone,


     First of all thanks for reading this.


 


    At Work we are expering a strange problem when sending emails, all of the suden our K2 Email stoped working from our processes, we pick up the message "No connection could be made because the target machine actively refused it" in the K2 Console.


No change was done in our K2 Installation (this has been working for over a year) and acording to our Exchange Admins no change was done on our Email Server.


We can send emails from the K2 server if, by example, we use telnet and SMTP commands, and other systems (outsystem, oracle, etc) can use the mail server.


At the Exchange Server, the firewall is down and we cannot pick up anything relevant on the logs, so we fail to understand this denie.



Does anyone know what can be causing this ?


Does K2 BlackPearl uses SMTP to send emails or does it use any other non standard (microsoft...) protocol to communicate with Exchange.


Can we check anything service (Ms Queue,Kerberos/SPN, MS Distributed Transactions,etc)


User Permissions ??


 


Thanks in Advanced


Miguel




 


 

2 replies

D
Badge +8

K2 makes use of the standard System.Net.Mail namespace and objects to send email (you can have a look at the code behind for the mail events to verify).


The usual causes for these types of failure are permissions and configurations from the Exchange side. By the sounds of it it seems like the K2 Service account's permission on Exchange might have been revoked. What I usually go about to resolve this is to create a simple Windows app using the same code as in the Mail event, log into the server as the K2 Service account and then try to send mail using the Windows app. Key here is that you need to log in as the K2 Service account to ensure that execution happens exactly as it would have when the K2 Server fires off the mail.


This is a useful way to prove to the admins that it isn't really a K2 issue since a standard app has the same issues, rather it is a config/permissions issue. Once you can send a simple test mail using this, chances are K2 will be able to do so as well.

S
Badge +9

This error may rise if McAfee is installed in your machine.


Sol : Go To McAfee -> Access Protection -> Properties -> Uncheck "Prevent mass mailing worms from sending mail" -> OK

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings