|
2
|
We setup FogBugz (on demand) integration with Perforce via the Perforce Defect Tracking Gateway. It worked great for about a week. Then all of sudden it stopped working. The Perforce Defect Tracking Gateway Configuration Editor now shows this:
It's been hung this way for weeks now. We've restarted all the Perforce services and restarted the entire machine. (Our Perforce depot/server is on the same machine that is hosting the DTG.) Nothing has helped. Any ideas? Any help would be appreciated! |
||
|
|
|
2
|
I'm encountering the same issue. The P4DTG process is running on Windows Server 2008 R2 X64, and to get the Config Editor to recover, I had to delete the file named "C:\Program Files (x86)\Perforce\P4DTG\repl\stop-FogBugzPerforceMapping" |
||
|
|
|
2
|
We use a script rather than the Perforce Defect Tracking Gateway and although the integration may not be as tight, we haven't had a single problem in all the time we've used it (since FogBugz v3). BTW, the script we use is |
|||
|
|
