RAR Job Scheduler Status Not Responding

[Former Member]

We are having issues with our RAR Job Scheduler. The Job Scheduler Status says "Not Responding", however the Background Job Daemon and the Analysis Daemon are running. We have also been able to complete a full Sync as a background job.

Does anyone have any ideas as to why the Job Scheduler Status still says "Not Responding" or what additional analysis steps we shoudl take?

Thanks In Advance.

[Former Member · Accepted solution]

Hello Mathew,

If you upgrade to latest SP13.1, then it is a bug in SP13.1. SAP is working on it and it will be resolved in SP14 which is expected in second week of December 2010.

Thanks,

Mohan

[Former Member · Accepted solution]

Thanks for your replies

We are currently on Service Pack 13.0. (is that bug still relevant for this servicepack?)

Here are the values in the VIRSA_CC_CONFIG file:

Row CNFGPARAM| CNFGSEQ| CNFGVALUE| COMMENT|

1 236 0 FunctionPermissionGenerated FUNCTION PERMISSION GENERATION

2 237 0 InactiveUsersDeletion PARAM INACTIVE INVALID USERS DELETION FROM MGRISKD

3 231 0 DIR_HOME

4 232 0 <server name>

5 233 0 grcftp

6 234 0 ****

7 101 0 QAS - 100

8 103 0 1000

9 118 0 1441

10 241 0 5

11 242 0 3

12 12 0 ObjAnl

13 20 0 *

14 21 0 1

15 8 0 YES

16 9 0 YES

17 10 0 YES

18 116 0 GLOBAL

19 127 0 YES

Any other comments or ideas would be appreciated. Thank you again for your help.

[Former Member · Accepted solution]

We did see an SAP note 999785 regarding the Background Daemon not starting that said to add entries into the VIRSA_CC_CONFIG table, however we saw that it was only applicable for Service Pack 10 or lower, and we are on Service Pack 13.

[Former Member · Accepted solution]

Yes i was checking the same values.

May be re-starting the server solve this issue.

Regards,

Surpreet

Note: if your sync job were sucessful then table VIRSA_CC_GENOBJ would be populated with user, role & profile data

Edited by: Surpreet Singh Bal on Oct 14, 2010 11:31 AM

[Former Member · Accepted solution]

Hello Mathew,

Yes. This bug belongs to SP13.

Thanks,

Mohan

[Former Member · Accepted solution]

Thank you both for your help. The jobs do seem to be running and it looks like we'll just need to wait until the new Servicepack.

Thanks again

[Former Member]

Does this mean it is a false error and things are working OK?

WE just went to SP13.2 and are seeing this now too.

[Former Member]

what are values in table VIRSA_CC_CONFIG ?