I finally got the Shadow folder to work, sort of. Vault created 190 folders and 135 files in the Shadow folder. Unfortunately there are 345 folders and 12,150 files in the repository.
Vault 2.0.6 and SQL 2000 are on their own identical servers: dual Xeon 3.06GHz, 2 GB of RAM, Windows 2003
They are on the same sub-net and don't have firewalls or anti-virus.
VaultShadowFolderService.txt and the Event Viewer show nothing but
sgvault.log contained the following:
----11/4/2004 10:01:51 AM [me]--[myIP]--SSL Disabled
Critical Error downloading file! Thread was being aborted.
at System.Web.UnsafeNativeMethods.EcbFlushCore(IntPtr pECB, Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Int32 kernelCache, Int32 async, ISAPIAsyncCompletionCallback asyncCompletionCallback)
at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async)
at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal)
at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush)
at System.Web.HttpResponse.Flush(Boolean finalFlush)
at System.Web.HttpWriter.WriteFromStream(Byte[] data, Int32 offset, Int32 size)
at System.Web.HttpResponseStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.BufferedStream.Write(Byte[] array, Int32 offset, Int32 count)
at VaultServiceSQL.VaultSqlSCC.GetDeltaChainForFullFile(VaultSqlConn conn, Int32 nUserID, Int64 nObjVerID, Int32 nBufSize, String strFileToken, Stream s)
at VaultServiceAPILib.VaultDelta.CreateFullFile(VaultSqlConn vsConn, Int32 nUserID, Int32 nRepID, Int64 nObjVerID, String strFileToken, Boolean& deltaIfAvailable, Stream sFullFileStream)
at VaultServiceAPILib.VaultDelta.DeltaCreate(VaultSqlConn vsConn, Int32 nUserID, Int32 nRepID, Int64 nBaseObjVerID, Int64 nTargetObjVerID, String strFileToken, Stream sDeltaStream)
at VaultServiceAPILib.VaultServiceAPI.GetVaultFile(Int32 nUserID, Int32 nRepID, VaultIntDnldItem& vidi, String strFileToken, Stream s)
at VaultService.VaultFileDownload.Page_Load(Object sender, EventArgs e)
----11/4/2004 10:01:51 AM [me]--[myIP]--SSL Disabled
Thread was being aborted.
----11/4/2004 10:37:48 AM [me]--[myIP]--SSL Disabled
Exception in plugin thread : The request failed with HTTP status 400: Bad Request.
----11/4/2004 1:21:02 PM [me]--[myIP]--SSL Disabled
Exception in plugin thread : The request failed with HTTP status 400: Bad Request.
Vault shadow folders largely failed
Moderator: SourceGear
It appears as the Vault server cannot contact your VaultShadowFolder web service.
Does your IIS server contain a virtual directory named VaultShadowFolder, which maps to the physical <VAULT SERVER INSTALL>\VaultShadowFolder (eg: c:\inetpub\wwwroot\vaultservice\vaultshadowfolder ).
Is it possible the virtual directory is corrupt. Sometimes deleting / re-creating the virtual directory ( mapping it to VaultShadowFolder ), solves the problem.
Does your IIS server contain a virtual directory named VaultShadowFolder, which maps to the physical <VAULT SERVER INSTALL>\VaultShadowFolder (eg: c:\inetpub\wwwroot\vaultservice\vaultshadowfolder ).
Is it possible the virtual directory is corrupt. Sometimes deleting / re-creating the virtual directory ( mapping it to VaultShadowFolder ), solves the problem.
Jeff Clausius
SourceGear
SourceGear
Thanks for the quick reply! I tried deleting and recreating it a couple of times and got a different number of files and folders every time. I moved Vault to the same server as SQL and everything seems to be working perfectly. Neither server was on a domain so I wonder if that was an issue. Thanks for your help!jclausius wrote:It appears as the Vault server cannot contact your VaultShadowFolder web service.
Does your IIS server contain a virtual directory named VaultShadowFolder, which maps to the physical <VAULT SERVER INSTALL>\VaultShadowFolder (eg: c:\inetpub\wwwroot\vaultservice\vaultshadowfolder ).
Is it possible the virtual directory is corrupt. Sometimes deleting / re-creating the virtual directory ( mapping it to VaultShadowFolder ), solves the problem.