Unhandled exception on get labelled version

[shipcreak]

Ensure this is a "clean get", i.e. there is no code locally before you start.

1) Open SOS client.
2) Navigate to project.
3) Right-click in project tree, select Show History....
4) On Project History Options, leave default selections and click OK.
5) On History dialog, highlight labelled version.
6) Click Get.
7) On Get Project by Label dialog, select Recursive and click OK.

Expect
All files to be downloaded for the labelled version.

Actual
SOS client crashes with JIT dialog (see attachment). Nothing recorded at all in the event log.

Additional Notes
I've noticed that app.config is always the last file in the status window (it's a .net 2.0 app), although looking at the filesystem it's there, so I think it's whatever the next file would be that's causing the problem. However, that's another copy of app.config (with some different settings for release builds). Most files that are downloaded appear to be either "Renegade" or "Needs Merge". Retrying the operation after this crash runs desperately slowly, I haven't waited long enough to see if it crashes at the same point - I've got other things to do.

This is the result of using VSS Analyze:

Analyze Visual SourceSafe Version 6.0d (Build 9848)
Database analysis in progress @ 2/08/07;12:32.
Analysis complete @ 2/08/07;12:32
No errors or inconsistencies found.

Can anyone help?

[Beth]

In order to tell what's happening, I'll need a bit more information. Can you send me an SOS server log? SourceOffSite log file (log.txt) is located on the machine where the SOS server resides in this path C:\Program Files\SourceOffSite Server. Also, it may help if you can increase the log level: Debug and Method Logging.

You can either post that here or zip it up and email it to support at sourcegear.com (attn: Beth) with a link to this forum post.

[shipcreak]

I enabled the options mentioned, and have attached the file.

I'm the only person working on this actual project at this time.

[Beth]

Can you tell me the approximate time that you tried the get by label and it failed?

You have a lot of network closings going on and that's not really good either. That's often caused by routers resetting connections or ports being allowed to close after a command goes through.

[Beth]

Also, I think we may need to look closer at this one. Can you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

[shipcreak]

I'm afraid it's not a timing issue or network traffic issue as it happens consistently and every time, with absolutely no relation to time of day or anything like that.

Not really sure what to do next?

[Beth]

I still need to know the time I should look at for when the fail happened. Otherwise, I'm just guessing at whether an error pertains to that or not.

Also, then send an email to support.

[shipcreak]

Ahh, I see what you mean. I took the file immediately after the fail, so if there's anything useful it should be at the bottom of the file. Quite literally the last few lines.