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 Common logging interface not available
In server.log the following messages appear many times. 2016-12-29 15:09:39,841 ERROR [http-nio-8243-exec-3] [com.serena.commonlogger.internal.db.HibernateSessionFactory:181] [::] -- Serena Common Log failed to initialize. com.serena.commonlogger.ClException: Could not find 'SCHEMA_VERSION' setting.
CMS-XML Error "Failed to get events: org.apache.axis2.AxisFault" or "Common logging interface not available. The error from the Repository was: org.apache.axis2.AxisFault"
Composer gives error: Common logging interface not available. The error from the Repository was: org.apache.axis2.AxisFault
CMS-XML SBM: Event viewer gives error "Exception caught in common logger while getting context types. Common logger will not be used."
Details: Failed to connect to database. - [Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces : Error Locating Server/
CMS-XML Common log entries are truncated in composer even when setting maxMessageSize = 128kb
limit is about 40960 (40 KiB) to allow for headers around the message. The workaround is to leave Composer set as-is or up to about 40 KiB, but to fetch records using the AR interface instead, where the complete record will be available. This will be fixed in a future release.
CMS-XML Query at Runtime Embedded Reports display error when clicking Show Full Interface
- create a listing report in SBM UI which uses a Query At runtime field and give it a reference name - open the process app in Composer - and add this listing report to a state form as an embedded report (the QAR parameter should get selected automatically) - deploy the process app
CMS-XML SBM Composer, when set dependencies,values list should be pinned at its original place
At Composer set dependencies interface , when you change the setting for the selected value, the values list will always change back to display the values list from the top. When the length of the values list is longer than the length of the view box, this will be a bit annoying.
CMS-XML Composer, mapping field, "mapped to" value allow format "fieldName" causing confusion, mapping disappear.
Composer interface , when you do mapping fields (Post transition for example), for "Mapped to" column, you can select the field name from the drop down by clicking the arrow button, and you will get the value with the format like this fieldName(FieldDatabaseName), for example, Title(TITLE).
CMS-XML WorkCenter form styling incorrect and does not match preview in Composer for aligning fields
The form styling shown in Composer differs from that in WorkCenter and may be misaligned incorrectly. Classic interface is fine.
CMS-XML Preview form of classic in Composer is not representative of the default upgrade to10.1.4.x whereby HTML5 is turned on
With the upgrade to 10.1.4.x the Form Preview in Composer of classic is not representative of the default interface after upgrade. After upgrade the default is that HTML5 is switched on in the classic interface . The Work Center view is a better representation of the HTML5 classic.
CMS-XML SBM Composer May Crash on Windows 10 After October 10, 2017 Update Is Installed - Error: Unable to load ‘penimc.dll’: The specified module could not be found
Go to Control Panel > Device Manager In the list of Human Interface Devices , locate HID-compliant touch screen
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs