2.0 Upgrade Error: Failed to start monitoring file changes

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
dprothero
Posts: 44
Joined: Sun Mar 21, 2004 12:18 pm
Location: Stockton California
Contact:

2.0 Upgrade Error: Failed to start monitoring file changes

Post by dprothero » Sun Mar 21, 2004 2:06 pm

I just installed the 2.0.1 server upgrade (upgrading from 1.2.3). The installation ran fine and didn't report any error messages. However, when I opened up the Admin tool, I'm getting an ASP.NET error "Failed to start monitoring file changes" (see full ASP.NET error below). I tried uninstalling and re-installing without success. I re-installed and used the Custom authentication method and had the software impersonate my Administrator account to rule out permissions issues, but it STILL gives me this error. Please help. I'm dead in the water now! - David

Server Error in '/VaultService' Application.
--------------------------------------------------------------------------------

Access denied to 'C:\inetpub\wwwroot\VaultService\VaultService.asmx'. Failed to start monitoring file changes.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Access denied to 'C:\inetpub\wwwroot\VaultService\VaultService.asmx'. Failed to start monitoring file changes.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[HttpException (0x80070005): Access denied to 'C:\inetpub\wwwroot\VaultService\VaultService.asmx'. Failed to start monitoring file changes.]
System.Web.DirectoryMonitor.AddFileMonitor(String file) +381
System.Web.DirectoryMonitor.StartMonitoringFile(String file, FileChangeEventHandler callback, String alias) +76
System.Web.FileChangesMonitor.StartMonitoringPath(String alias, FileChangeEventHandler callback) +495
System.Web.Caching.CacheDependency.Init(Boolean isPublic, Boolean isSensitive, String[] filenamesArg, String[] cachekeysArg, CacheDependency dependency, DateTime utcStart) +1535
System.Web.Caching.CacheDependency..ctor(Boolean isSensitive, String[] filenames, DateTime utcStart) +50
System.Web.Configuration.HttpConfigurationSystem.GetCacheDependencies(Hashtable cachedeps, DateTime utcStart) +144
System.Web.Configuration.HttpConfigurationSystem.ComposeConfig(String reqPath, IHttpMapPath configmap) +697
System.Web.HttpContext.GetCompleteConfigRecord(String reqpath, IHttpMapPath configmap) +434
System.Web.HttpContext.GetCompleteConfig() +49
System.Web.HttpContext.GetConfig(String name) +195
System.Web.CustomErrors.GetSettings(HttpContext context, Boolean canThrow) +20
System.Web.HttpResponse.ReportRuntimeError(Exception e, Boolean canThrow) +40
System.Web.HttpRuntime.FinishRequest(HttpWorkerRequest wr, HttpContext context, Exception e) +479




--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:; ASP.NET Version:

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Sun Mar 21, 2004 3:38 pm

I tried uninstalling and re-installing without success
let's start at the beginning...

1) un-install (keeping your database)
2) install the server (keeping your database).

how does it fail? error message? there should be a vault_install.log file. can you rename the extension to .txt, and send it to me?
Jeff Clausius
SourceGear

grennis
Posts: 3
Joined: Wed Aug 18, 2004 6:42 pm

Post by grennis » Sun Aug 29, 2004 10:27 am

I am also getting this error. The only thing weird about my setup is that the server is also a domain controller. Because of this I also had to use custom web.config identity. However, it seems to miss something during the setup because it APPEARS to not give the account permissions to do a FileSystemWatcher on that folder. I am still trying to figure it out. Anybody have any ideas?

grennis
Posts: 3
Joined: Wed Aug 18, 2004 6:42 pm

Post by grennis » Sun Aug 29, 2004 11:32 am

Wow, this error has nothing to do with Sourcegear Vault. I eventually tracked down the cause, which is that Win2000 DC's with SP4 installed do not allow impersonation by the IWAM account!

This fixed the problem:

http://support.microsoft.com/default.as ... -us;824308

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Sun Aug 29, 2004 8:57 pm

Thanks for the feedback. I'm glad you're up and running.
Jeff Clausius
SourceGear

Post Reply