is it normal to see exceptions in message window?

[jamesshaw]

I mention this not because there is a problem (for me at least) but because the presence of a callstack with a null reference in the message window made me wonder if you'd like to see it. I simply waited until the new session started and then checked in again...

[2/16/2005 12:00:10 PM] Beginning transaction
[2/16/2005 12:00:11 PM] Server unavailable for transaction begin
[2/16/2005 12:00:11 PM] Transaction failed
[2/16/2005 12:00:11 PM] An exception was encountered during the transaction. Exception: Server was unable to process request. --> Object reference not set to an instance of an object. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.BeginTx(Int32 nRepID, String strComment, VaultRequestItem[]& requests, String& strTxID)
at VaultClientNetLib.VaultConnection.BeginTx(Int32 nRepID, VaultRequestItem[]& requests, String& strTxID, String comment)
at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)

[mlippert]

I think the reasoning is that the target audience of Vault is developers and developers are probably happier with a stack trace error that gives them some information and potentially can be reported back to SourceGear to get the problem fixed.

So, I think it's good to report these here to SourceGear, because I'd consider them to be either caused by a bug, or by an unexpected condition that probably should be caught and handled somewhat more gracefully.

[lbauer]

We're always interested in reports of errors that crop up. It's helpful to know the steps leading up to the exception, and whether or not the problem is reproducible.