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 Dim12: Change Request Report fails to run on Unix server and gives no error message
If a Dimensions CM Windows server is available, this report runs to completion on a Windows server . This problem has been forwarded to R&D for correction in a future version.
CMS-XML Notification Server not sending updated fields
The notification rule is set to send an e-mail when an item changes . A user updates an item by adding an attachment. Shortly thereafter (30 or so seconds), the user updates another field within the same item.
CMS-XML How to install two versions of Serena Common Tomcat on the same server
This document was originally written with Release Manager upgrade in mind, but the same concepts apply for any system where two versions of the Serena Common Tomcat are needed. In these steps, we will change Tomcat 6 to use port 8081 and install Tomcat 8 on the default port 8080. The assumption is that Tomcat 6 will eventually go way, leaving Tomcat 8 alone on the default ports.
CMS-XML JBoss Server Does Not Shut Down after Stopping JBoss Service
The JBoss service mechanism was changed in SBM 2009R4.X to support 64-bit machines. It has been reported that this mechanism can sometimes leave the JBoss server running even after the controlling Windows service has been stopped. Serena believes this problem could be caused by the service user not having the correct Windows authorizations, but have been unable to confirm this.
CMS-XML Unable to make NS changes without restarting IIS/AE - regression
Now that the Notification Server (and mailclient) are part of the JBoss installation, be aware that if you need to apply changes to them (such as enabling Verbose logging), this will require a restart of JBoss and IIS when you click "Apply" in the Configuration Utility.
CMS-XML Changes to javascript are not deployed
Even after changes are deployed, the changes are not seen on the server or by the browser.
CMS-XML Changing the SSO Keystores password causes deploy and promotes to fail
Modify the KeystorePassword element for the 2 TrustedDelegator sections in the CONFIGURATION.xml file that exists in [SBM Install Dir]\common\jboss405\ server \default\deploy\idp.war\web-inf\conf.
CMS-XML Scheduled deployments are off by one hour on a WIndows 2008 R2 64-bit server in Chile time zone with Dimensions CM 12.2.2 and SQL Server 2008
The problem happens when time changes from standard time to summer time in Chile time zone. In this particular instance the problem appears to happen from 07-SEP-2019 to 13-OCT-2019; outside of this date range scheduled deployments work correctly.
CMS-XML Target Server information not saved correctly
ERROR -- Can't deploy a process app with orchestration to an environment that doesn't have target servers defined. This is caused because Chrome browser does not correctly save the information you put in the Target Server , although user had changed the target server , chrome put the type back to "System Event Manager" every time it was changed
CMS-XML Need to stop two configurators being able to be started on the same server as can overwrite each other and cause configuration issues
The way to resolve this may depend on the changes made. If just one server involved (i.e. not load balanced/clustered) then a re-installation might be the easiest option. Alternatively you need to change and reconfigure all the parts that both admins changed and apply.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs