Windows Event Log - Merging Branches

[Ocean10000]

I am trying to merge a temporary patch branch back into the main trunk. But the Merge Branch Wizard is taking a very long time for this operation considering how many files have changed. I am not noticed any major cpu or memory changes to signal anything is being done on the server or the client machines. I am assuming some thing is timing out because of the error listed below, which is listed multiple times in the windows event log.

Event Log - Errors

SourceGear Fortress (Server and Client)
Version 1.1.4.18402


Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 8/31/2009 8:17:20 AM
Event time (UTC): 8/31/2009 3:17:20 PM
Event ID: 134072aff7bb4394a543fc2003271c13
Event sequence: 204
Event occurrence: 10
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/Fortress-3-128955995565312500
Trust level: Full
Application Virtual Path: /Fortress
Application Path: C:\inetpub\wwwroot\Fortress\
Machine name: SRV03

Process information:
Process ID: 2204
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.

Request information:
Request URL:
Request path:
User host address:
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at MantisServiceLib.Helpers.LogMessage(DNLogEntryType let, String strMsg)
at MantisServiceLib.Helpers.DeleteSession(HttpSessionState hss, Boolean signOut)
at MantisServiceLib.Helpers.DeleteSession(HttpSessionState hss)
at Mantis.Global.Session_End(Object sender, EventArgs e)


Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[lbauer]

Application Path: C:\inetpub\wwwroot\Fortress\

This looks more like an error generated by the item tracking. Source control functions done by the Vault Service, in the c:\Inetpub\wwwroot\VaultService directory.

Are you updating bugs when you commit this merge?

What part of the Merge Branches is slow? Are there any errors in the Vault Server log that correspond to the slowdown? The the Vault Server log is called sgvault.log and is in %windir%\temp\sgvault on the server machine.

[Ocean10000]

The Merge operation would not allow me to select next, and just waited for me to select a range of merges but none were showing (I waited from the time of the previous post till just now). I had to cancel and restart the merge operation, which seems to be working now as expected. This is the first time trying to do a proper merge using the merge wizard. So I expected to run into some issues with my understanding how things were suppose to go. I can see the CPU pegged at 50% now trying to generate the check in list for the merge branch but at least I can see it doing something now. I will update the thread if I have any further issues.

[lbauer]

Okay lets us know if you have further questions.