Video Screencast Help

Not able to send Mail from NOM 6.5.6

Created: 14 Jan 2012 | 2 comments

Hi ,

Not able to  send mails from NOM. While scheduling reports in NOM getting below error .

0,51216,146,146,25667,1322707552059,0,65,0:,511:Scheduled email task failed for schedule Test- java.lang.Exception: java.lang.NullPointerException Exception:java.lang.Exception: java.lang.NullPointerException   at vrts.rs.engine.processor.EmailRequestProcessor.processRequest(EmailRequestProcessor.java:356)   at vr
ts.rs.engine.processor.RequestProcessingThread.run(RequestProcessingThread.java:154)   Caused by: java.lang.NullPointerException   at vrts.rs.engine.processor.EmailRequestProcessor.processRequest(EmailRequestProcessor.java:255)   ... 1 more   ,47:vrts.rs.schedule.EmailTaskHandler.launchTheTask,2

Can't find resource for bundle java.util.PropertyResourceBundle, key Unknown exception occured in sending mail.

Comments 2 CommentsJump to latest comment

tom_sprouse's picture

NOM 6.5.6 should have addressed all issues with sending Email / via SMTP.

However, please check the following...

./installpath/<nom_dir>/version.txt     <--- verify the contents and ensure 656 is the current version.

./installpath/<nom_dir>/eeb.info        <---  verify if any EEB's are installed.

----------

Additional items to check:

1) AntiVirus --- some A/V | Security Applications restrict SMTP traffic (port 25) 

2) SMTP Host --- verify the NOM server / IP is allowed to relay SMTP traffic through it

3) Test Connectivity from NOM to the SMTP host via command line:    telnet smtp_host.fqdn 25

 

 

Note: If this post provides you with a solution don't forget to mark the discussion as solved...

 

srvijay's picture

Hi Mark,

 

Thanks for the reply.

Kindly find the deteails

/opt/VRTSnom/version.txt => 6.5.6 is the current Version

/opt/VRTSnom/eeb.info    =>  Not Able to view any sunh files

 

NOM server is allowed to send mail using SMTP Server. Since my NOM Server Sends other mails . previously we were using NOM 6.5 during that time we were able to receive reports from NOM . only post upgragadation facing this issue .

 

Thanks