cancel
Showing results for 
Search instead for 
Did you mean: 

Job SWEQSRV is not active - cancellation not possible!

Former Member
0 Kudos

PI experts,

We have a PI7.11 system with following support pack levels:

SAP_ABA 711 0006 SAPKA71106

SAP_BASIS 711 0006 SAPKB71106

PI_BASIS 711 0006 SAPK-71106INPIBASIS

ST-PI 2008_1_710 0004 SAPKITLRE4

SAP_BW 711 0006 SAPKW71106

ST-A/PI 01N_710BCO 0000 -

OS = AIX 6.1 64bi

Kernel = 711 #118 UC

DB = 11.2.0.2.0

I setup all the required background jobs for PI, but our Early watch report dinged me on Job SWEQSRV . It says the job isn't running. But in SM37 it does run successful. The problem is what the job log says:

07/21/2011 14:40:43 Job started

07/21/2011 14:40:43 Step 001 started (program RSWEQSRV, variant &0000000019105, user ID XXXXX

07/21/2011 14:40:43 Job SWEQSRV is not active - cancellation not possible!

07/21/2011 14:40:43 Job finished

Don't get me wrong, no one is complaining about system problems. This is just something I noticed.

I found a few threads that dance around this but no real solution:

This describes the exact error in teh job log:

But no real solution, just links to others.

Here too good info:

http://wiki.sdn.sap.com/wiki/display/SM/PIHousekeepingJobsshowasunscheduledinEWAReport

I'm totally aware you control this job via SWF_XI_CUSTOMIZING and SWEQADM Tcodes. And it all looks good to me.

I'm more concerned about the statement in the job log.

I've also reviewed every note that comes up if you search for "SWEQSRV". We're at a fairly recent SP level, so none have applied to me at this time.

Any help appreciated.

NICK

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos
0 Kudos

hi,

one job is in ready state from long time and unable to stop/delete.

Error is like job is not active- cancellation not possible.

Kindly someone suggest me how to cancel the job on priority.

Thanks in advance!!

Regards,

Jeevan Reddy

Former Member
0 Kudos

SAP said this message in the log is expected if there is nothing to process. So everything is functioning normally

Former Member
0 Kudos

Check if the job is scheduled on "Depending on load (dynamic)" load. This means that the job is not scheduled periodically, but it schedules itself when the load is required. Then, EWA might be looking for this job and it is not finding it, since its schedule is done dynamically.