Vault 9.1: Find in Files Feature Not Working

[ejhansen71]

I am trying to turn on the "Find in Files" and we are running into issues and hope you can help. Below is the conversation between Steve Young and me. (Most recent first)

-------------------------------------------------
4. Steve: I checked the log again, same errors. I checked the web.config files, and the passwords match. I verified that the IndexAppPool restarted when IIS restarted. Sounds like we need Beth to help.
-------------------------------------------------
3. Eric: Still automatically switching off.
-------------------------------------------------
2. Steve: According to http://support.sourcegear.com/viewtopic.php?f=5&t=22575, a password in the config files must match and may not for some reason.

I changed the password in the Index Service web.config to match what was in the Shadow web.config, and did an IISRESET, as mentioned in that thread. Any way you can test the Find in Files feature now?
-------------------------------------------------
1. Steve: The Index Server Log file (as I have found) is on GHVAULT1 at C:\Windows\Temp\SGVaultIndex\Vaultindexservice.txt.

Here is what it says:

2/28/2016 4:37:16 PM <generic>: SourceGear Index Service started.
2/28/2016 4:37:16 PM <generic>: Failed to retrieve login information for the Vault Server. The Find In Files Index Server may not be able to contact the Vault Server for repository information. [VaultLib.VaultCryptoException: Bad Data.

at VaultLib.VaultCrypto.Decrypt(String strBase64Buf)
at VaultIndexService.VaultIndexManager.GetVaultPluginLoginInfo(String& strVaultServer, String& strLogin, String& strPlainPassword)] Bad Data.

at VaultLib.VaultCrypto.Decrypt(String strBase64Buf)
at VaultIndexService.VaultIndexManager.GetVaultPluginLoginInfo(String& strVaultServer, String& strLogin, String& strPlainPassword)

2/28/2016 5:11:20 PM <generic>: SimpleLogger finalized
2/28/2016 5:38:45 PM <generic>: GetEntryAssembly() returned null; not logging assembly name
2/28/2016 5:38:45 PM <generic>: SourceGear Index Service started.
2/28/2016 5:38:45 PM <generic>: Failed to retrieve login information for the Vault Server. The Find In Files Index Server may not be able to contact the Vault Server for repository information. [VaultLib.VaultCryptoException: Bad Data.

at VaultLib.VaultCrypto.Decrypt(String strBase64Buf)
at VaultIndexService.VaultIndexManager.GetVaultPluginLoginInfo(String& strVaultServer, String& strLogin, String& strPlainPassword)] Bad Data.

at VaultLib.VaultCrypto.Decrypt(String strBase64Buf)
at VaultIndexService.VaultIndexManager.GetVaultPluginLoginInfo(String& strVaultServer, String& strLogin, String& strPlainPassword)

3/3/2016 6:26:32 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:26:36 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:26:40 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:26:44 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:26:44 PM <generic>: The Find In Files Index Server could not obtain a client connection to the Vault server. Rep ID 6 will not be indexed.
3/3/2016 6:27:24 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:27:28 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:27:32 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:27:36 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:27:36 PM <generic>: The Find In Files Index Server could not obtain a client connection to the Vault server. Rep ID 6 will not be indexed.
3/3/2016 6:28:10 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:28:14 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:28:48 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:29:22 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 6. The username or password supplied is invalid.
3/3/2016 6:29:22 PM <generic>: The Find In Files Index Server could not obtain a client connection to the Vault server. Rep ID 6 will not be indexed.
3/3/2016 6:30:06 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 5. The username or password supplied is invalid.
3/3/2016 6:30:40 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 5. The username or password supplied is invalid.
3/3/2016 6:31:14 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 5. The username or password supplied is invalid.
3/3/2016 6:31:48 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 5. The username or password supplied is invalid.
3/3/2016 6:31:48 PM <generic>: The Find In Files Index Server could not obtain a client connection to the Vault server. Rep ID 5 will not be indexed.
3/3/2016 6:32:31 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 5. The username or password supplied is invalid.
3/3/2016 6:33:05 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 5. The username or password supplied is invalid.
3/3/2016 6:33:40 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 5. The username or password supplied is invalid.
3/3/2016 6:34:14 PM <generic>: Could not contact the server at https://GHVault1.healthds.com/VaultService for repository id 5. The username or password supplied is invalid.
3/3/2016 6:34:14 PM <generic>: The Find In Files Index Server could not obtain a client connection to the Vault server. Rep ID 5 will not be indexed.

[Beth]

You're looking in the right area.

In the Vault admin web page, expand Source Code Repositories and then a repository name. Click on Shadow folders to see if it works, or maybe even try to make a tiny test one. If you get a failure, that means that one also has an incorrect password.

[ejhansen71]

Beth - I tried to add a shadow folder setup and got the error you said would happen. I sent the info to Steve

From Steve:

"The forum answer was to copy the password from the Shadow Folder web.config file to the Index Service web.config, which is what I did. Does this mean that both of them were incorrect?

I’m assuming the password is the password of the Vault Standard Admin account? Is there a tool or way I can encrypt that password and then re-paste it in both of those web.config files, without reinstalling the software? I did run the installer as an admin, which is what Beth said would fix it in that forum post…"

[Beth]

Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?