Skip to end of metadata
Go to start of metadata
  1. Does the error happen to all FIM jobs?

    • If all FIM jobs are facing the same problem, then you’ll need to go to the FIM Admin page

      http://{your_server_name}:{port}/fim/admin

       

      Use the Check button in each section to make sure the information in all sections is correct.

       

      If your information in the section is correct, you will see this message.

       

       

      In some cases, you might also want to try removing the job server name in the DS section. See article 2199571 for more details.

      Also check that the job server entries on the DS side are correct. See article 1857149 for more details.

    • If some FIM jobs are able to run, then it means the underlying systems (DS, BOE, etc.) are configured correctly. You’ll need to check the job specific settings (Source and Target Data Stores, associated DS jobs, see below).

  2. Test the source and target data stores.

    Use the "Test" button on the Datastore configuration page to ensure that the datastores are working.

     

    If a datastore is utilizing an ODBC connection fails the test, go to the Windows start menu --> Administrative Tools --> ODBC Data Source Administrator and test the System Data Source (Configure … --> Next --> Next --> Next --> Finish --> Test Data Source … )

     

    Also try to use a Ping or Telnet command to test the network connection to the remote servers.

     

  3. Run the job from Data Services.

    Note: You might need to set some global variables, such as Job_Run_ID, in order to run the job outside of FIM.
     

  4. Check the Job Run History.

    See if the trace log, error log, and monitor log contain any detailed information on the error.

     

     

  5. Check the FIM TraceLog

    Default Path C:\ TraceLog_XXXXXXXXXXXXXXXXXXXXXXXXX_trace.glf

     

  6. Try disabling firewalls

    If you have firewalls enabled, disable them temporarily and run the job again.

 

  • No labels