SourceGear Support

Just thought I'd update this: We have just managed to resolve this... We eventually noticed a series of Warnings and Errors in the Windows 'System' logs. The most informative of these was this one: The identity of application pool VaultAppPool is invalid. The user name or password that is specified ...

on its' way.

No Recycling is set, pretty default setup.

browser also returns:

Service Unavailable
HTTP Error 503. The service is unavailable.

Where do I find the log you would like to see?

Thanks,

-- Peter.

Hi, We had a long overdue windows update on our vault server this morning. Once the server came back online we can no longer access our Repository. It consistently fails with the following error: Unable to connect to http://dbserver01/VaultService. No server was found at the specified URL. Please ve...

problem solved...

was a password issue with the account i'd set it up to run under.

all seems ok for now.

thanks for looking

-- Peter.

Hi, We have been using Vault 5 for a number of years without issue. Unfortunately the server on which it is on is at end of life and slowly dying. We have therefore built a new server and purchased Vault 8. I restored the vault database onto the new server (Windows Server 2012 R2 Standard with SQL S...

Thanks to Linda for the help yesterday. The local folders populated fine after your help. Unfortunately the remote ones still didn't want to play. This time for a different error though and it was permissions again, so I did a search to reset it all up, following: This thread this knowledgebase howe...

It looks like the Shadow Folder service may be having a problem updating the files in the shadow folder because it can't determine the status of the files. What version of Vault are you using? What OS is Vault installed on? Are there any errors in the Vault Server log that correspond to the failure...

Hi, After a change of NAS drive last year our Shadow Folders haven't been working. I initially thought it was just permissions, but that's been sorted (I think). All we get in the Shadowfolder service log file is the following: 10/04/2013 17:35:16 <generic>: [<No Name>:5548] Vault's Shadow Folders a...

now that was this morning - we fiddled alot and turns out it was database permissions on the loads of stored procedures and tables...

fixed now...

although the shadow folders aren't working correctly but that's a problem for another day now - hey ho.

Hi, Yesterday we attempted to turn on Shadow Folders (which we thought were already setup but weren't).. The complication being that we want to use UNC naming to put the shadow folders on a different server which gets backed up regularly. I was following the instructions found elsewhere on the about...