cancel
Showing results for 
Search instead for 
Did you mean: 

RA&R 5.3 - Error when mitigating a user

Former Member
0 Kudos

Good day.

I am in the process of testing Mitigation Controls and Mitigating a test user. On the Mitigation tab > Create Mitigated User... I successfull maintained all the relevant info. When I click save I receive the following error -

Error:Sending failed; nested exception is: javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25; nested exception is: java.net.ConnectException: Connection refused: connect.

Has anybody received this error and resolved it? Any thoughts & suggestions are welcome.

Regards,

Michael Hannie

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

I found SAP Note 1288865 - Error in sending the mail while maintaining the Mitigation. I am busy reviewing it.

Former Member
0 Kudos

The SAP Note did not work. We are still receiving the slightly different version of the error message-

Error:Sending failed; nested exception is: javax.mail.MessagingException: Unknown SMTP host: GRC.AccessControATbcx.co.za; nested exception is: java.net.UnknownHostException: GRC.AccessControATbcx.co.za

achristian17
Participant
0 Kudos

Hi Michael,

Based on the error, it seems like the system couldn't recognize your email server. So check your exchange(email) server and add the right value and give a try. Also remember to add mitigation owner/controller with right email ID. Hope this could help you.

Rgds,

Asok

Former Member
0 Kudos

Good day Asok.

Thank you for the reply - Please advise where I need to maintain the email server value? We have done so in the Visual Admin and the UME.

What else are we missing?

Former Member
0 Kudos

Two possibilities

1) Either your SMTP or Exchange Mail Server is not configured or you do not have access to port 25, this you can check with the admin ot IT department

2) You have not configured SMTP E-mail service settings in CUP and CUP web service for workflows not configured in RAR

First configure CUP then RAR

Procedure: CUP

1. On the Configuration tab, navigate to Workflow > SMTP Server. The SMTP Server screen appears.

2. In the Email Server Name field, enter the name of the SMTP server that Compliant User Provisioning uses to transmit messages.

3. Click Save

Also note that the emails are not sent automatically. To send the emails, run the Email Dispatcher as a

background job

Procedure: RAR

You need to configure AEWFRequestSubmissionService_5_2 web service in CC>configuration tab> workflow and it may be something like this [http://mysystem:50200/AEWFRequestSubmissionService_5_2/Config1?wsdl&mode=sap_wsdl&style=document|http://mysystem:50200/AEWFRequestSubmissionService_5_2/Config1?wsdl&mode=sap_wsdl&style=document]

If you have already configured the above mentioned things then the problem seems to be with SMTP service itself. Let me know if it doesn't solve the problem.

Best Regards,

Amol Bharti

amudee.com

Former Member
0 Kudos

Good day Amol.

Thank you for you suggestions, but unfortunately it did not solve or issue. I checked all the settings mentioned and I can positively confirm that the settings are correct.

Our new error message is as follows -

Error:Sending failed; nested exception is: javax.mail.MessagingException: Could not connect to SMTP host:exmid07.africa.enterprise.root, port: 25

Any other suggestions?

Regards,

Michael Hannie

Edited by: Michael Hannie on Jan 20, 2009 11:19 AM

Former Member
0 Kudos

Give a try to netstat -an to check if the port no. 25 is blocked by the firewall or not.

You may also try telnet exmid07.africa.enterprise.root 25 i hope i typed your host name correctly.

First confirm the port, then only we can think of something else.

Regards, Amol Bharti

Former Member
0 Kudos

Good day Amol.

Below is the feedback from netstat -an

C:\Documents and Settings\Michael Hannie>netstat -an

Active Connections

Proto Local Address Foreign Address State

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING

TCP 0.0.0.0:990 0.0.0.0:0 LISTENING

TCP 0.0.0.0:51493 0.0.0.0:0 LISTENING

TCP 127.0.0.1:1032 0.0.0.0:0 LISTENING

TCP 127.0.0.1:1032 127.0.0.1:3583 TIME_WAIT

TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING

TCP 127.0.0.1:5152 127.0.0.1:3117 CLOSE_WAIT

TCP 127.0.0.1:5679 0.0.0.0:0 LISTENING

TCP 127.0.0.1:7438 0.0.0.0:0 LISTENING

TCP 172.21.10.175:139 0.0.0.0:0 LISTENING

TCP 172.21.10.175:3209 172.21.31.143:1026 ESTABLISHED

TCP 172.21.10.175:3223 172.21.31.135:1245 ESTABLISHED

TCP 172.21.10.175:3305 172.21.31.149:44847 ESTABLISHED

TCP 172.21.10.175:3594 196.10.24.136:80 TIME_WAIT

TCP 172.21.10.175:3595 196.10.24.136:80 ESTABLISHED

TCP 172.21.10.175:3598 196.10.24.136:80 TIME_WAIT

TCP 172.21.10.175:3607 216.12.142.205:443 SYN_SENT

UDP 0.0.0.0:445 :

UDP 0.0.0.0:3212 :

UDP 0.0.0.0:51493 :

UDP 127.0.0.1:123 :

UDP 127.0.0.1:1057 :

UDP 127.0.0.1:1900 :

UDP 127.0.0.1:2682 :

UDP 172.21.10.175:123 :

UDP 172.21.10.175:137 :

UDP 172.21.10.175:138 :

UDP 172.21.10.175:1900 :

The new error message that I have when I create a mitigate a user on RA&R 5.3 and click save is -

Path not found

I think I am close to a resolution.

Regards,

Michael Hannie

Former Member
0 Kudos

Good day Amol.

Below is the system log from RA&R -

2009/01/20 03:38:18 com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://XGPMID01:50000/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=E:\usr\sap\XGP\...

2009/01/20 03:38:19 com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://XGPMID01:50000/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=E:\usr\sap\XGP\...

2009/01/20 03:38:20 com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://XGPMID01:50000/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=E:\usr\sap\XGP\...

2009/01/20 03:38:21 com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://XGPMID01:50000/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=E:\usr\sap\XGP\...

2009/01/20 03:38:22 com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://XGPMID01:50000/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=E:\usr\sap\XGP\...

2009/01/20 03:38:23 com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://XGPMID01:50000/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=E:\usr\sap\XGP\...

2009/01/20 03:38:24 com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://XGPMID01:50000/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=E:\usr\sap\XGP\...

2009/01/20 03:38:24 com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: WS Analysis Daemon ID E:\usr\sap\XGP\DVEBMGS00\j2ee\cluster\server0\. Thread ID 6 started

2009/01/20 03:38:24 com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: WS Analysis Daemon ID E:\usr\sap\XGP\DVEBMGS00\j2ee\cluster\server0\. Thread ID 5 started

2009/01/20 03:38:24 com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: WS Analysis Daemon ID E:\usr\sap\XGP\DVEBMGS00\j2ee\cluster\server0\. Thread ID 4 started

2009/01/20 03:38:24 com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID E:\usr\sap\XGP\DVEBMGS00\j2ee\cluster\server0\. Thread ID 1 started

2009/01/20 03:38:24 com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: WS Analysis Daemon ID E:\usr\sap\XGP\DVEBMGS00\j2ee\cluster\server0\. Thread ID 3 started

2009/01/20 03:38:24 com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID E:\usr\sap\XGP\DVEBMGS00\j2ee\cluster\server0\. Thread ID 2 started

2009/01/20 03:38:24 com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID E:\usr\sap\XGP\DVEBMGS00\j2ee\cluster\server0\. Thread ID 0 started

2009/01/20 03:38:25 com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://XGPMID01:50000/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=E:\usr\sap\XGP\...

2009/01/20 03:38:25 com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: WS Analysis Daemon ID E:\usr\sap\XGP\DVEBMGS00\j2ee\cluster\server0\. Thread ID 7 started

2009/01/20 03:41:45 com.virsa.cc.workflow.bo.WorkflowBO submit

INFO: END POOINT URL: http://xgpmid01:50000/AEWFRequestSubmissionService_5_2/Config1?wsdl&style=document

2009/01/20 03:41:45 com.virsa.cc.workflow.bo.WorkflowBO submit

INFO: before submit:

2009/01/20 03:41:45 com.virsa.cc.workflow.bo.WorkflowBO submit

INFO: wftype: MITIOBJ reqid: GRCUSER

2009/01/20 03:41:45 com.virsa.cc.rulearchitect.dao.dto.MitObjDTO getObjContext

FINEST: validfrom: 2009-01-20 validto: 2010-01-20

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: MITREFNO

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MOMITREFNO

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: B001

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: RISKID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MORISKID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: B001

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: LANG

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: LANG

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: EN

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: MONITORID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MONITORID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: BENGR

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: Integer

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: STATUS

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MOSTATUS

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: 0

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: DATE

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: VALIDFROM

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: VALIDFROM

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: 01/20/2009

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: DATE

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: VALIDTO

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: VALIDTO

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: 01/20/2010

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: BU ID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: BUID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: null

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: Approver ID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MOAPPROVERID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: null

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: OBJTYPE

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: OBJTYPE

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: U

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: OBJID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: OBJID

2009/01/20 03:41:45 com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: MICHAELTE

2009/01/20 03:41:46 com.virsa.cc.workflow.bo.WorkflowBO submit

INFO: Return code: 2013 Message: com.virsa.ae.workflow.NoPathFoundException: Initiator doesnt exist for the the request attributes : com.virsa.ae.workflow.NoInitiatorFoundException: No initiator found for attributes : {BUID=, MONITORID=BENGR, LANG=EN, OBJID=MICHAELTE, Priority=MO_HIGH, Request Type=MITIOBJC, VALIDFROM=01/20/2009, MOMITREFNO=B001, VALIDTO=01/20/2010, MOAPPROVERID=, OBJTYPE=U, MORISKID=B001, MOSTATUS=0} workflow id: null Status: null

2009/01/20 03:41:46 com.virsa.cc.workflow.bo.WorkflowBO submit

WARNING: 2013: null

Former Member
0 Kudos

I managed to successfully resolve the issue. The resolution, was simple - Create Mitigation Object in addition to the Create Mitigation Control.

Regards,

M Hannie