Alert Generation job gets ERROR in GRC 5.3 patch 12,but Alerts can be displayed from GRC RAR

[Former Member]

Hi,

We are using GRC 5.3 patch 12.

I schedule background job for Alert Generation - Alert Notification for Some Conflicting Actions(FS40,FS41,FS45) & Critical Action(F319).

I noticed that the job is running daily wise but its status is ERROR,even I tried in foreground also,same happens.

No mail triggered to the Risk Owners.

But when I checked in RAR Alert Tab,the Alerts are showing with some values with the message in the top of the page "Last run Date : - - Actual last run of Alert Generation Background Job - - ".

But the most interesting thing is that the Alert Log file in the GRC server is showing as size "0" which i maintain as the Alert log file name in the configuration of RAR.

I already checked :

1.Risks description are maintained or not.

2.Risk Owner ID and mail ID are maintained in the RAR or not.

3.CUP-Configuration-Workflow-SMTP Server is maintained and other normal mails(approval,rejection,waiting for approval etc.) are going to the user & approver,evidenced SMTP is working fine.

4.Alert Log file name and Location as maintained as "D:\usr\sap\Alerts\Alert_Log.txt" and physically the file is exist in the GRC server with size "0".But the file is exist.

Can anyone let me know another point,I have seen in some other post they suggest to check below settings also:

Visual Admin- Server(n) - Services-Java Mail Client

From where I can go and check it?I am unable to find this point from the system.Please suggest me step by step.But mails are going to the user.

Please let me know if anything I have to check,that I have missed.Below find the Log file of the job:

Thanks in advance.

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob

FINEST: Analysis Daemon started background Job ID:86 (Daemon ID [1890251]D:\usr\sap\GP2\JC00\j2ee\cluster\server1\. Thread ID 2)

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob

INFO: -----------------------Scheduling Job =>86---------------------------------------------------------------

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.bg.BgJob run

INFO: --- Starting Job ID:86 (GENERATE_ALERT) - Alert Generation RP2 daily 26 July 2012

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.bg.BgJob setStatus

INFO: Job ID: 86 Status: Running

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory

FINEST: --- @@@@@@@@@@@ Updating the Job History ----1@@Msg is Alert Generation RP2 daily 26 July 2012 started :threadid: 2

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert

INFO: ----------- Background Job History: job id=86, status=1, message=Alert Generation RP2 daily 26 July 2012 started :threadid: 2

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.bg.BgJob alertGen

INFO: @@@ Alert Generation Started @@@

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.bg.BgJob alertGen

INFO: @@@ Conflict Risk Input has 1 records @@@

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.bg.BgJob alertGen

INFO: @@@ Critical Risk Input has 1 records @@@

Aug 6, 2012 6:00:00 PM com.virsa.cc.xsys.bg.BgJob alertGen

INFO: @@@ Mitigation Monitor Control Input has 1 records @@@

Aug 6, 2012 6:00:00 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate

INFO:  @@@@@ Backend Access Interface execution has been started @@@@@

Aug 6, 2012 6:00:00 PM com.virsa.cc.common.util.ExceptionUtil logError

SEVERE: null

java.lang.NullPointerException

          at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IStatRecInputElement.wdGetObject(IPublicBackendAccessInterface.java)

          at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)

          at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)

          at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)

          at com.virsa.cc.comp.BackendAccessInterface.get_TcodeLog_Rec(BackendAccessInterface.java:2800)

          at com.virsa.cc.comp.BackendAccessInterface.alertGenerate(BackendAccessInterface.java:1940)

          at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.alertGenerate(InternalBackendAccessInterface.java:4355)

          at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.alertGenerate(InternalBackendAccessInterface.java:4824)

          at com.virsa.cc.xsys.bg.BgJob.alertGen(BgJob.java:1659)

          at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:690)

          at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:362)

          at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:287)

          at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:84)

          at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)

          at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)

          at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)

          at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)

          at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)

          at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)

          at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)

          at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

          at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

          at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)

          at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)

          at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)

          at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)

          at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

          at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

          at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

          at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

          at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

          at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

          at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

          at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

          at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

          at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

          at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

          at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

          at java.security.AccessController.doPrivileged(Native Method)

          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Aug 6, 2012 6:00:02 PM com.virsa.cc.xsys.webservices.workflow.Workflow execWFExitService

FINEST: workflow status: 1

Aug 6, 2012 6:00:02 PM com.virsa.cc.xsys.webservices.workflow.Workflow execWFExitService

FINEST: Working on WFID: 24 Type MITIOBJ

Aug 6, 2012 6:00:02 PM com.virsa.cc.common.message.util.MessagingHelper getMessage

[Former Member · Accepted solution]

Hi Surjit,

You can also ref SAP Note

#1562775: java.lang.NullPointerException in the RAR logs

Regards

Shaily

[Former Member]

Thanks to both of you for your advice...it works!thnx again..!

But still no data are saved in Alert Log file...still showing as size 0,but log says that it is saving the data to the file.Below find the log:

Aug 7, 2012 3:05:31 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate

INFO:  ------ No of Records Inserted in ALTCDLOG =>238 For System =>RP2 ----------

Aug 7, 2012 3:05:32 PM com.virsa.cc.xsys.util.RuleLoader getActRuleMatrix

N:B:Complete Log is attached with this post.

But a new ERROR came, now it showing:

"javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25;"

for that we have discussed with our Networking & Server Maintenance Team they suggest to open the port/register the GRC server in the SMTP server.we are working on that,let you know what happened!But still now after approval how the auto notification mails are going to user or next approver I does not know!

I have another query,what is the importance of maintaining the FTP Site Location,ID,password in the RAR -> Configuration -> Miscellaneous.

Thanks in advance!

Scheduling Job 133.txt.zip

[Former Member]

Hi Surajit,

Please refer to the SAP note 1727794 - Error sending notification in Alert Generation job.

I hope it helps to resolve your issue.

Regards,

Yukti