Object reference not set to an instance of an object.

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

Moderator: SourceGear

Post Reply
Tonyb
Posts: 20
Joined: Fri May 05, 2006 5:36 pm

Object reference not set to an instance of an object.

Post by Tonyb » Thu Sep 07, 2006 4:31 pm

I have vault setup to email me when a specific folder changes. The link in the email points to TransactionDetails.aspx?repid=1&txid=XXXX but when I visit that link I get a "Object reference not set to an instance of an object."

If it set the txid to 1 in the query string it works, but anything other than that fails. It doesn't look like anything gets logged to the sgvault.log

Any ideas on where the problem might be?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Sep 08, 2006 8:04 am

What version of Vault are you using?

Is this happening for any notification or just for this particular file?
Linda Bauer
SourceGear
Technical Support Manager

Tonyb
Posts: 20
Joined: Fri May 05, 2006 5:36 pm

Post by Tonyb » Fri Sep 08, 2006 8:11 am

V 3.5

Any notification, but its not really a notification problem, it is a problem on the TransactionDetails.aspx page. It gets the error when the transaction ID is anything above 1.

I have attached a screen shot of the error
Attachments
vault-error.png
VaultWeb Error Message
vault-error.png (68.64 KiB) Viewed 3915 times

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Sep 08, 2006 8:36 am

This is a known bug that is slated to be fixed in Vault 3.5.2. The workaround is to add a checkin comment for transactions. When items have a checkin comment, the link works properly.
Last edited by lbauer on Fri Sep 08, 2006 8:05 pm, edited 1 time in total.
Linda Bauer
SourceGear
Technical Support Manager

Tonyb
Posts: 20
Joined: Fri May 05, 2006 5:36 pm

Post by Tonyb » Fri Sep 08, 2006 8:58 am

Thanks, that appears to be the problem.

On related issue (not sure if this is a bug or not), the transaction Number shown on the recent checkin pages is not the same ID number that is in the email and on the transaction details page are different.

By email has ID 10258 where recent checkins show 10253. Not a big deal, i wouldn't have even noticed if I didn't hit the first bug.

Post Reply