Access History Page Remains Blank After Loading

[Marco_oliveira]

Which IIQ version are you inquiring about?

8.4p2

Please share any images or screenshots, if relevant.

Share all details about your problem, including any error messages you may have received.

Good morning/afternoon/evening everyone,

I need some help with an AccessHistory issue.

I recently started using AccessHistory in my environment, but every time I open the page, it remains blank and only displays information for a single user.

The strange part is that the exact same configuration works correctly in my DEV and QAS environments. I have compared the configurations and they appear to be identical.

Has anyone encountered this issue before or have any suggestions on what might be causing it?

I’ve attached a screenshot showing how the page appears in the affected environment.

Any help would be greatly appreciated.

Thank you very much.

[jchinnapareddy (Jaganmohan BC)]

Hi @Marco_oliveira ,

Connect to that database instance and run the following queries to check if rows are being successfully written:sql-- Switch to the Access History database
USE identityiqah;

-- 1. Check if ANY global identity snapshots exist
SELECT COUNT(*) FROM spt_hist_identity_capture;

-- 2. Check if account-level histories are being captured
SELECT COUNT(*) FROM spt_hist_account_capture;

-- 3. Check for specific application link history
SELECT COUNT(*) FROM spt_hist_accounts;

[sukarande (Sumit Ukarande)]

@Marco_oliveira

Have you checked SPT_HIST* Tables?

[Marco_oliveira]

Good morning/afternoon/evening everyone,

I checked the database and executed the recommended commands. Everything appears to be normal, including the Access History tables.

I also ran the following commands:

• accessHistory createExtractedObject Identity
• accessHistory publish Identity

The identity data was successfully captured and published to the IIQAH database. The logs indicate that the process completed successfully without any apparent errors.
2026-06-01T11:05:54,127 TRACE main sailpoint.server.SailPointConsole:150 - Exiting readLine = accessHistory publish Identity 0a1ce82f6f1016bf81701b2a8aa35491
…
2026-06-01T11:05:56,749 DEBUG main sailpoint.accesshistory.ImageProcessor:863 - Most recent Identity capture is a full capture. Nothing else to load.
…
2026-06-01T11:06:52,708 DEBUG main sailpoint.accesshistory.changeevent.Emitter:425 - Completed event generation in 4063 ms. Total Events: 279
…
2026-06-01T11:06:55,303 TRACE main sailpoint.accesshistory.IdentityImageProcessor:150 - Exiting process = *****

The main issue is that, even after running the Dispatch task multiple times, the Access History page still remains completely blank.

Thank you very much.

[sukarande (Sumit Ukarande)]

@Marco_oliveira

Change Some Data from trusted source or from debug page for Identity. Execute Refresh Identity Job and Just try below IIQ Console Command in Sequence and check AH UI Page.

1. accessHistory createEvent identity identity_name_or_id

2. accessHistory postEvent identity identity_name_or_id

[neel193 (Neelmadhav Panda)]

@Marco_oliveira Could you please check the network logs in case any error is logged while loading the page?

[Marco_oliveira]

Good morning/afternoon/evening everyone,

After reviewing your comments, I noticed that the page CSS was set to 0px, which prevented the page from displaying correctly. I updated it to 1000px, matching the configuration in my DEV and QAS environments, and the Access History page is now working properly.

Thank you all very much for your help!

The only remaining issue I have is related to the errors that occur when running the Access History Dispatch task.

Do these errors affect Access History functionality in any way? Is there anything I can do to troubleshoot or resolve them?

Thank you again for all your support.

[paul_hilchey]

Hi @Marco_oliveira, we get those errors too, and are waiting for a fix from SailPoint.

If you are on an Oracle database, I’ll suggest adding a few indexes:

-- add indexes to make Access History performant
-- remove these if a subsequent IIQ upgrade makes them redundant
create index identityiqah.spt_hist_ic_dname_ci on identityiqah.spt_hist_identity_capture(upper(display_name));
create index identityiqah.spt_hist_ic_iname_ci on identityiqah.spt_hist_identity_capture(upper(identity_name));
create index identityiqah.spt_hist_mattr_id_ic on identityiqah.spt_hist_mattr(upper(mattr_id));