Had 4.1.2 x86 installed on a server (Win2003R2x86).
Installed to a new server (Win2008x64). Seemed to go well, although a few trys were required.
The client on my work machine (Vista Ulitimate x86) then started throwing a null pointer error whenever I tried to access one of my repositories, but not the others.
I noticed that my client was 4.1.1, and decided to upgrade it. That's when the problems started
1) I first tried to install 4.1.2 on top of 4.1.1. That failed with the 2837 error (maybe a differnet number. It's the VBScript installer error that's common).
2) I then tried to uninstall 4.1.1. Same problem.
3) After going through the forums, I reregistered the vbscript dll
4) I removed the 4.1.1 client
5) I installed the 4.1.2 client.
No dice. I still get a null pointer exception when I try to access that one repository.
I then brought the original web server back up, and the client still acts the same.
I then installed the client on my wife's machine at home (Vista x86). Everything works as expected.
So, my assumption is that something is wacked on my client install. I can only assume that something in the server installation updated the DB (strange since it was already on 4.1.2). The update cause my client to get angry, and something is subsequently messed up.
Yes, there have been plenty of reboots along the way.
I've attached a simple log file. Please pass along some suggestions. I need to develop, and I use the integrated client.
Need help with a fouled client. I'm Dead in the water
Moderator: SourceGear
Re: Need help with a fouled client. I'm Dead in the water
First, please turn on Vault client logging and send us the log file. This may be an exception that we've never seen before. If so, we definitely want to fix it.
The second step will probably be to clear out one of your client cache files (the known changes one).
The second step will probably be to clear out one of your client cache files (the known changes one).
Subscribe to the Fortress/Vault blog
Re: Need help with a fouled client. I'm Dead in the water
Thank you. Clearning the cache did it. I should mention that under vista, the cache is in a hidden/protected place. I doubt that the average user (even the average developer) could easily get there with some windows Admin experience. Please consider adding an option to the tools menu of the client.
You may consider this case closed.
Barry
You may consider this case closed.
Barry
Re: Need help with a fouled client. I'm Dead in the water
There is a button in the Tools->Options dialog under the Local Files->Cache Location page which will open the directory. We should modify the KB article to point people to that button. Thanks!
Subscribe to the Fortress/Vault blog