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 Item type was not mapped error when using the SBM Report Mover widget in Agile.
Make sure the item type mappings are done for both sides. ... < Source >PES-User-Story</ Source > ... In the example above the Agile value for "PES-User-Story" can be found by going to the Configuration | Types Setup | Work Types screen and clicking on Story.
CMS-XML Get this error in Orchestration Workflow log from Agile to SBM integration "Unable to find selection operand value: XXX"
Look in the AgileToSBMAttributesMapping. config file in the Agile root directory. Near the bottom of the file are the Type mappings that occur between Agile and SBM. ... < Source >PES-User-Story</ Source >
CMS-XML Incorrect rollup type for End Date attribute
1. Launch Agile 2. Open Setup-> Configuration ->Attributes setup->Attributes 3. Select End Date attribute, check rollup type
CMS-XML How to move configuration changes from staging environment to production environment
Export the type system (Setup | Configuration | Types Setup | Item Types | Export Type System). For information about which configuration changes are exported as part of the type system, see KB S137457 .
CMS-XML Login failed unable to connect to the database using Agile Administrator
Following the installation and correct configuration of Agile and SQL Server the following error was generated when attempting to connect to Agile Administrator: "Login Failed: Unable to connect to the database"
CMS-XML Troubleshooting Microsoft Message Queue (MSMQ) Problems or Notification sending problems.
This document will describe common configuration mistakes and troubleshooting steps to follow when notifications are not being sent correctly. NOTE:
CMS-XML How can you make Agile not check the browser version you're using to login with?
By default Agile Planner checks which browser and version you're using to login with to make sure you're using a supported version. If you want to test other browsers there is an option in the web. config file that will keep Agile from checking.
CMS-XML External mashup events give error in alfeventmanager.log.
In the case of Agile 2.3 there are some built in external mashup events that will fire if you have the SBM Integration Settings filled in on the Configuration | Integration Settings screen. Those seem to work fine wether you have Single Sign On (SSO) turned on in SBM or not. These are predefined external notifications with names like AgileWICreate, AgileWIUpdate.
CMS-XML My Work view gives "The form you are trying to access has been removed, and is no longer available"
Message: Invalid filter rule: AND Task State is not blank Source : PacificEdgeSoftware.Common.ObjectServices Stack Trace:
CMS-XML Error: "Could not add database connection." Manually editing web.config prompts to "save as"
Locate the web. config file in the install directory of Mariner/PPM/Agile. By default the location is here
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs