Unable to connect to server

SeanP · Post by **SeanP** » Wed Sep 07, 2005 1:57 am

Yes, the same subject as the sticky in this forum. I am using v 3.1.1 (506). I can connect to a remote Vault Server, and I can run the default page (http://<server>/VaultService

I can even browse to the login page and peruse my files in the vault database. However, I can not connect to my local vault via the client or the web service. I used to be able to, but now I get the dreaded "Unable to connect error". The exact error I receive is below.

Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
AG.WebDevInfo.WebDevInfo._application_PostRequestHandlerExecute(Object sender, EventArgs e) +8
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87

Post by **Tonya** » Wed Sep 07, 2005 1:39 pm

I am going to need to get some additional information from you. Have you recently installed or upgraded Vault? What version of the Vault Server are trying to connect to?

Would you mind e-mailing me your Vault log file? You can send it to Tonya@SourceGear.com.

Thanks,

Tonya Nunn
SourceGear Support

rwholmes · Post by **rwholmes** » Thu Sep 08, 2005 6:53 pm

Might this happen as a result of a mismatch between versions of the client and server?

Post by **Tonya** » Mon Sep 12, 2005 7:58 am

According to the Vault Log file, the server and the client are the same version. Besides, a 3.0.7 Vault Client should work appropriately with a 3.1 Server.

Tonya Nunn
SourceGear Support

Post by **Tonya** » Mon Sep 12, 2005 11:17 am

This problem was due to a custom http handler. It was resolved by editing the web.config file and placing a new line in the system.web section.

<system.web>
<httpModules>
<remove name="WebInfoHttpModule" />

Tonya Nunn
SourceGear Support