EWA Alerts Not able generate

[Former Member]

Hi All

I am not able generate from last week,as i am able to get the Email alert of EWA for 9th March aft that i did not recive any alerts(but there are no changes done ). RFC working fine.

But when I check the authorization in the SM59 it is

Connection test SM1 Trusted

Connection type: R/3 connection

Cancel Name or password is incorrect (repeat logon)

For which user we have to check this? And how to find user??

Please let me know where to check?

Regards

Neni

Edited by: 21101982 on Mar 22, 2010 7:17 AM

[Former Member · Accepted solution]

Hello,

If you go in SM59 and in the RFC in question. Double click in it, then you click on "Logon & Security" tab on the top, you will see the user ID in question on the bottom of the screen.

Now you can go to change mode and modify the user-id/password to make sure it's the correct one. You may also verify in SU01 to ensure tha the correct Roles/Authorizations/password have been associated with this user.

Thanks,

Mark

[Former Member · Accepted solution]

Hi

When i checked in the satellite system-Tcode SDCCN logfile

Maximum number of retries reached ( 0003 )

Error refreshing service definitions from destination SM_DSPCLNT100_BACK

Problem is user SAPEWA is locked,this is user is Diolog use

I am not able to find why SAPEWA use is locked ever time?i had check the logfile but not able to find the root cause.

No one else know abt this user

please let me know the root cause?

Regards,

Neni

[Former Member · Accepted solution]

Hello,

You can go in Su01 and unlock this user in question and try again. I'm thinking perhaps your RFC settings have incorrect password for this user, so whenever this job runs, it locks the user after the 3rd attempt to logon. Confirm the password in SU01 and than on SM59 and try again.

Thanks,

Mark

[Former Member · Accepted solution]

Hi Mark,

I had unlock the user,still i am not geting the EWA.

Time set for EWA is Moday i had done

I have login in satellite ->SDCCN-Edit->StartNow

But i did not get the EWA?

1.Please let me know the solution

2.Not able to find why SAPEWA is geting locked

3.And also in EWA 2 Performance Indicators table is empty

Regards

Neni

Edited by: 21101982 on Apr 7, 2010 1:43 PM

[Former Member · Accepted solution]

Hello,

Have you tried to start an EWA report manually to see if it will get generated? Or are you only doing a refresh session on its own?

Thanks,

Mark

[Former Member · Accepted solution]

Hi Mark,

EWA is working fine.

1.oblem is every week the user SAPEWA is geting locked

Not able to find why the use is geting locked as not 1 else login into the system

2 and also in EWA report " Performance Indicators" table is empty ?

Regards,

Neni

[Former Member]

Hello,

Have you verified that your data is existant in ST03N of your Satellite system? If it is not, please review the note that Ruediger

has provided above to resolve the issue. If the data is missing from the source, in this case ST03N, then EWA will not have any data to populate.

Again, the note number is:

1443908 - ST03N - Weekly workload data can no longer be

Hope this helps you out!

Thanks,

Mark

[Paul_Babier]

Dear Neni,

What kind of user is this? A Dialog user, a Communication user?

It should be defined as a communication user, has this been verified?

Regards,

[Former Member]

Hi Paul Babier ,

The User is Dialog USER.

1.Since last two Early Watch reports data is not being fully captured.As 2 to 3 weeks the back the User status is same but

data is fully captured and every thig is working fine

Data is not captured for Perfomance Indicators and Perfomance Overview

2.SAPEWA User is geting Locked again?

Please let me know the problem.

Regards,

Neni

Edited by: 21101982 on Apr 9, 2010 6:59 AM

[former_member209604]

>

> Data is not captured for Perfomance Indicators and Perfomance Overview

Note 1443908 - ST03N - Weekly workload data can no longer be displayed

Ruediger

[Paul_Babier]

Hello,

Thank you for the information.

The user type should be "Communication" for the reason that type "Dialog" users have password aging and their passwords expire. This can cause locking because the saved password in the RFC settings eventually differs, and when it tried to logon it keep sfailing and locks the account, and then there becomes a large manual effort to update all the passwords in all the RFC definitions to match the new password that was forced to change due to password aging. So SAP recommends that Type Communication users are used for RFC users because the password is not aged, meaning it doesn't expire and cause this very issue.

Regards,

Paul

[Former Member]

Hi

I am able genrate the EWA but user is geting locked every time.

sapewa -->user for EWA type is Dialog

Please let me know if there is any note for this issue.

Error in Traget system (SDDCN)

Maximum number of retries reached ( 0003 )

pdating license data completed from destination SM_XXXCLNT100_BACK [Maintenance Package]

Error refreshing service definitions from destination SM_XXXCLNT100_BACK

Password logon no longer possible - too many failed attempts

> error reading function module interface BDL_DO_SESSION_REFRESH_NEW from SM_XXXCLNT100_BACK

Regards,

Neni

Edited by: 21101982 on Apr 13, 2010 6:41 AM

[Former Member]

Hi,

trusted RFC works for all the users, provided user exist at both ends(source and Target) and authorization objects S_RFC and S_RFCACL added to your user.

I dont think EWA uses trusted RFC. Satellite system uses Back RFC to send info to Solman.

From your post I understand that you are not getting mail.

Probably EWA is generated in system but thre is some problem with SCOT setting or mail server.

go to dswp--> solution monitoring --> Early watch alert and chcek if alerts are generated.

Regards,

Shyam