Aris Solman synchronization problem: Error writing data to SAP. ResponseCode: 401

[former_member443387]

Hello,

I am getting this error during synchronization of Aris 9.8.11 with solman 7.2

The error occurs only when I transfer large chunks of data. But when I transfer same processes one by one, I am not getting this error. Has anyone encountered this error? The description of error is not informative, so we don’t know where to look for the problem.

This is from synchronization log:

Error writing data to SAP. Erromessage from the SAP sytsem is: ResponseCode: 401

This is aris client log:

Tue Aug 27 10:33:06 ALMT 2019: node accepted: Operations Test

Tue Aug 27 10:34:20 ALMT 2019: java.lang.NullPointerException

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.serverproxy.solar.ASM72Proxy.convert(ASM72Proxy.java:197)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.serverproxy.solar.ASM72Proxy.synchronize(ASM72Proxy.java:133)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.components.solar.logic.actions.ADownloadProjectAction.download(ADownloadProjectAction.java:166)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.components.solar.logic.actions.ADownloadProjectAction.execute(ADownloadProjectAction.java:74)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.framework.menuAccess.OperationActionManager.execute(OperationActionManager.java:107)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.framework.menuAccess.OperationActionManager.actionPerformed(OperationActionManager.java:76)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.framework.flamingo.api.common.AbstractCommandButton.fireActionPerformed(AbstractCommandButton.java:673)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.framework.flamingo.api.common.AbstractCommandButton$ActionHandler.actionPerformed(AbstractCommandButton.java:626)

Tue Aug 27 10:34:20 ALMT 2019: at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.framework.flamingo.api.common.model.ActionRepeatableButtonModel.setPressed(ActionRepeatableButtonModel.java:126)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.framework.flamingo.internal.ui.common.BasicCommandButtonListener.mouseReleased(BasicCommandButtonListener.java:184)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:289)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:289)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.processMouseEvent(Component.java:6539)

Tue Aug 27 10:34:20 ALMT 2019: at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.processEvent(Component.java:6304)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Container.processEvent(Container.java:2239)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.dispatchEventImpl(Component.java:4889)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Container.dispatchEventImpl(Container.java:2297)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.dispatchEvent(Component.java:4711)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4904)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4535)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4476)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Container.dispatchEventImpl(Container.java:2283)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.dispatchEvent(Component.java:4711)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:760)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue.access$500(EventQueue.java:97)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue$3.run(EventQueue.java:709)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue$3.run(EventQueue.java:703)

Tue Aug 27 10:34:20 ALMT 2019: at java.security.AccessController.doPrivileged(Native Method)

Tue Aug 27 10:34:20 ALMT 2019: at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)

Tue Aug 27 10:34:20 ALMT 2019: at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:84)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue$4.run(EventQueue.java:733)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue$4.run(EventQueue.java:731)

Tue Aug 27 10:34:20 ALMT 2019: at java.security.AccessController.doPrivileged(Native Method)

Tue Aug 27 10:34:20 ALMT 2019: at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue.dispatchEvent(EventQueue.java:730)

Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.container.common.AFocusManager.dispatchEvent(AFocusManager.java:164)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)

Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)

[former_member443387 · Accepted solution]

Thank you for your reply. I just wanted to report that SAP Basis team finally could solve the issue. It was indeed a timeout problem. These two parameters needed to be changed to avoid the problem:

rdisp/plugin_auto_logout
http/security_session_timeout

as well as these ones:

icm/server_port[0] = PROT=HTTP PORT TIMEOUT PROCTIMEOUT

icm/server_port[2] = PROT=HTTPS PORT TIMEOUT PROCTIMEOUT

[tsoyalex]

Hello Daniyar,

The Security Audit Log (SM19/SM20) can be very helpfull to analyze http errors with response code 401. Logon failed messages contain reasons (causes) and methods (auth modes). After finding out the cause you can proceed with log tracing (icm or whatever).

Good luck!

[patelyogesh]

Seems check icm timeout setting including processing timeout

[former_member443387]

Thank you, will ask basis team to check for that and let you know if it helps.

[patelyogesh]

This is seems consuming webservice.

[former_member443387]

Yes, using Solman API

[patelyogesh]

Can you let me know what is the process?

[former_member443387]

screen-shot-2019-08-28-at-220108.jpg

This screenshot is from Aris manual and it describes how it works on general high level. Or do you need more detailed information on how it is configured from solman side?

[patelyogesh]

It this processing in Dialog mode?

-Yogesh

[former_member443387]

No, not dialog mode

[patelyogesh]

Can you make sure it is not timeout issue!

[former_member443387]

That is what we thought too. Our basis team checked for timeouts, and they were all fine. Can you maybe suggest which specific timeouts I should ask them to check? The last one they increased was http and https timeouts, but it made no difference.

It is also confusing that they don't see any error messages in SAP when checking the synchronization user activities.

[patelyogesh]

Hello Daniyar Amanchin

The error message what I see is as below

Error writing data to SAP. Erromessage from the SAP sytsem is: ResponseCode: 401

Can you please check user authorizations?

Thank you

Yogesh

[former_member443387]

Hello, Yogesh Patel!

Yes, we checked that, we even tried assigning SAP_ALL to the user, and that did not help.

It is very interesting that transfering say 3 processes one by one is working fine, but when all three are synchronized at once, we get this error.

Do not know what else we could try.