cancel
Showing results for 
Search instead for 
Did you mean: 

Java Add-In installation ADS_AGENT fails

Former Member
0 Kudos

Hi all,

I'm installing a Java Add-in on our Productive machine. Everything seems fine, but at the step Configure Adobe Document Services installation fails with the following error:

Incorrect password for user account ADS_AGENT

In usercheck.log:

Jul 12, 2007 1:37:57 AM Info: User management tool (com.sap.security.tools.UserCheck) called for action "checkCreate"

Jul 12, 2007 1:37:57 AM Info: Connected to backend system EFT client 050 as user DDIC

Jul 12, 2007 1:37:57 AM Info: Called for user ADS_AGENT

Jul 12, 2007 1:37:57 AM Info: User ADS_AGENT exists

Jul 12, 2007 1:37:57 AM Error: Exception during execution of the operation

[EXCEPTION]

com.sap.security.tools.UserCheck$UserLogonException: Incorrect password for user account ADS_AGENT (USER_OR_PASSWORD_INCORRECT)

at com.sap.security.tools.UserCheck.checkUser(UserCheck.java:833)

at com.sap.security.tools.UserCheck.main(UserCheck.java:268)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Jul 12, 2007 1:37:57 AM Info: Leaving with return code 2

We are using CUA. I'm sure I've entered the correct password during install. This is the second time this error occurs. I'm able to log on to the system using SAPGUI and the password provided.

Any help would be greatly appreciated.

Casper

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Casper,

Passwords can get tricky during upgrade and I have had bad experiences. Try to disable login/* parameters while upgrading and check if it works.

The procedure I followed was to take the client out of CUA, complete the upgrade and then pull user master data back into CUA.

Hope this helps.

Regards,

Nisch

Former Member
0 Kudos

Thanks for your reply Nisch.

Disabling login parameters is not an option for me, because evertyhing is running fine right now and I don't want to start over the installation. The client I am using is also the master system for CUA, so that doesn't seem a good idea...

Former Member
0 Kudos

Dear fellow forum members,

For future reference:

After a very very long time we received advise from SAP to perform actions we already suggested.....

We have ´hacked´ the keydb.xml file. We must say that SAP gave good detailed advise on which entries to change:

1#. Log on to ABAP and check what password was set for user "ADS_AGENT"

2#. Go to:

/tmp/sapinst_instdir/NW04S/LM/AS-JAVA/ADDIN/ADA/CENTRAL/CI/

1. Save a backup of "keydb.xml" first.

2. Find the following lines at the keydb.xml:

This solved the problem for our customer, so this question can be marked as answered by Casper (my colleague). We hope that SAP will launch a patch to solve this problem, as it has cost us a lot of time and we can imagine that other consultants are facing the same issues, as this seems to be a hashing mechanism that does not perform/work correctly.

Best regards,

Jan Laros