Hi all
I upgraded our vault from version 3.5.x to 4.0.5.
If I try to check out or check in a file, it does the checkin/checkout, but shows the following message afterwards:
Object reference not set to an instance of an object.
The server-log shows the following message:
----11/30/2007 5:18:16 PM Daniel Frey--sbe5665.swissptt.ch(10.50.20.21)--SSL Disabled System.NullReferenceException: Object reference not set to an instance of an object.
at VaultWebLib.ShadowFolderData.Select() at VaultWebLib.ShadowFolderData.Select()
Any help would be great. I have 20 people on the system who'd like to start working on this system by Monday!!!
Thanks in advance
Daniel
Error after checkout/checkin - Object reference not set to..
Moderator: SourceGear
-
- Posts: 3
- Joined: Fri Nov 30, 2007 11:07 am
Error after checkout/checkin - Object reference not set to..
- Attachments
-
- Client error snapshot
- snap.gif (7.29 KiB) Viewed 3077 times
-
- Posts: 3
- Joined: Fri Nov 30, 2007 11:07 am
Hi Jeff
Thanks for the fast reply. Unfortunately I can't send the entire log right now because I just returned home (it's late over here in Europe ;.)) and I have no access from home.
Until I can send the log it would be too late for you to work.
But the log was beside a few logins and logouts totally emtpy.
Is there any chance how I could fix the bug?
You tell me that the bug "is benign and would not cause a check out to fail", but in my eyes it is quite difficult to work under such circumstances. Using Vault from within VS2005 with it's build-in plugin (not Vaul-Plugin) it tells me, whenever I want to edit a file (checkout), that the sourcecontrol-system threw an error and VS2005 won't check out properly.
What puzzels me is that if I access another Vault (which works fine for others) I get the same error. Is this error a client-side error and not a server side error?
Thanks for your help
Daniel
PS: I will send the whole log as soon as possible
Thanks for the fast reply. Unfortunately I can't send the entire log right now because I just returned home (it's late over here in Europe ;.)) and I have no access from home.
Until I can send the log it would be too late for you to work.
But the log was beside a few logins and logouts totally emtpy.
Is there any chance how I could fix the bug?
You tell me that the bug "is benign and would not cause a check out to fail", but in my eyes it is quite difficult to work under such circumstances. Using Vault from within VS2005 with it's build-in plugin (not Vaul-Plugin) it tells me, whenever I want to edit a file (checkout), that the sourcecontrol-system threw an error and VS2005 won't check out properly.
What puzzels me is that if I access another Vault (which works fine for others) I get the same error. Is this error a client-side error and not a server side error?
Thanks for your help
Daniel
PS: I will send the whole log as soon as possible
I think you are correct. If there was any kind of server log, you would see an error in the messages tab within the Vault GUI client. Do you see any kind of error message within the GUI client before the "obj reference not found"?
It could also be related to a Tree Cache issue. Try logging in, and from the Tools -> Options -> Local Files click the Reset Repository Tree Cache button. Afterwards see if that solved the problem.
It could also be related to a Tree Cache issue. Try logging in, and from the Tools -> Options -> Local Files click the Reset Repository Tree Cache button. Afterwards see if that solved the problem.
Jeff Clausius
SourceGear
SourceGear
-
- Posts: 3
- Joined: Fri Nov 30, 2007 11:07 am
Hi
The solution is to delete the cache directly on the disk by deleting this directory:
C:\Documents and Settings\[user]\Local Settings\Application Data\Sourcegear\Vault_1\Client”.
Deleting the Cache via Tools menu didn't succeed.
I don't know the implications this action has, but at least I can work again.
Thanks to all!
Daniel
The solution is to delete the cache directly on the disk by deleting this directory:
C:\Documents and Settings\[user]\Local Settings\Application Data\Sourcegear\Vault_1\Client”.
Deleting the Cache via Tools menu didn't succeed.
I don't know the implications this action has, but at least I can work again.
Thanks to all!
Daniel