Erroneous Merge on Share - Causes Failure

gadzuk · Post by **gadzuk** » Mon Apr 26, 2004 12:01 pm

We're evaluating SOS 4.0 (server config is Win2k SP4, SrcSafe 6.0c). Standard Edition (no encryption).

4/21/2004 2:57:16 PM - Server Information
4/21/2004 2:57:16 PM -     Operating System: Microsoft Windows 2000 Server
4/21/2004 2:57:16 PM -     Service Pack: 4.0
4/21/2004 2:57:16 PM -     OS Version: 5.0.2195
4/21/2004 2:57:16 PM -     Locale: Ox0409
4/21/2004 2:57:16 PM -     OSLanguage: 1033
4/21/2004 2:57:16 PM -     Total Physical Memory: 253.43 MB
4/21/2004 2:57:16 PM -     Time Zone: (GMT-07:00) Mountain Time (US & Canada)
4/21/2004 2:57:16 PM - 
4/21/2004 2:57:16 PM - SSAPI.dll Information:
4/21/2004 2:57:16 PM -     Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
4/21/2004 2:57:16 PM -     DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null

When I attempt to Share a project folder (about 10 sub-folders, with 200 source files), the share aborts after prompting me to "Merge" (because status is unknown). I've tried choosing Overwrite, but the Share still fails.

The server-side log says

Code: Select all

4/21/2004 5:26:40 PM - 	The process cannot access the file "DabsBootleg.mdl.z" because it is being used by another process.
4/21/2004 5:26:40 PM - Connection accepted from 10.21.9.2:4042, session id is 5.
Send failed: An existing connection was forcibly closed by the remote host
4/21/2004 5:28:47 PM - 5: Exception: An existing connection was forcibly closed by the remote host
4/21/2004 5:28:47 PM - 5: Error removing user temp folder 'C:\Program Files\SourceOffSite Server\temp\cunningh632181652010234375'.

Seems to run fast, just doesn't seem to work

On a related note: When I'm attempting this Share (we're cutting an as-built project folder to snapshot what we've done so far), the shared files are copied to my hard disk workspace. I realize that this simply emulates what the stock SourceSafe would do, but would have hoped that SourceOffSite could do this operation totally server-side.

Questions:

What can I do to fix SOS's perceived sharing violation on this file?

gadzuk · Post by **gadzuk** » Fri Apr 30, 2004 12:44 pm

We have two weeks to conclude our evaluation, any thoughts at all?

corey · Post by **corey** » Fri Apr 30, 2004 2:15 pm

Is the DabsBootleg.mdl.z file the same one that you're being prompted on to merge? Does that error in the log coincide with the time you were doing the share?

Are you trying to share to a location where all of the files currently exist in the working folder on your local machine?

gadzuk · Post by **gadzuk** » Fri Apr 30, 2004 4:03 pm

Hi Corey,

When I begin, the location that I'm sharing TO does not yet exist on my hard disk, only in SOS / SourceSafe.

I start by creating a new project folder in SOS (representing a particular released version of my software that I want to keep frozen).

I then go to that new (empty) project folder and share my existing software recursively into that folder.

The system then runs off and starts sharing (copying) folders and subfolders recurseively to the new location and stops on this file (DabsBootleg.mdl, don't know where the ".z" comes from).

And yes, the time the server log matches the time that I had the problem.

If I delete all the files from the target folder in SOS, and restart the process it will continue past DabsBootleg.mdl and then choke on another file (again, it thinks it has to merge something, but there's no *^%^* files on my hard disk so what's it think it's "merging" with).

Hope that helps ;-`)

Peter

corey · Post by **corey** » Mon May 03, 2004 8:15 am

The SOS Client wouldn't prompt to merge a file unless a copy already exists in the location where its trying to write the new file. If its of Unknown status, then perhaps files were left there after the first unsuccessful share?

You may have temp directories that need to be removed from the server by hand. Stop your Server, then go to your SOS Server installation folder and remove the "temp" folder, and then restart your Server.

Also, before restarting your Server, enable verbose logging by following the instructions at:

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

Then retry the share and if it again fails, email to me your entire log file from the server.

gadzuk · Post by **gadzuk** » Mon May 03, 2004 10:21 am

I've stopped the server, removed everything from my hard drive, turned on verbose logging, cleaned up the temp file on the server, and restarted the server.

I create a new project folder in SOS, then do a share (recursive yes, branch no). I can also reproduce the error when "recursive = no".

The client almost immediately comes back with "An unknown error occurred while accessing "C:\Users\Peter\DABS\Dabs3.30b\Program\BXL Interface\BXL_LINK.MDB". I tried this twice, creating a brand new target SOS folder each time.

I don't have your email address so I'll attach the server log .

My email address is peter_cunningham@elkvalleycoal.ca

gadzuk · Post by **gadzuk** » Thu May 27, 2004 2:35 pm

Thanks to tech support, the solution turned out to be for us to turn off compression on the client-side.

We've now reproduced the problem with 4.0.1 professional. If no one else is having this problem, I'm left wondering which DLL or registry setting is causing this.

Good news is that there appears to be no significant performance hit without compression. We have a fast (10 Mb/s) WAN, but the 50ms latency was making MS SourceSafe take forever.