Find Answers

Filter Search Results
All Products:

Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML KM-Dim10: Upgrading server to 10.1.3 can leave some older shortcuts in place
Dimensions CM 10.1.3
CMS-XML Eclipse project rename doesn't rename project in Dimensions
After renaming the Eclipse project and delivering to Dimensions the Serena perspective view, Eclipse container node , still displays the old name. Steps to reproduce the problem? a. Right click Eclipse project b. Refactor -> Rename c. Input new name, click OK d.
CMS-XML Dim CM 14.x: dm.cfg variable DM_REJECT_OLDER_CLIENTS prevents valid Eclipse versions from connecting
PRG3300001E Error: Your Client is older than Dimensions Server . Please upgrade your Client.
CMS-XML Using vtransfer -r to rename or move an archive on an old VM File Server does not move the Revision Library directory
Using vtransfer -r to rename or move an archive on an old VM File Server does not move the Revision Library directory
CMS-XML DTK: File Server can no longer fetch old revisions from split archives after trying to update a corrupt archive 16 times
If the Revision Library of a File Server contains one or more corrupt delta.d archives, the DaemonServer that works on behalf of the File Server will stop working after processing 16 requests to write to or read from a corrupt delta.d file.
CMS-XML VM 8.3 File Server creates numerous *.ser.old# files for *.ser files
When using a Version Manager 8.3 File Server , project updates on a File Server -based Project Database will receive *.ser. old # copies for *.ser files involved in the update process, with # being an ever increasing sequence number (e.g. pvcsproj.ser. old 132).
CMS-XML "Server error" popup message
A migrated task plan has an Actual Finish date in the old data structure of 2009-08-03 00:00:00.000. After migration, it gets an Actual Start of 8/3/09 8:30 AM and no Actual Finish. This results in an error when publishing because the previous Actual Finish is before the new Actual Start.
CMS-XML SLM vendor daemon cannot use "localhost" as SERVER identifier
On systems with local product installations (including SLM) that frequently get disconnected from the network for extended periods of time, use of "localhost" as the server name in the license file would be advantageous, as the server name associated with the old IP address will become invalid after the DHCP lease runs out or the network card goes off-line.
CMS-XML VM crashes when updating old-format LDAPINFOFILE (pvcsldap.ini)
) was changed to support multiple independent LDAP servers , each with its own search criteria. Whenever a VM 8.2 clients detects an LDAPINFOFILE that specifies multiple LDAP servers in the [LDAP] section of this file (= old format, used to specify redundant LDAP servers) it will rewrite the file into the new format, with a dedicated [LDAP#] section for each subsequent LDAP server.
CMS-XML VM 8.6.1: VM I-Net Web Client Agent cannot connect to server if IIS or Tomcat requires an SSL Client certificate
With VM 8.6.0 and older , the Java plug-in would use the network connection that was already established by the browser. If the server was configured to require an SSL Client certificate, but the browser had this certificate, the Java applet would therefore transparently be allowed access.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs