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 Update from Configuration Database for multi node systems always think one node is out of sync with the Configuration database
The issue presents itself for multi node SBM systems when the administrator is trying to synchronize the nodes when a node is update the other node then thinks it is out of sync even though they we both updated from the same configuration version. At this point the SBM Configurator thinks that the Node is now not in sync with the configuration database and then asked to Admin if they would like to sync it with the Config DB again. For a 2 node installation, this seem to back and forth forever.
CMS-XML Notification Server not sending updated fields
A user updates an item by adding an attachment. Shortly thereafter (30 or so seconds), the user updates another field within the same item. The email will sometimes show the old data instead of the updated data.
CMS-XML Dim CM: Updating Dimensions connection details for Eclipse following a change of server
file is called ConnectionSettings.xml and is located in C:\Users\<user> \AppData\Roaming\Serena\Dimensions\10.1 on Windows 7 or C:\Documents and Settings\<user>\Application Data\Serena\Dimensions for XP. Using the menu option requires that the other details are re-entered on changing the hostname. Directly editing the files does not require this but should be performed with adequate backup of the original file.
CMS-XML SBM: After promote changes, replication to other load balance and cluster servers does not occur (UDP Multicasting)
To verify if changes (such as javascript updates or orchestration changes) are synced across servers , you can compare the date/time stamps on the files in these folders: C:\Program Files\Serena\SBM\Application Engine\bin\javascript C:\Program Files\Serena\SBM\Common\tomcat\server\default\work\processes
CMS-XML DimCM: Pulse: Moving Pulse schema or data from one server to another
However, there is a reference to the location of the Dimensions CM server. If you are just moving Pulse, but NOT moving Dimensions CM then this won't need changing and/or updating .
CMS-XML ZDD: Site information updated in HLLX PUPD0007 displays but cannot be updated on Server
Similarly, if other changes are made to the package properties which do result in the ‘Apply’ button being enabled, pressing that or ‘OK’ again fails to update the installation date information.
CMS-XML KM-Dim7: Error! Another running instance of LVU was detected on this base database.
sqlplus <basedb>/<password> SQL> update lvu_lock set lock_state=0; 1 row updated
CMS-XML KM-Dim10: How to install a second tomcat server on the same host using https
You need to update following ports: modification des ports utilisés par le serveur web dimensions: http : 8585 Server : 8505 Ajp12 : 8507 Ajp13 : 8509 0- pour modifier le port < server : Modifie la ligne suivante dans $DM_ROOT/webtools/tomcat/conf/server.xml < Server debug="0" port="8405" shutdown="SHUTDOWN
CMS-XML #SERx member does not update application SYS LPAR details at Server task startup
) and is, at best, inconsistent. It is possible there could be other implications.
CMS-XML DS Server migration from on server to another
Then connect to the existing database. The 'Properties.Srv' file should be updated to include the new host or database name. The same thing should be done to the 'vcs_serv.ins'
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions RM: Importing Requirements
This demonstration show you how to import requirements from CSV, Microsoft Word, and Microsoft Excel files to Dimensions RM.
Dimensions CM: Introduction to streams (demonstration)
This demonstration introduces Dimensions CM streams.

Additional Assistance

  • Submit a Case Online
  • FAQs