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 Cannot use the VM I-Net Web Client with Firefox, Chrome or Edge when running VM 8.6.0 or older
The solution to this problem is to upgrade to VM 8.6.1 or newer. As of this release, the Web Client switched to an Agent based approach, where a small stand-alone agent runs on the end user's PC to run the file I/O operations previously performed by the Java-based applet. The remaining browser code can now run in all of Internet Explorer, Firefox, Edge and Chrome.
CMS-XML VM 8.6.1+: Microsoft Edge browser shows error that cannot be reached after pressing Configure button for the Agent.
Hmmm...can’t reach this page This website could not be found. Error Code: INET_E_RESOURCE_NOT_FOUND The same operation works without problems from Chrome, Firefox or Internet Explorer.
CMS-XML Problem accessing DS Web Client or ALM Java Client
After upgrading to 5.5.0 from a previous version on Windows with an Oracle database, unable to access the DS web client or ALM Java client. Previous version had no problems accessing thru the web client and able to login to ALM. With upgraded release, cannot login thru web client. Login page appears but entering valid username and password displays page cannot be found.
CMS-XML Dim CM: Performance problems with Web Client using IE11 having upgraded to Java 8 Update 65 or 66
Following an upgrade of Java 8 to either update 65 or 66 it was noticed that the performance of operations in Web Client was poor when using IE11. Browsers such as Firefox appear to be unaffected.
CMS-XML Dim CM 2009R2: Problems with Web Client functionality having upgraded to Java 1.7 Update 45
Following the release of Java 1.7 Update 45 a number of Dimensions CM 2009R2 users complained that they were not able to install or run the Dimensions applet when connecting to the Web Client . Access to the tool was allowed but functionality was severely restricted.
CMS-XML Problems running the VM I-Net web client with Java 7 Update 21 and Java 6 Update 45
and Java 6 Update 45 , released by Oracle on April 16th 2013, introduced a number of problems when used with the VM web-client due to way fixes for security issues were implemented. Currently known effects on the Version Manager Web Client are:
CMS-XML Fix for defect DEF188927 - VM SSO problems with SourceBridge
Fix for defect DEF188927 - VM SSO problems with SourceBridge
CMS-XML DTK: Calling convention problems when using VM's Developer's Toolkit (DTK) with Power Builder (PB) applications
DTK: Calling convention problems when using the DTK with Power Builder (PB) applications As stated in the documentation, the functionality of VM Developer's Toolkit (DTK) can be used by C/C++ but also Visual Basic and Borland Delphi programmers.
CMS-XML VM 6.7.x performance problems on AIX 4.3.3 Multi-processor Machine
Aside from following the standard procedures to optimize performance in VM on UNIX, for AIX 4.3.3 you also need the following versions of JAVA patches on the system. JAVA this includes the following patches : 1. Java rte.bin version 12
CMS-XML Problem: Files do not remain under version control after closing and reopening a Codewright project interfaced with VM using the SCC interface.
There are two ways to associate a Codewright project with a VM project using the SCC interface. While in Codewright, the two ways are as follows:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs