painful install object reference not set to an instance

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

Moderator: SourceGear

Post Reply
rshillington
Posts: 42
Joined: Mon Feb 16, 2004 6:10 am

painful install object reference not set to an instance

Post by rshillington » Wed Apr 06, 2005 6:30 am

I've downloaded and installed the 3.05 server bits.

I uncommented the line:
<trust level="Full" originUrl=""/>
as per another post in the forum.

I confirmed that I'm able to view the VaultService.asmx file, using the browser, however when I try and log in using the admin tool, so that I can set the demo license key I get

Server was unable to process request. --> Object reference not set to an instance of an object.

The server is Windows 2003
the database is local

and here's the vault log file
----06/04/2005 8:22:01 AM sgvaultsystem--()--
System Started
Version 3.0.5.2833
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://server2.ifoundtime.com/VaultService
Identity = NT AUTHORITY\NETWORK SERVICE

And suggestions

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

Post by jclausius » Wed Apr 06, 2005 8:01 am

If that is the entire log, then the Admin Tool is defintely not connecting to the server. Otherwise there would be a login entry recorded in the log.

Are you running the Admin Tool directly on the Vault server itself? If so, have you tried using just plain "localhost" for the Vault server's name?
Jeff Clausius
SourceGear

rshillington
Posts: 42
Joined: Mon Feb 16, 2004 6:10 am

Object reference not set to an instance of an object

Post by rshillington » Wed Apr 06, 2005 11:18 am

Yes, I'm running the the Admin tool directly on the server, and tried using the NetBois Name, 127.0.0.1, localhost, FQDN you name it..... The odd thing is that from the Browser I have I no trouble hitting the VaultService.asmx file.

Any other suggestions?

Ralph

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

Post by jclausius » Wed Apr 06, 2005 11:50 am

Let's try this.

On the Server itself, browse to http://localhost/vaultservice/vaultservice.asmx.

Scroll down the list until you see the test for Ping. Click that. You should get a new page, in which you can invoke the Ping method. Invoke it. Do you get an XML document which contains a 1?
Jeff Clausius
SourceGear

rshillington
Posts: 42
Joined: Mon Feb 16, 2004 6:10 am

Post by rshillington » Wed Apr 06, 2005 11:56 am

Prior to your suggestion, I removed the 3.0.5 version and installed 2.0.6 and got the same general behaviour. With the 2.0.6 version installed however I was able to follow your instructions and do a ping --- I got an int 1 as an xml document as a reply.

Any other troubleshooting suggestions?

Ralph

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

Post by jclausius » Wed Apr 06, 2005 1:10 pm

Can you

1) Uninstall Vault 2.0.6, keep the database.
2) Install Vault 3.0.5 (keep the database).
3) Try the ping test
Jeff Clausius
SourceGear

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

Post by jclausius » Wed Apr 06, 2005 1:26 pm

If you get past the ping test, one other thing you could try is the Vault Command Line Client ( assuming you've installed Vault 3.0.5 client side tools as well ).

Something like: vault listrepositories -server localhost -user admin -password <PWD>
Jeff Clausius
SourceGear

rshillington
Posts: 42
Joined: Mon Feb 16, 2004 6:10 am

Post by rshillington » Wed Apr 06, 2005 3:24 pm

Basically the same as with the windows client: THis is what I get from the command prompt client:

C:\Program Files\SourceGear\Vault Client>vault listrepositories -server localhos
t -user admin -password password
<vault>
<error>
The connection to the server failed: server cannot be contacted or uses a protoc
ol that is not supported by this client. Server was unable to process request. -
-> Object reference not set to an instance of an object.
</error>
<exception>
System.Exception: The connection to the server failed: server cannot be contacte
d or uses a protocol that is not supported by this client. Server was unable to
process request. --> Object reference not set to an instance of an object.
at VaultCmdLineClient.VaultCmdLineClient.Login(Boolean bAllowAuto, Boolean bS
aveSession)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandListRepositories()
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
</exception>
<result success="no" />
</vault>

C:\Program Files\SourceGear\Vault Client>

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

Post by jclausius » Wed Apr 06, 2005 3:46 pm

Did the ping test succeed?

Can you send me the vault_install.log file as well as Vault Server's sgvault.log file? You can use the email button below to contact me.
Jeff Clausius
SourceGear

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

Post by jclausius » Wed Apr 06, 2005 3:51 pm

One other question.

Start up the Vault GUI client. Cancel the Login. Can you also send me the information from Help->About?
Jeff Clausius
SourceGear

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

Post by jclausius » Thu Apr 07, 2005 7:39 am

We could not get Vault to work correctly on this installed machine. AFAIK, there was nothing in the Windows Event Log, nothing in the server log. It just would not work.

However, when Ralph installed Vault on a different Win2003 Server, everything worked as expected. Since Vault is now operational, Ralph is going to possibly look at this particular machine at a later date.
Jeff Clausius
SourceGear

Post Reply