painful install object reference not set to an instance
Moderator: SourceGear
-
- Posts: 42
- Joined: Mon Feb 16, 2004 6:10 am
painful install object reference not set to an instance
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
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
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?
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
SourceGear
-
- Posts: 42
- Joined: Mon Feb 16, 2004 6:10 am
Object reference not set to an instance of an object
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
Any other suggestions?
Ralph
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?
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
SourceGear
-
- Posts: 42
- Joined: Mon Feb 16, 2004 6:10 am
-
- Posts: 42
- Joined: Mon Feb 16, 2004 6:10 am
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>
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>
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.
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
SourceGear