UXM: Scripts are not running because status is CONFIGURED

[timkudla]

Hey community,

I am faced with the problem that two of our UXM scripts no longer run, although the scripts themselves are bug free.

From one hour to the next, execution has stopped even though no change has been made. When trying to trace the execution of the scripts, the warning "[script name] not running because status is CONFIGURED" (see appendix) is displayed again and again.

The errors with the user SM_EXTERN_WS already existed during the successful execution, so I assume that they have no effect.

Firstly, I cannot find any SAP note for this warning (or other solutions), and secondly, I do not know of a corresponding status, let alone could I find it in the error search...

Do any of you know the cause or the corresponding parameter?

Many thanks in advance!

[jan_j_novak · Accepted solution]

Hello Tim,

have you tried stopping, re-configuring and starting the script again?

It seems to me that the scripts are sometimes prone to get stuck during any changes.

Please, let me know.

//Jan

[timkudla · Accepted solution]

Hey Jan,

yes, that's what it all came down to in the end. The problem was the technical user for the connection between agent and SolMan, who regularly locked himself out. So neither config information was transferred in one direction, nor results in the other. After changing the user and several restarts of the client, the problem was solved.

Best regards

Tim

[jan_j_novak · Accepted solution]

Hey Tim,

Glad you have been able to resolve this.

To be completely honest, setting up UxMon or changing/correcting anything comes to me sometimes as more like alchemy then IT work 😄

Have a nice day!

//Jan