Alerts

VM: Known issues with Version Manager 8.0.2.0



ID:    A4
Published:    09 July 2005
Updated:    24 April 2008

Operating System(s)

  • AIX
  • All Windows
  • HPUX
  • Linux
  • Solaris
  • Unix
  • Windows 2000
  • Windows NT

Product(s)

  • PVCS Version Manager
 

Description

1. Any single user cannot open more than one PDB at a time when using Professional_named licenses.

In a simple scenario, you install named licenses and assign them to developers. One of the developers starts the VM desktop client and opens a PDB. Next, that developer attempts to open a second PDB, using the identical user id as used with the first PDB. That developer will now be denied access to this PDB (and subsequent ones) with an error stating that the login account was unable to obtain a license.

Workaround:

  • In the Merant License Server directory, modify the file licmgr.ini file such that the '[AUTOADD_FEATURES]' section includes 'VersionManager_named=true', even if you don't have VersionManager_named licenses.

    The downside of this workaround is that if you have both Professional_named and VersionManager_named licenses, the Professional_named users will also be assigned assigned a VersionManager_named licenses.  This can be prevented by making sure all users who should be using a VersionManager_named license are listed first in the users.lst file, meaning there is an 'INCLUDE VersionManager_named USER VMUserID' line for every VersionManager_named license.

    The workaround will add additional 'INCLUDE VersionManager_named ...' lines to the users.lst file, referencing Professional_named users, which should be removed once a solution is put in place (the VM 8.0.2.3 patch; see Solution section below).

2a. Users receive an A: drive error while browsing the local file system in the VM desktop client.

When using the "browse" capability for local file systems or when trying to open a PDB, some users get the error:

This is an issue with the VM desktop client.  The dialog can be dismissed and the user can successfully browse to the desired path.

2b. Users are not able to browse the local file system in the VM I-Net client using certain versions of the Sun Java plug-in.

Clicking the "browse" button ([...]) in any VM I-Net dialog with a file browse button causes an exception to be displayed in the Java Console, and no browse dialog is displayed.

  • Problem occurs in Mozilla/Netscape on all Sun JVMs (tested 1.4.0_04, 1.4.1_01, 1.4.1_07, 1.4.2_06, 1.5.0)
  • Problem occurs in IE on Sun JVMs version 1.4.1_07 and up (tested 1.4.1_07, 1.4.2_06, 1.5.0)
  • Problem did not occur in IE with either the Microsoft JVM (MS JVM) or on Sun JVMs 1.4.0_04 and 1.4.1_0

Workarounds:

  • Use the Microsoft JVM (MS JVM) with IE. 
    If you currently don't have the MS JVM installed on your system, you can download it from our KB Article 49641.
  • Use a Sun JVM with IE that does not exhibit the problem.
  • Manually type the full path name to the file/folder.

3. The VM Web Application Server (I-Net / WebDAV / File Server) will not launch on a system that does not have a direct, non-proxy connection to the internet.

The VM Web Application Server does not work in environments that are not directly connected to the Internet, as the server is trying to access a DTD file from java.sun.com.  If your server is on a secure network, this may prevent you from using VM I-Net / WebDAV / File Server.

When this problem occurs, your Tomcat logs would show:

Merant VM web client 8.0.2.0 (651)
Servlet Locale = en_US
xmlFile=C:/Program Files/Serena/vm/common/tomcat/webapps/vminet/WEB-INF/web.xml
Loaded remote dtd: http://java.sun.com/j2ee/dtds/web-app_2_2.dtd
java.net.UnknownHostException: java.sun.com
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3232)
        ...

or

Merant VM web client 8.0.2.0 (651)
Servlet Locale = en_US
xmlFile=C:/Program Files/Serena/vm/common/tomcat/webapps/vminet/WEB-INF/web.xml
Loaded remote dtd:
http://java.sun.com/j2ee/dtds/web-app_2_2.dtd
java.net.ConnectException: Connection timed out: connect
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3232)
        ...

Workaround:


Issues #1 and #2 are resolved in the VM 8.0.2.3 patch, which can be applied to VM 8.0.2.0.

Issue #3 can be resolved using the workaround listed above, or by installing VM 8.1.0.

Migration ID

KB70649

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs