Possible way to duplicate duplicate project entries

[2cbtaylor]

I just had duplicate project entries for the second time. I am not sure, but I believed that project lead couldn't fix the problem the first time around by deleting C:\Documents and Settings\MyUserName\Application Data\SourceGear\SOS\servers\172016196024\database1.sos.

When this failed, he just merely renamed the the servers subdirectory which forced a rebuild of the project tree.

This bug just happened again, this might be a way to duplicate the problem and thus fix it.

SourceOffSite was previously successfully opened earlier in the day via a VPN connection to my company. The VPN connection was closed, without closing SourceOffSite. This afernoon, not noticing that an instance of SourceOffSite was already opened, I logged in to VPN and created another instance of SourceOffSite. I immediately noticed a duplicated project tree. Remember that we had to rename the directory last time, I closed all instances, renamed the directory, and then created a new instance of SourceOffSite. The application subsequently went about refreshing the project tree, but this time without any duplicates.

Hopefully this will give the SourceGear developers some chance of duplicating the problem and thus fixing it.

Cheers,
Carl in Suwanee GA
gocbt@yahoo.com >> what I use when I expect a lot of spam

[lbauer]

Thanks for the information. I'll include it in the bug report for bug 13863.

[BrianDrab]

Can I get verification that this is still a known bug. If it is, is there a scheduled release date yet?

Thank you.

[jclausius]

Brian:

We will be addressing this in the upcoming SourceOffSite 5.0 release. Also note, we are looking for people to test a "SourceOffSite 5.0 Preview" which will be available in the upcoming months. Any parties interested in testing/using the preview should mail "sosbeta AT sourcegear DOT com".

Thanks.

[BrianDrab]

Can you verify for me that this is now fixed in the current version? Before I upgrade I would like to know.

Thanks.

[lbauer]

This bug has been fixed in SOS 5.0.