Event 41021 - Archived items in Vault Store Waiting to be Indexed

Have you just tried rebooting the server?

Is the Indexing service running?

Any eventlog entries?

Cheers

Check in the VAC to see if the indexes are in backup mode. If yes the indexes will not be updated and the queue will build.

Liam,

 I'm right clicking on the server and browing to the "Set State" options. The "Set Backup Mode on all index locations" and "Clear Backup Mode from all index locations" are not Greyed out.

 My understading per the above is that the Indexes are not in backup mode. Anywhere else I can check?

Thanks,

Dennis

STS Symantec Enterprise Vault 2007
STS Symantec Enterprise Vault 8.0 for Exchange

Michelz,

Have you just tried rebooting the server? Last Reboot was about 5 Days ago. It has not been rebooted since that date.

Is the Indexing service running? Indexing service is running. EV services have been stopped and restarted. EV is currently archiving items fine with no issues.

Any eventlog entries? Event 41021 is displayed, but its description is the same as the critical one reported in the VAC per this original posting.

Thanks for your help!

Dennis

STS Symantec Enterprise Vault 2007
STS Symantec Enterprise Vault 8.0 for Exchange

All,

 Although the "Set State" of (Set Backup Mode on all Index Locations) was not greyed out. Meaning that the Index location was not running in backup mode. I still selected the "Clear Backup Mode from all Index Locations" on the server reporting the above "Alert".

 Once the above was applied and re-running all checks from the VAC again...the number of "Archived items waiting to be indexed" is going down.

Thanks,

Dennis

Try the following query to give you the counts for each individual awaiting an index to be written, change "yourVaultStore.dbo." to the name of your Vault Store database

Also remember that Index Commits can be in JournalUpdate and JournalDelete as well
The three main statements are

SELECT COUNT(*) FROM JournalUpdate WHERE IndexCommitted = 0
SELECT COUNT(*) FROM JournalDelete WHERE IndexCommitted = 0
SELECT COUNT(*) FROM JournalArchive WHERE IndexCommited = 0

Note that above, JournalArchive has one T in commited, where as JournalUpdate and JournalDelete have two T's

but anywho, here's the main query, you can modify the SELECT, FROM and WHERE to show how many items are in either of those three tables. Once you've identified some big hitters, just go to their index volumes and process an Update against the index OR try searching the index (any time an index is searched, its the same as hitting Update through the VAC)
 

EDIT: ha! it'd been solved by the time i posted this, sometimes the simplest answers are the right ones :) but still this is a good query for reference

Anywho, here's the query

SELECT TOP 100 A.ArchiveName "Archive Name", 
      (IRP.IndexRootPath + '\'+ IV.FolderName) "Index Location",
       IV.IndexedItems "No. Indexed Items",
       IV.Rebuilding "Is Rebuilding",
       IV.Failed "Is Failed",
       IV.Offline "Is Offline",      
       IV.FailedItems "Items Failed To Index",
       COUNT(JA.IndexCommited) "Items awaiting index (JA)"
       
FROM   EnterpriseVaultDirectory.dbo.IndexRootPathEntry IRP,
       EnterpriseVaultDirectory.dbo.IndexVolume IV,
       EnterpriseVaultDirectory.dbo.Archive A,
       EnterpriseVaultDirectory.dbo.Root R,
       yourVaultStore.dbo.JournalArchive JA,
	   yourVaultStore.dbo.ArchivePoint AP
WHERE  JA.ArchivePointIdentity = AP.ArchivePointIdentity
  AND  AP.ArchivePointId = R.VaultEntryId
  AND A.RootIdentity = R.Rootidentity
  AND R.RootIdentity = IV.RootIdentity
  AND IV.IndexRootPathEntryId = IRP.IndexRootPathEntryId 
  AND JA.IndexCommited = 0
GROUP BY ArchiveName, IndexRootPath, FolderName, FirstItemSequenceNumber, HighestItemSequenceNumber, IndexedItems, Rebuilding, Failed, Offline, FailedItems
ORDER BY "Items awaiting index (JA)" DESC

Good to know you have a solution. Select a posting which is the solution so the posting can be closed

JesusWept2,

 I edited the solution because the count stop going down after a couple of minutes. Although I applied the workaround in posting again and it started to go down once more...I do not want to mark it yet till I'm 100% sure.

However looking into your QUERY further as well to determine if it does the trick. Can you help me out?

This section is highlighting when I run the QUERY and I get the below error.

'\' --> From: (IRP.IndexRootPath + '\'+ IV.FolderName) "Index Location",
 I replaced it with the INDEX Location of that server as well, but the below error is still displayed:

Invalid object name 'EnterpriseVaultDirectory.dbo.IndexRootPathEntry'.

Please let me know on your comments,

Thanks,

D

what version are you on?
Is the Vault Store and the EnterpriseVaultDirectory database on the same server?

JesusWept2,

We are on 8.0 - SP4.

Is the Vault Store and the EnterpriseVaultDirectory database on the same server?

These are not on the same EV Server. This particular Vault Store is actually on a different SQL cluster than the one where the Enterprise Vault Directory database is located.

Please advise on any comments,

Thanks and Best Regards,

Dennis