Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Issue(s)

You might experience a slow system, changes are not provisioned to a target system, attribute values are not beeing update or any other unexpected behaviour.

Cause(s)

There is a multitude of reasons that could cause this isse. This guideline will give you a few tips on where you can start.

Solution(s)

If you are experience any issues, follow the listed steps below:

  • Identify in which part of the software is affected and check the appropriate Log files documented here Logs

  • If you do not know where to start the log_log table or the appropriate file log (usually C:\Program Data\itsense\Log) is a good place to start

  • If there are errors in those places it’s good practice to identify the the task that is causing this. In the log_log table you can do this by identifying the thread column which contains the guid of the task. This looks something like this

    Task 9c2349cf-25db-4366-b285-41efbe374492
    • In the CoreOne Suite Web Interface you can browse to Task Managenent / Task and find the appropriate task by simply entering the guid

    • The Task Detail page will contain a detailed error description that might help you sort the issue out

  • If there are to many errors or you dont find any, you can also check the tasks for any errors. You can do this either on the database or in the CoreOne Suite Web Interface

    • Simply check for any task with a last run message that is not “Finished” in the CoreOne Suite Web Interface

    • Or simply run the following query on the database

SELECT * FROM taskscheduler_task_definition where lastrun_message like '%error%'
  • Again, identify which tasks are failing and have a look at their output

  • Within those ouptpute messages you usually get clear indication about what the issue is and which object it affects. The following message for example indicates that no identity could be created because no unique SAM-Account-Could be generated with the provided attribute mapping configuration.

    Not all identiy values could be resolved while creating identiy of type '2' for CoreIdentity '324'. Detailed Message: Could not generate a unique value for attribute 'SAM-Account-Name'. Plrease check your attribute mapping. Last value: johndoe
  • If you don’t have errors at all it’s also possible that the expected feature is not turned on. So please check the appropriate target system and identity or resource features.

  • No labels