VaultIndex Service

[hwapdc]

Hi
I see these errors in vaultindexservice.txt.
Users can do check-in and out.
Would it be adviseable to disable indexing for this repository, purge data and enable indexing.
It's OK if it takes all weekend.


07-02-2014 00:26:48 <generic>: GetEntryAssembly() returned null; not logging assembly name
07-02-2014 00:26:48 <generic>: SourceGear Index Service started.
07-02-2014 00:26:50 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 11:05:19 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 11:36:49 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 11:44:14 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 11:48:24 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 12:54:59 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 12:58:49 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 13:08:49 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 13:09:39 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 14:24:19 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 14:28:06 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 14:28:08 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 14:40:36 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 14:57:44 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 15:17:53 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 15:24:09 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 15:44:49 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 15:46:14 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 15:47:34 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 15:51:17 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 16:07:57 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 16:08:21 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 16:13:29 <generic>: SimpleLogger finalized
07-02-2014 16:17:37 <generic>: GetEntryAssembly() returned null; not logging assembly name
07-02-2014 16:17:37 <generic>: SourceGear Index Service started.
07-02-2014 16:20:38 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 16:21:08 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 16:22:32 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 16:32:02 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 16:37:31 <generic>: During an UPDATE work request, it was detected the database is in an unknown state. Find in Files Indexing for repository "Aviation" (5) will be out of date.
07-02-2014 16:41:14 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 16:42:30 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.
07-02-2014 16:43:06 <generic>: The Find In Files Index Server halted processing due to too many errors. Rep ID 5's index is out of date. After fixing the problem that caused the errors, turn off Find in Files indexing (do not purge the data), and then turn it back on.

Vault Information
---07-02-2014 16:13:51 sgvaultsystem--()--
System Started
Version 7.1.0.2028
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = E:\SourceGear\sgVault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 10080
SGVault Working Directory = C:\Windows\Temp
SGVault Server URL = vault.pdc.xx
Identity = PDC\sa sgvault

[Beth]

Would it be advisable to disable indexing for this repository, purge data and enable indexing.

That's the first thing to try. If it still has issues after that, just let me know.

[hwapdc]

Thnx. The vaultindexservice.txt now contains:

2014 18:03:32 <generic>: Started index build for repository "5"
07-02-2014 18:30:31 <generic>: An error occurred retrieving the files in "....xyz........" for repository "5". Some of the versions for the following files may not be searchable. [System.NullReferenceException: Object reference not set to an instance of an object.
at VaultClientOperationsLib.ClientInstance.ProcessFile_NonWorkingFolder(String tempFile, VaultClientFile file, VaultResponseGetFile response, String ancestorFullPath, String ancestorDiskPath, SetFileTimeType setFileTime, MakeWritableType makeWritable, MergeType merge, OverwritePrompt PromptData)
at VaultClientOperationsLib.ClientInstance.ProcessGetFileRequests(GetFileInfo[] infos, MakeWritableType makeWritable, SetFileTimeType setFileTime, MergeType merge, Boolean updateHiddenFilesOnly, String ancestorFullPath, Boolean flat, String ancestorDiskPath, OverwritePrompt PromptData, Boolean isLabelGet, String currentPathToLabelItem, Int64 labelID, Boolean isRetry, Boolean isGetByDisplayVersion)
at VaultClientOperationsLib.ClientInstance.GetToNonWorkingFolder(VaultClientFile[] files, Boolean forceLatest, Boolean overwrite, MakeWritableType makeWritable, SetFileTimeType setFileTime, String ancestorFullPath, String ancestorDiskPath, OverwritePrompt PromptData)
at VaultIndexService.IndexServiceProcessWorkerThread.GetAndProcessFolderFileList(VaultIndexManager vim, Boolean bLoggingFileList, PluginRepositoryConnection repConn, ObjVerIDToUpdateIndexDeltaItem hashModifiedFiles, PluginFolder folder, String strRepPath, SortedList`2 listFiles, String strTempThreadPath, String strTempFolderPath, String strTempPath)] Object reference not set to an instance of an object.
at VaultClientOperationsLib.ClientInstance.ProcessFile_NonWorkingFolder(String tempFile, VaultClientFile file, VaultResponseGetFile response, String ancestorFullPath, String ancestorDiskPath, SetFileTimeType setFileTime, MakeWritableType makeWritable, MergeType merge, OverwritePrompt PromptData)
at VaultClientOperationsLib.ClientInstance.ProcessGetFileRequests(GetFileInfo[] infos, MakeWritableType makeWritable, SetFileTimeType setFileTime, MergeType merge, Boolean updateHiddenFilesOnly, String ancestorFullPath, Boolean flat, String ancestorDiskPath, OverwritePrompt PromptData, Boolean isLabelGet, String currentPathToLabelItem, Int64 labelID, Boolean isRetry, Boolean isGetByDisplayVersion)
at VaultClientOperationsLib.ClientInstance.GetToNonWorkingFolder(VaultClientFile[] files, Boolean forceLatest, Boolean overwrite, MakeWritableType makeWritable, SetFileTimeType setFileTime, String ancestorFullPath, String ancestorDiskPath, OverwritePrompt PromptData)
at VaultIndexService.IndexServiceProcessWorkerThread.GetAndProcessFolderFileList(VaultIndexManager vim, Boolean bLoggingFileList, PluginRepositoryConnection repConn, ObjVerIDToUpdateIndexDeltaItem hashModifiedFiles, PluginFolder folder, String strRepPath, SortedList`2 listFiles, String strTempThreadPath, String strTempFolderPath, String strTempPath)

Many entries like
07-02-2014 18:30:31 <generic>: In repository "5", "...<repository ... file>.." was not retrieved, and could not be added to the index.

Do we have a problem with the internal structure?
The SQL databases are check for consistency every day.

[Beth]

I'm going to have you turn off the indexing again. Make sure you select the option to purge the index.

Next, on the Vault server go to C:\Windows\temp\sgvaultindex\cache. Inside the cache folder you will find folders with long GUIDs on them. Delete each folder that has a GUID.

Then start up the indexing again and wait until it says it's ready.

What are your results?

[hwapdc]

Just returned from vacation I see this in VaultIndexService.txt - I guess it translates to everything is OK.

08-02-2014 23:29:02 <generic>: SimpleLogger finalized
09-02-2014 00:23:03 <generic>: GetEntryAssembly() returned null; not logging assembly name
09-02-2014 00:23:04 <generic>: SourceGear Index Service started.
09-02-2014 23:29:02 <generic>: SimpleLogger finalized
10-02-2014 00:06:46 <generic>: GetEntryAssembly() returned null; not logging assembly name
10-02-2014 00:06:46 <generic>: SourceGear Index Service started.
10-02-2014 23:29:02 <generic>: SimpleLogger finalized
11-02-2014 00:32:50 <generic>: GetEntryAssembly() returned null; not logging assembly name
11-02-2014 00:32:50 <generic>: SourceGear Index Service started.
11-02-2014 23:29:02 <generic>: SimpleLogger finalized
12-02-2014 00:37:07 <generic>: GetEntryAssembly() returned null; not logging assembly name
12-02-2014 00:37:07 <generic>: SourceGear Index Service started.
12-02-2014 23:29:02 <generic>: SimpleLogger finalized
13-02-2014 00:46:26 <generic>: GetEntryAssembly() returned null; not logging assembly name
13-02-2014 00:46:26 <generic>: SourceGear Index Service started.
13-02-2014 23:29:02 <generic>: SimpleLogger finalized
14-02-2014 00:28:02 <generic>: GetEntryAssembly() returned null; not logging assembly name
14-02-2014 00:28:02 <generic>: SourceGear Index Service started.
14-02-2014 23:29:02 <generic>: SimpleLogger finalized
15-02-2014 00:22:50 <generic>: GetEntryAssembly() returned null; not logging assembly name
15-02-2014 00:22:50 <generic>: SourceGear Index Service started.
15-02-2014 23:29:03 <generic>: SimpleLogger finalized
16-02-2014 00:47:59 <generic>: GetEntryAssembly() returned null; not logging assembly name
16-02-2014 00:47:59 <generic>: SourceGear Index Service started.
16-02-2014 23:29:02 <generic>: SimpleLogger finalized
17-02-2014 00:32:01 <generic>: GetEntryAssembly() returned null; not logging assembly name
17-02-2014 00:32:01 <generic>: SourceGear Index Service started.
17-02-2014 15:46:42 <generic>: SimpleLogger finalized
17-02-2014 15:53:09 <generic>: GetEntryAssembly() returned null; not logging assembly name
17-02-2014 15:53:09 <generic>: SourceGear Index Service started.

[Beth]

Looks good. Thanks for the update.