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 SBM Configurator on Japanese OS writes Unicode characters to database as a string of question marks
3) Go to email page, observe the value of the sender field (Notifcation Server tab => Options groupbox => Sender that appears in email subject or body) 4) Check that it correctly displays "SBM 通知サービス" 5) Click Apply
CMS-XML Taskplan: Inserting Columns does not save correctly.
You can save the taskplan columns settings to the taskplan view, but the behaviour is not right and confusing. It is replicable on PPM 10.2.6 Sample DB . - Test 1:
CMS-XML RLC: non-ASCII text fields are not saved or decoded correctly (impacts Tasks and Deployment Units)
This is only a problem with SQL databases that were initially created with RLC 6.2.6. This defect does not apply if the database was created with an older version of RLC and later upgraded.
CMS-XML Problem: Choice field values not saved correctly when viewing an SCR (submitted via TRKINET) in regular\classic Tracker Gui,
A problem was found recently where by under certain conditions, users may submit an scr via Tracker inet having set the value of a choice field to a particular choice and when they view the record in regular\classic Tracker Gui, the value of this choice field is different from that displayed in Tracker inet. If a customer reports this problem please confirm the version of Tracker and most importantly the database type and version and see a senior member of the Tracker team.
CMS-XML Dim12.2.2: Correcting the Wrong Database System Identifier.
set db_name = ‘Correct Database System Identifier ' where db_name = ‘wrong Database System Identifier '; SQL> commit ;
CMS-XML KM-Dim9:42964-CM_DB_NO_COMMITError: Failed to commit changes to database
The Database platform and version being used The exact list of steps to recreate the error message A detailed control plan report
CMS-XML Document view gives error "Database specified in security token was not found in the collection of supported database servers" followed by "The Document Repository is not configured correctly"
Click Save .
CMS-XML Event triggers compiled in c++ on Unix or Linux systems may not work correctly with unicode database
endif #endif Save the ARCH file and compile/build your event.
CMS-XML Import From Database results in incorrect times
When doing an Import From Database in Mashup Administrator from the Tools menu for an Access database with the Serena Business Mashups date/time field mapped to an Access date/time field storing only date values, date/time values are written to the database without being adjusted to GMT so they display in the web interface with the correct value. In the Pacific timezone (GMT -8:00), the web interface displays a value of 4:00PM on the day before the correct value.
CMS-XML Common Log Messages Not Stored Correctly
Common Log errors appear in the Event Viewer and Application Engine messages are not written to the Common Log if your SQL Server database is stored in a named instance.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs