on 09-25-2009 1:24 AM
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
The issue is resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.