Source Vault Issues as Virtual Directory

[brianjlowry]

I have Vault up and running fine on a Windows XP box. I have IIS 5.1 and am trying to set up Vault as a Virtual Directory. I use a JetStat tool XP Pro IIS Admin that allows me to create multiple websites for development. If I set up Vault on the default website, all goes well, but with IIS 5.1, you can only have one website running at a time.

What I am trying to accomplish is have Vault set up as a Virtual Directory to each of the websites so that when I am working on one of them, I can always hit Vault.

It also appears that if I reinstall Vault choosing one of the other websites, then the webservice doesn't work correctly.

Any ideas?

Thanks in advance,
Brian

[brianjlowry]

By the way... i have Vault 3.1.9. Also, I am getting a 403.1 error when trying to connect to VaultService.asmx, but the ServerInstall.html comes up fine.

Thanks.

[lbauer]

Here are a couple of posts which report a 403 error -- perhaps they can help:

http://support.sourcegear.com/viewtopic.php?t=6223
http://support.sourcegear.com/viewtopic.php?t=6555

What I am trying to accomplish is have Vault set up as a Virtual Directory to each of the websites so that when I am working on one of them, I can always hit Vault.

We don't support multiple instances of Vault hitting one database. It can lead to corruption since there's no "regulator" for transactions.

[brianjlowry]

Thank you. I actually figured out the problem moments after my post, only to run in to another issue with multiple web.config in the virtual directory and my application.

I ended up doing away with the JetStat setup and went back to the single website method.

Thanks for the help,
Brian