I upgraded Vault from 5.x to 6 a couple of days ago and have been unable to turn Find in Files on within any repository that I've tried. It always returned the following error when selecting On and clicking Save.
An error occurred updating the Find in Files for some of the repositories. The underlying connection was closed: An unexpected error occurred on a receive.
Find in Files Status - OASIS Repository
On
Suspend
Off
Purge Index data
Note, if you purge the Find In Files Index data and subsequently re-enable Find In Files, re-indexing the repository may take longer to complete.
Status Msg:
Vault 6 Find in Files failing on upgrade from 5.x
Moderator: SourceGear
Re: Vault 6 Find in Files failing on upgrade from 5.x
Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread and the following server log files?
Vault server log found at %windir%\temp\sgvault\sgvault.log
Vault index log found at %windir%\temp\sgvaultindex\vaultindexservice.txt
Vault server log found at %windir%\temp\sgvault\sgvault.log
Vault index log found at %windir%\temp\sgvaultindex\vaultindexservice.txt
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 6 Find in Files failing on upgrade from 5.x
We are having the same problem and it appears that the web application automatically assumes that the asmx is available at the 127.0.0.1 loopback. Which is not the case for our server. The vault service runs on a secondary host entry on the server and not under the main listening site. Is it possible to change where the service is looking to? E.g. give it a full URL instead of 127.0.0.1
Here is the error from the logs:
---11/26/2012 8:21:18 AM User--Host IP(Host IP)--SSL Enabled An error occurred updating the Find in Files on http://127.0.0.1:443/VaultIndexService/ ... rvice.asmx for Repository Repository. The underlying connection was closed: An unexpected error occurred on a receive.
Inner Exception: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Inner Exception: An existing connection was forcibly closed by the remote host
Which makes perfect sense, since 127.0.0.1:443 is not the vault web site.
Here is the error from the logs:
---11/26/2012 8:21:18 AM User--Host IP(Host IP)--SSL Enabled An error occurred updating the Find in Files on http://127.0.0.1:443/VaultIndexService/ ... rvice.asmx for Repository Repository. The underlying connection was closed: An unexpected error occurred on a receive.
Inner Exception: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Inner Exception: An existing connection was forcibly closed by the remote host
Which makes perfect sense, since 127.0.0.1:443 is not the vault web site.
Re: Vault 6 Find in Files failing on upgrade from 5.x
Nevermind we were able to find this http://support.sourcegear.com/viewtopic ... les#p72397
Which gave us enough information to get it solved.
Which gave us enough information to get it solved.
Re: Vault 6 Find in Files failing on upgrade from 5.x
Thanks for the update.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support