sending report via email to user via #BI Job Scheduler Agent, which fails at random

Anwar Sadat_Orakl

Hi All,

I am facing another problem in sending reports via email to users using BI Job Scheduler Agent, which fails at random.

Almost 500+ mails needed to be delivered. Some failed by getting the below error message.

[nQSError: 75004] Failed to send HELO command. 4.3.2 The maximum number of concurrent server connections has exceeded a per-source limit, closing transmission channel (abc.adjd.local)  AgentID: /shared/ER Assigned Weekly Email

  ...Trying SMTP Delivery loop again... Sleeping for 3 seconds

Sometime no error.

BalaGuddeti-Oracle

In the earlier post, you have set the Maximum recipients to 100, hence Email server control mechanism is activated to control spam emails. if you expect 500 emails, change the Maximum number of recipients to 500

Gianni Ceresa

4.3.2 The maximum number of concurrent server connections has exceeded a per-source limit, closing transmission channel

This is not an OBIEE/OAS error message, the issue is not here, you are looking in the wrong place....

This is a mail server error message.

You should speak to your mail server administrators giving them that error and explaining what you were (or what the tool was doing on your behalf) when the error appears in the logs.

Do not touch the maximum recipients number, leave it to 0 as Joel said in the other thread: 0 means unlimited. That setting is used more for other reasons, like when you want to avoid somebody setup an agent spamming your entire company sending an agent delivery to 1000+ people, it's a way to limit the freedom of people creating agents based on company's rules.

Your issue is that OBIEE/OAS is sending the emails in a way that is outside the limits of the mail server, not on the OBIEE/OAS side, but on the mail server side.

Speak your mail server administrators, also telling them you don't really have options to slow down the sending process on the OBIEE/OAS side.

Maybe they will ask you to send these emails in batches, and for that you will need some creativity (like using 2 agents running at separate times doing each half the list of emails).