FSAUtility -b stuck on "Processing File List .. 16%"
FSAUtility -b stuck on "Processing File List .. 16%" I can't seem to find what the error is. So far nothing I have looked at in logs has been helpful.
Forum Discussion
dtrace showed zero activity and the fsautility report had no entries other than the source. I had restarted the server previously. I have the service a restart and am re-running the utility. seems to be doing something now
Thank you for the update. You should see CPU activity in both of those processes on the EV server and this could be used to verify it is still processing. Dtrace could also be run to verify.
Regards,
Patrick
actually seems to be doing the same thing ...
ran for a while in async mode then said complete report has no files being restored drace log stops apending to. ran in sync mode hung listing files:
3461 14:21:02.788 [5280] (FSAUtility) <7916> EV-H {BulkRecall.ScanForFileCount} Error in counting files:Error accessing the file: \\?\UNC\xxx\xx\*, error code: 3 3868 14:24:37.165 [5280] (FSAUtility) <5424> EV-H {BulkRecall.CrawlAndEnqueueFiles} Path not found \\?\UNC\xxx 3869 14:24:37.165 [5280] (FSAUtility) <5424> EV-H {BulkRecall.CrawlDirectory} Failed to crawl directory\\?\UNC\xx\xx, error:Error accessing the file: \\?\xxx\xx\*, error code: 3 3870 14:24:37.165 [5280] (FSAUtility) <5424> EV-H {BulkRecall.CrawlDirectory} Failed to crawl directory\\?\UNC\xxx\xx, error:Error accessing the file: \\?\UNC\Fxx\xx\*, error code: 3 3871 14:24:37.165 [5280] (FSAUtility) <6476> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3872 14:24:37.165 [5280] (FSAUtility) <8380> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3873 14:24:37.165 [5280] (FSAUtility) <1608> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3874 14:24:37.165 [5280] (FSAUtility) <9168> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3875 14:24:37.165 [5280] (FSAUtility) <1216> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3876 14:24:37.165 [5280] (FSAUtility) <8768> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3877 14:24:37.165 [5280] (FSAUtility) <7004> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3878 14:24:37.165 [5280] (FSAUtility) <1252> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3879 14:24:37.165 [5280] (FSAUtility) <9892> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3880 14:24:37.165 [5280] (FSAUtility) <7248> EV-M {BulkRecallThread.Process} Item processor thread has completed its work and will stop 3881 14:24:37.165 [5280] (FSAUtility) <5424> EV-H {BulkRecall.WaitForBulkRecallThreadsToComplete} All item processor threads have completed their processing 3882 14:24:37.165 [5280] (FSAUtility) <5424> EV:L CContentManagementAPI::FinalRelease() clearing SimpleStore cache 3883 14:24:37.165 [5280] (FSAUtility) <5424> EV:L CContentManagementAPI::FinalRelease() clearing ArchiveFolders cache 3884 14:24:37.165 [5280] (FSAUtility) <5424> EV:L CContentManagementAPI::FinalRelease() clearing RetCategories cache 3885 14:24:37.165 [5280] (FSAUtility) <6732> EV:L {CSecurityWrapper::UnloadAzStoreCache:#1876} Unloading authorization store cache from [D:\Program Files (x86)\Enterprise Vault\EvAzStore_Svc.xml]... 3886 14:24:37.165 [5280] (FSAUtility) <5424> EV-L {FSARestoreCommon.GetFileServerId} Get FileServer ID of \\xxxfileserver 3887 14:24:37.165 [5280] (FSAUtility) <5424> EV-L {Computer.get_SiteId} Reading from reg entry EV 3888 14:24:37.165 [5280] (FSAUtility) <5424> EV-L {FSARestoreCommon.GetFileServerId} Get all the FileServers with site id 1CBEA7C2A693EB54DABD0D2D25A4960D81d10000EVVault. 3890 14:24:37.165 [5280] (FSAUtility) <5424> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Entry [m_nNumTries = 40] 3891 14:24:37.165 [5280] (FSAUtility) <5424> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Successfully communicated with an EV Directory Service on the local machine 3892 14:24:37.196 [5280] (FSAUtility) <5424> EV:L {VaultCoCreateInstanceEx} CLSID [{4EC6FF76-C97A-11D1-90E0-0000F879BE6A}] Server Name [(null)] Used Server Name [(null)] Num of attempts [1] Total elapsed [0.000s] Result [Success (0)] 3893 14:24:37.196 [5280] (FSAUtility) <5424> EV-M {FSARestoreCommon.GetFileServerId} Found FileServer 178E15888D1DC2446B88A78301B1273071z10000EVVault. 3897 14:24:37.196 [5280] (FSAUtility) <5424> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Entry [m_nNumTries = 40]The only thing i can see is that it is complaining about a directory that is a shortcut
0% cpu for the fsautility.exe ...
Are you running FSAUtility as the vault service account (VSA) in an Admin CMD prompt?
Is the Enterprise Vault File Placeholder Service running on the file server if it is Windows?
The VSA has full control on share and NTFS level?
Error 3 is cannot find path specified.
The following can be used to check SQL for the archive folder paths for each archive.
USE EnterpriseVaultDirectory
SELECT * FROM ArchiveFolderView
WHERE ParentFolderRootIdentity is Null
AND Type = 130Regards,
Patrick
