Problems with default user on WDA Application

[Former Member]

Hi All,

I have an WDA application that uses a default user to logon. We've noticed that after some time the application starts fail in some screens, like don't showing some screen components, for instance. After trying some solutions, I've decided to change the user and, for my surprise, the application start working fine.

So, now the problems with the application starts happen again. The first thing I've did was change the user and it works again. I seens like there was a counter or something like that on the user that, after some time, stops working parts of the application.

Does anybody has faced this kind of problem?

Thank's in advance,

Nelson Bertolino

[Former Member · Accepted solution]

Hi ,

It seems to be an authorization issue. You use the same user for which application is not running. try to run it again on portal and then trigger transaction SU53 to check authorization failure log. If you find any dtails of authorization failure, connect with ur basis person to fix it.

Regards

Vishal Kapoor

[Former Member · Accepted solution]

Hi,

We don't use SAP Portal. We're using Webdynpro ABAP running on WAS from ECC 6.0. The default user I've mentioned is put on the the SICF service created by the WDA Application.

I've tried to use SU53 but it didn't show me anything. There is another way of tracing this? The user I'm using (all of then) has SAP ALL profile.

Regards,

Nelson Bertolino