cancel
Showing results for 
Search instead for 
Did you mean: 

ADSUSER is getting locked automatically

Former Member
0 Kudos

Hi Experts,

The Updates are terminated frequently in function module: RV_MESSAGE_UPDATE each time (for all update records) while executing MB1B, MIGO, MB1C etc transaction codes. System ECC6.0 and Windows-SQL server backend.

Error Details: FPRUNX 102: No job started

Finally, as BASIS consultant, it was discovered that ADSUSER was locked, and after unlocking update was going fine.

But, ADSUSER got locked again automatically and it is repeating.

Any suggestion from anybody why it is happening and what is the solution for this?

Also, any other reason for the update error?

Looking forward for reply ASAP. Just unlocking the user everytime constantly.

Please help me AT THE EARLIEST with some work aorund.

Thanks & Regards,

Sujit.

Edited by: Sujit Kumar Banerjee on Sep 25, 2009 2:31 AM

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

The issue is resolved.

Former Member
0 Kudos

Hi Sujit,

we are facing the same problem. Since we've activated GRMG for ADS the ADSUSER frequently get locked.

Could you tell us, where exactly you have checked the password for ADSUSER in VisualAdministrator and did you mean the SolMan-VA or the Backend-VA?

Thanks in advance,

Uwe

Former Member
0 Kudos

Hi Uwe,

You need to check all places where ADSUSER password is maintained. Most probably in the following places.

1. RFC ADS in respective ABAP systems.

2. GRMG in solman.

3. Backend VA in the path Server <x> u2192 Services u2192 Web Services Security-->Web Service Clients u2192 sap.com > tcwdpdfobject u2192 com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document.

Hope it helps.

Thanks,

Siva Kumar

Former Member
0 Kudos

Hi,

Kindly check the status in Visual admin.

Log on to the Visual Administrator

2. On the Cluster tab, choose Server <x> u2192 Services u2192 Security Provider.

3. On the User Management tab, choose Create Group to create a group called ADSCallers, if the group does not exist.

4. Check the status /Chose Create User if the user ADSUser is not available.

Prashant

Former Member
0 Kudos

Hi All,

Thanks everybody for their time. The issue is resolved.

The issue was with CCMSR agent installation/configuration and hence GRMG was activated in solution manager.

The ADSUSER password was not updated in Visual Admin all places and hence, while availibility monitoring for the production server was happening, everytime it was trying with old wrong password and hence ADSUSER was locking.

Changing the ADSUSER password in respective places in VA, the problem was resolved.

It was a good learning infact.

Thanks & Regards,

Sujit.

former_member186775
Contributor
0 Kudos

Hi Sujit,

check the links It might help you

regards,

Manjula.

Former Member
0 Kudos

Hi Manjula,

Thanks for your reply.

We already checked the links. It was not useful unfortunately in this case.

If you have some thing other in mind, please ket me know.

Thanks,

Sujit.

Former Member
0 Kudos

Hi Gurus,

Can anyone help me out on this regard?

Really struggling with this issue since last 12 hours. ADSUSER is still getting locked automatically and updates are failed. It is a SYSTEM user currently.

Could not replicate the user with other one as we dont know the entire impact as it is a major production server.

Please let me know if anyone needs any system configuration information to help me with some workaround for the time being.

Thanks & Regards,

Sujit.

Former Member
0 Kudos

Hi Experts,

One added information with above, ADSUSER user automatically getting locked by user SAPJSF_PRJ.

ADS RFC is also working fine.

Can anyone help me to stop ADSUSER getting locked?

Thanks & Regards,

Sujit.

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

How SAPJSF_PRJ user is locking ADSUSER ?

Thanks

Sunny

Former Member
0 Kudos

Hi Sunny,

The SM21 log is like below:

Time SAP instance Type Nr Clt User Tcode Grp N Text

-


23:56:46 <host>_PRD_20 DIA 008 900 SAPJSF_PRJ US 1 User ADSUSER locked due to incorrect logon

Task...... Process User...... Session Program Cl Problem cl Package

-


07956 Dialog work process No. 008 SAPJSF_PRJ 1 SAPMSSY1 X Miscellaneous SUSR

Any suggestion on this ?

Thanks & Regards,

Sujit.

sunny_pahuja2
Active Contributor
0 Kudos

Hi Sujit,

This is because somewhere you have given wrong password of ADSUSER. You need to find it out.

As a workaround you can create another user as a copy of ADSUSER and use that in place of ADSUSER.

Thanks

Sunny

Former Member
0 Kudos

Thanks for your reply Sunny. It was also thought, but afraid as we do not know the impact as its a most important production server...any other idea...

Is there any way to find where all the ADSUSER is being used?