Search in documentation yields 404 (v4)

[neal007]

I'm trying to search the documentation to see what is required for FogBugz setup but the search button causes a 404 to show on left side.

I need information on how to configure the mail setup (server URL) and the FogBugz integration please.

I'm nothing short of shocked at the lack of quality in this major release!

[jeremy_sg]

You can read the documentation for configuring FogBUGZ at:

http://download.sourcegear.com/Vault/la ... ltonly.htm

Email configuration information can be found here:

http://download.sourcegear.com/misc/vau ... ttings.htm

[neal007]

Thank you, a drop down box to select from one of the two URL's for FogBugz would be nice. No one is going to know that long URL.

Also when entering the long url for diff support into a specific repository, a asp.net security error occurs.

[jeremy_sg]

Can you give me more information? What security error? How long is the URL?

[neal007]

It's the ole page validation error message that started with asp.net 1.1. You don't get this when you put it in the top level/repositories page, but if you go to a specific repository and enter the FogBugz URL you get the warning that this URL may be harmful, blah blah blah

[lassevk]

Is there anything I can look at in order to get fogbugz integration working again? That the vault client did not manage to attach the files to fogbugz isn't very helpful.

Nothing changed, except upgraded to vault 4.0. The url for fogbugz is as prescribed in the documentation (and which worked in 3.5.2), and is reachable from both the server and the client, verified that the url is still correct in the admin tool.

Looked through the event logs and the sourcegear logs, couldn't see anything.

[jeremy_sg]

The client side of the program is the one that should be logging if there are any issues with updating FogBUGZ. You will need to turn on Vault client logging to investigate this further.

[lassevk]

Ok, tried the logging capabilities of the client, error message in the message pane:

[06.06.2007 14:53:19] Unable to update one or more of the following bug(s): 101

Nothing in the log that I can trace back to this. Nothing called FogBugz, 101 not found as text, etc. What should I look for?

The entries in the log file around that time are as follows:

06.06.2007 14:53:18 <upload>: [Upload_0:7912] uploading item: $/Test/Main/Sub/dddd.txt
06.06.2007 14:53:18 <connection>: [Upload_0:7912] UploadFile started.
06.06.2007 14:53:18 <connection>: [Upload_0:7912] UploadFile finished.
06.06.2007 14:53:18 <eventengine>: [Upload_0:7912] Event fired: VaultClientOperationsLib.ProgressChangedEvent
06.06.2007 14:53:18 <eventengine>: [Upload_0:7912] Event fired: VaultClientOperationsLib.ProgressChangedEvent
06.06.2007 14:53:18 <upload>: [Upload_0:7912] finished uploading item: $/Test/Main/Sub/dddd.txt
06.06.2007 14:53:18 <eventengine>: [GUIClientWorkerThread:6148] Event fired: VaultClientOperationsLib.ProgressChangedEvent
06.06.2007 14:53:18 <eventengine>: [GUIClientWorkerThread:6148] Event fired: VaultClientOperationsLib.ProgressChangedEvent
06.06.2007 14:53:18 <eventengine>: [GUIClientWorkerThread:6148] Event fired: VaultClientOperationsLib.MessageEvent
06.06.2007 14:53:18 <eventengine>: [GUIClientWorkerThread:6148] Event fired: VaultClientOperationsLib.StatusMessageEvent
06.06.2007 14:53:18 <connection>: [GUIClientWorkerThread:6148] EndTx started.
06.06.2007 14:53:19 <connection>: [GUIClientWorkerThread:6148] EndTx finished.
06.06.2007 14:53:19 <eventengine>: [GUIClientWorkerThread:6148] Event fired: VaultClientOperationsLib.StatusMessageEvent
06.06.2007 14:53:19 <eventengine>: [GUIClientWorkerThread:6148] Event fired: VaultClientOperationsLib.MessageEvent
06.06.2007 14:53:19 <refresh>: [GUIClientWorkerThread:6148] Refresh started
06.06.2007 14:53:19 <refresh>: [GUIClientWorkerThread:6148] delta passed in was null, retrieving one

I can't see anything related to the fogbugz integration here.

Any more hints?