Upgraded to 4.2 admin can't abort job

[former_member205400]

We upgraded to 4.2 and I ( admin ) went in to abort a job and we got the error message:

[Failed to stopped the job-myjob in Repository bods_mehta. Error message: bods_myrepo]

So I'm looking at the permissions on repo bods_myrepo and admin has FULL_CONTROL so I'm not getting what is up here.

Anyone see this before on a 4.2 upgrade?

Mike

[DayaJha]

Hi Hill,

Please share the details to debug the issue:

• After migration of BODS application you are facing this issue in all BODS Jobs or specific to one job?
• What is Job type batch Job or Real Time Jos?
• Have you test the job with sample data before connecting to real time database.?

Or

You can refer below SCN thread for more details

Thanks,

Daya

[former_member205400]

I know how ....

The user gets this error mesage ... the administrator gets this error message:

[Failed to stopped the job-myjob in Repository bods_mehta. Error message: bods_myrepo]

Mike

[DayaJha]

Hi Hill,

Can you please check from SAP Business Objects Data Services Management console you can abort the job or not.

Because i have found that with some versions of BODS there is a bug whereby the status remains running, but if you open the error log there is an error and the job has actually aborted.

If there's no error in the error log then the only sure way to know if the job's still runnning is to check for an al_engine on the job server task manager. If no al_engine process then the job's not running,however the reverse is not always true because if you have other jobs running or real-time jobs then those will have al_engine processes running.

Fo this you can use Process Explorer which is available for free to download and it is basically a click and run app for the Task Manager and it will give the time at which a Process is started!

Thanks,

Daya

[former_member205400]

Jha,

I understand all that ..... I was expecting you to talk about additional privs required. But since you didn't it must be a bug.

Mike