Find In Files

[stvyrayvhn]

When trying to enable the Find In Files feature on the default repository, I'm receiving this error:
"An error occurred updating the Find in Files for some of the repositories. The request failed with HTTP status 400: Bad Request."

We are running SourceGear Vault Standard Version 6.0.1.598. Our database is SQL Server 2005 and the web server is Windows 2003 IIS6.

Steps to reproduce are below:
1. Login to the Vault Admin console
2. Select "Source Control Repositories"
3. Select "Default Repository"
4. Select "Find In Files"
5. Select "On"
6. Click "Save"

-Larry

[Beth]

Could you run the following query:

Code: Select all

select * from sgvault.dbo.tblplugins

[/size]

Then look at the URLs that are set to True. There will be one for the index service and it may look like http://127.0.0.1/vaultindexservice/vaul ... rvice.asmx and that one is true by default. You may need to switch that one to false and make the other URL listed be true, or you may need to enter in a different URL that works.

To find out what will work, try the following URLs in a browser.
http://127.0.0.1/vaultindexservice/vaul ... rvice.asmx
http://<Vault server name>/vaultindexservice/vaultindexservice.asmx
http://<Vault IP address>/vaultindexservice/vaultindexservice.asmx

[stvyrayvhn]

Beth,
THanks for your reply, I checked the settings and there were two entries for the indexservice and one was sent to true and the other was set to false. I set both entries to false, I went in and was able to check the "Find In Files" checkbox, then get prompted to select the repositories that I want to index, I select all (I've also tried just selecting one), it allows me to make the changes, then I click the "Save Default Repository" button. Everytime I go back and to see if the "Find In Files" checkbox is checked and it's not saved. No errors are displayed and I get a message that the settings have been saved.

Any thoughts?

Thanks,
Larry

[Beth]

You need at least one entry in the dbo.tblplugins for the index service set to true or it can't find the service. Try both URLs in a browser to see which one will bring up the index service page. Which one works? If neither work, then one of them should be edited to something that will work. That is why you will want to try http://<Vault server name>/vaultindexservice/vaultindexservice.asmx or http://<Vault IP address>/vaultindexservice/vaultindexservice.asmx to see if the server name or its IP address works there.

If none of those bring up the index service page, let me know.