Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Get "Fatal WebException occured with status: NameResolutionFailure." error in application event log every minute or so.
0f192379-1d8e- 4 b5c-82c3-08f3445d168d User Message: Fatal WebException occured with status: NameResolutionFailure. Dev Message: Fatal web exceeption
CMS-XML Displaying incorrect Logs Widget headings on Homepage
4 . Add Logs widget to the form and set this to AAA that you saved at Step2. Save.]
CMS-XML Updated log item name does not reflect correct for the first time
3. Now change the item1 to Itemfirst from Summary tab and save it using the SAVE icon in lower view. 4 . You will notice that in the upper view the sequence become Item2 and then following by ItemFirst 5. In upper view the system highlighted Item2 but in lower view it displays ItemFirst
CMS-XML Active users are logged out with "Your session has timed out. Please log back on to continue where you left off" message
4 . Repeat step 3 over and over. On the 4-7th time, when you click the resources name, you will get kicked out to a login screen that says "Your session has timed out. Please log back on to continue where you left off".
CMS-XML Discussions, Issues, Risks, Change Log tabs are not refreshing correctly
3. Go to the Risk Tab and notice that the converted issue is not displayed 4 . Refresh browser and now the converted issue is displayed 5. If there are a list of Risks already present, you can click on any existing risk which will "refresh" and the converted issue will show up.
CMS-XML Home page log widget won't open investment when clicked.
2. Go to the Configuration | View Management | Log View screen 3. For the Discussion log make sure the "Can Assign" option is enabled. 4 . Now go to the Home page and select an investment that has some discussion logs for the log widget you created.
CMS-XML Rich text field in discussion log causing slow script error
4 . Now cycle through all three like you did before and notice after cycle off the one with the lines the browser hangs and eventually says "Stop running this script?" 5. Not sure what it's doing in the background in this situation but it's causing the page to stop responding. Only workaround I could see was to either not use multiple lines in the field or change the Rich Text field to Non rich text.
CMS-XML Notification service gives error "Log entry string is too long. A string written to the event log cannot exceed 32766 characters" and must be restarted
at PacificEdgeSoftware.Notifications.Processor.NotificationProcessor.PollConnections(Object sender, ElapsedEventArgs e) --- End of inner exception stack trace --- 19 Jun 2010 20:07:14,988 [Default] (null) ERROR 4 - An item with the same key has already been added.
CMS-XML New log type: Role permission description is wrong.
Found in PPM9. 4 .
CMS-XML Reporting on Custom Log Views
Reporting on Custom Log Views
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs