Solution Manager Addon Stuck BBPCRM SAPKU50008

Question

Dear Experts,
When I am implementing ADDON BBPCRM SAPKU50008 in Solution Manager .In Queue Import  It stuck in "Execution of report after put"
When I check SLOG .It show nothing.
START tp_getprots          SAL R      20101211160827              DDIC         testserver                    
STOP  tp_getprots          SAL R      20101211160943              DDIC         testserver                    
STOP  EXECUTION OF REPORTS SAL R      20101211160943              DDIC         testserver                    
START EXECUTION OF REPORTS SAL R      20101211161147              DDIC         testserver                    
START tp_getprots          SAL R      20101211161148              DDIC         testserver                    
But when I check  \usr\sap\trans\log\SAPKU50008
2 EPU122XPost-import method "BEFB_AFTER_IMP" started for "BEFT" "T", date and time: "20101210153150"
A3 E/BEF/GENERATOR 008XGeneration of BE Application "CRMB" (Start Time "15:31:51")
A3WE/BEF/GENERATOR 010 Generation of application "CRMB" (user "DDIC") is already running
1AETR012XProgram terminated (job: "RDDEXECL", no.: "15313100")
1AEPU320 See job log"RDDEXECL""15313100""SAL"
1 ETP162 EXECUTION OF REPORTS AFTER PUT
1 ETP110 end date and time   : "20101211094736"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
Transport is proper configure.
Whats the problem ?

Answer 1

Hello Pooja,
One thing you want to check is based on your SP level that the following notes have been applied on your system:
1172948 SAP Solution Manager: Basic functions (18 & 19)
1334252 SAP Solution Manager: Basic functions: SP20 and SP21
1405878 SAP Solution Manager: Basic functions: SP22 to SP24
1468591 SAP Solution Manager: Basic functions: SP25 and higher
If the relevent note is not already applied to your system, then please do so.
As Tom has already suggested you want to check the Job log for RDDEXECL.
You can do this with transaction code SM37.
Check for lines like:
ABAP/4 processor:...
Which indicates there was a short dump created and the program terminated.
You can look at the dump via ST22. This can be used for a Note search that may address the cause for the dump.
Hope this helps!
Regards,
Paul