cancel
Showing results for 
Search instead for 
Did you mean: 

SPAM UPDATE ERROR

Former Member
0 Kudos

Hello,

I have installed BW7.0 on windows 2003 Cluster environment.My data base is MSSQL2005 . I have imported spam,abap,basis and BI CONT703 initially. But I applied more patches rather than required level on BI CON 703. So I have restored my backup to initial level. After data base recovery when i try to update SPAM i am getting error it is not moving. I checked SM50 enough work processes are there. When i checked the dev_evt log from work directory. I got the following error.

DEV_EVT LOG displays like this

Fri Jun 26 15:08:05 2009

Trace File of External Event Raiser (Level=2, Append=0)

EventID: SAP_TRIGGER_RDDIMPDP

      • ERROR ***: Cannot determine mshost

Fri Jun 26 15:08:45 2009

Trace File of External Event Raiser (Level=0, Append=1)

EventID: SAP_TRIGGER_RDDIMPDP

      • ERROR ***: Cannot determine mshost

My SPAM TP LOG as follows :

Few Sample Logs from last page of the log screen

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.

WARNING: System SBG. Warning. 20090626152605 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=SBG

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.

WARNING: System SBG. Warning. 20090626152705 :

WARNING: Background job RDDIMPDP could not be started or terminat

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.

WARNING: System SBG. Warning. 20090626153005 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=SBG

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.

WARNING: System SBG. Warning. 20090626153045 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=SBG

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.

WARNING: System SBG. Warning. 20090626153203 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=SBG

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.

Can some body help me to resolve this problem?

Regards,

Sankar.G

Basis Consultant

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

I have rectified this problem

Thanks for all the people help.

Regards

Sankar

Former Member
0 Kudos

How did you rectify the problem?

We are having a very similar problem

Thank you in advance.

Former Member
0 Kudos

Hi Sankar ,

THis error can be caused due to folloiwng reasons:

1. Job RDDIMPDP is not scheduled properly in the system.

This background job is used for the communication between the

transport tools (TP and R3trans) and must be scheduled in all the

clients (included client 000) by user DDIC. Therefore, in order to

schedule job RDDIMPDP properly in all the clients you should do the

following:

1. Logon into client 000 with user DDIC

2. Go to transaction SE38 and run report RDDNEWPP

3. A new window will pop-up asking you if you want to schedule the background job with normal or high priority. Choose 'Normal'

4. Repeat the above steps in all clients.

In order to check that RDDIMPDP job is properly scheduled by user

DDIC you can do the following:

SM37 > Job name: RDD*

User name: *

> Under 'Job Status' select the check boxes "Sched.",

"Released", "Ready" and "Active"

> Under 'Job start condition', leave the "From" and "To"

fields empty.

> click the 'Execute' (F8) icon

A list of jobs will show up. There will be one RDDIMPDP job for

client 000 and one RDDIMPDP_CLIENT_<nnn> for each client different

from 000 (where <nnn> is the client number). All these jobs must be

created by user DDIC.

Refer Following Note:

11677:Transports with event-controlled RDDIMPDP

Also OS level issues may cause such issues , in that case better to restart your system at OS level and if again the issue persists, you have to apply necessary service packs .

Regards,

Nibu Antony

Edited by: Nibu Antony on Jun 27, 2009 7:23 PM

Former Member
0 Kudos

Start the RDDNEWPP in client 000 and your target client too.

sunny_pahuja2
Active Contributor
0 Kudos

Hi

Check SAP Note 449270 - Job RDDIMPDP is not triggered by sapevt..this describes your problem..

Thanks

Sunny

Former Member
0 Kudos

Hi,

Please schedule RDDNEWPP in client 000 with DDIC and then try .

Thanks

Rishi Abrol

JPReyes
Active Contributor
0 Kudos

maintain parameter system_pf in the tp profile TP_<domain>.PFL. Make sure that rdisp/mshost is maintained in the DEFAULT.PFL.

Read,

http://help.sap.com/saphelp_nw04s/helpdata/en/3d/ad5bf64ebc11d182bf0000e829fbfe/frameset.htm

Similar problem,

Regards

Juan