Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML How to install an Agile patch
How to install an Agile patch
MS-EXCEL AOD Supported Platform Matrix.xls
S R&D believes the platform should functional normally and will fix defects against the platform. Unsupported
CMS-XML Agile 2010 R2 Hot Fix 1 Release
This patch should only be installed on top of Agile 2010 R2.00. If you are running any other version, do not apply this hot fix. If you are unsure of your current release, contact support at for additional help.
CMS-XML Online help has erroneous reference to Demand vs. Capacity tab
This has been reported as a documentation bug to be fixed
CMS-XML When trying to create or delete a work item you get Backlog Name (xxx) has been modified since last retrieval and item won't create or delete.
You may start to get this error after changing the Date and Time settings or Time Zone settings on either the Agile server or the Database server if the two boxes are different. In order to fix this run the following sql statement against the Agile database and log back into Agile and try the create or delete again. update PES_Object set obj_LastChange = GETDATE()
CMS-XML Browser flashes and nothing happens when click Print, click Save, or try to view a file
If you try one of these actions, your browser may flash but nothing happens. Or, you may get an "Access Denied" error. This document describes how to fix this problem.
CMS-XML Agile help may point to old version of online help file on certain screens.
To fix this run the two sql scripts against the agile database. update PES_DesignerForm set dfm_Layout=REPLACE(Cast(dfm_Layout as nvarchar(max)),'appVersion=2009.03.00.9999','appVersion=2010.01.00.9999') update PES_DesignerForm set dfm_Layout=REPLACE(Cast(dfm_Layout as nvarchar(max)),'','')
CMS-XML How to upgrade from Agile 2010 R1 or Agile 2010 R2 to Agile Planner 2.3
It is STRONGLY RECOMMEND that you deploy all releases, service packs, and patches to a test environment prior to deploying to production. A test environment should have:
CMS-XML Error: "Could not add database connection." Manually editing web.config prompts to "save as"
This is a permission problem on the server. To fix it:
CMS-XML "Name" field and "Description" fields are not available on the Feature work item
Workaround: There are actually other fields that should also be included. The following script will fix all of them.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs