A FIM Reporting ETL job has not been run for the last 7 days. This could mean that your scheduled ETL jobs are not running properly, or that you have explicitly disabled running these jobs. To fix this issue, verify that the FIM Reporting SQL Agent Job defined in the FIM Service Database has a proper schedule defined, and that there are no errors associated with job execution. If there are no issues with the job schedule, then ensure that you can successfully run a FIM Reporting Incremental ETL job by starting a job manually. If you no longer wish to use the reporting feature, run a change install using the FIM Service and Portal installation package and remove the ""FIM Reporting"" feature. This will disable writing to the export log on the FIM Service Database.
A failed installation may result in a corrupt MIM CM database. To recover, you must restore the orginal database. Please ...
A file that is required cannot be installed because the cabinet file 2 has a digital signature that is not valid. This may ...
A file that is required cannot be installed because the cabinet file 2 has an invalid digital signature. This may indicate ...
A file that is required cannot be installed because the cabinet file 2 is not digitally signed. This may indicate that the ...
A FIM Reporting ETL job has not been run for the last 7 days. This could mean that your scheduled ETL jobs are not running ...
A global catalog server is not reachable from this domain controller. This will result in failed authentications attempted ...
A KDS Root Key with a valid effective time was not found. The root key is required to generate gMSA passwords. Please try ...
A list of service principal names (SPNs) associated with the service principal. An SPN must be unique per company tenant ...
A list of service principal names (SPNs) associated with the service principal. An SPN must be unique per company tenant ...