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]
XML Tasks_and_Assignments_by_Resource_by_Investment.rdl
8wAAMwAM8wAZswAmcwAzMwA/8wzAMwzM8wzZswzmcwzzMwz/8xmAMxmM8xmZsxmmcxmzMxm/8yZAMyZM8yZZsyZmcyZzMyZ/8zMAMzMM8zMZszMmczMzMzM/8z/AMz/M8z/Zsz/mcz/zMz///8AAP8AM/8AZv8Amf8AzP8A//8zAP8zM/8zZv8 zmf 8zzP8z//9mAP9
MS-EXCEL Mariner On Demand_Supported_Platform_Matrix.xls
Comments ZMF ZMF 5.6.0, ZMF 5.6.1
MS-EXCEL PPM 2009 R1 Supported Platform Matrix-Customer.xls
Comments ZMF ZMF 5.x, 6.x
CMS-XML How are event notifications sent (email and internal notification)?
How are event notifications sent (email and internal notification )?
CMS-XML On Update notifications shouldn't get sent for changes not in Attribute History
Summary Summary Description of the item Nightly Post Job and Nightly Recalc job sometimes causes On Update notifications to fire and get sent out as well as the corresponding Web Service event if there is one but the changes that happened don't show in the Attribute History tab on the particular investment. It looks like certain attribute updates that occur because of these two nightly jobs are intentionally left out of the Attribute History log which is fine but the corresponding notification about a change to the investment does get fired and sent out where it shouldn't.
CMS-XML Can new system notifications be created?
ANSWER: Noc System Notifications are out-of-the-box notifications. You may, however, add notifications which will function similarly to System Notifications ( event based, multi-recipient) in the Workspace-> Notification Definitions."
CMS-XML Unable to send email from Mariner / Agile test message button or stop getting email notifications and reports.
You may get errors like below in the Application Log of the Event Viewer on the Mariner / Agile server which results in email notifications no longer being recieved. Event Type: Error Event Source: Pacific Edge Software
CMS-XML Get "Fatal WebException occured with status: NameResolutionFailure." error in application event log every minute or so.
Open the Windows Services window and restart the following services Pacific Edge Notification Service Pacific Edge Scheduler Service
CMS-XML Event viewer has error: "Exceeded maximum number of attempts to invoke webservice. status: ProtocolError url: http://localhost/PESWebUI/WebServices/peswebconfig.asmx"
If any of these keys are missing, manually create them. Then, restart the "Pacific Edge Notification Processor" and "Pacific Edge Scheduler" services and IIS. One reason these keys may be missing is if the Migration Utility is uninstalled from the Mariner server.
CMS-XML Troubleshooting Microsoft Message Queue (MSMQ) Problems or Notification sending problems.
NOTE: The user who is running the PPM/Agile IIS Application Pool must have permissions to write to this folder. Event Viewer: Check the event viewer on the web server for any error messages that may indicate the problem.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs