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 PDF widget will not work if there is a special character in the SBM field name
SBM 2009 R4.03
CMS-XML DIM CM - SBM: Dimensions CM Connect for Business Mashups shows invalid characters
Check TS_STRINGVALUE and TS_STRINGDEFAULT in TS_SYSTEMSETTINGS where TS_NAME='Pre-Unciode Charset'. If they have a value then set them both to NULL, restart the system and try again.
CMS-XML Import from Tracker to SBM in Oracle - some characters change language
Doing a data import into SBM from a Tracker project, special characters that were Portugese turned into what appeared to be Chinese. This can happen when the character set the Oracle client uses when connecting to the Tracker database and the character set used connecting to the SBM database do not translate correctly. Oracle does the translation so all the character sets must be identified correctly to Oracle.
CMS-XML Special characters in email templates being cut off
SBM 2009 R3.02
CMS-XML Requiring special characters in password is satisfied by a number
SBM 2008 R2.03
CMS-XML Mashup: special characters in field database name cause Publish to fail
SBM 2008 R1
CMS-XML Reports using xml/report template incorrectly encode special characters (double encode)
SBM 11.3.1
CMS-XML Add URL action may percent-encode special characters in the URL resulting in a broken link
SBM 11.1
CMS-XML Sub-relational field with special characters used in query at runtime in embedded report causes Composer to error
SBM 10.1.2.2
CMS-XML When editing a user in the web admin with a special character, this can cause TeamTrack to crash
This has been fixed in Serena Business Mashups 2008 R2.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs