Vault Admin - Object reference not set to an instance of an

[jerwin]

We have a Vault 4.0.4 server that started life as a Vault 3.0.x version almost 3 years ago.

I had to get in to the Vault admin interface today for the first time since mid-January and am having some big problems. When I attempt to click on any administrative page for any Vault repository (Groups, Repository Access, Folder Security, etc....) I get an error "Object reference not set to an instance of an object" displayed on the page.

We have over 30 repositories. I have tried this on at least half of them, ranging from Repositories created in the last few months, to some of them that were imported from VSS back in mid 2005 and they all exhibit this behavior. It sounds similar to the user from this thread http://support.sourcegear.com/viewtopic ... nce+object .

I'm needing to perform a number of administrative tasks, and cannot perform them at this time due to the errors. I have a number of the following entries in my Vault Log.

Code: Select all

----2/12/2008 2:23:41 PM     admin--cnb-dev-jde(192.168.1.91)--SSL Enabled	System.NullReferenceException: Object reference not set to an instance of an object.
   at VaultWebLib.Helpers.RepName(Int32 repid)
   at VaultService.FileTypes.Page_Load(Object sender, EventArgs e)
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)    at VaultWebLib.Helpers.RepName(Int32 repid)
   at VaultService.FileTypes.Page_Load(Object sender, EventArgs e)
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Just replace FileTypes with any of the other administrative functions, switch the date/time and the entries are all the same.

I haven't been into the admin pages to perform any tasks since mid-January, but everything was working just fine then.

regards,

JE

[Beth]

Object reference errors can often be the result of a cache problem. The easy way to clear out the server side would be to just perform an iisreset on the Vault server (Start - Run - iisreset). That will disconnect everyone from the web services for about a minutes.

[jerwin]

Beth,

Thanks so much for the very prompt response. Based on your suggestion, I've scheduled a maintenance window this evening to reset the server. Everyone's clients appear to be connecting just fine, so we would prefer not to interrupt velocity in the middle of the development day.

If the iisreset doesn't work, I'm going to reboot the box. I'll post the results here later tonight regardless of the outcome (good or bad).

thanks,

JE

[jerwin]

Performing an iisreset on the server appears to have cleared the problem up. What still seems odd to me is that this server hadn't been rebooted for a few months and never exhibited this behavior. It was rebooted 10 days ago, which should have cleared cache, and then we have the issue.

Thanks again for the prompt response.

regards,

JE

[Beth]

One thing I have noticed is that sometimes, when a change is made to a server be it manually or an update, it sometimes won't go into effect until a reboot. My gut tells me that it could have been the order of operations from something new going into effect that confused the cache. For example, maybe the IIS cache was repopulated with old information, then the change implemented. It's hard to say.