cancel
Showing results for 
Search instead for 
Did you mean: 

GN_GENERATE_CHECK and SM_SERVICE_CONTENT_UPDATE background jobs are failing

laurie_mcginley
Participant
0 Kudos

We recently upgraded our Solution Manager to 7 ehp1. A couple of the background jobs are not able to complete.

Both jobs have the following entry in the job logs

Step 001 started (program RAGS_DSWP_SERV_CONTENT_UPDATE, variant , user ID SOLMAN_ADMIN

No authorization

I'm not sure where to look for the authorization issue. Any advice would be appreciated.

Thanks

Laurie McGinley

View Entire Topic
mateus_pedroso
Employee
Employee
0 Kudos

Did you finish all steps of transaction AGS_UPDATE ?

laurie_mcginley
Participant
0 Kudos

Apparently not. Just went into the transaction and I don't recognize it. Is saying the ST-SER is out of date.

I knew ST-A/PI was out of date per the EarlyWatch report. I expect I need to get these both updated then to address these report errors?

Thanks

Laurie

Former Member
0 Kudos

Hi

Please try to run the report

RAGS_DSWP_SERV_CONTENT_UPDATE or you can execute

transaction AGS_UPDATE. It can also be started in the work center

'SAP Engagement and Service Delivery'.

SAP Note 1143775 - SAP service content update describes the steps

involved.

There are three steps in the process:

- 1. Search for updates

- 2. Download updates

- 3. Activate updates

So it may take a long time for the report to complete.

Hope this helps.

Cheers

SH

nanda_kumar21
Active Contributor
0 Kudos

Hi,

I have a similar problem, in my case "GN_GENERATE_CHECK" is failing due to

Job started

Step 001 started (program GN_GENERATE_CHECK, variant , user ID SOLMAN_BTC)

Object requested is currently locked by user SOLMAN_BTC

Job cancelled after system exception ERROR_MESSAGE

Please tell me how to solve this

Nanda

former_member209604
Active Contributor
0 Kudos

Nanda, please find information how to solve the "currently locked by user SOLMAN_BTC" issue.

Jobs GN_GENERATE_CHECK and GN_WORKLIST_GENERATE are currently scheduled in parallel by SOLMAN_SETUP.

Parallel execution leads to error:

Object requested is currently locked by user SOLMAN_ADMIN

Please change the start time of GN_GENERATE_CHECK to let the job run later.

Proposal: 00:15:00

Change the start via transaction SE16:

Table: SMCONFIGJOBS

REPORTNAME GN_GENERATE_CHECK

REPVARIANT

JOBNAME GN_GENERATE_CHECK

PRIORITY 50

PERIOD TYPE DAY

PERIOD INTERVAL 1

START TIME 00:15:00 <==========

ISIMMEDIATE

INACTIVE

WORKLOAD M

REPORTNAME GN_WORKLIST_GENERATE

REPVARIANT

JOBNAME GN_WORKLIST_GENERATE

PRIORITY 50

PERIOD TYPE DAY

PERIOD INTERVAL 1

START TIME 00:01:00

ISIMMEDIATE

INACTIVE

WORKLOAD L

Best regards,

Ruediger

P.S.: SOLMAN_SETUP uses different times as of SolMan 7.0 SPS 25 (ST 400 SP25) and SolMan 7.1

christoph_ostrop
Active Contributor
0 Kudos

we are on SM 7.01 (EHP1) - and we have the same problem:

Jobs GN_GENERATE_CHECK and GN_WORKLIST_GENERATE

both jobs end abnormal with joblog:

Object requested is currently locked by user SOLMAN_BTC
Job cancelled after system exception ERROR_MESSAGE

but the job-start is not corresponding to the entries in table SMCONFIGJOBS

both jobs are startet at 00:01:44 (both !!!)

in table SMCONFIGJOBS the entry are

REPORTNAME GN_GENERATE_CHECK

REPVARIANT

JOBNAME GN_GENERATE_CHECK

PRIORITY 50

PERIOD TYPE DAY

PERIOD INTERVAL 1

START TIME 00:15:00

ISIMMEDIATE

INACTIVE

WORKLOAD M

COMM2SAP

REPORTNAME GN_WORKLIST_GENERATE

REPVARIANT

JOBNAME GN_WORKLIST_GENERATE

PRIORITY 50

PERIOD TYPE DAY

PERIOD INTERVAL 1

START TIME 00:01:00

ISIMMEDIATE

INACTIVE

WORKLOAD L

COMM2SAP

any suggestions why the jobstart is not corresponding to the starttime in table SMCONFIGJOBS

what job is scheduling these 2 Jobs GN_GENERATE_CHECK and GN_WORKLIST_GENERATE

which other job maybe responsible for the object lock???