Control Compliance Suite (CCS)

Schedule jobs are failing and the following error appears:

An error occurred while attempting to run the scheduled job.  Reason for failure: Unable to retrieve job definition from ADAM due to the following error: Object reference not set to an instance of an object.

Similar errors are recorded in the logs:

An error occurred while attempting to run a scheduled job; Reason for failure. Unable to retrieve job definition from ADAM due to the following error: Object reference not set to an instance of an object.
"at
Symantec.Implementtaion.AppServee.JobManager.JoBmanager.executeSchedulejob(GuidADAMJobID,
String userName. Dictionary '2 namedArgumentValues)
--------Object reference not set to an instance of an object.
"at
Symantec.Implementtaion.AppServee.JobManager.JoBmanager.executeSchedulejob(GuidADAMJobID,
String userName. Dictionary '2 namedArgumentValues)
 

Or if using 12.6.0 from the logs.

022-09-08 12:35:53.309,2022-09-08 06:35:53.309,######,Error,Symantec.Core,AppserverService,3716,Scheduled Jobs Manager:74,74,Bind,,0,0,"RetryHelper.Call(CreateLdap) - failed [The server is not operational.], context [Directory.Directory], stop retry flag [False], failed retry counter [0 of 10] : System.Runtime.InteropServices.COMException (0x8007203A): The server is not operational.

Then 90 minutes later:

2022-09-08 14:08:48.965,2022-09-08 08:08:48.965,######,Error,AppServer.Jobs,AppserverService,3716,Scheduled Jobs Manager:74,74,Call,,0,0,"AppServerAdamPersist unable to bind to ADAM after 3 minutes of retrying : System.Runtime.InteropServices.COMException (0x8007203A): The server is not operational.

   at Symantec.RetryHelper.Call[TReturnType](String retryName, RetryOperation`1 retryOperation, FailureOperation failureOperation, String context)
   at Symantec.Implementation.AppServer.Jobs.AppServerAdamPersist..ctor(String servername, String username, String password)"
2022-09-08 14:08:48.965,2022-09-08 08:08:48.965,######,Error,AppServer.JobManagement,AppserverService,3716,Scheduled Jobs Manager:74,74,.ctor,,0,0,"System.Runtime.InteropServices.COMException (0x8007203A): The server is not operational.

   at Symantec.Implementation.AppServer.Jobs.AppServerAdamPersist..ctor(String servername, String username, String password)"
2022-09-08 14:08:48.965,2022-09-08 08:08:48.965,######,Error,AppServer.JobManager,AppserverService,3716,Scheduled Jobs Manager:74,74,ExecuteSchedulerJobInternal,,0,0,"Error retreiving job definition in ExecuteJob( : System.NullReferenceException: Object reference not set to an instance of an object.
   at Symantec.Implementation.AppServer.JobManager.JobManager.ExecuteSchedulerJobInternal(Guid AdamJobID, String userName, Dictionary`2 namedArgumentValues)"
2022-09-08 14:08:48.965,2022-09-08 08:08:48.965,######,Error,AppServer.JobManager,AppserverService,3716,Scheduled Jobs Manager:74,74,ExecuteSchedulerJobInternal,,0,0,"Error executing scheduled job : System.ApplicationException: Unable to retrieve job definition from ADAM due to the following error:Object reference not set to an instance of an object."" ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Symantec.Implementation.AppServer.JobManager.JobManager.ExecuteSchedulerJobInternal(Guid AdamJobID, String userName, Dictionary`2 namedArgumentValues)
   --- End of inner exception stack trace —
   at Symantec.Implementation.AppServer.JobManager.JobManager.ExecuteSchedulerJobInternal(Guid AdamJobID, String userName, Dictionary`2 namedArgumentValues)"
2022-09-08 14:08:48.965,2022-09-08 08:08:48.965,######,Error,AppServer.JobManager,AppserverService,3716,Scheduled Jobs Manager:74,74,ExecuteSchedulerJobInternal,,0,0,"An error occurred while starting scheduled job : System.ApplicationException: Unable to retrieve job definition from ADAM due to the following error:Object reference not set to an instance of an object."" ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Symantec.Implementation.AppServer.JobManager.JobManager.ExecuteSchedulerJobInternal(Guid AdamJobID, String userName, Dictionary`2 namedArgumentValues)
   --- End of inner exception stack trace —
   at Symantec.Implementation.AppServer.JobManager.JobManager.ExecuteSchedulerJobInternal(Guid AdamJobID, String userName, Dictionary`2 namedArgumentValues)
   at Symantec.Implementation.AppServer.JobManager.JobManager.executeSchedulerjob(Guid AdamJobID, String userName, Dictionary`2 namedArgumentValues)"
2022-09-08 14:08:48.981,2022-09-08 08:08:48.981,######,Error,AppServer.WorkFlowSvc,AppserverService,3716,Scheduled Jobs Manager:74,74,GetIdentity,,0,0,"Could not retrieve user context for job instance <GUID/GUID> to save result container to ADAM. Object will be created using AppSErver context : System.ApplicationException: The user identity for the workflow job could not be found.

CCS 12.6.0 - Application Server

This issue is fixed in CCS 12.6.1

This error can occur for a couple of reasons:

1) Controlled delegated authentication has not been configured correctly in CCS.

or

2) If modifying the CSV Platform settings through editing a job, then you go to Settings -> Deployment View, and then edit the settings for a CCS Manager by right-clicking and selecting "Edit Settings".
This causes the Application Server to change to the setting "Use controlled delegation of security", even if you cancel out.

1)  If you are using Constrained delegation, verify that all the steps have been followed to correctly setup delegation.

Configuring constrained delegation

or more likely

2) Use the following steps to set the Application Server setting back to have CCS store the users password.

1. In the CCS Console go to Settings > Deployment View
2. Right-click the Application Server component and click Edit Settings
3. In the Edit Settings dialog box, under the Application Server tab on the left, click on 'Basic'.
4. In the 'Authentication Type' section, select 'Use Control Compliance Suite to store the password'
5. Click Save.
6. Back in the Deployment View, in the Infrastructure Tasks dropdown select 'Sync Configuration'
7. Make sure you have the current password for any user(s) that are set to run any scheduled jobs entered into CCS.  You will need to be logged in to the CCS console as that user, and then go to Admin > Scheduled Job Management > Scheduled Job Credentials and enter in the password for that user for CCS to use to run scheduled jobs.
8. A reboot of the Application server is required for the 'Use Control Compliance Suite to store the password' setting to remain selected, and the changes to take effect.

This issue will be fixed in 12.6.1