solman_setup initial configuration - No execute authority

I am performing the initial configuration step of SOLMAN_SETUP, when I receive the error below.

Error: E 002 No execute authority

Step: Get ABAP System Info

This occurs when I click the "Start J2EE Configuration" button on the J2ee Configuration screen(Step 3). This opens another browser window, where I enter the solman_admin user that was created in an earlier step. On the first screen, I enter the

Solution Manager Administrator(solman_admin), J2EE Administrator(j2ee_admin) user/password, as well as the password for the Technical Users (SLDDSUSER, etc).

The script then starts and stops on step 5 of 118, with the error shown above. Below is the output from the link provided on the error window. It is not clear to me, what execute authority is missing and for which user. Any suggestions on where to look for further details about this error, or possible solutions would be appreciated. Thanks.

InvokeService:Get ABAP System Info
Library: sap.com/tc~lm~config~bs
SourcePath ./com_sap_sld70x_scenario_simulate/process/process_2/S_TCC_LMCFG_LIB_GET_SYSINFO_Minimal
Time 2011/03/22 at 12:41:32
WSDL service/NW/AbapServer/S_TCC_LMCFG_LIB_GET_SYSINFO_Minimal.wsdl
Destination 
 SUZUKISOLMAN_ADMIN% secure content %00001en  
Destination parameters 
user : SOLMAN_ADMIN 
password : % secure content % 
host : SUZUKI 
sysnr : 00 
client : 001 
language : en 
 
function name: S_TCC_LMCFG_LIB_GET_SYSINFOInput 
   
 
 
InvokeService- Result: Error
Duration:734 ms
SourcePath./com_sap_sld70x_scenario_simulate/process/process_2/S_TCC_LMCFG_LIB_GET_SYSINFO_Minimal
Refresh Env. Messages: false
Output 
         E SCTC_API 002 No execute authority  000000      0  SMXCLNT001     

Regards,

Venkat.

Solution:

first reviewed note 1451426, but the changes discussed in that note, were already present in my system.

I then performed a trace while repeating the error, but I did not find any trace output (at first). I then added SAP_ALL and SAP_NEW to users SOLMAN_ADMIN and J2EE_ADMIN (just in case), and repeated the initial configuration step. After adding these profiles, the step completed successfully.

One additional note, after reviewing the trace information closer, I did find the failing object that was causing the issue originally (see below). This occurred for user SOLMAN_ADMIN. The other option would have been to add this object/value to one if the roles in use, as Ragu had suggested.

S_CTC RC=4 ACTVT=16;

Also, I noticed that in the trace, the only users reported were SOLMAN_ADMIN, SAPJSF and SLDAPIUSER, so the profiles were definitely not needed for user J2EE_ADMIN.