SourceGear Support

Here is the detail of the exception. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at VaultClientPresentati...

After upgrade from Vault 4.1 to Fortress 1.1, I can't rebind the solution. It gives me "Object Reference not set" error. I can select the Repository but after the dialog closes, nothing happen. Then when i click Bind again, it ask me to choose Repository again. the error happens & show...

User is using Visual Studio 6. After he restart the IDE, the error message no longer appear.

I have one user reported this error. Check the sgvault.log - no error message captured. Vault ver 4.1.0

Reopen again the workspace from Source Control solve my problem. After that, don't delete *.opt file.

Deleting *.opt file causes the same observation on the "Test" project (this was added correctly into Vault Server). So, i guess that's where the problem is - i have deleted the *.opt file in the working project - thinking that it can be re-generated.

I have done that. Nothing unusual. Is MSSCCPRJ.SCC the only file responsible for the login & repository lookup?

Back to work on earlier projects coded in VC++ using VS6. The files were added in through Vault client & not thorough the IDE. Due to some reason, i do not want to alter the files - so i practically hand coded the binding information: 1) Created the MSSCCPRJ.SCC file manually with the following ...

Hi AGBrown, sorry for the 'hijacking'
Hi Beth, alright.

Run into this error while performing export. Vault ver 4.1 Server log: ----3/26/2008 12:00:01 PM admin--SDD-JOEL(192.0.0.88)--SSL Disabled VaultServiceSQL.VaultDbTreeException: An error was encountered looking up the owner of a folder or file for the source code tree. The tree was not built. Base Tr...

Even though this discrepency does not affect the overall functionality of Vault Server, i really hope i can resolve it.
BTW, I am going to perform an upgrade to ver 4.1

This is a good article worth reading - Chapter 8: Merge Branches
In fact, i faced the same issue & i will adopt the principle mentioned in this article for our source code change management.

Vault version: 4.0.6
The folder was created in ver 3.1.7. I have recently perform the upgrade to ver 4.0.6

I have a few folders which even though their access right has been set to (none), other user still can see them in the repository. Is there any DB query i can run to resolve this?

Prev version: 3.1.7
Current version: 4.0.6

I encounter this error when i select the Properties menu at a folder. No exception was recorded in Server log file.