Search found 15 matches
- Mon Jan 09, 2017 6:27 pm
- Forum: Support (Vault Professional)
- Topic: Logout of Vault in Visual Studio
- Replies: 2
- Views: 4975
Logout of Vault in Visual Studio
I am using the Vault Visual Studio plugin. There does not appear to be a way to logout a Vault user after the project has been bound and login as a different Vault user. Is there a way to do that?
- Tue Oct 29, 2013 10:25 am
- Forum: Support (Vault Professional)
- Topic: "My Open" / "My Unresolved" fault with Vault Pro 7
- Replies: 6
- Views: 6256
Re: "My Open" / "My Unresolved" fault with Vault Pro 7
Email sent. Could you send me your VaultPro log from C:\Windows\temp\SGVaultPro\vaultpro.log? Also, try to bring up the "My Open" again that causes the error. Immediately after that grab the IIS log file from C:\inetpub\wwwroot\logs\logfiles. Please send the IIS log file that should show y...
- Mon Oct 28, 2013 2:26 pm
- Forum: Support (Vault Professional)
- Topic: "My Open" / "My Unresolved" fault with Vault Pro 7
- Replies: 6
- Views: 6256
Re: "My Open" / "My Unresolved" fault with Vault Pro 7
We are getting the exact same error after upgrading to Vault 7. I checked %windir%/temp/sgvault/sgvault.log but it did not contain any information on this error. I even changed the logging level from Quiet to Debug but it didn't make any different. We have just upgraded to Vault Pro 7. We are runnin...
- Mon Oct 21, 2013 1:44 pm
- Forum: Support (Vault Professional)
- Topic: Error after upgrading to 7.0
- Replies: 4
- Views: 4695
Re: Error after upgrading to 7.0
It appears to be working now, I'm not sure what changed.
- Mon Oct 21, 2013 10:17 am
- Forum: Support (Vault Professional)
- Topic: Error after upgrading to 7.0
- Replies: 4
- Views: 4695
Re: Error after upgrading to 7.0
Win Server 2008 R2 64-bit
- Fri Oct 18, 2013 5:22 pm
- Forum: Support (Vault Professional)
- Topic: Error after upgrading to 7.0
- Replies: 4
- Views: 4695
Error after upgrading to 7.0
After upgrading Vault Pro from 6 to 7, I got the following error starting the admin interface.
HTTP Error 500.21 - Internal Server Error
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list
HTTP Error 500.21 - Internal Server Error
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list
- Fri Aug 06, 2010 12:39 pm
- Forum: Support (Fortress)
- Topic: From checkin to Fortress item
- Replies: 1
- Views: 4554
From checkin to Fortress item
Is there a way to find the Fortress item that the checkin linked to? Currently, we have to enter a Fortress item # whenever we checkin a change, however, there does not appear to be a way to find the Fortree item # when viewing the checkin history of a file.
- Tue Jun 01, 2010 3:35 pm
- Forum: Support (Fortress)
- Topic: Feature Request - Show me what I'm undoing!
- Replies: 4
- Views: 6957
Re: Feature Request - Show me what I'm undoing!
Saint168, if you just want to undo changes to the Project file, but not other files in the project, have you tried doing this in the Fotress Pending Changes window in Visual Studio, rather than in the Solution Explorer? I have done this several times successfully, myself. Just right-click on the Pr...
- Thu May 27, 2010 2:38 pm
- Forum: Support (Fortress)
- Topic: Feature Request - Show me what I'm undoing!
- Replies: 4
- Views: 6957
Feature Request - Show me what I'm undoing!
This has happened more than once for me. When I undo checkout on the project level, I accidentally undid changes several levels deep inside my project tree. Is it possible to show a list of file changes I'n undoing like the tree dialog I get when I check in changes recursively? Currently, all I get ...
- Thu May 27, 2010 2:33 pm
- Forum: Support (Fortress)
- Topic: Error deleting a milestone
- Replies: 5
- Views: 8374
Re: Error deleting a milestone
Is that milestone used in any recorded tasks or bugs? If so, then it cannot be deleted. The error you see suggests that it's being used by some items. I ran a quick test to confirm this behavior. Probably a better error from us to let you know that the milestone is in use would be the way to go. I ...
- Wed May 26, 2010 9:49 am
- Forum: Support (Fortress)
- Topic: Error deleting a milestone
- Replies: 5
- Views: 8374
Re: Error deleting a milestone
Here it is: 2010-05-25 08:57:08.447 VM-DevServer01.cms.local (192.168.42.12)-Stephen : Helpers::DeleteMilestone The DELETE statement conflicted with the REFERENCE constraint "fk_items_milestones". The conflict occurred in database "sgdragnet", table "dbo.items". The sta...
- Tue May 25, 2010 10:01 am
- Forum: Support (Fortress)
- Topic: Error deleting a milestone
- Replies: 5
- Views: 8374
Error deleting a milestone
When I try to delete a milestone on Fortress, I got the following error from IE: Webpage error details User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6.4; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; MS-RTC EA 2; .NET CLR 3.0.4506...
- Fri May 14, 2010 10:54 am
- Forum: Support (Fortress)
- Topic: Feature Request - Email Generation
- Replies: 1
- Views: 3960
Feature Request - Email Generation
I've seen this feature in many other item tracking products. Please add the ability to generate an email from a Fortress item OTHER than the Resolver, Assignee and Reporter. It would be best if I can enter the email address manually and the generated email contains all comments from that item. Occas...
- Fri May 14, 2010 10:26 am
- Forum: Support (Fortress)
- Topic: Problem with Email from Fortress
- Replies: 1
- Views: 4183
Problem with Email from Fortress
The name of our Fortress server is "Fortress". When Fortress send out the notification emails, the machine name is missing from the URL ONLY when the machine name is "Fortress". If I name rename the machine to anything else, the generated URL is correct. Seems like there is some ...
- Sat Aug 29, 2009 2:59 pm
- Forum: Support (Fortress)
- Topic: Feature suggestion
- Replies: 1
- Views: 3364
Feature suggestion
It would be nice if there is a way to copy source code from one branch to another branch. We always create a hotfix branch after a release so we can continue to develop new features while doing emergency hotfixes on the hotfix branch. We usually perform the fix on the main branch, then copy the chan...