Skip to main content

Hello everyone, I have a very particular problem.

We have a large number of bots deployed in production that use the same SAP user, and these bots work perfectly. Only ONE particular bot uses a different user due to business process reasons. This bot was working correctly and recently started failing in the following strange way.

It happens during the connect action of SAP. The bot logs in perfectly, but for some reason, it throws the following error: 

I have searched the entire community forum and there is no information about it.

Our team is lost.

The SAP version is compatible with the package (we have already checked the documentation) and we have tested it in several versions just in case.

Could someone help us?

Thank you

Have you checked credentials in sap:connect step?


I have the same problem - were you able to solve it? Any insights would be super valuable. Please and thank you!! ​@leandro.castello 


@domerentnest can you show the error line in your code, and also the screenshot of the error?


@Semih 3318 Yes, here it is.

This is line 20, where the bot is connecting to SAP. This setup works for all my automations that use different boxes - it just breaks with this one.

 

And this is the error I got:

 

Thank you!


Nos contactamos con el administrador de SAP y nos ayudó a validar, se dio cuenta de que este parámetro sapgui/user_scripting_per_user estaba activado y nos ayudó a desactivarlo, de esa manera ya pudimos acceder a SAP sin problemas.

 

Espero les ayude.

 

Saludos!


Hi ​@JesusReuFlores,

Keep comments in english language would help more people I guess. 😊

 

Thanks 

Cheers

Marc


Nos contactamos con el administrador de SAP y nos ayudó a validar, se dio cuenta de que este parámetro sapgui/user_scripting_per_user estaba activado y nos ayudó a desactivarlo, de esa manera ya pudimos acceder a SAP sin problemas.

 

Espero les ayude.

 

Saludos!

Here’s the English translation of the above comment:
“We contacted the SAP administrator and he helped us validate, he noticed that this parameter sapgui/user_scripting_per_user was activated and helped us disable it, so we could access SAP without problems.

I hope it helps.

Regards!”

Hope this solution helps the OP!


@domerentnest if any of these answers help you, please mark them as best answer!


Reply