Two Default Repositories...neither have correct files :-(

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

Moderator: SourceGear

Post Reply
dweller
Posts: 8
Joined: Wed Jul 28, 2004 9:09 pm
Location: Redmond
Contact:

Two Default Repositories...neither have correct files :-(

Post by dweller » Wed Oct 20, 2004 10:55 am

I just upgraded to 2.0.6. When I log in, I'm presented with two default repositories. The choices say:
Revision 243, 1599 files, 57 folders
Revision 234, 1599 files, 57 folders

However, the folder list only shows 4 folders and about 80 files when I pick either repository.

This is colossally ungood :(

Any suggestions on what might be wrong? I'm on a short release deadline now and I can't (apparently) get to my files. Hopefully somebody here will point out that I'm doing something stupid or some such. Hopefully.

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Wed Oct 20, 2004 11:32 am

Did you upgrade to the 2.0 framework?

dweller
Posts: 8
Joined: Wed Jul 28, 2004 9:09 pm
Location: Redmond
Contact:

Post by dweller » Wed Oct 20, 2004 2:25 pm

I have the 2.0 Fx on that machine, but I'm also running the 1.1 Fx as well. Is there something I should do to make sure Vault only runs with the 1.1 version?

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

Post by jclausius » Wed Oct 20, 2004 2:50 pm

Was the 2.0 .Net Fx installed when you started using Vault or did you just install it recently?

If you recently installed the 2.0 .Net Fx, do you have a backup of your Vault database before 2.0 .Net Fx was installed?
Jeff Clausius
SourceGear

dweller
Posts: 8
Joined: Wed Jul 28, 2004 9:09 pm
Location: Redmond
Contact:

Post by dweller » Wed Oct 20, 2004 4:47 pm

Hmm...I rebuilt the system a couple of months ago...the sequence probably was: Install Fx 1.1, install Vault, Install Fx 2.0. However, I'm old, and my memory doesn't serve me well :-)

And, I do have a DB backup....what is the best approach I should take to correct this problem (note: In my case, it's perfectly acceptable to say "rebuild your machine and don't put the 2.0 Fx on it")

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

Post by jclausius » Wed Oct 20, 2004 9:09 pm

I could be wrong, but I don't believe we fully support .Net 2.0 Beta Fx, as it is still beta. We haven't done a full test run with Vault 2.0.6 on .Net 2.0. However, I can report preliminary testing of earlier versions of Vault 2.0.5 identified one subtle, but incompatible change in the 2.0 Beta Framework, which creates the scenario you've encountered.

Getting back to your question... If you don't care about the history of your files, you could start with a fresh installation of Vault 2.0.6 and a brand new empty database w/ .Net 1.1 SP1 Fx. However, if you have a backup which was created while still on .Net 1.1 or .Net 1.1 SP1, you could additionally use that database with Vault 2.0.6 and the .Net 1.1 or .Net 1.1 SP1 framework.

Note, if you un-install .Net 2.0 Beta Fx, you will need to re-register the 1.1 .Net Fx w/ IIS. You should use the "aspnet_regiis.exe" within the 1.1 Framework dir. Make sure to specify the /i option.
Jeff Clausius
SourceGear

Post Reply