This file lists the defects fixed, enhancements made, and behaviors changed in each release of Version Manager. For information on installing and using the current release of Version Manager, see the <Install_Directory>\vm\readmevm.html file.
NOTES:
Each service pack contains all previous defect fixes released since the last full Version Manager release. It is not necessary to install the previous service packs.
Items marked with a "Δ" (Delta) symbol include BEHAVIOR CHANGES that are more extensive than simply restoring function to an existing feature (starting with version 8.1.4.2).
For additional information on using a new or modified feature listed below, see the relevant Version Manager manual, Help system, or readme file as indicated below.
Version Manager now runs natively in 64-bit mode on the 64-bit Operating Systems listed in the Support Platform Matrix.
BEHAVIOR CHANGE:
The Serena VM Web Application Server can only be installed on a 64-bit operating system. Users running a 32-bit version of Windows can still install the Desktop Client components of Version Manager.
The Serena VM Web Application Server no longer reads server configuration parameters from the registry when it is running as a Windows service. To change the default settings, modify the line:
set JAVA_OPTS=...
in the file VM_Install_Dir\vm\common\bin\pvcsstart.bat. These settings are used in service mode as well as in application mode.
Added logging for security changes, configuration changes as well as changes in workspaces for projects and files.
To show whether a path to a (default) workfile location or default archive location is absolute or relative to its parent, the UI has been updated to show both the stored path as well as the computed full path this results in. This change affects several dialogs (SetWorkspace, Properties Workspace on project, Properties Workspace on file, etc.)
BEHAVIOR CHANGE:
The fields where users can change the (default) workfile location and default archive location now show the data exactly as stored in the project database. An additional field is shown immediately below that has the computed path.
Added correct handling of Add Files operations being canceled by an Event Trigger.
BEHAVIOR CHANGE:
When an Event Trigger action fails, the Add Files operation on the given file is aborted and the file is not added to the repository.
The Source Bridge integration for SBM can now be installed as a components during the installation of Version Manager itself.
BEHAVIOR CHANGE:
The format of the file VM_Install_Dir\vm\common\pvcsprop\pvcs\vm\sso\card.config was changed so a 32-bit and a 64-bit PKCS#11 library can be specified independently. This is necessary when using SSO from an SCC-based IDE on a 64-bit OS, as SCC itself is always 32-bit. Example:
name = CARD_CONFIG
library32 = "C:/Program Files (x86)/ActivIdentity/ActivClient/acpkcs211.dll"
library64 = "C:/Program Files/ActivIdentity/ActivClient/acpkcs211.dll"
If ActivClient was already installed during the installation of Version Manager, the paths to the ActivClient PKCS#11 libraries will automatically be added to the card.config file.
The processes of creating, importing, exporting and verifying SSO and SSL configuration for VM installation can be much easier now by utilizing certtool. This utility is able to compare JKS files, generate a CSR to have a CA sign your SSL certificate, examine SSL server certificates chain, import certificates into VM and many other trust stores, and work with SBM exported zip files containing SSO truststore.
To make future upgrades easier, it is recommended to no longer add certificates directly to the cacerts file of Version Manager's JRE and JREs used by Eclipse RIDE-based IDEs, for example to facilitate the integration with SBM over HTTPS (SSL). Instead, simply put the .cer files for these certificates in the folder VM_Install_Dir/vm/common/pvcsprop/pvcs/vm/ssl/customer-certs (using any name you want) and run the following command to update the JRE that Version Manager uses with these certificates:
certtool -ssl-updatecacerts -target-vm-jre-cacerts
If you use the Eclipse RIDE integration, also run the following command to update the JRE/JDK used by that IDE:
certtool -ssl-updatecacerts -target-eclipse-jre-cacerts "PathToEclipse"
Prior to using this command the Eclipse RIDE integration needs to have run at least once using VM 8.6 or newer, as doing so creates a .pvcsvm_jre file in the Eclipse directory that certtool needs to locate the JRE Eclipse is using.
If the password on the cacerts keystore was changed from its default value ("changeit"), add the option -keystorepass "KeystorePassword" to the command to specify the new password.
Added tracking of installed features and added ability to add features later, and skipping several setup pages.
BEHAVIOR CHANGE:
If the SSO component is installed, you can skip the LDAP configuration section and edit the Configuration.xml file later. If the Eclipse RIDE component is installed, you can leave the Eclipse installation path empty and link Eclipse to Version Manager post-installation by running VM_Install_Dir/vm/Integrations/plugitin.
BEHAVIOR CHANGE:
The "User naming attribute" field in the LDAP Server configuration dialog is currently a free-text field with a drop-down list providing quick access to commonly used values.
You can now specify compound (complex) LDAP queries using the (Attribute={0}) format, where {0} is replaced by the User Name value of the user trying to login. Any syntax supported by your LDAP server is permitted. When using this feature, make sure all Version Manager clients are running VM 8.6 or later to avoid login failures.
These have been fixed by upgrading Tomcat to version 7.0.75.
These have been fixed by upgrading to latest JRE 8 version
Many improvements were implemented for setuid mode:
BEHAVIOR CHANGE: vmlinklib on Linux uses ldconfig to update the list of shared libraries. vmlinklibs is now supported on HP-UX as required by the default OS configuration on Itanium (IA64).
To help analyze memory related problems that are not caused by a HeapSize (-Xmx) set too low, the Serena VM Web Application Server now automatically save heap dumps for OutOfMemory exceptions.
BEHAVIOR CHANGE:
Heap dump is always created in ${PVCS_HOME}/common/tomcat/logs/heap_dump.hprof on OutOfMemory exceptions. These files can be quite large and should be deleted if analysis is complete or not needed.
The Copy Project Wizard now includes 'Do not add a Configuration File' and 'Do not add an Access Control Database' to allow copying projects without their Configuration file(s) and/or ACDB file(s).
It is now possible get a a list of published Project Databases from connected File Servers by using the newly added option -fp. This runs much faster than using -z and shows Project Databases from all published Path Maps.
When a PCLI command encounters an archive that lacks the revision, label or group it was asked to operate on, it prints a warning message for this file and sets a non-zero exit code. You can now specify the option -qr to quietly ignore these missing revisions, labels and groups without affecting the command's exit code.
When the option -qe is used with PCLI commands to quietly ignore invalid entity paths, you still get the error "This command requires one or more projects or versioned items to ..." when no valid entity path is left. By additionally specifying the option -qz you can now suppress that error as well, and avoid PCLI setting a non-zero exit code.
If the delta-todo.d file for a split archive instructed the Background Processor to add a revision to the delta.d file that either already existed there or that did not exist as a RevNumu file on disk, the attempt to do so would always fail, leaving a trail of error messages in the logs. As the process runs every 24 hours, this unnecessarily cluttered the log files. The Background Processor now makes note of this problem once and no longer tries the operation during future runs.
BEHAVIOR CHANGE:
The offending record will be removed from the delta-todo.d file, and the event will be recorded in the file delta-error.log that is stored in the same Revision Library directory.
This has been fixed by additional paths validations on create and modify path maps, preventing the use of relative project and revision paths and empty project paths.
While performing a recursive Get on a version label or group, Version Manager would create subdirectories for every project, even if no file in that project had a matching label or group. This could result in the creation of empty workfile directories. On the flip-side, customers wanting empty folders to be created for projects without files found Version Manager would not do this either.
This was fixed by adding the option "Create empty workfile directories" to all clients.
BEHAVIOR CHANGE:
By default Version Manager no longer creates empty folders during a Get or Checkout operation if a project has no matching files or no files at all. Selecting the option "Create empty workfile directories" will create empty folders for projects that have no matching files or no files at all.
If the locale that was used when a file or project was added to the Project Database has a different sorting sequence than the locale of a user trying to access it, the file or project may become inaccessible. This issue was fixed by automatically resorting the project on open if a non-matching collation sequence is detected.
The date format for the Desktop Client GUI now supports 'ddd' and 'dddd' to display the day of the week.
This issue was caused by a bug in Java 7 and was fixed by the upgrade to Java 8.
This has been fixed.
This has been fixed.
Attempting to rename a file to one containing bracket characters gave the error "invalid name for a versioned file." This has been fixed.
This issue was fixed by changing the library search path such that OS libraries have precedence over the ones Version Manager provides.
The following issues were fixed:
This has been fixed.
The failure was triggered by Solaris 11.3 changing the standard shell commands (sh, mkdir, etc.) from 32-bit executables (ELF 32-bit MSB executable SPARC32PLUS Version 1) to 64-bit ones (ELF 64-bit MSB executable SPARCV9 Version 1), which was incompatible with the use of $LD_PRELOAD in the launcher script. This issue was fixed by removing the $LD_PRELOAD dependency.
The Desktop Client GUI on UNIX may disappear after the initial splash screen depending on the X server configuration that was used. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
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. This has been fixed.
This issue has been fixed by removing the need to use this directive.
Certain types of archive corruption would go undetected by vsplit's archive validity check. This has been fixed.
PCLI lacked the ability to display or copy a variable as-is if its value contained a double quote character. This was solved by the introduction of the -tq (trim quotes) option for the Echo and Set commands, which lets you display and copy the contents without modification. Examples:
echo -tq "$EVENTUSERID:$EVENTPASSWORD"
set -tq PCLI_ID="$EVENTUSERID:$EVENTPASSWORD"
You can also enable this option by settings the PCLI or environment variable PCLI_TRIM_QUOTES to true. As such, the following commands will behave identically to the ones above:
set PCLI_TRIM_QUOTES=true
echo "$EVENTUSERID:$EVENTPASSWORD"
set PCLI_ID="$EVENTUSERID:$EVENTPASSWORD"
Passing arguments to PCLI from a Linux/UNIX shell required the use of escape characters beyond what is typical for Linux/UNIX commands (see KB doc S141561). PCLI command line argument handling was improved to more closely match the behavior of common Linux/UNIX commands. This only affects arguments getting passed to PCLI from the command line; argument processing inside PCLI scripts remains unchanged.
Prior to VM 8.6:
$ pcli echo -ns "PCLI_VERSION=\\\$PCLI_VERSION"
Serena PVCS Version Manager (PCLI) v8.5.3.0 (Build 071) for Linux/80x86
Copyright (C) 1985-2015 Serena Software. All rights reserved.
PCLI_VERSION=8.5.3.0 en_US (Build 071)
$
As of VM 8.6:
$ pcli echo -ns "PCLI_VERSION=\$PCLI_VERSION"
Serena PVCS Version Manager (PCLI) v8.6.0.0 (Build 370) for Linux/x86_64
Copyright (C) 1985-2017 Serena Software. All rights reserved.
PCLI_VERSION=8.6.0.0 en_US (Build 370)
$
BEHAVIOR CHANGE:
PCLI commands using pre-VM 8.6 escape characters need to be changed to remove extraneous escape characters. If you do not want to do this, create the environment variable PCLI_PRE_VM9_QUOTING to re-enable the old argument handling behavior. Example:
Attempting to use pre-VM 8.6 escape characters with VM 8.6:
$ pcli echo -ns "PCLI_VERSION=\\\$PCLI_VERSION"
Serena PVCS Version Manager (PCLI) v8.6.0.0 (Build 370) for Linux/x86_64
Copyright (C) 1985-2017 Serena Software. All rights reserved.
PCLI_VERSION=\8.6.0.0 en_US (Build 370)
$
Re-enabling old argument handling:
$ export PCLI_PRE_VM9_QUOTING=true
$ pcli echo -ns "PCLI_VERSION=\\\$PCLI_VERSION"
Serena PVCS Version Manager (PCLI) v8.6.0.0 (Build 370) for Linux/x86_64
Copyright (C) 1985-2017 Serena Software. All rights reserved.
PCLI_VERSION=8.6.0.0 en_US (Build 370)
$
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
The following improvements were made when PCLI debugging is enabled by using the (environment) variable PCLI_SCRIPT_TRACE:
To encrypt the password, run the command:
VM_Install_Dir\vm\common\bin\sso_encstring -e "Password"
The resulting output can be used in place of the plain-text password in the SSO Configuration.xml file. See KB doc S141849 for more information.
Added support for Eclipse 4.5 (Mars) & Eclipse 4.6 (Neon).
This issue was fixed by adding 64-bit support to Version Manager.
Fixed confusing message in RIDE consoles.
BEHAVIOR CHANGE:
If a user specifies 'No' for remaining files during a multi-file checkin, the log now shows 'Unlocked unchanged revision' instead of the invalid status 'Checked in file'.
This has been fixed.
This has been fixed.
This has been fixed.
Users can now also rename files in the Web Client, if Rename was enabled from Configure Project.
For certain operations the VM I-Net Web Client creates temporary .cmd files in the %TEMP% directory from which it launches an application, like the Diff/Merge tool. On some systems, this is blocked by security software or the Windows configuration. Changing the Default Location for New Applet Installations on the end-user's system (via /vminet_install.html) would move the executables themselves to this directory, but the temporary .cmd files were still written to %TEMP%.
The .cmd files are now created in a "launchers" subdirectory of the applet directory (DefaultLocationForNewAppletInstallations\serena.vm-*-*\launchers).
These errors were displayed if one of the following scenarios was true:
Version Manager now shows the IOException as reported by the OS.
This has been fixed. Version Manager now shows the IOException as reported by the OS and moves on to the next file.
This has been fixed.
This has been fixed.
If a user leaves the login page on the screen for a long time and the Tomcat instance running the Serena VM Web Application Server has since been restarted, the user can still login but gets an "Unexpected Error has occurred" message afterwards. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. To use this feature, you still need to add:
vsd=application/vnd.visio
to the file VM_Install_Dir\vm\common\pvcsprop\pvcs\vm\mimetypemapper.properties to ensure the browser receives the proper MIME type.
After upgrading the Java Plug-in to JRE 8 Update 91, attempts to use the VM I-Net Web Client via Firefox fail with the error: "This browser has no Java Runtime Environment (JRE) or access to it was blocked." This issue was caused by a Firefox specific change in the JRE.
This issue has been fixed. This fix was also made available for VM 8.5.3 in Patch 003.
The date format for the servlet now supports 'ddd' and 'dddd' to display the day of the week.
This has been fixed.
Version Manager now has a single installer that detects a Japanese Windows environment and will suggest installing additional localization support.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When a Project Database is copied via the Desktop Client using Edit -> Copy, the VCSDIR directive in the Configuration File is not updated to reflect the target location.
This has been fixed.
A localized version of PvcsMerge was absent from VM 8.5.1 Japanese.
This has been fixed.
The Locks section of the Change History output now includes a time stamp for each lock in the archive. The Change History output can be obtained via the commands pcli vlog or vlog (CLI), the 'Show History' report in the Desktop Client or the 'History' report in the Web Client.
BEHAVIOR CHANGE:
If you have scripts that parse the output of CLI or PCLI vlog commands, and those scripts cannot cope with the added timestamp information, you can disable displaying the lock timestamp by adding pvcs.showLockDateInVlog=0 to the [PVCSGUI_6.5] section of your ISLV.INI or .islvrc file.
Built-in JRE version was upgraded to latest (and last) JRE in 7 line.
This has been fixed.
On systems with multiple IP addresses, including mixed IPv4 / IPv6 configurations, Version Manager sometimes does not detect that a client was local to the server. Depending on the File Server configuration, this can affect the ability to run the File Server Admin utility as well as running readdb, makedb, vsplit and vtransfer.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
The online help (-h) for AddFiles now show descriptions for the options -ph (Preserve hierarchy), -pw (Preserve hierarchy workdir), -r (Initial revision number) and -n (Generate new archive if there is an existing one).
This has been fixed.
This has been fixed.
Using VTRANSFER from VM 8.4.6 or newer to rename a split archive on an File Server running VM 8.1.3.2 or older does not rename the revision library for the archive, effectively leaving a non-functional archive.
This has been fixed.
This has been fixed.
This has been fixed.
Support for Visual Studio 2013 was added.
Support for Visual Studio 2015 was added.
This has been fixed.
When using Server-Side Processing with a Project Database that has the Login Source HOSTID, RIDE operations are executed as the user running the Serena VM Web Application Server process on the server.
This has been fixed.
Prior to VM 8.5.3, files were read-only after an 'Open from source control' operation, even if the 'Make writable' option was enabled in plugin options.
BEHAVIOR CHANGE:
Now 'Make writable' flags disables read-only flags at all for all workfiles and all operations, so there are no message about 'Overwrite read-only files.'
Prior to VM 8.5.3, all project and solution files were read-only after 'Open from source control' operation.
BEHAVIOR CHANGE:
Now all project and solution files are always writable after all operations.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
New prompt alerts user if a local file is about to be deleted to protect against accidental file deletion.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When using Server-Side Processing with a Project Database that has the Login Source HOSTID, certain RIDE operations (like Compare Workspace) are executed as the user running the Serena VM Web Application Server process on the server.
This has been fixed.
This has been fixed.
This has been fixed.
The contents for several dialogs didn't fit into their allotted space and were inconvenient to read.
This has been fixed.
This has been fixed.
Users can now also manually input revision information without having to use an additional selection window.
A new message was added to hint at the various root causes for the message.
This has been fixed.
This has been fixed.
The Application Server and the VM clients were enhanced to also work in an IPv6-only environment on all platforms except HP-UX. On AIX, only the connection to the Serena License Manager (SLM) needs to still be IPv4 based.
Sometimes on UNIX/Linux platforms internal path storage did not store the paths properly on copy operations, causing the subsequent Rename operation to fail.
This has been fixed.
If a Project Database name contains Japanese character, the list of project databases shows invalid characters.
This has been fixed.
If a Project Database has a login method that requires a password, entering the wrong password in the first dialog that shows up will lock up the GUI, requiring a restart of that application. This can also happen if there are problems with the configuration for the login source, like having an invalid SSO server URL.
This has been fixed.
If the path to an archive contains the directory "ROOT" anywhere, attempts to access the archive will fail.
This has been fixed.
VM 8.5.0 included an updated third-party axis2 module that contained a new temp file handler. Unfortunately this code dealt poorly with concurrent use, affecting concurrently running PCLI processes that authenticate via SSO.
This has been fixed.
This has been fixed.
This has been fixed.
When a File Server-based PDB has a missing pvcsid.ser file, adding an entity or trying to rebuild the pvcsid.ser file using pcli ScanPDB give an "Array Index Out of Bounds" error.
This has been fixed.
The vjournal option -oGET is supposed to show locking get operations (check out) and non-locking get operations (if those configured to be logged), but it only shows the latter.
This has been fixed. The option -oGET now shows both types of get operations.
To only show locking get operations, use vjournal -oCHECKOUT
To only show non-locking get operations, use vjournal -oGETNOLOCK
This has been fixed.
The Configure Project dialog for Event Triggers did not include __EventLock__ as an option for trigger where it should be available.
This has been fixed.
This has been fixed by upgrading the JRE.
These have been fixed by upgrading to Tomcat version 7.0.55.
The Version Manager File Server has a Background Processor task that runs once a day to perform maintenance on the Revision library. This task can be fairly resource intensive, so the File Server administration web page now includes the ability to set the time this task is run at, letting the administrator pick a time that does not interfere with regular system use.
This has been fixed.
You can now edit this and other parameters from the Advanced tab in VPADMIN.
Prior to VM 8.4.6, selecting 'File Servers' would show the list of project database. As of VM 8.4.6, this choice leads to an intermediate page where you have to choose between that list and a list of path maps. Serena received requests to cut out this intermediate step.
This has been implemented. The choices 'File Servers - Project Database View' and 'File Servers - Path Map View' can now directly be selected from the Look in drop-down list.
BEHAVIOR CHANGE:
The intermediate page that used to show these two options was removed, as well as the 'File Servers' choice in the drop-down that lead to it.
This has been fixed.
This has been implemented. The Serena VM Web Application Server launcher pvcsstart.sh now warns about possible problems if the user running it is different from the one that installed Version Manager. If, in addition to this, the user running the launcher is root, the startup with abort unless an override option was provided.
This has been fixed.
The PCLI List command now supports an easier way to refer to branch revisions on versioned files. Previously, accessing the branch revision 1.0.1.2 would require an entity path like /chess/server/server.bat/1.0/1.0.1/1.0.1.2. As of this release, you can also use the more obvious path /chess/server/server.bat/1.0.1.2.
Starting with VM 8.2.0.0, if you change the pvcsldap.ini file location on the LDAP screen using the file browse button, you cannot apply the configuration file change(s) as neither Apply nor OK will close the Configure Project dialog anymore. The only way to close the dialog is to press Cancel, which causes you to lose the changes.
This has been fixed.
If an Add Files operation fails on an instance of Version Manager running on Linux or UNIX, the meta-data archive that was briefly created for the failed operation will not be deleted if it is located on a remote File Server.
This has been fixed.
The fix for DEF166804 in VM 8.3, which aims to delete Revision Library (RevLib) components when Version Manager rolls back a failed Add Files operations involving a split archive, contains an undocumented requirement that writable utilities have to be enabled on the File Server.
This requirement was removed.
Support for Eclipse Luna was added.
Support for Eclipse Kepler was added.
File edit operation is blocked for all projects, not just the one being import into.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
BEHAVIOR CHANGE:
To implement fixes for the problems listed above, the communication between the RIDE clients and the Serena VM Web Application Server was significantly improved. However, a single pre-8.5.1 RIDE client can effectively cancel out these improvements. To prevent this from happening, the server will reject these old clients by default.
If there is an urgent need to let older RIDE clients connect, you can add the following to the ISLV.INI / .islvrc file used by the Serena VM Web Application Server:
[APP_SERVER]
pvcs.appserver.rejectClientsWithoutHugeSetsCapability=false
The VM I-Net Web Client now officially supports Java 7 through Update 71 (1.7.0_71) as well as Java 8 (1.8.0_25).
Version Manager ignored failures to issue associations made from the VM I-Net Web Client via the SourceBridge Web Client.
This has been fixed.
It is now possible to access a branch revision on a file without having to specify the intermediate branch revisions. Prior to this fix, accessing the branch revision 1.0.1.2 would require a path like /chess/server/server.bat/1.0/1.0.1/1.0.1.2. As of this release, you can also use the more obvious path /chess/server/server.bat/1.0.1.2.
When using a project with a promotion model, Get operations that specify a version label or revision number in the Revision field would incorrectly trigger the warning "For Get operation group name and revision/version are mutually exclusive.", even though no promotion group was selected. Additionally, using Get with Force revision lookup based on Promotion Group without specifying a promotion group would fail with the error "The value <> for the parameter <ArchivePath> is invalid." instead of indicating that the group is missing.
These issues have been fixed.
If the "Desktop Client" feature was unselected during the installation of a full VM release on Windows, it will subsequently be impossible to a VM patch on that system.
This has been fixed - patches can now be applied to any installation.
A memory optimization improvement for storing archive paths (DEF238716, DEF251070) caused performance degradation in all clients.
This has been fixed - VM speed is similar to that of 8.4.6
The Serena VM Web Application Server shows a message indicating that the APR based Apache Tomcat Native library was not found, which may raise a concern.
This has been fixed - the info message is now suppressed.
This has been fixed.
The VM Server Admin tool (VPADMIN) did not handle Unicode symbols in servlet description field correctly, which would break the VM I-Net server.
This has been fixed.
Communication with the Application Server may include very large MTOM messages, which could affect server responsiveness to all clients.
This has been fixed - the Application Server now pays attention to the network speed and keeps messages below ~11MB. This increases server stability and responsiveness.
Eclipse RIDE client had problems processing multiple large parallel requests to the server.
This has been fixed - RIDE now maintains a task queue which is visible to the user.
Eclipse RIDE would load all Project Database metadata instead of just what was needed for the affected projects, causing potentially large delays for the initial operation.
This has been fixed - the improved loading process reduces memory usage and execution times.
The DaemonServer process may fail to start correctly if there are problems reaching one or more File Servers defined in servers.ini.
This would cause a number of VM I-Net operations to hang indefinitely, as also lock up attempts to fetch non-cache revisions from the local File Server.
This has been fixed - the DaemonServer now works regardless of File Server access issues.
Each time the PVCS Diff/Merge tool was launched it started with the default font.
This has been fixed - the last font settings are now preserved.
Version Manager installer did not clean up the installation directory, which caused axis2 errors. This has been fixed.
Version Manager Command Line Macros, Environment Variables and the EventParmFile have incorrect values for EVENTFQPWORKFILE. This has been fixed.
Version labels could contain CR/LF characters if assigned from PCLI script. This has been fixed.
BEHAVIOR CHANGE: Characters CR/LF are added to forbidden characters list if DISABLEBADLABELFILTER directive is set.
After upgrading to VM 8.4.6, some systems intermittently showed the Mutex Error "failed to lock lockable".
This has been fixed - the Mutex waiting implementation has been improved.
Errors occurred in desktop client when working with files or project which contained '5c' Japanese code characters. This has been fixed.
Due to security vulnerabilities in Tomcat 7.0.25, Version Manager has upgraded to use Tomcat 7.0.34.
The Promotion Group tab in the desktop client showed the selected entry with black text in a blue bar, making it hard to read.
This has been fixed - the selected entry now uses white text on a blue bar.
Archives of controlled files could not be renamed in Version Manager.
BEHAVIOR CHANGE: It is now possible to rename archives in Version Manager desktop client.
To enable or disable the feature for desktop client GUI users, use Configure Project | Archives | Modification | Rename/Move Archive when Workfiles is Renamed/Moved.
To prevent users from renaming files, remove the newly added Project privilege Rename/Move Archive with Workfile for these users.
At present neither setting will affect the previously existing ability of SCC and RIDE users to rename files, which does not change the name or location of the archives.
Warnings "log4j:WARN No appenders could be found for logger" appeared in Version Manager application server console. This has been fixed.
Error "CAC Login Error: Unable to load pkcs11 provider" was shown when trying to use CAC login on a Windows 64-bit system with ActivClient installed in the default directory.
Following symbols could not be used in the path '(', ')', '~', '"'. This has been fixed.
Version Manager on UNIX/Linux did not have the file vm/common/tomcat/logs/sso-gatekeeper.log which led to errors in the file "catalina.out". This has been fixed.
Version Manager privileges "Check Out" and "Check In" as shown in the desktop client security administration do not correspond to access database privileges, causing confusion.
BEHAVIOR CHANGE: Desktop client now has the privileges Get, Get Tip, Get Non-Tip, Put, Put Tip and Put Branch.
If ActivClient 6.2 was installed, the Version Manager installer did not put the location of its PKCS#12 DLL in vm\common\pvcsprop\pvcs\vm\sso\card.config.
This has been fixed - The location of the DLL is now also recorded when using ActivClient 6.2 installations.
Version Manager File Server logging was directed to tomcat.log instead of pvcsfs.log. This has been fixed.
Syntax of PCLI scripts when values started with the '@' character was incorrect.
This has been fixed - PCLI scripts values are now parsed correctly.
If customers perform a promote from the Version Manager desktop client there was no way to get the revision number that was promoted in either of the promotion event triggers.
This has been fixed. The value for EVENTREVISION is now computed if there is a PrePromote or PostPromote Trigger.
Manually created users always received the Unlimited privilege by default, without an option to change it, unlike the auto-create user feature that let you specify a default privilege.
BEHAVIOR CHANGE: Default privileges can now be defined for manually added users from the Version Manager desktop client in the Admin menu | Security | New User Privileges dialog.
In addition, the auto-create user settings can be configured to use the same privilege as the Configure Project Database dialog | Security | Login Sources | Source Detail.
PCLI now preserves leading and trailing spaces when expanding the output of a command through $[...].
For rare situations where a script might rely on these spaces being trimmed, the old behavior can be restored by creating a PCLI or environment variable named PCLI_TRIM_AUTOVAR and assigning it the value true.
When an LDAP login source is configured and during the Test operation the LDAP server responds with LDAP_ADMINLIMIT_EXCEEDED this was treated as a failure, preventing the use of the LDAP server.
This has been fixed - Version Manager treats the LDAP_ADMINLIMIT_EXCEEDED response as a success while performing a Test connection, as it indicates that the chosen settings provided at least one result.
Installation steps on UNIX/Linux for 3rd party web server configuration were confusing, as it was not clear you could run without using a 3rd party web-server by not selecting any of them.
BEHAVIOR CHANGE: New option None (use internal Tomcat Server) is now selected by default.
The filter section did not allow users to use multiple file names with a delimiter in Version Manager desktop client.
BEHAVIOR CHANGE: Now multiple file names separated with a delimiter can be used in the filter section.
If the first file being opened in the desktop client GUI had many revisions, the revision pane did not scroll to the top by default. This has been fixed.
It was not possible to change the description of Version Manager controlled items from the PVCS DTK.
DTK API method PvcsSetDescription() has been made available.
The File Server component in the Serena VM Web Application Server has a Background Processor task that cleans up the Revision Libraries every 24 hours.
This process could consume too much memory. This has been fixed.
On systems running Windows Vista, Windows 7, Windows 2008 or newer, access to the group Everyone was granted to files created by Version Manager with no way to disable this behavior.
You can now prevent Version Manager from adding the group Everyone to newly added files by creating the environment variable PVCS_DISABLE_GRANT_ACCESS and assigning it the value true.
Administrators may mistakenly specify direct paths to files in the project database, bypassing the File Server. This can prevent other users from being able to access these files, without a clear error message.
BEHAVIOR CHANGE: Version Manager will now show an alert when Archives, Configuration Files or Access Control Database files are accessed using a non-File Server path if the Project Database was opened from a File Server.
The way Version Manager stored paths to archives in memory was not optimized, which could cause an out of memory failure on very large data sets. The code has been improved to reduce the memory usage.
Visual Studio solutions that were added to a Project Database from interfaces other than the RIDE plugin could not be used by that plugin. This has been fixed.
BEHAVIOR CHANGE: Visual Studio solution bindings can now be changed using the new Change Binding feature.
When opening a Version Manager controlled project in the SCC integration, a report dialog was opened even if there were no messages to display.
This has been fixed - the report dialog is shown only if there are messages to inform the user.
In addition, SCC will check for the environment variable PVCS_SCC_NO_REPORT_ON_OPEN and disable these report dialogs altogether if that variable exists.
VM Project Database with HOSTID as the login source could not be opened in Eclipse RIDE plugin.
This has been fixed - HOSTID login source is honored.
Error 'OutOfMemory' was shown on Version Manager server when Eclipse RIDE plugin clients tried to work with very large data sets. This has been fixed.
The Version Manager web client supports Java plug-in version 1.7.0_45 in the web browser.
The issue appeared after changes in the Oracle Security mechanism for Java. This has been fixed.
Please refer to Oracle Java SE Critical Patch Update Advisory - June 2013 for details.
The issue appeared after changes in the Oracle Security mechanism for Java. This has been fixed.
Please refer to Oracle Java SE Critical Patch Update Advisory - June 2013 for details.
The issue appeared after changes in the Oracle Security mechanism for Java. This has been fixed.
Please refer to Oracle Java SE Critical Patch Update Advisory - June 2013 for details.
The issue appeared after changes in the Oracle Security mechanism for Java. This has been fixed.
Please refer to Oracle Java SE Critical Patch Update Advisory - June 2013 for details.
Version Manager I-Net applet had support for 32 bit browsers only.
This has been fixed. The correct I-Net applet will be installed depending on the browser.
An error was shown when working on file/project with characters in its names from double byte characters set in VM I-Net. This has been fixed.
I-Net servlets did not have any attribute to be hidden in comparison with File Server path maps.
BEHAVIOR CHANGE: I-Net servlets can now be hidden from the /vminet.html page if their Description fields contain the string [HideServlet].
Floating labels were not shown for files that were just checked-out in I-Net. This has been fixed.
Previously only one instance of Diff/Merge applications could be started from I-Net.
Multiple instances of Diff/Merge applications can now be started with tabbed interface support for 3rd party Diff/Merge applications.
The Diff/Merge application failed to start if the "TMP" and "TEMP" variables were not defined. This has been fixed.
When using the Copy archives to project location option, the user is allowed to proceed without specifying a project location. The operation does nto complete successfully and no error is given.
This has been fixed. The Next button will remian grayed out until the needed information is provided.
BEHAVIOR CHANGE: On the Advanced tab of the Show Difference and Show Merge dialogs, you can now specify a Record Length without invoking Column Masking. Also, this field now actually works.
A message like the following sometimes occurred, but for reasons different than it implies:
Unable to read File Server configuration information from \\my-server\servers.ini. The path may no longer be valid, or you may not have permissions to read this file.
The following file servers are correctly configured:
This has been fixed. The message no longer displays in that inappropriate case.
If the Version Manager File Server is installed alone (without the Version Manager Web Server Application) or the Web Server Application has no servlets defined, the File Server will not work.
This has been fixed. The servlet issue has been fixed, and it is no longer possible to install the File Server without the needed Web Server Application component.
If the path to the Version Manager installation includes spaces and 8.3 filename support is turned off in Windows, you will not be able to configure the Version Manager Application Server as an NT service.
This has been fixed.
BEHAVIOR CHANGE: By default, a path map conflict now occurs when a user tries to access two, or more, path maps that fully or partially overlap but reside on different servers. The Version Manager client will deny access to the conflicting path maps and display a message. In the Open Project Database dialog, conflicting path maps will be shown in red. This new default behavior prevents the wrong files from accidentally being acted upon.
See the Serena PVCS Version Manager Administrator's Guide for information on resolving or working around path map overlaps.
If vtransfer -r is used to rename the directory of a project database, the old path is persisted in the Open Project Database dialog. This has been fixed. The new path will now appear after restarting the client or clicking the Test button.
BEHAVIOR CHANGE: When using the Open Project Database dialog (and other dialogs that implement the same fields), you can now browse for project databases located on File Servers via a new Path Map View or the previously implemeted Project Database View. To do so, select File Servers in the Look in field then select the desired view.
BEHAVIOR CHANGE: There is now an option to expand all branches in the Revision pane. By default, all branches are shown collapsed. To change the default to expand all branches, do the following:
Running PCLI AddUser without specifying a new user caused damage to the access control database. This has been fixed.
If the actual destination project name happens to include a character that PCLI uses as a wildcard, then the command will not work.
This has been fixed.
If the user running the command is not in the Access List, a null pointer exception or stack overflow is thrown. This has been fixed.
If you see an error like the following:
/lib/libcrypt.so.1: /usr/serena/vm/common/lib/linux/libfreebl3.so: version `NSSRAWHASH_3.12.3' not found (required by /lib/libcrypt.so.1)
linux-gate.so.1 => (0x00989000)
libc.so.6 => /lib/libc.so.6 (0x004f3000)
libfreebl3.so => /usr/serena/vm/common/lib/linux/libfreebl3.so (0x00b51000)
/lib/ld-linux.so.2 (0x00adf000)
libplc4.so => /usr/serena/vm/common/lib/linux/libplc4.so (0x00441000)
libplds4.so => /usr/serena/vm/common/lib/linux/libplds4.so (0x00110000)
libnspr4.so => /usr/serena/vm/common/lib/linux/libnspr4.so (0x0020b000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00b1f000)
libdl.so.2 => /lib/libdl.so.2 (0x009c3000)
It is becuase the library installed with Version Manager is incompatible with a newer library in use by something such as Eclipse.
This has been fixed.
If a given workfile already exists in a project database and you attempt to add it to the same location again, the results dialog will appear a second time after being dismissed.
This has been fixed.
BEHAVIOR CHANGE: New options and behavior have been added to the Workspace Settings section of the Copy Project Database dialog (Edit | Copy). The default behavior is the same as in previous releases. However, the non-default behavior has been revised to address an oversight in the original implementation, and a new option has been added (Include the Workfile Location setting).
The Copy Workspaces checkbox is now named Copy workspaces and workspace settings. In the past, deselecting this option would still result in some project-level workspace settings being copied. Now no workspace settings are copied if this checkbox is deselected.
The new Include the Workfile Location setting checkbox allows you to include the Workfile Location when copying the workspace settings, else it is not copied and you must specify a new location in the Workfile Location field.
See the help topic for the dialog for more information.
If a file does not have a file extension, the association is not created with an SBM issue. This has been fixed.
BEHAVIOR CHANGE: Exit Code 4 will no longer be returned in the case of a directory that contains no files, unless a file was specified for that directory. Previously, a directory that contained sub directories, but no files itself, would generate Exit Code 4.
When trying to access the VM I-Net web client through IIS running on a 64-bit server, you get the following error:
Calling LoadLibraryEx on ISAPI filter "C:\Program Files (x86)\Serena\vm\common\tomcat\bin\win32\isapi_redirect.dll" failed.
This has been fixed.
This has been fixed.
This is fixed in 8.4.6.
If the target location for the applet installation is read only, the applet install process will fall into an endless loop. This has been fixed.
Due to a caching issue, sometimes an installed web client applet would not be listed on the Version Manager Web Client Configuration page. This has been fixed.
This has been fixed.
If you apply a filter while the Content pane contains many pages of content and you are not currently viewing the first page of that content, the filter may appear to return a blank Content pane. This happens when the filtered content would be short enough not to reach the page you were on when you applied the filter.
This has been fixed. When applying a filter, the Content pane will now open to the first page of the results.
If the user invokes and submits the Diff or Merge dialog without completing the necessary fields, Version Manager hangs.
This has been fixed.
The Version Manager web client does not work with Java 7 Update 4 (1.7.0_04) or newer. An error like the following would result:
This browser has no Java Runtime Environment (JRE).
This has been fixed.
When adding files to source control, the user selected option of [NONE] was ignored and the default promotion group was applied. The has been fixed.
The user can see the projects and files just fine, but any attempt to update a file (check out, check in, label, lock, etc.) will fail with an Internal error 201 or a "Cannot create semaphore" error message. If the server is restarted or enough other users access the system, the problem resolves itself.
This has been fixed.
If the Version Manager 8.4.5 patch was installed to a Version Manager Web Application Server that did not include the SSO server components, an error like the following shows up in the catalina.YYYY-MM-DD.log file:
Oct 2, 2012 8:05:26 AM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /usr/merant/vm/common/tomcat/webapps/ALFSSOLogin Oct 2, 2012 8:05:26 AM org.apache.catalina.startup.ContextConfig webConfig SEVERE: Unable to determine URL for WEB-INF/classes
This issue has been fixed, meaning that future patches will not introduce this problem. However, that does not retroactively fix the problem for those who installed 8.4.5 to a non-SSO server.
To fix the issue on a non-SSO server:
The associated text entry field should be grayed out if the All Users or All revisions by selected users(s) option is selected. This has been fixed.
If the Web Server Application is being used in conjunction with a File Server, it may fail to shutdown. This has been fixed.
If one tries to add a workfile while not checking in the workfile, the archive is not created and the following error is shown: "Error, Unexpected error: java.lang.NullPointerException." This has been fixed.
CLI and DTK throw a General Protection Fault (referenced memory at "0x00000000"), and the Desktop client and PCLI throw an error similar to: UnknownException at line 686 in WIN32/Tip/src/ProjectFileAPI.cpp. The problem was poor handling of the case of the File Server client cache being an invalid location. This has been fixed.
The default date and time format for the locale was being used instead of the specific format, if other than the default, specified in the Regional Settings of the O/S.
Fixed. New error messages for when CLI command fails due to File Server being inaccessible or the Revision Library having problems.
When dragging and dropping a project to a new location in the project database tree, the project does not appear in the new location until one collapses and re-expands the tree. This has been fixed.
If a Reference directory is in effect and the directory is inaccessible to the current user (perhaps another user has file(s) open there), an error is returned at Checkin implying that there is a problem with a temporary file. This has been fixed to provide a more accurate and useful error message.
This has been fixed.
When you create a new admin user from the Version Manager File Server Administration Utility and use a semicolon (;) in the ID or password, the next login to the administration utility fails and nobody will be able to log in until the user has been removed from the server-config.wsdd file. This has been fixed. Semicolons are now allowed in the password, and the Administration Utility prevents the creation of users with a semicolon in the ID.
When using the Desktop Client from the same system that hosts the Version Manager File Server, you will be unable to access the files and projects if all of the following are true:
This has been fixed.
This issue can occur only if the archive size is not changed by the operations. For example, if an event trigger applies a label to a file on check in, a subsequent operation from the client that called the event trigger may cause the label operation to get undone if the label operation from the trigger did not cause the size of the archive to change, as could happen when an existing label is moved to a different revision. If this all occurred within one second, the label would revert to whatever revision it was associated with prior to the call of the event trigger. This has been fixed.
If the workfile directory overlaps with a File Server Path Map and the workfile already exists, a Get operation may fail. This has been fixed.
This has been fixed.
If one manually edits the journal file and introduces extra lines or other unexpected formatting, the journal report will not function correctly. This has been fixed by making the journal report more tolerant of non-standard formatting.
In some cases a variable length keyword can unexpectedly transform into a fixed length keyword. This has been fixed.
If multiple LDAP servers were implemented, a single entry of a bad password could be sent to all of them and result in the user being locked out due to too many failed login attempts. This has been fixed so that the login process stops at the first server that recognizes the user name.
The format of the LDAPINFOFILE was enhanced for the 8.2 release to support multiple independent LDAP servers. When accessed, any existing LDAPINFOFILE that included multiple servers would be rewritten into the new format. Unfortunately, this change introduced a bug that resulted in a crash when the file was rewritten. This has been fixed.
As of 8.2, CLI commands no longer work with paths that contain /./ or \.\ or end in /. or \. in case of directories. This has been fixed.
When used to display all projects in a project database, it stops with "No Access" message when it reaches the first project with its own access control database if the user running the command is not on that access control database. This has been fixed. A message will appear if the user does not have access to a given project.
Features to prevent scripts from making repeated requests for licensing were not working correctly in some configurations. This has been fixed.
When specifying the Semaphore directory, one must browse to it and select it rather than type it into the field. This has been fixed; you can now browse or type the value.
The menu item Admin | SourceBridge Settings is enabled if a project is selected. It should only be enabled when a project database is selected. This has been fixed.
If you pass the vsplit command a path that cannot be resolved to a Path Map, the error you get depends on the type of file that is being processed. This has been fixed.
If the archive path includes a double-byte Shift-JIS character before a backslash (\), and the second byte of this character is 5c, then the operation reports that the file could not be found. This has been fixed.
Starting with VM 8.1.4, the File Server and the vtransfer -r command were updated to allow an in-place rename as opposed to using the old multi-step mechanism. Unfortunately, if the target directory did not exist, this resulted in a scary looking message in the tomcat.log and the command fell back to working in the old way. This has been fixed.
The error appears in the Eclipse RIDE console when attempting to check in files if the NODISABLEBADLABELFILTER directive is set in the CFG file of the target project database and illegal characters are entered for the label. This has been fixed. The expected error about illegal characters in the label will now appear.
This has been fixed.
Attempting to view a .bat file as HTML from Internet Explorer resulted in a prompt from the browser to Save or Run the .bat file. This has been fixed.
The revision number was not being shown in the Output tab for label assign events. This has been fixed.
When entering a checking description, the Enter key activates the default button and closes the dialog rather than creating a new line in the description text. Pressing Ctrl+Enter does create a new line, but that is different than our other description dialogs and may not be expected. This has been fixed so that pressing the Enter key adds a new line in the description text rather than activating the default button.
This has been fixed.
When using Java browser plugin 1.6.0_29, attempting to associate issues with files results in the user being sent to the Login page. This has been fixed.
BEHAVIOR CHANGE: You no longer have to install client-side, browser-specific components for the web client. The applet now downloads automatically if you don't already have the applet version that matches the server. Any existing applets are retained, in case you will be accessing servers running different releases of Version Manager. You can delete the applet files, and specify a location for future applet downloads, from the Version Manager Web Client Configuration page. See the Help or Web Client User's Guide for details.
All URLs ending in ".dll" were being redirected to Version Manager's Tomcat. This has been fixed.
Even though the user does in fact have the revision checked out, an error appears when they attempt to checkin saying that the revisions are not locked by that user. This occurs if another user accesses the project while the first user is in the midst of the checkin operation. This behavior was a side effect of a change made in 8.4.3. It has been fixed.
This has been fixed.
If the URL does not include a Port number, we return an incorrect URL in the popup blocker message: Please add the server "ServerName/vminet_images/frame.jsp" to your popup blocker exception list. This has been fixed.
Some Version Manager operations would not work correctly if the web client was invoked using a URL that specified a project. For example, http://Server:8080/SampleDB/chess/server. This has been fixed.
A number of Tomcat vulnerabilities were identified that affect the Tomcat application server included with prior 8.4.x releases. These have been resolved by upgrading the embedded Tomcat server to version 7.0.25.
Due to the discovery of a security vulnerability in Axis2 1.4.1, Version Manaqer has upgraded to Axis2 1.5.5.
Note that, for now, Axis2 1.4.1 is still used by the SSO feature. However, this implementation has no exposed services or endpoints and is thus not vulnerable to the XSD Parameter Directory Traversal Vulnerability.
Due to the discovery of security vulnerabilities in Tomcat 6.0.21, Version Manaqer has upgraded to Tomcat 7.0.16.
Some commands (such as vsql and vsplit) waste time searching the network if the Path Map Client Name looks like it is a UNC path.
This has been fixed.
By default, Version Manager checks for illegal characters during label creation and rejects the label if it contains illegal characters. If you must create labels that include illegal characters, you can disable the filter that checks for illegal characters in labels. See the DisableBadLabelFilter directive in the Serena PVCS Version Manager Command-Line Guide.
NOTE The use of illegal characters in version labels can have unexpected and undesirable outcomes. See Using Dashes (-) in Version Labels (Caution!) in the Usage Cautions readme.
NOTE Use of this directive effectively turns off the fix that was added for: All Clients Accepted Disallowed Characters (* : - +) in Version Labels [DEF78103].
If LDAP or SSO authentication was enabled for a given file server path map, you had to disable authentication before creating a new project database on that path map. Else an error dialog would appear, and the project database would not be functional.
This has been fixed. It is no longer neccessary to disable authentication before creating a project database.
BEHAVIOR CHANGE: In the event of an empty Access List Group, Version Manager would search the network to try to establish group membership (if the login source is HOST, LANMAN, or NETWARE). This feature caused significant login delays and could result in unexpected behavior. This behavior is now disabled by default. However, you can restore the old behavior by adding the following line to the [PVCSGUI_6.5] in your ISLV.INI file: pvcs.queryOsForEmptyGroups=true
If an Add Workfile operations fails and the initiating user lacks the privileges needed to clean up after the attempted add operation, artifacts of the failed operation are left behind.
This has been fixed.
When performing a GET operation on a split archive to a target directory that cannot be written to, the error message is wrong and misleading. This has been fixed.
The purpose of the PCLI ListRevision command is to output a list. However, that output is suppressed if the PCLI script is run in quiet mode (by using the -q switch with the run command or by defining the PCLI_QUIET variable).
This has been fixed.
When doing a History or Difference based upon the Default Version, the operation will fail if the Default Version looks like a revision number ("1.5" for example).
This has been fixed.
When your SSO authentication token expired, the Desktop client gave the following inaccurate error message: "Access denied because of invalid login account".
This has been fixed. It will now display the correct error message: Error signing on to File Server: "SSO authentication token is expired".
If a sub project has somehow developed an invalid reference to its parent project, it cannot be deleted.
This has been fixed. The invalid reference will be detected and corrected, thus allowing deletion of the sub project.
5c is a backslash (\), and a backslash can act as an escape character in Version Manager paths, so if a double-byte character with 5c as its second byte appears in front of a backslash character, the trailing backslash character is removed from the path.
This has been fixed.
The "Multiple problems" dialog appears when Eclipse is launched. Selecting the Serena menu results in the message: "The Chosen operation is not currently available".
This has been fixed.
If SSO authentication is enabled on the path map and it is being accessed by a Rich IDE client at the same time as the web client, then errors may occur during login and file operations.
This has been fixed.
If a date format has been specified in Version Manager for the servlet, the date fields on the Advanced tab of the Show History dialog will not work correctly.
This has been fixed.
If SSO authentication is enabled on the path map and it is being accessed by a Rich IDE client at the same time as the web client, then errors may occur during login and file operations.
This has been fixed.
If for some reason a given project database is temporarily inaccessible when the first user tries to access it after a server restart, the project database will remain inaccessible to all users until the Version Manager Application Server is restarted again.
This has been fixed.
This has been fixed.
Corrupt Filter entries in the ISLV configuration file were causing the Desktop Client to lockup as it launched. This has been fixed. Now, when the client encounters a corrupt filter entry at launch, it will delete the entry and startup normally.
This has been fixed. A backslash (\) will now automatically be prepended when selecting a label or promotion group that looks like a revision number.
This message is the result of several attempts to update an ACDB file while there is a pre-existing semaphore for this ACDB blocking those updates. After 5 update attempts, with every attempt reporting "Could not access file because it is in use by another user", Version Manager will no longer be able to modify any ACDB or login to any PDB until the affected Version Manager instance is restarted. The attempts to update the ACDB could either be explicitly performed by an Administrator from the Desktop client (using Admin -> Security), or happen when auto-create users is enabled on a project database and a new user is trying to login. Restarting the Desktop client fixes this for such users. For Web client users, one must restart the Version Manager Application Server.
This has been fixed. You will no longer receive the "...maximum number of open files..." warning in the event of a stale semaphore, no matter how many login attempts are made.
NOTE This fix does not clear the underlying stale semaphores. Users of the Version Manager File Server should use the File Server Admin web page for this purpose. Non-File Server users can clear out the stale semaphore files from disk.
The following fix was contained in 8.4.2. It fixed a defect introduced in 8.4.1. It has been removed from 8.4.3 pending further work. If you have installed Patch 8.4.1 and you are using Server-Side Processing, you must restart the Version Manager Application Server each time you create a new Path Map. Else the new path map won't be seen and the connection will revert to Client-Side Processing. This fix has been REMOVED.
This has been fixed. Now if you deselect the "Use description for all" option you will be prompted to enter a description for each item.
This has been fixed.
This has been fixed.
Version Manager now supports integration with Visual Studio 2010 SP1.
If there is a series of values to pass and one of the values is empty, the next value will be used instead of a null value. This has been fixed.
This has been fixed.
This has been fixed.
When performing a multi-file Get operation from a location with high latency, Internet Explorer 6 tends to get the files significantly faster than Internet Explorer 7 or Internet Explorer 8. All Firefox browsers are also slower. This has been fixed.
This has been fixed.
This has been fixed.
If your JRE is too old, Version Manager displays the following message:
"Detected out of date Java Runtime Environment. VM 8.2 client needs Sun JRE 1.5 or later. Please click on this link to download and install the Sun Java Plug-in."
The reference to VM 8.2 was unneeded and confusing. It has been removed form the message.
When using Sun's JRE, you cannot switch from one Version Manager server to another without first restarting your web browser. There is now a helpful error message to remind users of this requirement.
This Version Manager 8.4.2 specific defect has been fixed.
This has been fixed.
This has been fixed.
One should be able to modify the description of a versioned file from the Properties dialog (right-click on a versioned file and select Properties from the pop-up menu). However, any changes made to the description in the dialog are not written to the archive, thus the change does not take effect. This has been fixed.
The use case can be as simple as having opened the PDB in the past with a user ID that either is "in use" by the license manager on another PC, or has been dropped from the license manager users list. When you attempt to open the PDB from the Most Recently Used (MRU) list, VM will attempt to use the last known user ID from the MRU list. In case that ID does not have a password, VM will not bring up the login dialog at all, attempt to login, fail (due to not being able to get a license) and simply show the PDB with a red X on it. Closing the PDB and attempting to re-open it from the same session won't help, as the user ID for the PDB is kept in memory and reused during the reopen attempt.
This has been fixed. In the above use scenario, the user can now close the PDB, and reopen it, at which time they will be prompted to log in.
As of 8.4, if a PCLI script applies a label via a variable that is inside of double quotes (since the name of the label in the variable sometimes contains a space), the command will fail with an error about invalid characters in the label. This has been fixed.
If you have installed Patch 8.4.1 and you are using Server-Side Processing, you must restart the Version Manager Application Server each time you create a new Path Map. Else the new path map won't be seen and the connection will revert to Client-Side Processing. This has been fixed.
This has been fixed.
NOTE There is a dependency upon the library libexpat.0.so. Your SuSE installation probably has a newer version of this file, for example libexpat.1.so. Unfortunately there are several third-party libraries that depend upon the older version of the file. To avoid sporadic crashes, you must download and install a compact pack specific to your operating system in order to acquire the needed version of libexpat0. See http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/libexpat.so.0
The eclipse package explorer is showing all the folders which are in the project which includes _serena. _serena is the folder which is created by VM workspace manager to manage the workspace. This has been fixed. The _serena folder is no longer displayed.
When trying to import a project from a local project database into a workspace with Server-Side Processing enabled, the following error is displayed in the console:
[INFO] Server-side processing cannot be used with pre 8.4.1 server, switching to Client-side processing.
This has been fixed.
In RAD when we right click a TeamTrack item and select add to active list we receive the following error: "Error Serializing Activated Issues". This has been fixed.
If the Application Server is restarted while using Server-Side processing mode with the Rich IDEs, you must also restart the IDEs. This has been fixed. You can now restart the server without restarting the IDE's.
Users cannot log in to the IDEs and the following error appears in the Application Server console:
"java.lang.OutOfMemoryError: PermGen space" in Server console
This has been fixed.
With Server-Side Processing enabled, SSO login to a project database may fail if it is done simultaneously from both Eclipse and Visual Studio IDEs. This has been fixed.
If the project was imported with a CAC login with Server-Side Processing enabled, you could not commit files from compare workspace operation. This has been fixed.
If the connection to the Application Server (Server-Side Processing mode) is down and we try to perform a compare workspace operation in the IDE, it looks as if all the files in the remote location are deleted, but that is not true.
This has been fixed. Also a message is displayed any time the IDE is unable to access the Application Server during an operation.
When opening a Visual Studio project that contains an .sln file, a message like the following is displayed in the console of the Version Manager Application Server:
[ERROR] BEEP BEEP BEEP. Invalid use of API. A file asset was added to the selection set as an asset folder./VS2008-RIDE/WindowsFormsApplication3/WindowsFormsA pplication3.sln
This issue has been fixed for open operations. It may still occur for migration operations
The incorrect timestamp is used for some of these operations. This has been fixed.
The selection dialog never finishes loading, preventing the user from specifying a version label or revision. This has been fixed for all use cases. The previous fix in 8.4 only addressed the case of files located at the root of the project database.
This has been fixed.
A path was incorrectly specified on pages 63 and 64 of the Installation guide installed with Version Manager 8.4.0.0. The part number of the old version is: MA-VMINST-008. See the copyright page of the guide to verify the version you are using. This has been fixed in MA-VMINST-008A (which was available online for 8.4.0.0) and MA-VMINST-009 (which is included in 8.4.1.0).
After the File Server is restarted, it is supposed to resume the background scan of the Revision Library where it left off. This feature was disrupted by a code change in 8.1.1 JA, causing the scan to restart at the beginning rather than where it left off. This has been fixed.
To enhance performance, server-side processing has been added to the Eclipse RIDE and Visual Studio RIDE integrations.
BEHAVIOR CHANGE: Server-side processing is enabled by default, so by default all event triggers will be executed on the server. If this is incompatible with your processes, you can revert to the previous behavior of client-side processing. See the Serena PVCS IDE Client Implementation Guide for more information (the section on setting default options for your particular IDE).
BEHAVIOR CHANGE: The Tomcat implementation installed with Version Manager can stand on its own. Optionally, you may use a supported third-party web server to access the servlets hosted on the Version Manager Web Server. This may be convenient if you have already configured a third-party web server and wish to use the existing front-end and HTTPS certificates with Version Manager.
NOTE
Version Manager does not require a third-party web server. By default, the Tomcat-based Version Manager Web Server will stand on its own.
A third-party web server does NOT take the place of Version Manager’s Tomcat implementation, but rather runs in addition to it.
If there is an error when attempting to connect to an LDAP authentication server, user sessions may become locked and remain that way. This has been fixed. If a connection cannot be attained in 30 seconds, the attempt will be aborted, a message will be displayed, and the user will be free to try again.
SSO/CAC has been added as a login source. It is available to the following Version Manager clients: Desktop Client, Web Client, Eclipse RIDE, Visual Studio RIDE, and PCLI. It requires the use of a Serena Single Sign On Server. See the Serena PVCS Version Manager Installation Guide for installation and configuration information.
The use of an Asterisk (*), Colon (:), Dash (-), or Plus (+) in version labels can cause unexpected behavior. For that reason, those characters are supposed to be disallowed. This has been fixed.
BEHAVIOR CHANGE: A warning message is now displayed when an asterisk, colon, or dash is entered in a version label, and the label is not created. (See the 8.4.4.0 notes if you want to default to the original behavior.)
The issue occurs if the directory pointed to by the WORKDIR directive (which by default is the current directory for CLI and DTK apps) has the setgid bit enabled on it (drwxrws...), and the group owner of that directory does not match the effective group owner running the VM command. This has been fixed.
This behavior started in Version Manager 8.1.2. It occurred only if the "Retained shared archives" option was selected during the copy process. This has been fixed.
On Windows systems, changes to the case of a portion of an archive path resulted in journal entries for each version of the path. This has been fixed.
This has been fixed.
Added cache logic to improve performance.
This has been fixed.
Mover gets confused if the project name is also part of the path. This has been fixed.
This has been fixed.
The Installation package for VM 8.3 was run with the /R option to create a setup.iss file (Silent install Answer file). The SampleDB was not created on the original install, however when the install package was run with a /S option the Sample Project Database is Created. This has been fixed.
This has been fixed.
This behavior started in Version Manager 8.3 as an unintended side effect of another fix.
This has been fixed. Any existing pvcsproj.old#### files will be deleted and new ones will not be created.
This has been fixed.
This has been fixed.
This has been fixed.
As an ATL project is added to source control an error appears in the Output window:
Error: Unknown asset path "/CPlus_ATL_New_I".
Created project: //CPlus_ATL_New_I
Despite the error, the project was successfully added to source control. This has been fixed.
In certain circumstances, all other users were blocked from logging in to a given subproject as long as one user already had a login dialog open for that subproject. This has been fixed.
This has been fixed.
Operation fails with the error: "Action was not performed because there were no items to process". This has been fixed.
The selection dialog never finishes loading, preventing the user from specifying a version label or revision. This has been fixed for files located at the root of the project database.
This has been fixed.
This has been implemented.
If you have modified the settings for File Type [undefined], the directives written to the cfg file are based on the assumption that [undefined] is not modified by the user. If the user modifies these settings it could lead to workfile corruption.
This has been fixed.
When used in a version label, the characters would be displayed as "???" or cause an error to be thrown. The characters are: č, ě, ř (c, e, and r with a caron). In Windows CP1250 Latin, these are the High ASCII characters 200, 227, and 236.
BEHAVIOR CHANGE: This has been fixed. Windows CP1252 Latin (Western Eurpean Languages) does not contain these characters. To use these characters, you must change the region and language settings of your system to one that uses Code Page 1250, such as Romanian.
If errors are encountered during a get command with the -q option, then the -q option may be disabled for subsequent "get -q" operations.
This has been fixed.
This has been fixed
This has been fixed.
This has been fixed.
With PowerBuilder, Crystal Reports, and Version Manager installed, the Version Manager Desktop client does not work correctly and the SCC component will not initialize. These same DLLs could also interfere with CLI and PCLI.
This has been fixed. Version Manager now loads the specific version of the DLLs it installs rather than depending upon the DLL search-order logic within Windows.
NOTE: If you encounter a conflict with another third-party DLL, try adding the name of the DLL to the ISLV.INI file. If there is not already a [THIRDPARTY] section in the ISLV.INI file, create one and list the conflicting DLL's under it as follows:
[THIRDPARTY]
PVCS.VM.THIRDPARTYDLLS=libeay32.dll:ssleay32.dll
Any DLL names should:
Be separated by the delimiter colon ( : )
Contain only the filename, not the full file path.
It only occurs if the user has ACDBs at multiple non-root levels and they want to create new ACDBs during the copy operation. This has been fixed.
This has been fixed.
This has been fixed.
Having an embedded ACD can also cause this problem. This has been fixed.
If the File Server contains a Path Map where the Project Database location is set to the root of a drive, attempts to launch a client on this File Server (GUI, PCLI, CLI) will cause those clients to crash.
This has been fixed.
This has been fixed.
The PDB cache lifespan setting of "0 seconds" on the File Server Options page was intended to allow you to turn off the PDB cache. With the cache disabled like this, the list was supposed to be computed at the time of each request. Instead, the PDB cache rebuild thread runs continuously, causing a 100% CPU load.
This has been fixed.
This has been fixed.
In the case of split archives, this can result in empty archives remaining on the server. This has been fixed.
When the login source is set to VCSID, VLOGIN (in that order), and you DON'T have a VCSID variable defined, VM is supposed to ignore the VCSID login source and just use VLOGIN.
This works well for all operations, except Show History / PCLI vlog involving a version label. For those operations, every other file(!) in the report fails with the error:
"Error: <EntityPath>: You have encountered an internal processing error: 50 (PVCS_E_NO_USER_ID: Unable to obtain the user ID.)"
This has been fixed.
Entering a hostname will work, but if you try to specify a port (ie. 27000@abc-flexlm), then it will fail to connect.
This has been fixed.
This has been fixed.
This has been done.
Merge cannot be performed using the merge tool tkdiff merge. It displays the error: "*.tmp is not a part of revision control system."
This has been fixed.
When running in setuid mode, non-pvcs users (= users other than the owner of the executables) can corrupt archives when they are not a member of the group that owns the vcs executable, given a normal umask setting (002 or 022).
This has been fixed.
This has been fixed.
When assigning a promotion group to revisions based on a label comprised of numbers, VM returns the message that it "Could not find a revision named 123456 in the archive <archive path>" Where "123456" is the selected version label.
This has been fixed.
When issuing a PCLI list command against an archive that has an access list but the user running it is not part of that list, they will get a java.lang.nullpointerexception.
This had been fixed. A "No Access" error message will now be displayed as expected.
If there is a problem in the project database where a PvcsId on one of the entities has a higher number than the one stored in pvcsid.ser, then PCLI ScanPDB does not detect this problem. When you add additional elements to this project database, you will introduce corruption due to duplicate element IDs.
This has been fixed.
This has been fixed.
This has been fixed. A message now appears warning that if no privilege set is assigned the effective privilege set will be Unlimited.
When a promotion model is in effect, a checkout operation uses different revision lookup logic than a get operation.
BEHAVIOR CHANGE: Force revision lookup options have been added so that a checkout operation can be made to use the same revision lookup logic as a get operation. These options can be selected from the Get and Checkout dialogs at run time. The default configuration of those dialogs can be specified in the user options and/or configured by the administrator in the Promotion section of the Project Configuration dialog. An -FG and -FR option have been added to the Get command in CLI and PCLI. The relevant sections of the Version Manager documentation have been updated; refer to them for implementation details.
Single sign-on functionality is now restored for project databases and projects accessed from the Desktop Client.
BEHAVIOR CHANGE: The administrator can configure Version Manger projects and project databases to recognize a user who has already logged in to Version Manager. When single sign-on is enabled, a user can login once and access all single sign-on enabled projects without logging in again.
NOTE Your Version Manager user ID and password combination must match across the project databases and projects on which you wish to use single sign-on.
Single sign-on is supported only in the Desktop Client.
If an existing PDB visible in the Desktop Client has SSO enabled, and if we create a new PDB using the Desktop Client, by default it shows the "Enable Single sign-on" SSO option is selected in the project configure dialog. If SSO is not enabled for the existing PDB, it works as expected: creation of new PDB shows the default option as "Enable Single sign-on" DISABLED.
This has been fixed.
If a subproject contains an ACDB with VLOGIN and the user name and password are the same (ie UserID = "Bob" and PW = "Bob") but the UserID is different than that in the root project, then when you navigate into a subproject, a stack overflow exception will be thrown. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When attempting to un-install Version Manager, the user will be prompted with a message "PCLIOutProc is not responding".
This has been fixed.
Users should be able to manage the memory heap Xmx and Xms settings for their workstation. The PCLI, GUI and web clients all allow this capability.
This feature has been added.
Java based clients use the following memory heap parameters:
-Xms Minimum heap size JVM parameter for loading JVM.
-Xmx Maximum heap size JVM parameter for loading JVM. If heap value grows above this value application will throw "Out of memory" error.
BEHAVIOR CHANGE: The feature is implemented as follows for the various IDE clients:
SCC Clients
In ISLV.ini file add a section and key value pair in the following format:
[CPCLI]
JAVAARGS=-Xms128m -Xmx512m
Visual Studio RIDE
In ISLV.ini file add a section and key value pair in the following format:
[SVE]
sve.dotnet.jvmloader.jvm.initialHeapSize=<value>
sve.dotnet.jvmloader.jvm.maxHeapSize=<value>
Eclipse RIDE and SCC
In the eclipse.ini file located in the eclipse folder, add a section in the following format:
-vmargs
-Xms40m
-Xmx256m
Here 40m and 256m corresponds to 40MB (min Heapsize) and 256MB (max Heapsize).
In Eclipse, the default options set for Label under Windows | Preferences | Team | Serena | Checkin, do not get picked up when performing Compare Workspace, Synchronize, or Commit To Repository actions. It does when performing Check In.
BEHAVIOR CHANGE: A Commit dialog now appears in the above mentioned scenarios. It is similar in function to the Checkin dialog and provides access to the same options.
For a few scenarios error codes are displayed instead of Error messages in the Serena Output console; for example, if the user cancels an operation.
This has been fixed.
This has been fixed.
This has been fixed.
The SCC integrations (as of 8.1.4.1) were prompting users to login multiple times. This has been fixed.
When trying to perform merge using the SCC integration, the Merge Tool is adding the project name twice to the path. This results in setting path to the workfile as invalid and resulting in an error like: "Error: Unable to access the following file for reading: E:\vs\WebApplication2\WebApplication2\Default.aspx".
This has been fixed.
User checks out revision, whether tip or non-tip, from the History view but cannot check in file from the same view. Checks in file from the Solution Explorer but the changes made to the modified file are lost. Also when looking at the contents of a file through the History View and when looking at the file opened through the Solution Explorer, the contents are not identical.
This has been fixed.
This has been fixed.
This has been fixed.
When the user eventually adds a workfile to a previously empty folder, it could not be added to source control without first deleting the empty folder from the Visual Studio project. This has been fixed.
BEHAVIOR CHANGE: A previously empty folder will now be added to source control when the user adds files to it. Until then, it will not be added to source control.
This has been fixed.
The Next Difference button stops at the next difference in the file pane that is currently selected. By default the pane on the left is selected which contains the file that is currently on the tip. If you click the Next Difference button the focus does not go to the next difference because all the Add changes are referenced against your local workfile. You will need to switch focus between the two panes to be able to use the next difference button to see all the differences.
This has been fixed.
This has been fixed. Rather than crashing, a message now appears stating that the name contains disallowed characters.
This has been fixed.
For a newly added file (no content, file size of 0KB), merge operation on empty file throws an unhandled exception. This has been fixed.
Viewing locally modified file from compare workspace shows the repository file instead of the local file. This has been fixed.
This has been fixed.
This has been fixed.
If the Version Manager Admin is attempting to edit the configuration at the same time that a user logs in via the Web Client, the changes configuration changes may not be retained.
This had been fixed.
Attempting to do so resulted in the error: "Empty Selection Set - Browse to select directory or files." This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
The Version Manager Web client applet may not install on FireFox and Mozilla browsers if the server is running IIS 6 on Windows 2003. You can avoid this issue by defining a MIME type for .xpi files.
This has been fixed. The MIME type work around is no longer needed.
Get with default revision fails with error: "Can not locate specified revision label" even though no label was specified. The problem shows up whenever the PDB explicitly sets "DefaultVersion" to an empty value, although "BranchVersion" and "BaseVersion" can also wreak havoc.
This has been fixed.
This has been fixed.
If an inet client is doing a get on a PDB with a VLOGIN login source and the client has no password in the access database, and another process assigns a password to that userid, then the daemon server processing the inet client's requests can crash. New daemon servers will get created, but they also will crash.
This has been fixed.
This has been fixed.
The "View" and "Edit" functions no longer work if you click the "View / Edit file" icon next to a file. The "View as html" function still works, but "View" and "Edit" leave the dialog window open when you click OK.
This has been fixed.
The conversion code may not be smart enough to take the current locale into account when reading checkin dates from VSS.
This has been fixed.
After performing a Get operation, the Details information indicates that the revision was "Checked out". This led some users to believe they had accidentally executed a Checkout operation.
BEHAVIOR CHANGE: This has been fixed. To avoid confusion, Get and Checkout operations now both report which revision number was "Fetched".
When you use the SCC Integration from PowerBuilder, your first attempt to assign a version label during check-in fails to assign the label. The new revision is checked in, but the label is not applied and has to be manually applied afterward. Subsequent check-in operations succeed in applying a label.
This has been fixed.
If you click the browse button next to Add Workfiles From in the Add Workfiles dialog box and then click Cancel in the file browser that opens (choosing to keep the default location), the Add Workfiles operation fails with the following message after you click OK:
Empty Selection Set – Browse to select directory or files
This has been fixed.
*.255 [DEF162200]In certain archives with trunk tip revisions greater than *.255, attempts to assign a floating label to a branch fail with the following misleading error message:
Could not access the file archivePath, because you do not have the appropriate privileges.
This has been fixed.
A number of security vulnerabilities were identified in the Apache Tomcat 5.0.28 application engine that is running the Version Manager Web Application Server used by File Server, VM I-Net, and WebDAV.
These issues have been addressed by replacing the application engine with Apache Tomcat release 6.0.20.
Attempts to use this API return PVCS_E_INVALID_PARAMETER when the application is using the DTK from Version Manager release 8.2.0.1 or 8.2.1.0.
This has been fixed.
The PvcsVersionToRevision() call must be passed the size of the buffer used to store the revision number and version label information. Because this size is declared as an unsigned short data type, the call cannot succeed if the buffer must be larger than 65535 bytes, which causes it to return PVCS_E_BUFFER_OVERFLOW.
This has been fixed. The buflen parameter is now declared as an unsigned integer, which supports buffers larger than 65535 bytes.
Although Version Manager 8.2.1 supports Windows 2008, it does not support the IIS 7 Web server. Attempts to use VPADMIN to configure Web Client access through IIS fails.
This has been fixed. As of Version Manager release 8.2.1.1, the use of IIS 7 is officially supported and VPADMIN can be used to enable it.
A Version Manager security violation has been found that allows a user to perform actions on an archive based on the user's base privileges, even though the archive has an access list (of which the user is a member) that does not include the privilege for the action performed.
This issue arises only when both privileges are restricted to a promotion group. In that scenario, user restrictions on promotion groups have preference over access list restrictions on promotion groups. The issue exists in all Version Manager releases as of version 8.1.1.
This has been fixed.
The LDAP login debug output written to the file referenced by the PVCS_LDAP_DEBUG_FILE environment variable is not flushed, which complicates the debugging of running server processes.
This has been fixed.
In the File Server Configuration dialog box, the tooltips incorrectly reference operations being performed on an LDAP server if the user's locale is not set to English.
This has been fixed.
If the server running Mover has Version Manager 8.2.0.0–8.2.1.0 installed on it, deployments sometimes fail, especially with File Server–based project databases. This is triggered by the modified default location of the ISLV.INI file, which changed in Version Manager 8.2.0.0.
This issue has been resolved. The primary fix for this issue is available in Mover patch 2.3.0.04, but Version Manager itself has been improved as well to better deal with unpatched Mover releases.
A layout problem sometimes prevents users of Firefox 3.0 from selecting the Include files in subprojects option when a promotion model is in effect, because this can cause the option to get obscured in the dialog box.
This has been fixed.
A layout problem sometimes prevents users of Firefox 3.0 from clicking the OK or Cancel buttons in the Advanced Filter dialog box when a promotion model is in effect, because this can cause the buttons to get obscured in the dialog box.
This has been fixed.
The Version Manager Web Server sometimes enters a state in which users can no longer log in. Users attempting to log in to the VM I-Net Web client sometimes get an error message saying that "The resource is locked by session xxxx", or the dialog box hangs with the OK button locked in the Wait state.
This has been fixed.
The View As HTML option does not work correctly for some file types in common use today, particularly the docx, xlsx, and pptx extensions used by Office 2007. For example, rather than viewing the file in the browser as expected, the user might be asked to open a Zip file because Office 2007 files are compressed XML files.
This has been fixed. The new file types have been added to the default mime-type list, and the list itself has been externalized to a file (vm/common/pvcsprop/pvcs/vm/mimetypemapper.properties), enabling administrators to add missing file types in the future.
If a default version label is defined and a check-in is performed to a new line of development (for example, 1.* ‑‑> 2.*), the CLI Put command reassigns the label, whereas the PCLI and the desktop client do not.
This has been fixed. The CLI Put command no longer attempts to move the label.
Under certain circumstances, the File Server can crash or become unresponsive on Win32 platforms. This generally happens when someone is performing a mass Get while the File Server Background Processor is running.
In the vm\common\tomcat\logs\tomcat.log file, the following indication can be found:
java.lang.Exception: Unknown Exception at line 600 in PVNMSystem.cpp
at pvcs.io.file.PvcsFileDirect.stat(Native Method)
…
This has been fixed.
If a workspace other than the default workspace is selected when you share projects to the repository, the selected-workspace settings are ignored.
This has been fixed.
When adding a work file using the RIDE interface to the Eclipse IDE, the default promotion group is not assigned to the initial revision.
This has been fixed.
This has been fixed.
This has been fixed.
When a Project Database has been configured to remove locks on unchanged revisions, Version Manager removes the lock on an unchanged revision and does not increment the tip revision number when the user answers No in the Confirm Check In Unmodified Workfile dialog box ("Workfile … unchanged, check in anyway?"), or when the user selects Don't check in for the If Workfile Unchanged or Older field in the Check In dialog box, and the file is unchanged or older.
As Version Manager goes through an Unlock scenario at that point, the Pre Unlock and Post Unlock triggers should get executed; however, this does not happen in the 8.2.1 release.
This has been fixed.
In some project databases with numerous subprojects that are almost all configured with separate Access Control Database (ACD) files, the desktop client sometimes locks up when a subproject is selected that does not contain the user whose credentials were used to log in to the project database itself.
This has been fixed.
This has been fixed. The license is now checked out for the user ID under which the Remote Build Server is running.
This has been fixed in the Japanese release of Version Manager 8.2.1.0
This has been fixed.
Using the desktop GUI, you can enter a new password for a project for which your old password has expired. However, using the Web client, there is no way to regain access to a project for which the password has expired.
When you import a Version Manager project into Eclipse, the default revision settings associated with the workspace are not imported; instead, the latest revisions of all files are imported.
Project labels on shared files in Visual SourceSafe are not converted when migrating from SourceSafe to Version Manager.
The Web client should check whether you have a Sun JRE installed, but it does not.
This has been fixed.
When you use the -p option with the PCLI get command, a copy of the file is created in the workfile location. The revision should only be output to stdout.
This has been fixed.
If the temporary file location in the TEMP variable has a space in it, attempting to show differences from the Version Manager desktop GUI fails with the error "Configuration file does not exist."
On exit, Show Differences attempts to delete the workfile that was compared rather than the temporary file created during the difference operation. This has been fixed.
Installation fails on non-English language Windows systems with an error regarding security settings and invalid users.
When attempting to use the Web client, the Java Runtime Engine (JRE) displays a warning message that the certificate on the UTF8Encode applet from Serena Software has expired (in March 2009).
NLSPATH environment variables for other software applications may conflict with Version Manager and cause it to crash. This has been fixed.
This may occur when there is a promotion model active and module associations are enabled. As a result, it may be impossible to click the OK or Cancel buttons.
Check-in dates are displayed incorrectly on machines with a Brazilian locale setting.
This occurred because the File Server client transmits too much data, or in other words is too chatty.
This occurred in the Web client.
The file icons should display a lock icon to indicate that other users have them checked out.
After making changes to the Version Manager installation using Add / Remove Programs in the control panel, an error displays that the diffmerge.properties file could not be found. This occurs with the Web client and desktop GUI.
The Web client check-in dialog box does not give you an option to keep workfiles writable. This is inconsistent with options in the desktop GUI. It should be possible to keep a writable workfile, and the options should be consistent.
Firefox 3.0 is now supported.
Rich integration to Visual Studio 2008 is now supported.
Apache 2.2.x is now a supported Web server on Linux and UNIX platforms.
The Visual SourceSafe migration tool applies the current date to all revisions that are migrated.
Windows Server 2008 is now a supported server platform.
Internet Explorer 8 is now a supported browser for the Version Manager Web Client.
You can now use third party merge tools with Version Manager that support additional character sets.
When you display the Manage Promotion Groups dialog box from the Visual Studio source control options, the Promote From field is truncated.
In the Japanese edition of Version Manager, you cannot click the OK or Help buttons in the SCC integration.
In the Japanese edition of Version Manager, an exception occurs when you run the journal file.
In 8.2.0.0, having multiple items selected would run the tool multiple times, passing a single selection at a time. This broke scripts that were expected to be executed just once, while being passed a comma separated list of selected items.
A new option is now available in the Tool Configuration dialog that allows you to select the desired behavior when multiple selections are present. By default this option is set to use the pre-8.2.0.0 behavior of running the tool once, and passing it a comma separated list.
This defect was introduced in Version Manager 8.2. This has been fixed.
This defect was introduced in Version Manager 8.2. This has been fixed.
This has been fixed.
Version Manager server process memory usage keeps growing steadily, to the extent that the process needs to get restarted.
A number of memory leaks have been eliminated. The server no longer needs to be restarted as frequently.
Prior to 8.2.0.1, get and check out operations behaved differently when looking up default revisions. By default, get operations looked up the tip revision of the trunk, and checkout operations looked up the revision associated with the lowest level promotion group.
This has been addressed by providing an option to lookup the revision. See the document on changes to address promotion group and default revision behavior issues that has been released along with this patch.
If the SourceBridge setting "Show Association Dialog on Checkout/Checkin" is selected, the Issue Association dialog box does not appear while checking out / in in both the desktop and Web clients. This has been fixed.
This has been fixed.
This has been fixed.
SCC: When using the SCC integration, Rational Application Developer and Powerbuilder do not stop the javaw.exe, eclipse.exe or pclioutproc.exe processes [DEF151876]
Closing an instance of Rational Application Developer or Powerbuilder that has a workspace connected to the Version Manager repository via the SCC integration does not terminate the javaw.exe, eclipse.exe and pclioutproc.exe processes.
This has been fixed.
.Net Rich Integration: Serena Business Mashup details are not displayed in the Issue window [DEF153908]
This has been fixed.
VS2005 RIDE: Version control history not recorded in Business Mashups item [DEF156030]
Version control history is not being recorded in the Serena Business Mashups item that was associated with the check-in.
This has been fixed.
Web client does not find pvcsmerge.exe in its default location [DEF153827]
Users who only have the Version Manager Web client installed will get a java.lang.RuntimeException in the applet console when they try to run a difference report. This has been fixed.
Version Manager 8.2.0.0 no longer detects applet mismatch , resulting in random failures [DEF154191]
When a new version of the Web cliente applet loads an old native library version, there is no message that tells you that you need to download and install the latest version of the Web client. As a result, a java.lang.UnsatisfiedLinkError message appears when you attempt to Check out, Check in, and Get files. This has been fixed.
Unix: Setuid mode does not work out of the box on Linux & Solaris [DEF153339]
This has been fixed.
Hotspot error when running vss2vm utility [DEF155299]
Conversion of Visual SourceSafe projects to Version Manager using the vss2vm utility fails with nested directory structures. An unrecoverable stack overflow error occurs. This has been fixed.
No error reported in deployment log when Version Manager user doesn't have add label permission [DEF149541]
This has been fixed.
The Event Trigger parameter __EventFQPWorkfile__ (variable EVENTFQPWORKFILE) does not contain the correct path in Pre and Post Create Archive triggers during Add Workfiles operations.
This has been fixed.
This has been fixed.
Version Manager ignores the "NODELETEWORK" (and "DELETEWORK") directives in the project configuration file. Instead, the Check In dialog uses the settings in the islv.ini file to control what is displayed as a default. This has been fixed.
BEHAVIOR CHANGE: A new control has been added to the Workfile | Attributes page on the General tab of the Project Configuration dialog so that the administrator can specify which After Check In option is the default and which options the user gets to select from at check in.
This has been fixed.
This has been fixed.
This has been fixed.
BEHAVIOR CHANGE: A -s option has been added to the vjournal command so the user can specify a delimiter character for use in parsing filenames. Use this when filenames may contain the default delimiter character of a comma (,).
The -b option of the VMRG command causes garbled output. The -b option is supposed to do the following: Ignores white space at the beginning and end of the line during the comparison process (with this option, white space between words is not ignored). White space characters are spaces, tabs, carriage returns, line feeds, and form feeds.
BEHAVIOR CHANGE: The -b option has been removed from the VMRG command so as to avoid undesirable and unpredictable results.
When trying to split an archive from a directory where the current user lacks write privileges, the vsplit command would crash. This is because a temp file must be created in the current directory. This has been fixed. The user will now receive an error message stating that cannot create the temp file.
BEHAVIOR CHANGE: You can now use -d with -z to delete a directory. Since this is dangerous, you will be prompted unless you pass the new -y option.
This has been fixed.
This feature has been added. You can view the delete and rename actions in the file vtransfer.vcs, which is kept at the root of the Path Map. You can also view this information using Actions -> Show Journals and selecting the VTransfer option.
Using the vtransfer command with the combination of the -r -z options to move archives from a parent to a child directory location results in the archives being recursively deleted. This has been fixed. The command no longer accepts a target directory that is a child of the source directory.
When using "vtransfer -i" to import a split archive into a File Server, the split archive location will not be updated if the path you import it into does not perfectly match the one the file was exported from.
This has been fixed.
Options now work as documented.
BEHAVIOR CHANGE: The vtransfer command options -c, -i, and -r now prompt to overwrite if the file already exists.
This has been fixed.
A get with a wildcard fails if a non archive file is encountered and a target dir is set. This has been fixed to ensure that the calculated logfile is a valid archive prior to calculating the workfile name and path. This avoids the invalid warning condition that caused the command to exit prematurely.
After upgrading to VM 8.1.4.x, File Server clients may crash if more than 50 path maps are defined on the server. This has been fixed.
Copy/Import of split archives would fail with a stack trace if an archive or archive path was missing or corrupted.
This has been fixed. An "Archive does not exist" error will now be displayed under such circumstances.
The fields on the Advanced tab of the Create Project Database dialog box did not allow keyboard entry (you had to invoke the browse dialog). This has been fixed. You can now type directly into the fields.
In some circumstances it was possible for a user without the Create Project privilege to create a project. This has been fixed.
Customer wants the default Version Label automatically assigned to the initial revision on create archive.
BEHAVIOR CHANGE:
Desktop Client & Web Client: During AddFiles if there is a default version label, Version Manager will prepopulate the Version Label field with it and enable the Float label with tip checkbox.
PCLI Checkin: To use the default label, omit the -v option. To not assign the default label, use the -v option with no label specified.
Actions | Show Journal does not work if the journal files are located on a File Server and the path to them is accessible only through that File Server.
This has been fixed.
In certain circumstances, the advanced filter can result in 100% CPU usage.
This has been fixed.
This has been fixed.
Selecting View | Refresh or browsing to a different project did not always refresh the client with the latest changes that someone else has made to the workspace information.
This has been fixed.
This has been fixed.
This enhancement has been made.
This has been fixed. Performing a Refresh or changing the column sort order now correctly sorts on the updated Check In dates.
This has been fixed. Performing a Refresh or changing the column sort order now correctly sorts on the updated Locked By users.
When you try to save information, the information is not correctly stored in the following scenarios:
1. If you select keyword expansion option in "Configure Project" dialog box, the backward Slash (\) is replaced with a forward Slash (/) on reopening the option.
2. In General module | semaphore, if you enter 5.000 in "Number of Retries" field and save the information, the number is changed to 3.000 on reopening.
3. Changes are not saved in "Cobol Renumbering" when the option is checked in Configure project | File types.
This has been fixed.
This has been fixed. If a Client Name resembles a UNC path, VM no longer tries to access paths using this Client Name on the network.
If you remove a file from source control and delete its archive from the file server, you will get an error upon trying to re-add the workfile to source control unless you first restart the VM client where the file was deleted from the project (and web server if using the web client). This has been fixed.
Selecting refresh now from the PDB cache lifespan drop-down menu on the Server Options page of the Version Manager File Server admin utility does not remove deleted project databases from the project database cache.
This has been fixed.
If a workfile is being checked into an archive that doesn't have GENERATEDELTA set, the "lines deleted/added/moved:" statistics that get recorded into the archive is a copy of however many lines were deleted/added/moved in the last (and different!) archive that did have GENERATEDELTA set (during the current VM GUI session). This has been fixed. An archive with NOGENERATEDELTA set now always records 0/0/0 for "lines deleted/added/moved".
This has been fixed.
BEHAVIOR CHANGE: A new checkbox, Include Get Operation, has been added to the Journal File page of the Configure Project Database dialog box. Select this new checkbox to include non-locking Get operations in the journal report. By default, they are not included, so as to maintain the previous behavior.
This has been fixed.
BEHAVIOR CHANGE: Keyword expansion has been enhanced to recognize $Id$ as the equivalent of $Header$.
There is no mechanism to deal with multiple LDAP domains.
BEHAVIOR CHANGE: Version Manager now supports multiple LDAP servers, each of which can have its own Base User Context and User Naming Attribute. Version Manager will search all available LDAP servers until it finds a match for the entered user name, and then verifies if the password matches. Version Manager purposefully does not try subsequent LDAP servers if the user name matched on an LDAP server, but the password did not. As such, the requirement is that user names need to be unique among all LDAP servers used in the configuration.
If a project database has:
- ArchiveSuffix +-arc
- ArchiveSuffix . +.-arc
at the root of the project database, and:
- ARCHIVESUFFIX .? = +_v
at a subproject level, Version Manager will corrupt memory. This can lead to a crash.
This has been fixed.
The title bar for each of the panes showed the file name as /tmp/_1pziob19.tmp or some other random tempfile name. There was no way of telling which revision is the newer one. This has been fixed.
BEHAVIOR CHANGE: You can now configure Version Manager to use the third-party Diff/Merge tools of your choice. Besides allowing for greater choice, this allows an effective and easy means of avoiding any aspects of the PVCS Diff/Merge tools that are not suitable to your needs.
This has been fixed. Version Manager is now supported for Client platforms using the HP-UX Aries PA-RISC emulator.
This has been fixed.
The colon is an illegal character for version labels, since it is used by the CLI commands as a revision separator. The PCLI label command allows version labels containing colons to be added, using either the "Label" or the "RenameLabel" command. This makes it impossible to operate on these labels using CLI commands. This has been fixed.
BEHAVIOR CHANGE: PCLI commands can no longer create a label containing a colon character (:). This was always blocked in all other interfaces and was never intended to be possible.
PCLI commands send some non-error information to StdErr and some error information to StdOut. This has been fixed so that each type of information is sent to the expected destination.
BEHAVIOR CHANGE: All PCLI commands have been modified so as to send information to the correct destination: StdErr or StdOut. In addition, some commands previously output only the entity name. They now output the full entity path.
This has been fixed.
This has been fixed.
This has been fixed as follows:
Modified ImportPDB so that it will not fail when importing an 'old' export which has a workspace with trailing whitespace.
Also modified CreateWorkspace so that it strips off whitespace from the start and end of the name to avoid the further creation of troublesome workspace names.
This has been fixed.
This has been fixed.
This has been fixed. PCLI based event triggers that are executed from a VM I-Net server are now able to reuse the same license that was checked out for the user calling the event trigger
BEHAVIOR CHANGE: Two command options have been added to the List command so that you can format its output as XML, -fx and -nx. -fx includes an XML header tag in the output, -nx does not. See the PCLI User's Guide and Reference for more information.
BEHAVIOR CHANGE: The -g option will now climb the promotion model if used with the new -c option.
This has been fixed.
Test -i Command works for = and != comparisons. When you enter the command using < <= > or >=, the -i option is ignored. This has been fixed.
This has been fixed. The Label command now shows the fully entity path and the revision number for files that the label was applied to.
From the command line there was no way to set the default workspace. A command has been added to allow this. See the Serena PVCS Version Manager PCLI User's Guide and Reference for complete information on using the new command.
BEHAVIOR CHANGE: SetDefaultWorkspace allows an administrator to set the default public workspace for users and for users to set their own default public or private workspace. It can also display the workspace currently in effect for the user.
If quotes are missing around an argument, PCLI does not return any explicit error message, which makes it hard to spot the problem when you've got lines of programme. Instead, it just hangs.
This has been fixed.
This has been fixed. You can now use -v< label>* to delete all revisions between the specified label and the tip.
This has been fixed.
A script that invokes the ImportPDB command on multiple project databases may fail if the same project name exists in some of the project databases.
This has been fixed.
This has been fixed.
This has been fixed. Users can now update the workfile location in their private workspaces without having the Modify Project Privilege.
Running several PCLI scripts in parallel may result in contention for write access to the change.log file.
This has been fixed.
Power Builder 11 is now supported by Version manager 8.2.
The PvcsMerge tool on UNIX/Linux (Desktop Client and I-Net) does not label the revision panes. This has been fixed.
As of Version Manager 8.0.0.2, the RSE (Redirect Standard Error) executable no longer works with batch files that are being passed arguments. This has been fixed.
Users who did not have rights to update the Root workspace were allowed to set the workfile location for an individual workfile during an Add Workfile operation by clicking on the Advanced tab and selecting the Use workfile's current location option. However, the same user was not allowed to update the workfile location of the versioned file after it was added to Version Manager. This was seen as a discrepancy in the user's rights which could result in versioned files being copied to an incorrect/undesired location on check out/get. This has been fixed.
BEHAVIOR CHANGE: When adding files using a public workspace, users must now have the MODIFY_PROJECT privilege to select the Use workfiles's current location radio button.
In the PCLI client, an error message will be displayed prior to command execution if the privilege check fails:
The user UserName does not have permission to set the workfile location for project ProjectName in workspace WorkspaceName. Specify an alternative workspace or use the '-c' or '-co' option.
When creating a project, Version Manager automatically creates a directory with a unique name and a pvcsproj.ser file. Since those created directories are always 11 characters (Pxxxxxx.prj), if end users try to add work files under more than a 21 deep directory structure, it would fail because the total path length of the directory for the ser file exceeds the Windows path length limitation (256 chars).
This has been fixed as follows:
BEHAVIOR CHANGE: The suffix (.prj) will not be included in new project directories. The project directory creation process will first attempt to create a 3-character Pxx format directory name. If after 50 attempts it cannot generate a unique 3-character directory name, it will then attempt to generate a 7-character name Pxxxxxx.
NOTE There are two cases where this change does not apply. The first is for Version Manager 5.3 projects which will remain in the old format. The other is the process of moving a project where the target directory of the move already has an existing directory name as the source location. In this case, the new target directory to be created will remain in the old format.
SourceBridge may prompt for login even after being disabled. This has been fixed. Provided "Cleanup associations on undo checkout" is not selected in the SourceBridge Settings for the Project Database, the I-Net client no longer prompts for a Tracker / TeamTrack login.
This has been fixed.
BEHAVIOR CHANGE: It is now possible to delete or rename a blank version label via the desktop client, CLI, and PCLI.
This has been fixed.
If a project is imported from Version Manager using VLOGIN into Eclipse RIDE and then the password of the VM user is changed or removed, the user is prompted to authenticate each time Eclipse is restarted. This has been fixed.
Version Manager was enhanced so that it is possible to run it on Eclipse 3.1.1.
This has been fixed.
If requesting a file history would invoke a password prompt, Eclipse would hang rather than display the prompt. This was a threading issue and has been fixed. In addition, a new field was added to give users more control over login behavior.
BEHAVIOR CHANGE: A new checkbox, Remember password, has been added everyplace the Password field appears. To persist your password across sessions, select the Remember password checkbox, else you will have to login at the beginning of each session.
When in the Conflicts mode of the Compare Workspaces view, the Resolve All Changes button should be disabled as it can do nothing in that mode. This has been fixed by disabling the button in Conflict mode.
This has been fixed.
Special HTML characters like @ and & do not work correctly in passwords.
This has been fixed.
When doing a get and choosing "Prompt if workfile is unchanged", the prompt does not identify which file it is referring to. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. NOTE some features are not supported in VS Ride 2005, Eclipse and Visual Basic 6.0 SCC.
This has been fixed.
When Microsoft Windows locale is set to United Kingdom English, in few instances, error codes are displayed instead of error messages. This has been fixed.
When a solution is opened from source control in VS2005 RICH, projects referenced in the solution are automatically placed into sub folders below the solution file. A problem arises when projects were not originally under the solution file. In this scenario, VS2005 will display a warning that some projects could not be loaded because they could not be located. This has been fixed.
The solution explorer tree does not display the latest file status for check-in and checkout files. This has been fixed.
When a file is checked in with the "Update after keyword expansion" checkbox enabled, the keyword still displays an old revision. This has been fixed.
The "Apply to all remaining files" checkbox on the Confirm Check In Unmodified Workfile dialog is ignored.
This has been fixed.
This has been fixed. You can now check in a directly modified code-behind file.
This has been fixed.
BEHAVIOR CHANGE: Added the ability to work while offline. If you attempt to login into a project database while the system hosting the project database is unavailable, a Work Offline button appears at the bottom of the Log In dialog. Click the button to initiate an offline session. See the IDE Client Implementation Guide for details.
This has been fixed.
This has been fixed. The workspace settings are now properly persisted in the local workspace manager rather than returning to the user default after a restart.
Adding a solution to source control that contains a NetCOBOL project throws an error:
Exception of type SystemStackOverflowException was thrown
This has been fixed.
Overwriting a project file by Force Updating from Compare Workspaces removes the file from the SCC bindings in the Solution file. The result is that the project will not be loaded when the solution is opened from source control.
This has been fixed.
This has been fixed.
The check-in option Update local file after keyword expansion was implemented with inverted logic. This has been fixed.
If the login source of a Version Manager Project Database (PDB) is set to "HOST", and the account has a password, attempts to connect to the PDB through a File Server Path Map that has "Access Control Database" security enabled fails. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
The column sort order was not maintained after invoking an action, such as a Get or Check Out. This has been fixed.
If an embedded configuration file contains a promotion group, the project configuration file seems to be ignored. This can be seen by the Access List creation attribute not being placed on the file when a new workfile is added to source control. This has been fixed.
If an "&" character was used in any field on the Servlets tab of the Version Manager Application Server Admin, an "Error: 500" will be returned.
After doing a get on a file with a & character in the file name, clicking on the ... button next to the revision field to select a version label would produce an Error 500. After this has happened, the same operation would fail for every file regardless of the name. This has been fixed.
When trying to perform the action Merge "Revisions in different versioned files" using a file that resides at the root of a project database, attempts to select the file and revision using the ellipsis button in "Branch 1" or "Branch 2" will yield: "HTTP Status 500 ".
This has been fixed.
If the project database root directory name included a "&" character, the web server would give the following error: HTTP Status 404. This has been fixed.
In some configurations, when a user logs back into a servlet after it has timed out, attempts to perform a Get or Put operation can fail with the error:
java.lang.UnsatisfiedLinkError: pvcs.io.file.PvcsFileDirect.stat()
This has been fixed.
If the LDAP configuration for a project database is setup to follow referrals, an attempt to login can crash the Version Manager server when the referral logic has to kick in, for example because the UserID is unknown due to a typo.
This has been fixed.
Under certain circumstances, accessing both the LDAP Servers and the LDAP Configuration options in the Configure Project dialog could result in a loss of the list of LDAP Servers. This has been fixed as part of a renewed LDAP server configuration system..
When attempting to do a Get to a workpath that was currently not accessible, the incorrect workpath would be displayed in the error message. This has been fixed.
BEHAVIOR CHANGE: An option was added to the Web Client, Add Workfiles dialog to allow keeping revisions locked when adding them to source control.
This has been fixed.
When accessing a WebDAV folder on the file server and on refreshing the view, a memory leak is noticed. This has been fixed.
In Japanese edition of Version Manager, the Serena Business Mashups item ID information did not appear as a version label after checking in. This has been fixed. NOTE You require Serena TeamTrack 6.6.1.13 or Serena Business Mashups 2009 R1 editions or later to view this fix.
This has been fixed.
If a project was checked-in with different description for each work file, the check-in comments were unavailable in Team Track revision history window. This has been fixed. NOTE You require Serena TeamTrack 6.6.1.13 or Serena Business Mashups 2009 R1 editions or later to view this fix.
The Version Manager Web Server leaves a large amount of temporary files in the vm\inet\temp directory. This has been fixed. The directory now gets cleaned up at startup.
This has been fixed.
Users need the ability to immediately remove a stale login session, else the old session may remain open and consume a license until it times out.
BEHAVIOR CHANGE: To allow the user to close his stale login sessions, the following checkbox has been added to the login page: Automatically close all other sessions for your user ID on this server.
In some circumstances, when users switch from a subproject to another subproject or if the user tries to log into another servlet in the same server, all icons are grayed out. The solution was to restart the Apache TomCat. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. View files are now stored in the temporary file location (Microsoft Windows - C:\DOCUME~1\user\LOCALS~1\Temp\pvcs and in Linux - /tmp/pvcs)
This has been fixed. Temporary files are removed on restarting the server.
This has been fixed.
This has been fixed.
In the case of a private workspace and a user without SUPERUSER or UNLIMITED privileges, the link to the workfile location will not be displayed.
This has been fixed.
To add workfiles recursively the user was required to have the Create Project privilege even if the user had no intention of creating projects because the projects already existed. This has been fixed.
When doing a get or check out of a file to a workfile location where there is an existing workfile, the new workfile would overwrite the existing workfile, but would not inherit the folder's permissions. This has been fixed.
This has been fixed. Version Manager no longer throws an exception and stops working if it cannot create the initial ISLV.INI file (Windows) or islvrc file (UNIX) when trying to open a project database.
From the command line there was no way to set such workspace attributes as the default version. A command has been added to allow this. Use the -H option for information on using the new command. (An updated PCLI guide will be included in the 8.2 release.)
BEHAVIOR CHANGE: SetWorkspaceAttributes allows you to set the default version, base version, branch version, and default lowest level promotion group for the current workspace. You can clear the value in effect for the target workspace (to inherit one from a higher workspace or project entity). You can also display the values in effect for the specified project and workspace, including values inherited from higher level projects/workspaces.
Running CLI commands with wildcard characters contained in quoted strings (single or double quotes) on Solaris 10 results in a segmentation fault for certain directories. The same command without the single quotes works fine, but that would not be a workaround for path names that have spaces. This has been fixed.
If you have Remove lock on unchanged revision set in your VM project database, and you check in files associated with TeamTrack items through SouceBridge, Version Manager will label unchanged files with a TeamTrack item label. This has been fixed so that only items that are being checked in receive the label.
When adding workfiles and selecting the option to "Don't check in work file" the SourceBridge association can hang. Since no revisions exist in this situation, it is impossible for SourceBridge to associate a record. This has been fixed.
On UNIX with 8.1.4 or 8.1.4.1 installed in setsuid mode, running CLI commands like "get" as a user other than the setuid user may fail if the WORKDIR CFG file directive points to a directory that is not writeable by group (if a member of the group) or other. This defect was introduced in 8.1.4. It has been fixed.
Version Manager was enhanced so that it is possible to run it on Windows Vista.
If you tried to execute View or Edit a file that did not have a Windows file type association, an exception would be shown saying "pvcsexec.exe has stopped working". This has been fixed.
This defect was introduced in Version Manager 8.1.4.1. This has been fixed.
This has been fixed.
The customer is able to successfully generate a web service only once. Any attempts after that result in an error:
"IWAB0443E Error parsing webservices.xml: org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources."
This has been fixed.
This has been fixed.
If the user has a default workspace set for the project database, it is used regardless of what workspace they select while importing the project. This has been fixed.
BEHAVIOR CHANGE: The workspace the user selects during the project import will be used.
After installing VS2005 SP1, archive actions return assertion failure errors. This has been fixed.
The user is manually creating a folder on disk under the solution and adding solution items from that folder. When the solution is added to source control, the physical solution folder gets added to VM the same as project folders. When opening from source control, the solution files are retrieved first and then each project folder is opened individually. Since the folder containing the solution items in VM is not a project folder, it is overlooked. This has been fixed
This has been fixed.
A sufficiently knowledgeable person may be able to spoof or impersonate a login to the Web client if HOST ID is the login source. This hotfix increases the security of the HOST ID login source and the Web client. Details have been omitted from this description to limit exposure and reduce risk to those who have not upgraded.
The VM Web Server would randomly crash on UNIX, referencing pvcs.vm.vms.AccessDatabase.PvcsLogin() in the crash dumps. This has been fixed.
If you close the browser without first logging out of Version Manager, the license is held until the servlet timeout period passes. This has been fixed.
BEHAVIOR CHANGE: If you close the browser or use the same browser instance to open a different URL, the license is released immediately or within a few seconds, depending upon the browser used.
BEHAVIOR CHANGE: The password length limit has been removed.
Check-in time is GMT rather than the "Mexico City-New" timezone the server box is set to. This has been fixed.
This has been fixed. You no longer must be an Admin in order to install the Version Manager Web client to Internet Explorer 7 on a Windows Vista system.
Jobs are saved under the user account folder corresponding to the OS user running the VM Web Application server (instead of the VM user id). To Builder, it looks as though the job was created as "system" if the VM Web Application server is running as a service as LocalSystem. As a result, a user won't be able to update or execute the jobs created in the VM Web client, no matter if using the VM Builder integration (once they leave the wizard) or Builder Web Client. This has been fixed.
The Builder integration wizard prompts the user for a Search Path and Build Job name. However, unlike the Desktop client, it does not prevent the user from progressing through the wizard without choosing a search path. The result is a malformed build job. This has been fixed.
When executing a build using the VM/Builder integration, the step of fetching revision information using the VMMBI_GetRevInfo.pcli script will fail when encountering an archive that has no revisions. This has been fixed.
If you select a remote build machine instead of My Computer, the resulting job is not created correctly. The MachineName of the machine selected shows My Computer. This leads (I think) to Builder Web Client showing only one machine in the job (My Computer) and it having no activities. This has been fixed.
This has been fixed.
When creating a new build job through the Builder wizard in VM, the parameters in the task for the build job are not saved correctly. The <Command> portion is correct, but the other parameters where the build job is derived from do not have the information necessary to reconstruct the commands in the Builder Web client. This has been fixed.
BEHAVIOR CHANGE: Changed the "options" command patterns field to include the integration parameters for the associated buildmake and OM tasks. This was done because it was possible not to have any OM command pattern options which triggered the Openmake Web client to reset all of the build job parameters back to their defaults if the build job is changed from the Web client.
The VSS2VM tool doesn't run in the Japanese locale, throwing an EXCEPTION_ACCESS_VIOLATION error. Attempts to run the converter in the English locale as a workaround fail if a filename or a label has a DBCS character containing 0x5C.
This has been fixed. You can now run VSS2VM in the Japanese locale.
This issue occurs only if an archive is empty, that is the archive contains no revisions.
This has been fixed.
Manually refreshing the Desktop client (View | Refresh) can be very slow. Although it is not hung, one could easily assume that it is due to the slow progress.
This has been fixed.
This issue results in the following error: "[Info] No journal information exists matching the requested specification".
This has been fixed.
Patch installer does not detect whether the executables it is replacing were running in setuid mode.
This has been fixed.
When the Builder 6.3.1 to 6.41.1 patch and build job conversion is performed, a space is added to the end of each environment variable. When the Version Manager integration loads one of these converted build jobs, it fails to populate the integration dialogs with the information stored in the environment variables. To the user, it appears that the build job information has been lost. If the user goes through the dialogs and saves the build job, all of the original build job information is lost. However, if the spaces are manually removed from the build job, the VM integration correctly populates the dialogs.
This has been fixed.
A build based on the promotion model requires that the target promotion group be on the TGT file. Else the integration refuses to start the build definition and an error is returned: "No targets found with: group name".
This has been fixed.
The integration was looking for a TGT file revision to use to get the project name from. It was doing an exact match for a promotion group. Instead it needed to chase the promotion chain to find a revision. For example if the promotion model is dev, qa, prod and the TGT archive does not have the "dev" promotion group assigned but does have "qa" assigned and the user specifies that they want to build at the "dev" level, then the integration would first look for a revision at "dev" and when that is not found it would then look for "qa" which it does find.
Certain combinations of filter options could produce incorrect results.
This has been fixed.
Customer request to make workspace information available. The follow event information has been added: EventWorkspaceBase; EventWorkspaceBranch; EventWorkspaceName; EventWorkspacePromoGrp; EventWorkspaceVersion. See the Serena Version Manager Administrator's Guide for more information.
Open (Serena-SB | Open from Serena Team Provider) fails if subproject/folder name is more than 60 characters long.
Error Message:
Failed to open Project VTPTerminierungWAR - Error Code: SCC_E_OPENNOTPERFORMED
This has been fixed.
IDE's hang onto license longer than desired after being closed.
This has been fixed.
Add SCC and Rich Integration support for Rational Application Developer 7.
This feature has been added.
IMPORTANT! See Integrating with IBM Rational Application Developer 7 in the Install_Info.html readme file for information on installing this integration.
When checking in multiple files, the Use for all checkbox is not honored if one or more of the checked out revisions are non-tip revisions.
This has been fixed.
This has been fixed.
The integration correctly handles projects outside of the solution if the projects and solution are added to source control at the same time. However, it does not work correctly if the project was added to the solution after the solution was controlled. In this case, Open from Source Control will fail for the added project.
This has been fixed
Selecting the Servlets tab of the Version Manager Application Server Admin may sometimes result in the error:
"Unable to open properties file C:\Program Files\Serena\vm\inetprops\PVCS Servlets.properties".
This has been fixed.
At startup, it does not log on automatically. Instead the Login page appears with the Username field grayed out and a field to put a password in.
This has been fixed.
This has been fixed.
In some circumstances, using vtransfer -r to make a case-only name change to an archive could result in the deletion of the archive. This has been fixed.
This has been fixed.
The customer wants to see those files where the promotion group and the label are pointing to the SAME revision. At present, the filter cannot provide this information, since the invert option ("Show files not matched by this filter") also shows files that don't have the label and/or group at all.
The filter has been enhanced to support the customer use case.
Customer's build hangs when a PCLI Get command randomly locks up after an otherwise successfully completion.
This was an issue with licensing. This has been fixed.
Done.
If a copy project operation fails due to exceeding the path-length limits of the operating system, the error message did not state which specific projects exceeded the O/S limits. This feature has been added.
Various operations in setuid mode would fail for invalid reasons. This has been fixed.
This has been fixed.
Completed.
The combination of enabling case sensitive client path and creating a UNC style client path from Windows on a UNIX file server, can result in backslash (\) characters in the UNXI-based project database. This has been fixed.
This has been fixed.
In some obscure circumstances, Path Map security on the File Server might be ignored. This has been fixed. For reasons of security, details of this issue will not be published.
For increased File Server security, Serena recommends upgrading the clients as well as the File Server to release 8.1.4.
To mitigate this issue on older releases and to maximize security on 8.1.4:
Ensure that utility access is restricted. (On the Options page of the File Server Admin, change Enable Utilities to LocalOnly or to Off.)
Limit login access to the system that is running the Version Manager File Server so that only Version Manager administrators can login to the operating system.
Both the AddUser and DeleteUser commands are equipped with the -pp option to specify a project. According to the manual, the function of this option is that it:
"Specifies the project or folder to which the user will be granted access"
When you run the command with the -pp option that command completes successfully, but the user is added to the ACD defined at PDB root level, not the one associated with the specified project level. This has been fixed.
Show History returns "Unknown Exception at line 2446 in VMNMArchiveFile" instead of the expected message of: "No history exists matching the requested specifications". This has been fixed.
The data in the Folder Name field is unreadable. One can type correct data in there, it is still unreadable, but it works. This has been fixed.
Command line users may occasional see the confusing message "DTK after clearing cache mkfile returned -1". This has been fixed.
The History pane has been enhanced so that it can display revisions using a tree structure so that the hierarchy of branched revisions can be shown.
Added Force Branch option at check in.
Migration of Visual Studio 2005 web projects from the SCC integration to the rich integration fails. This has been fixed.
Added a configuration option to the desktop client so that the administrator can require users of the rich integration to Visual Studio 2005 to check out files in order to edit them.
Customer is trying to authenticate to TeamTrack by selecting the TeamTrack Login icon (not by launching TeamTrack from within the IDE - which works fine) and is getting "Invalid User" in the issues pane. Everything looks set up properly. This has been fixed.
This support has been added.
If one archive is renamed, moved, or deleted all files will appear as incoming changes when compare workspaces is run. This has been fixed.
A user may log out and not be able to log back in from the same system with the same ID until the web server is restarted. When attempted, the login dialog would hang (with the OK button showing Wait). This happened intermittently. This has been fixed.
If you run a PCLI or CLI command from an Event Trigger, that command will cause a second license to get consumed. This has been fixed.
This causes problems for sites that needs to access the server from both sides of a firewall, where the server has distinctly different names depending on what side you look from. This has been fixed.
If the top level project contains no files
and you do a recursive get based on a label
and you specify a non-default "Copy to" location,
then the first sub project will be placed in the specified location, but any others will be placed in the default location.
This has been fixed.
This has been fixed.
If a subproject has an access control database, LDAP authentication may not work correctly. This has been fixed.
If HostID is the login source and a subproject has a different password than the project database, you will lose access to the project database level once you log into the subproject. This has been fixed.
If the option to Ignore Ctrl-Z is enabled, the last line of the file will not be displayed by the Merge Tool. This has been fixed.
When accessing TeamTrack through the Eclipse RIDE interface, concurrent licenses are not released by the license manager after the TeamTrack window or the IDE itself is closed. This has been fixed.
If the path to an archive, or the archive name itself, contains double-byte characters, attempting to unsplit the archive will result in data loss. This has been fixed.
Under some circumstances, history reports on Windows sometimes fail. On UNIX, they sometimes crash. This has been fixed.
PCLI VLOG -bv can be used to find out what revision a version label is assigned to. If no label is specified the system should report on the default version label, but it does not--it gives a report showing all version labels on all revisions. This has been fixed.
This has been fixed. Version Manager now works with full length multi-byte paths in Windows.
Filters, such as "Locked by" sometimes do not accurately reflect the current state of the archives. This has been fixed.
The advanced filter would confuse a label that contained a comma for two separate labels. This has been fixed. It is now possible to filter on a label that contains a comma by setting the delimiter character to a semi colon (or the other way around).
If the case of the user id in the access control database differs from the case of the user id for the host login source (i.e. admin vs. Admin), the user can do everything with a file (lock, unlock, etc.) except a check in. A check in results in "Could not complete action because the revision is not currently locked by this user." This has been fixed.
A Windows web client hitting a UNIX/Linux server will receive the incorrect End of Line character if the archives are split. This has been fixed.
SSL connections fail after restart, but will work if restarted multiple times. This was a defect in Tomcat. This has been fixed.
This has been fixed.
The underlying cause of the error has been fixed, also the error messaging has been improved to better identify the true cause of certain errors.
An error similar to the following would be returned and the operation would fail:
ChangeMan Version Manager could not create the semaphore "//FS/...../archive-arc" for this project....
A file that has been branched multiple times and that has had an interim branch renamed will fail with an "unable to build branch" error. This has been fixed.
If your project database used LDAP as a login source, an attempt to access any of these security dialogs:
- Admin | Security | Users
- Admin | Security | Privilege Sets
- Admin | Security | Access List Groups
- Admin | Security | Show Report
Would result in an error similar to the following:
12:03:40 Apr.14.06 [Error] You have encountered an internal processing error: 50 (PVCS_E_NO_USER_ID: Unable to obtain the user ID.)
If a Version Manager client is configured to access a Version Manager file server that is unavailable, the client will hang. This has been fixed.
SCC and rich integration support has been added for Visual Studio 2005.
NOTE This new integration resolves most limitations and issues associated with the Visual Studio .NET 2003 integration--but only for Visual Studio 2005. The integration to Visual Studio 2005 is a separate install from the integration to Visual Studio .NET 2003, so it cannot resolve any issues in the Visual Studio .NET 2003 integration.
This feature was added to the rich integration to Visual Studio 2005.
In Visual Studio 2005, the results text distinguishes between get and check out operations.
When adding large solutions to source control, the solution is added to Version Manager correctly, but the IDE becomes unresponsive. Once the IDE has been killed and relaunched, the solution is under source control context. This has been fixed.
Adding web projects to source control resulted in the following error:
"Unable to create a session for VMPro - Failing ClientAPI unable to createSession Possible UVE_Lib definition Error"
This feature is supported in the integration to Visual Studio 2005.
This is fixed in the integration to Visual Studio 2005.
When attempting to open a solution from source control, the user may receive the following error:
"Unable to create session for \\CEI\InformationTechnology - Failing ClientAPI unable to createSession Possible UVE_Lib defintion error"
This was seen on systems with Crystal Reports 10 and also sometimes if a web project had been loaded first. This has been fixed.
Open From Version Manager produces the following error if the root folder contains both the project and solution file:
"System.NullReferenceException: Object reference not set to an instance of an object"
Having both the solution and project files in the root directory is not a supported configuration.
The new integration to Visual Studio 2005 will: Catch the exception, add a logging message to indicate the error, and skip the solution/project file. This allows the remaining solutions to be opened.
This is fixed in the integration to Visual Studio 2005.
This is supported in the integration to Visual Studio 2005.
This is fixed in the integration to Visual Studio 2005.
End-of-Line translation is now performed correctly.
This patch includes several hotfixes that have previously been released. Since the patch installer does not remove content from the Install_Dir\vm\common\lib\patch directory, any pre-existing patch files will still be present after installing this patch. This could have adverse impact because the "old" content in the patch directory will be used instead of the "new" content in the vm.jar that was shipped with this patch.
To avoid potential conflicts, remove any files in the Install_Dir\vm\common\lib\patch directory before installing the 8.1.2.2 patch. If you have any patches newer than 8.1.2.2, re-install them after installing 8.1.2.2.
If a file with a double-byte name is added from a Windows-based system, the UNIX Version Manager client will hang when it tries to access it because it uses a different and incompatible code page. This has been fixed for the PCLI, Desktop client, and Web client.
However, some CLI operations (such as Get and Put) will continue to fail if the workfile name in the archive contains a character incompatible with the client code page. To work around this issue, use the "archive(workfile)" syntax to explicitly pass a workfile name that is valid in the client's code page.
Intermittently, and on a non-reproducible basis, the contents of a random archive would be replaced by the contents of another. This has been fixed.
When File Server archives are updated (either unsplit or the meta-data part of a split archive), the updated archive remains in the ARCHIVEWORK directory and is not moved over to the FS_TMP directory. Because of this, the cleanup routine will not be able to cleanup these temporary files. This has been fixed.
Quoting a command string containing brackets [] was not sufficient to make it work correctly. This has been fixed.
If a PCLI command runs into an internal error, instead of printing that error the application will crash. This has been fixed.
Customer would like Version Manager to warn if the project structure gets too deep when creating a new project so it won't hit the Windows limitation of 256 bytes. This feature has been added.
When running an EventTrigger on Linux kernel 2.4.20 or beyond, the following error appears:
You have encountered an internal processing error: 106 (PVCS_E_TRIGGER_FAILED: The event trigger failed.)
If the trigger is of the Pre* type, the operation will subsequently fail. This has been fixed.
On some Linux platforms, a non-expected error message is displayed while opening a History Report or Journal Report, even though the report is shown correctly. Likewise, external PCLI commands (run -e) execute correctly but return an error code indicating failure. This has been fixed.
If an archive has been deleted or corrupted outside of the interface, all files will be erroneously marked for removal at the next synchronization. This has been fixed.
Several processes continue to run when the user attempts to close the IDE. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
The Show Issue report title is replaced with the title of an issue from the list. This has been fixed.
Intermittently lose the ability to see existing version labels and promotion groups.
We were not able to reproduce this issue in house, but are reasonably sure we have resolved the cause. If anyone continues to experience this issue, we would like to hear more about your configuration, usage, etc.
Adding a large number of files while associating issues using TrackerLink may throw a General Exception when the login authentication method is LDAP. This has been fixed.
This has been fixed.
Some text may still appear a bit smaller than expected, but for the most part this issue has been fixed.
In order to make sure that Version Manager got project information (such as configuration file locations) from the Version Manager File Server, you had to make sure that the location was not also mapped by an entry in the nfsmap file. This has been fixed.
Error messages for a variety of circumstances have been made more specific and helpful. Some specific instances include:
DEF81501: vsplit does not report cause for failure when File Server authentication fails.
DEF81504: VTRANSFER error message "Move Failed!" is much too generic.
DEF82350: Error due to lack of permissions on ACDB does not get reported as such.
INT82352: Inability to create semaphore files should be reported as such.
ENH78863: You have encountered an internal processing error 117.
DEF78667: Fatal permission problems on %TEMP% and %FS_TMP% shall be identified as such.
DEF80554: Wrong error message when AIX user unable to write to /tmp/pvcs and /tmp/pvcsfs.
If you login to a project database using LDAP and then log out without closing the GUI, upon logging back in you do not need to supply a password in order for the login to succeed. This has been fixed so that the LDAP password is required when you log back in.
Open VM with the option 'open any previously opened project databases'. Log in to one pdb. Highlight a file in the versioned file pane. Then click on the plus sign (+) next to the name of another pdb on your list. If this pdb has as its login source "host id" and needs a password, this action hangs the whole of VM - you can only exit using Task Manager. This has been fixed.
Unix client gets "java.lang.IllegalArgumentException" with PCLI put command if past revision contains specific Japanese character. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Other than the scroll bar, this has been fixed. The scroll bar still may not behave correctly on large files. Use the Next, Previous, and Go to line features instead.
This has been fixed.
This has been fixed.
Attempts to manually launch the Diff/Merge tool via the executable (pvcsmerge.exe) fail with a licensing error.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This feature has been added.
This has been fixed.
This has been done.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This change has been made.
This has been fixed.
This has been fixed.
This feature has been added.
This feature has been added.
This feature has been added.
This has been fixed.
This has been fixed.
The Desktop Client would lock up after displaying the login dialog for a second project database. This has been fixed.
In the .NET IDE, if you add a project from Version Manager and specify the local workspace used by the current solution, files with names similar to those in the current project may fail to open. You must then reopen the project from source control to another location so that you can clean things up. This has been fixed.
This has been fixed.
This has been fixed.
Running the operation twice would complete the process. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
If ARCHIVEWORK and WORKDIR are defined in the configuration file as "", which resolves to current directory, all file actions fail. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This affects both the Web server and the File server.
This was fixed in a previous release cycle, but was reintroduced before GA. This has been fixed.
This feature has been added.
This has been fixed.
This has been fixed.
This feature has been added.
This has been fixed.
Login to a PDB located on a file server may fail if the user name contains high ASCII or Asian characters. This has been fixed.
This has been fixed.
This has been fixed.
CLI commands using an @list may not execute correctly or may fail with a protection fault. This has been fixed.
The fix for this defect was omitted from the previous patch. This has been fixed.
The closing "$" character may not be properly detected, resulting in the loss of file data up to the next "$" character or the end of the file, which ever comes first. This has been fixed.
NOTE As part of this fix, the syntax for fixed length keyword expansion has changed. This change is not yet reflected in the documentation, but is included below:
If the content of a keyword contains a "$" character, you must use the new syntax:
$Keyword::$123456::$
Where:
Keyword is the keyword.
123456 is the length delimiter. The length is determined by the number of characters. Any characters can be used as the length delimiter.
::$ marks the beginning and the end of the length delimiter character string.
If the content of a fixed length keyword does not contain a "$" character, you may use either the new syntax or the original syntax, which follows:
$Keyword::123456$
There is a Copy button to allow you to copy the results of an operation to the Clipboard. This button does not work if you are using a workstation installation installed from a UNC path. This has been fixed.
If you assign a version label or promotion group that matches a revision number to a different revision, you can no longer access the revision with the matching number using the desktop client, the web client, or the PCLI. For example, if you apply the label "1.5" to revision number 1.7, it is longer be possible to access revision 1.5, because attempts to access revision 1.5 yield revision 1.7.
This has been resolved. Whenever the Revision field or corresponding PCLI option (-r) has a value that looks like a revision number (like 1.5 or 1.4.2.1), Version Manager tries to get a matching revision number and not check whether there is a label or group by that name. If you need to use the Revision field or corresponding PCLI option to access a version label or promotion group that looks like a revision number, precede that label or group with a backslash (\).
Caution: In dialog boxes where you pick a label or group from a list, this release of Version Manager does not automatically precede the label or group with a backslash when the label or group looks like a revision number.
To avoid confusion, we strongly recommend never using labels or groups that look like revision numbers.
This has been fixed. See DEF78155.
This has been fixed.
This has been fixed.
If you execute vsplit -u from the directory containing the metadata archive, the archive may be deleted.
This has been fixed.
This has been fixed.
Under some circumstances it was possible to see LDAP passwords. This has been fixed. In the interest of security, the details of this defect will not be described here.
This has been fixed.
In certain circumstances, unsplitting a split archive will cause the metadata of the new unsplit archive to reflect the information stored in the delta.d file.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Using the Version Manager web client with an Apache 1.3.x server configured to use EAPI produces an error when you try to start the Apache server. This has been fixed.
If a default version label is defined, the History Report ignores the specified revision and always checks the Default Version against the tip revision. This has been fixed.
Following the otherwise successful completion of a command or script, PCLI prints:
Exception in thread "main" java.util.ConcurrentModificationException
at java.util.Hashtable$Enumerator.next(Hashtable.java:976)
at pvcs.vm.VmFlexFactory.checkinAllLicenses(VmFlexFactory.java:52)
at pvcs.cmd.CmdProcessor.pcliMain(CmdProcessor.java:202)
at pvcs.cmd.CmdProcessor.main(CmdProcessor.java:174)
This issue has been resolved.
When the Version Manager desktop client opens on a remote X Windows display, screen updates can take a very long time.
This has been fixed.
After you perform certain operations in the project pane of the Version Manager desktop client, the project pane occasionally collapses, requiring you to browse back to your original project.
This has been fixed.
The default semaphore suffix used by vsplit (??$) results in a failure when you try to split an archive that has a dollar sign ($) in the file-name suffix.
This has been fixed. The vsplit command now supports the -C option, which you can use to pass the command a configuration file that redefines the semaphore suffix to be used (for example, SemSuffix = +-sem). For more information, see the SemSuffix directive in the Serena PVCS Version Manager Command-Line Reference Guide.
When an event trigger executed from a UNIX client tries to access a file on a File Server (for example, through a CLI command), that trigger fails with a SOAP FAULT message.
This has been fixed.
The description of the different types of configuration files is somewhat confusing.
This has been fixed.
This has been fixed.
If TRANSLATE is on, the "unchanged" prompt does not appear on Unix. This has been fixed.
When vtransfer -r is used only to change the case of the name of an archive, it can result in the loss of the archive.
This has been fixed.
A UNIX File Server configured to be case-insensitive sometimes treats an archve in a case-sensitive manner. Such archives are temporarily unavailable to the Version Manager clients.
This has been fixed.
The Version Manager Web Application Server process used to provide the File Server, the Version Manager Web Server, and WebDAV services sometimes shuts down on Windows systems when someone logs off from that system's console.
This has been fixed.
Attempts to run vsplit or vsql against a DBCS (double-byte character set) archive on a File Server locks up those commands. This has been fixed.
In Version Manager 8.0.2.x, the Visual SourceSafe convertor fails with the message "ERROR: PVCS_E_ACCESS_DENIED". This has been fixed.
A user without rights to create a project in Version Manager in other environments is able to create a project in Eclipse/WSAD environment. This has been fixed.
This has been fixed.
This has been fixed. For details, see the online help for the new promotion dialog boxes.
When an https: connection string is specified to connect to the File Server, the IDE integration prefixes that string with http:. This makes it impossible for the IDE integration to connect to the File Server via HTTPS.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Some of the default configurations in the Tomcat server used by Version Manager can expose potential vulnerablilities.
This has been fixed by switching to Tomcat 5 and by modifying and removing vulnerable configurations.
Under certain circumstances (generally involving users logging off), the temporary files stored in the File Server client cache directory are not cleaned up on exit. This issue is being addressed by a new feature that automatically cleans up old files whenever a Version Manager session first contacts the File Server.
You can exert some control over this feature by adding entries to your islv.ini file.
NOTE: Time values are in seconds by default, but you can specify minutes or hours using the <n>m or <n>h syntax.
New settings of interest are as follows (shown with the default values that will be used if the entry is absent):
[PVCSGUI_6.5]
pvcs.fileserver.cache.cleanup.frequency=12h
Wait at least 12 hours following a cleanup operation before attempting to clean up the cache directory again.
pvcs.fileserver.cache.cleanup.age=24h
Clean up all files that are at least 24 hours old.
pvcs.fileserver.cache.cleanup.mode=m
Determine the age of the file based on its modification time ('m'). Can also be set to 'a' (file access time) or 'c' (file creation time). The default is highly recommended as some file systems could exhibit bad behavior with the other options.
NOTE: The location of the File Server client cache directory is determined by the environment variable FS_TMP or, if FS_TMP is not defined, FS_TEMP. If neither is defined, the directory defaults to %TMP%\pvcsfs or, if TMP is not defined, %TEMP%\pvcsfs.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed for the Solaris platform.
This has been fixed.
This has been fixed.
When using the browse capability for local file systems or when trying to open a project database, some users receive the following error: "There is no disk in the drive. Please insert a disk into drive A:."
This has been fixed.
Clicking the file browse button in any Version Manager web client dialog box can cause an error message to appear in the Java Console referring to an A: drive security problem. In that case, the browse dialog box does not open.
This has been fixed.
The job fails with one or more of the following messages:
VMMBI6200: verify_gets: Error: The get for: '<file_name> failed', the work file time does not match:
If the current time is within Daylight Saving Time, the error message is produced for those Version Manager workfiles that have a "last modified date" outside of Daylight Saving Time. Likewise, if the current time is outside of Daylight Saving Time, the error message is produced for those files within Daylight Saving Time.
The failure occurs only when the build directory is located on a FAT or FAT32 disk volume. It does not occur on NTFS volumes.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. Wheel mice now work correctly in the desktop client, and they work in any web client that uses version 1.4.1 or higher of the Jave Runtime Environment (JRE).
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
There is no good way to obtain the entity path for the versioned file for which an event trigger is executed.
This has been fixed. There is a new event parameter, EVENT_ENTITY_PATH, for all the event types, and the EVENT_WORKFILE parameter is enabled for the events Lock, Unlock, Promote, and Create Archive.
If a user is a member of an access list group, and that group is specifed in an archive after an empty access list group, the user cannot see the revisions even if the user has unlimited privileges.
This has been fixed.
CLI commands on UNIX interpret the SemaphoreDelay as a value expressed in seconds rather than tenths of a second. This has been fixed.
This has been fixed.
A certain combination of ACD privileges can make a user UNLIMITED. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
If a specific port is specified for the license server during installation, Version Manager adds an extra @ character in islv.ini.
This has been fixed.
This has been fixed. The AddUser command now has a new -ps option for specifying a custom privilege set.
The following example creates a new user with Developer and PromoteToQA privileges:
AddUser -ps"Developer,PromoteToQA" Simba
The -ps option is not required. If you specify the option, you must include an argument specifying a list of one or more privileges. Use commas to separate multiple privileges. If the argument contains spaces, enclose it within double quotation marks.
If you do not specify the option, the new user will have the Unlimited privilege set.
If the default font size used by Version Manager is too small in the your UNIX environment, you can increase the font size through the pvcs.fontSize property; however, some dialog boxes do not reflect the change.
This has been fixed.
This has been fixed.
This has been fixed.
If you are a member of multiple privilege sets and one of these privilege sets is restricted to a promotion group, attempts to view the Granted Privileges on an archive (right-click | Properties) generates a Java exception (Windows) or causes a crash of the desktop client (UNIX).
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. The command now returns –1 if the import fails.
This problem occurs when your Access Control Database has a file-name extension of .acd.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
In a heterogeneous environment where the Client Name of a Path Map is specified as "windows style", a UNIX client cannot read the pvcsldap.ini file from the File Server.
This has been fixed.
If you check in an unchanged file, and the option to not check in an unchanged file is enabled, the file is unlocked as expected, but a prompt asks whether you want to merge the branch to the tip (even though there may be no branch revision).
This has been fixed.
This has been fixed.
This has been fixed.
When you delete a file from your workspace, you get the option of deleting the file from the Source Control Tool; however, if you do not delete the file from the project at that time, you do not get the option again when you run synchronize.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Using the Diff/Merge tool from the Version Manager web client on UNIX shows the revision contents in DOS style, even if the archive being examined has the TRANSLATE archive attribute enabled. If you compare a revision against a checked-out workfile that has TRANSLATE enabled, the Diff/Merge tools reports all lines as being different.
This has been fixed.
This has been fixed.
This has been fixed.
When the user ID is the same throughout the PDB but the password is different among projects or subprojects, the login dialog box does not appear when the user selects the plus sign (without selecting the folder) to expand a project or subproject tree.
This has been fixed.
This has been fixed.
This has been fixed.
If a version label starts with a digit, the PCLI isDifferent command fails, and the error message displays the wrong version label.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When the $(Command) alias is used in configuration files, it incorrectly identifies PCLI as "VMGUI" on UNIX and Linux platforms.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Access to a File Server PDB is denied when you log in using a DBCS (double-byte character system) ID. This has been fixed.
If your ARCHIVEWORK and WORKDIR directories point to a slow drive, such as a network volume, attempts to update an archive on the File Server may corrupt the archive. Because ARCHIVEWORK and WORKDIR default to the current directory for command-line interface (CLI) operations, you could trigger this result just by running a CLI command when the current directory is a mapped network drive, or even by using a local drive on a busy system.
This has been fixed.
This has been fixed.
The security report (Admin | Security | Show Report) shows the passwords stored in the ACD if the user running the report is a SUPERUSER. Because it is fairly easy for an UNLIMITED user to become a SUPERUSER, we need a way to disable this feature.
This has been fixed. By default, the Security Report no longer shows passwords, even if the user running the report is a SUPERUSER.
To allow a SUPERUSER to see passwords (as they could prior to this change), there must be a file called:
VM_Install_Dir/vm/common/pvcsprop/pvcs/vm/security.properties
with these contents:
vm.showpasswords=enabled
New revisions are not created when you check in files from Interdev. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When the File Server and the Version Manager web server are running in the same instance of Tomcat, journal files and reference directories are sometimes modified with information pertaining to delta.d file changes. This has been fixed.
The setting of the %TEMP%, %FS_TEMP%, and %FS_TMP% directory environment variables can cause heap corruption that leads to Java "unknown exception" and other failures. This has been fixed.
These occur if there is no diskspace left on the Temp directory defined under File Server Administrator | Options. This has been fixed.
If temporary directories are not specified, temporary archive files get created in the product installation directory. This has been fixed.
This has been fixed.
This has been fixed.
With LDAP authentication in place, users sometimes receive an error stating that they lack the privileges to access files. This has been fixed.
This has been fixed.
The documentation suggests that a read-only network share is a valid location for the servers.ini file; however, this configuration causes error conditions.
This has been fixed; the product now supports this documented configuration.
If the chosen or default device-specific temp directory is invalid because the specified name already exists as a file name, attempts to update files through the Version Manager File Server result in these files being replaced by 0-byte files.
This has been fixed; an appropriate warning now appears.
When you run the vsplit command, the .??$ semaphore file that gets created for the archive does not get removed. This has been fixed.
This has been fixed. The section on licensing workstation installs has been removed; the subject is covered correctly in another part of the guide.
This has been fixed.
The default location for the new pvcsldap.ini file is the Version Manager installation directory, which causes problems when the Version Manager installation is local.
This has been fixed; the default location is now the root of the PDB.
If the case of the login ID returned by the HOST login source changes (for example, as a result of the customer switching domains) in a case-insensitive PDB, the private workspaces for the users are permanently deleted. This has been fixed.
To preserve path names with spaces in an @list, you normally need to enclose the invidual path names within quotation marks; however, the vsplit command silently ignores quoted path names. This has been fixed.
The file server client does not honor the total cache file size limit. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
If you are using version 4.0 or 4.0.1 of Collage and you try to interface Version Manager and Collage, the files are not uploaded to Collage. This has been fixed.
This has been fixed.
This has been fixed.
From within an IDE, performing a Show History operation on revisions locked by a specific user returns all users. This has been fixed.
If a user that does not have version label permissions within WSAD connects to a Version Manager Project Database and attempts to label a file from within WSAD, the operation seems to proceed with no errors; however, viewing the file in Version Manager reveals that it does not contain the version label. This has been fixed.
Populating your Access Control Database by adding authenticated LDAP users using the auto-create feature doesn't work if you are using the Version Manager web client. This has been fixed.
This has been fixed.
The documentation incorrectly refers to a Tracker project rather than a Tracker server in connection with configuring servlets. This has been fixed.
This has been fixed.
Though we are shipping mod_jk 1.2.1 for Apache 1.3, a customer noticed that we are still shipping the 1.2.0 release for Apache 2.0 on Solaris. This has been fixed.
If you run VSPLIT on archives stored on the File Server, and the archives contain an AccessList at the time of the split, attempts to retrieve revisions from the archives will fail. This has been fixed.
When you use Version Manager Server 7.5.1.0 on Windows with a client on Solaris, the execuatlable bits of a read-only workfile are lost after a check-in. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
UNIX: Any attempt to start the Version Manager web server with daemons enabled produces an error.
This has been fixed.
When a sufficiently large promotion model is being edited in the desktop client, it gets deleted from the CFG file. This has been fixed.
This has been fixed.
When not utilizing File Server, Version Manager should recognize a split archive and display a useful message stating that the archive is split and must be referenced through a file server. This has been implemented.
Changes made to web.xml are not read until the server is restarted, and may cause incorrect operation of the server. This has been fixed.
Licenses allocated to Version Manager web-client user sessions are never returned to the license pool; the license should be returned to the pool five minutes after the user logs out from the web client.
This has been fixed.
The client appears to work but applet operations fail. This has been fixed.
When the customer performs simultaneous Show History operations on multiple PDBs (in multiple browser windows), Version Manager hangs. This has been fixed.
This has been fixed.
On a multiple-file check-in or add, the Use Change Description for all check box is not selected by default. This has been fixed.
If you set up a post-put event trigger, configure the PDB to remove the lock on an unchanged file, check out a file without changing it, check in the file with "Prompt" selected for unchanged workfiles and with "Keep read-only workfile" selected, and reply "no" when asked if you want to check in an unchanged file, an event trigger fires even though no check-in occurred. This has been fixed.
This has been fixed.
If you perform an action that results in an error in the desktop client, the Details window takes about five seconds to auto-expand. This has been fixed.
The documentation for the pcli list -ca command contains errors (:= should be =). This has been fixed.
If the selected workfile location does not match the project's default location, selecting "Don't check in workfile" changes the default workfile location. This has been fixed.
The comma should remain the default delimiter. This has been fixed.
The PCLI manual contains references to PCLI PR and PCLI ID (without the underscore). This has been fixed.
In the Add Workfiles dialog box, clicking the Browse button sometimes displays a path with an extra \*.*. This has been fixed.
This has been fixed.
When checking if the allusers.ser data in memory is out of date compared with the persistent data, the code looks for the file in the wrong directory. This has been fixed.
If you modify an existing user to have an expiration date of today (or any date before today), a blank dialog box appears and cannot be dismissed except through the Windows Task Manager. This has been fixed.
The IsDifferent command always performs the comparison against the tip rather than the default revision. This has been fixed.
When you enter a new user name in the Switch User dialog box, the user name in the status bar is sometimes repainted incorrectly. This has been fixed.
The -v option should be treated as a label and accept numeric characters without requiring escape characters. This has been fixed.
This has been fixed.
This has been fixed.
The PCLI commands ImportArchives and AddFiles do not observe the Run options -y, -n and -np. Instead of accepting the Yes, No, and No Prompt options being passed through Run, the functions still pass the question to the user.
This has been fixed.
This has been fixed.
If you try to update an ACD file (for example, add a user) and the ACD file is flagged by the operating system as being in use (for example, because another process is reading the file), the ACD file is deleted and must be restored from backup. This has been fixed.
During import, , a corrupt archive will generate the error "Unexpected error: java.lang.NullPointerException" and halt the process. This has been fixed.
This has been fixed.
On a branch, checking in a file creates a new revision even with a "remove lock if unchanged" option selected ("Don't check in" or "Prompt" when the file is unchanged). This has been fixed.
This has been fixed.
You can no longer highlight a project by selecting the Project Database root on the left side (Project Pane) and then typing the first letter of the project you want to work on. This has been fixed.
"Show Journal" doesn't display the proper journal information when the "Date Range" is set from the morning of the current day to the night of current day, even though actions have taken place on the versioned file during the current day. This has been fixed.
If you run two exports within a few seconds of each other, duplicate IDs can occur. This should be avoided, and a note has been added to the documentation.
When archive operations are performed between midnight and 1:00 AM during Daylight Savings Time, the date incorrectly specifies the previous day. This has been fixed.
This has been fixed.
The -a option of the Readline command should be able to assign the individual words in a line of input to elements of an array; however, all words are placed into the first array element. This has been fixed.
The Version Manager product link is out of date in the installation guide. This has been fixed.
When you edit a large promotion model in the desktop client, the model gets deleted from the configuration file. This has been fixed.
The installation does not allow you to select a Program Folder for all users on the machine; it lets you select a Program Folder only for the current user. This has been fixed.
When you access a project database through a file server, the journal files do not get created or updated with your last action. This has been fixed.
The vtransfer command option -f to fix a RevLib path does not work. This has been fixed.
When accessing a project database through a file server, you may get lock errors after attempting to check in files. This has been fixed.
In the desktop client and web client, long label names are not allowed to fill up the available space in the Filter Selection list, and so get unnecessarily truncated. This has been fixed.
This has been fixed.
For Eclipse-based IDEs, the Serena menu and the source-control glyphs are not enabled by default. The information is saved in the user workspace, so you have to enable the menu and glyphs for each new workspace you create. This has been fixed.
When the TD plug-in is installed, it should create the following registry key:
HKEY_LOCAL_MACHINE->SOFTWARE->Mercury Interactive->Version Manager->Test Type
The value of the string should contain the test types for TD, separated by commas.
This has been fixed.
An "Unable to get file" error occurs during a Get that includes Get latest version of... or Refresh Project View. This has been fixed.
In the desktop client and web client, long label names are not allowed to fill up the available space in the Filter Selection list, and so get unnecessarily truncated. This has been fixed.
On a multiple-file check-in or add, the Use Change Description for all check box is not selected by default. This has been fixed.
This has been fixed.
You do not receive a prompt to enter different passwords to enter subprojects with a different password for the same User ID. This has been fixed.
On check-in of an unmodified workfile, the "modified" date is changed if an UnconditionalPrePut event trigger is defined for that project. This has been fixed.
This has been fixed.
If you are using a Netscape browser and you resize the results window during a checkout, the action is aborted and the results information is lost. This has been fixed.
The VMINET.HTML page, the vminet_install.html page, and the sample project database servlet page come up blank when you try to access them in your web browser. This has been fixed.
End Release Notes
Copyright © 2003–2017 Serena Software, Inc. All rights reserved.