Can't enable "Find in Files" on my repositories

[marct]

Hi,

I am getting this error when trying to enable Find in Files (indexing) from Vault Admin web site:

An error occurred retrieving repository Find In File information. An error occurred updating the Find in Files for some of the repositories. The request failed with HTTP status 403: Forbidden.

I have two repositories: the initial repo (which I use for testing stuff) and our "official" repository we manage our production codebase with. Both exhibit the same problem.

Any help in resolving this appreciated.
Marc-Andre

[Beth]

What URL does it appear to be trying to get to?

Run the following query against your SQL database and check the results.

select * from sgvault.dbo.tblplugins

That will give you the URLs that is used for the Find in Files. Try the URLs for the index service in a web browser to see if they all work or if they fail.

The URL should look something like http://<your Vault server>/vaultindexservice/vaultindexservice.asmx

[marct]

Hi Beth,

I ran the SQL script and got 5 rows. Most interesting were the 'duplicated' rows for IndexService and NotifyService. For each, I have 1 row pointing to 10.0.0.201 (the server were Vault is installed) but the "active" column indicates 0 for some reason. The other row points to 127.0.0.1 with active = 1.

I deduct Vault is using only rows where active=1 to get its URLS, so it's taking the 127.0.0.1 URL. Pasting this on a browser (obviously from a session on the Vault Server, not on my workstation) returns a 403.1 Forbidden saying the Execute permission is not allowed.

I gave a shot with the 10.0.0.201 URL instead and these work fine in the web browser... I'm guessing I would simply need to change the "active" column accordingly and it should work?

What do you recommend doing?

Thanks
Marc-Andre

[Beth]

I

would simply need to change the "active" column accordingly and it should work?

You're right. Give that a try first.

[marct]

Hi Beth,

Switching the "active" column lead me to a different error. I was getting an ASP.net configuration error when trying to activate indexing, which led me back to the tblplugins contents and it is then I noticed the difference was more than just the IP address:

10.0.0.201 had different path such as 10.0.0.201/VaultService/VaultIndexService/VaultIndexService.asmx
whereas 127.0.0.1 was formatted as : 127.0.0.1/VaultIndexService/VaultIndexService.asmx

The path that will actually work, based on how the installer set the application/app pool bindings on IIS would be:
http://10.0.0.201/VaultIndexService/Vau ... rvice.asmx

SO I restored the "active" the way it was initially, and updated the URL to change any 127.0.0.1 to 10.0.0.201 and it seems to work without errors now. I still don't see Indexing as active but as noted by the admin tool "it may take a while before you see this screen changed" so I will be patient and see how it goes...

Thanks,
Marc-Andre

[Beth]

Thanks for the update.