{"id":230,"date":"2016-10-14T13:03:09","date_gmt":"2016-10-14T08:33:09","guid":{"rendered":"http:\/\/www.enhisecure.com\/isecureblog\/?p=230"},"modified":"2016-12-01T11:08:02","modified_gmt":"2016-12-01T06:38:02","slug":"solving-problem-sailpoint-identityiq-mark-invalid-error","status":"publish","type":"post","link":"https:\/\/www.enhisecure.com\/isecureblog\/2016\/10\/14\/solving-problem-sailpoint-identityiq-mark-invalid-error\/","title":{"rendered":"Solving problem SailPoint IdentityIQ &#8220;Mark Invalid Error&#8221;"},"content":{"rendered":"<h4><strong><span style=\"text-decoration: underline\">Problem description<\/span>\u00a0<\/strong><\/h4>\n<p>When we try to correlate the accounts into <a href=\"https:\/\/www.sailpoint.com\/products\/identityiq\/\">SailPoint&#8217;s<\/a>\u00a0<a href=\"https:\/\/www.sailpoint.com\/products\/identityiq\/\">identityIQ <\/a>using multiple authoritative sources the following<br \/>\nexception may arise.<\/p>\n<h4><span style=\"text-decoration: underline\"><strong>Why this happens<\/strong><\/span><\/h4>\n<p>The main reason for this error is ambiguity of accounts. After the account aggregation task completed\u00a0when we try to run the task refresh identity cubes. Task is not running and error is displays as Task\u00a0stopped by user. When you see the log file there a exception named <strong>Mark Invalid<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: center\">.<img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-231 size-full\" src=\"http:\/\/www.enhisecure.com\/isecureblog\/wp-content\/uploads\/2016\/10\/erroe_scrn_sht.png\" alt=\"erroe_scrn_sht\" width=\"1327\" height=\"390\" srcset=\"https:\/\/www.enhisecure.com\/isecureblog\/wp-content\/uploads\/2016\/10\/erroe_scrn_sht.png 1327w, https:\/\/www.enhisecure.com\/isecureblog\/wp-content\/uploads\/2016\/10\/erroe_scrn_sht-300x88.png 300w, https:\/\/www.enhisecure.com\/isecureblog\/wp-content\/uploads\/2016\/10\/erroe_scrn_sht-1024x301.png 1024w\" sizes=\"auto, (max-width: 1327px) 100vw, 1327px\" \/><\/p>\n<h5><strong>Case 1<\/strong><\/h5>\n<p>The main cause for this error is, If you have added more than one\u00a0authoritative sources marked for one identity.\u00a0The following exception will arise. that means you have added two Authoritative sources representing\u00a0the same data if run the aggregation task the accounts will be populated with their name then If we\u00a0perform refresh identity cubes task the accounts will not linked its respective manager account because\u00a0there will be an ambiguity between two accounts which has to be correlate as manager account.<\/p>\n<h5><strong>Case 2<\/strong><\/h5>\n<p>In other cases if you have any accounts or identities not properly deleted.<\/p>\n<h4><span style=\"text-decoration: underline\"><strong>Solution<\/strong><\/span><\/h4>\n<p>The solution I found is to get backup of the rules and application into a <a href=\"https:\/\/en.wikipedia.org\/wiki\/XML\">xml <\/a>file using the console.Shutdown the application server and drop all the tables in database using the <a href=\"https:\/\/en.wikipedia.org\/wiki\/SQL\">sql <\/a>scripts provided by\u00a0<a href=\"https:\/\/www.sailpoint.com\/products\/identityiq\/\">identityIQ <\/a>then create the tables using the scripts. Import the <strong>init.xml<\/strong> using the <strong>iiq<\/strong>\u00a0<strong>console<\/strong>.Then import the <a href=\"https:\/\/en.wikipedia.org\/wiki\/XML\">xml <\/a>file which represents the application object. Then if you run the aggregation and\u00a0correlation tasks you can see that all the identities and their managers are correlated in identity\u00a0warehouse.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Problem description\u00a0 When we try to correlate the accounts into SailPoint&#8217;s\u00a0identityIQ using multiple authoritative sources the following exception may arise. Why this happens The main reason for this error is ambiguity of accounts. After the account aggregation task completed\u00a0when we try to run the task refresh identity cubes. Task is not running and error is [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":231,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,15,14,16],"tags":[10,11],"class_list":["post-230","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-identity-governance","category-implementation-problems","category-sailpoint","category-technology","tag-identity-iq","tag-sailpoint"],"_links":{"self":[{"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/posts\/230","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/comments?post=230"}],"version-history":[{"count":9,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/posts\/230\/revisions"}],"predecessor-version":[{"id":240,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/posts\/230\/revisions\/240"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/media\/231"}],"wp:attachment":[{"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/media?parent=230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/categories?post=230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.enhisecure.com\/isecureblog\/wp-json\/wp\/v2\/tags?post=230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}