RE: serious Vault IDE issue - I'm stumped

Brandon Casci <[email protected]>
Newsgroups gmane.comp.version-control.sourcegear-vault.user
Message-ID <[email protected]>
UPDATE:

it looks like my VS/NET project file was corrupted.

I unbound, then binded the project back to Vault.

I then forced an overwrite of the project file.

Everything seems ok now.


-----Original Message-----
From: Brandon Casci [mailto:[email protected]]
Sent: Friday, January 30, 2004 2:46 PM
To: [email protected]
Subject: [vault-list] serious Vault IDE issue - I'm stumped



This is a strange on. 

One one particular machine, the Vault IDE won't perform any check outs or
check-ins with the Vault Server. TheIDE behaves like it is working
disconnected. MEaning : it will go through the motions of check-in and
check-out..but it actually isn't pulling or posting any of its work into the
Vaulr repository. The procject source control bindings are correct too.

I can perform check-in/check-out just fine with the Vault Client.


I've cleared the "applicaiton data" as well, and restarted Visual Studio.net
and still have this problem.

Any ideas?


-----Original Message-----
From: Dan Schreiber [mailto:[email protected]]
Sent: Friday, January 30, 2004 11:20 AM
To: Michael Dorfman; Shaw Terwilliger
Cc: [email protected]
Subject: RE: [vault-list] "The File Exists"


I wonder:  What are the philosophical implications of too many temporary
files?

"Can't create permanent life - temporary life is too full"

-Dan

> >
> > If the problem does not go away with a different working
> > folder, it could be that you're temporary directory is full
> > (or all possible combinations of names of temp files are
> > used--see below).
> >
>
> Bingo!  We have a winner!  I cleaned out the %temp% directory, and life
> again is good.
>
> As usual, Vault support rocks.
>
> Thanks,
>
> Michael Dorfman
> Mercatus as

_______________________________________________
vault-list mailing list
[email protected]
http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list

Get the latest news on SurfControl and our products,
subscribe to our monthly e-newsletter, SurfAdvisory at:
http://www.surfcontrol.com/resources/surfadvisory/surfadvisory_signup.aspx

*********************************************************************
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken
or omitted to  be taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error,
please contact the sender.
*********************************************************************
SurfControl Inc.
100 Enterprise Way, Suite A110
Scotts Valley, California 95066
831-440-2500
_______________________________________________
vault-list mailing list
[email protected]
http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list

Get the latest news on SurfControl and our products,
subscribe to our monthly e-newsletter, SurfAdvisory at:
http://www.surfcontrol.com/resources/surfadvisory/surfadvisory_signup.aspx

*********************************************************************
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken
or omitted to  be taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error,
please contact the sender.
*********************************************************************
SurfControl Inc.
100 Enterprise Way, Suite A110
Scotts Valley, California 95066
831-440-2500
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.