• Support for Windows 10
• Support for Visual Studio 2013 (UC) and 2015 (RC)
• Usability improvements for Eclipse RIDE and Visual Studio RIDE
• United Windows installer for Japanese and English VM versions
• Numerous defect fixes (see list below)

• To use the newly added Visual Studio Rich IDE (RIDE) integrations with VS 2013 or VS 2015, it is necessary to have some RIDE component installed in the VM 8.5.0.0 base release. If your system only contains VS 2013 and/or VS 2015, the 8.5.0.0 installer will not have offered this as a choice for Visual Studio because it could not recognize these newer VS releases.
  
  To solve this problem, please select the component Plugin for Eclipse 3 (rich integration) during the installation of VM 8.5.0.0, which can be installed regardless of whether or not Eclipse is installed on your system. If you do not have Eclipse installed, just press Next when the Eclipse Installation dialog comes up.
 
• Versions of the 8.5.3 Windows installer downloaded prior to August 6th 2015 mistakenly removed the Eclipse RIDE integration if it was installed on top of VM 8.5.2. (It worked fine when installed on top of VM 8.5.0.) The installer has been modified to correct this error.
  
  Old vm8530w32.exe:

• After installing this patch on a server, please also install the patches VM 8.5.3 Patch 004 and VM 8.5.3 DEF307915.

1.0 Defects Fixed in Version Manager 8.5.3.0

1.1 Desktop Client, CLI, File Server, and PCLI Defects Fixed

1.1.1 File Server vtransfer utility lets users delete or move files, ignoring the "enable utilities" configuration [DEF252641]

This has been fixed.

1.1.2 United Windows installer for Japanese and English VM versions [ENH262987, DEF266672, DEF266372]

Version Manager now has a single installer that detects a Japanese Windows environment and will suggest installing additional localization support.

1.1.3 Desktop Client no longer supports right-click context menu to copy and paste label names (Windows specific) [DEF258878]

This has been fixed.

1.1.4 Making changes in FS Admin causes manually created backup files of server-config.wsdd to be deleted [DEF265030]

This has been fixed.

1.1.5 Empty "pvcsldap.ini" file is created for some cases [DEF265634]

This has been fixed.

1.1.6 vmprofile and vmcshrc display "Must be attached to terminal for 'am I' option" errors from processes without a tty [DEF265981]

This has been fixed.

1.1.7 VCSDIR directive not updated when PDB is copied via Desktop Client. [DEF249135]

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.

1.1.8 Japanese localized version of PvcsMerge Tool is absent. [DEF257622]

A localized version of PvcsMerge was absent from VM 8.5.1 Japanese.
This has been fixed.

1.1.9 Include the locktime in the vlog output [ENH268520] Δ

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.

1.1.10 Update JRE to latest 7u80 version [ENH267886]

Built-in JRE version was upgraded to latest (and last) JRE in 7 line.

1.1.11 Version Manager Service vulnerability: Admin Tool (VPADMIN) should create Windows Service with quoted path to EXE [DEF254142]

This has been fixed.

1.1.12 Local IP address for connection from client on server not always recognized [DEF266043, DEF237838]

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.

1.1.13 Version Manager on Solaris adversely affected by incompatible Java directories in LD_LIBRARY_PATH [DEF262295]

This has been fixed.

1.1.14 VTRANSFER rename command (-r) can delete files from directory when a trailing path separator is used [DEF265309]

This has been fixed.

1.1.15 vtransfer -c -z (copy directory) and vtransfer -r -z (rename / move directory) do not retain directories with no files [DEF234926]

This has been fixed.

1.1.16 Expose hidden options of the PCLI AddFiles command [ENH238425]

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).

1.1.17 Desktop Client: Diff/Merge tools can not be changed. [DEF232742]

This has been fixed.

1.1.18 Can no longer access 5.3/6.0 project domains as of Version Manager 8.4.6 Combo Hotfix 1 [DEF267529]

This has been fixed.

1.1.19 Using VTRANSFER utility to rename a split archive on an older File Server leaves non-functional archive [DEF264542]

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.

1.1.20 Show History, pcli vlog -l and vlog -l output show multiple copies of the same revision when it contains multiple locks [DEF265753]

This has been fixed.

1.1.21 Desktop Client/PCLI crashes on Linux when using VCSID login source if HOST does not yield a username [DEF263762]

This has been fixed.

1.2 IDE Client Defects Fixed

1.2.1 Version Manager integration with Visual Studio 2013 [ENH257170, DEF267613, DEF264501]

Support for Visual Studio 2013 was added.

1.2.2 Version Manager integration with Visual Studio 2015 [ENH263118, DEF263781, DEF263801, DEF264634, ENH264376, DEF267613, DEF264501]

Support for Visual Studio 2015 was added.

1.2.3 Visual Studio RIDE: after binding operation, Visual Studio intermittently crashed. [DEF241216]

This has been fixed.

1.2.4 Visual Studio RIDE: Server Account used for Login Source HOSTID with Server-Side Processing enabled [DEF232705]

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.

1.2.5 Visual Studio RIDE: Don't make workfiles read-only if Make writable is enabled [DEF263226, ENH263934, DEF263467] Δ

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.'

1.2.6 Visual Studio RIDE: Don't make project files read-only [DEF263225, DEF264634] Δ

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.

1.2.7 Visual Studio RIDE: 'Output' is empty in the application. [DEF236053]

This has been fixed.

1.2.8 Eclipse Juno/Luna RIDE: 'Activated Issue' are is hanging in Eclipse. [DEF244677]

This has been fixed.

1.2.9 Visual Studio 2008 Japanese Edition RIDE: 'Change Binding' option is missing. [DEF265821]

This has been fixed.

1.2.10 Visual Studio RIDE: Visual Studio Japanese Edition localization for RIDE plugin is broken. [DEF265790]

This has been fixed.

1.2.11 Eclipse RIDE: plugin warning message for local file deletion. [ENH243154]

New prompt alerts user if a local file is about to be deleted to protect against accidental file deletion.

1.2.12 Eclipse RIDE: Plugin doesn't see outgoing changes if new folder was created. [DEF253142]

This has been fixed.

1.2.13 Eclipse RIDE: Conflicts cannot be resolved when comparing workspace. [DEF256820]

This has been fixed.

1.2.14 Visual Studio RIDE: AppServer-.Net: ERROR "BEEP" on opening the project in migration wizard. [DEF197329]

This has been fixed.

1.2.15 Eclipse Ride: "Apply to all..." action works incorrectly if selected for one file. [DEF268583]

This has been fixed.

1.2.16 Eclipse RIDE: Check in action works incorrectly after Cancel action. [DEF268426]

This has been fixed.

1.2.17 Eclipse RIDE: Server Account used for Login Source HOSTID with Server-Side Processing enabled [DEF266897]

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.

1.3 Web Client Defects Fixed

1.3.1 Web Client on Solaris sometimes fails to load because it mistakenly detects a 32-bit JRE as 64-bit [DEF250342]

This has been fixed.

1.3.2 Web Client throws exception when viewing revisions of files renamed in the Deskop Client GUI [DEF264729]

This has been fixed.

1.3.3 Web Client dialog content should be stretched to available space [ENH245079, DEF264806]

The contents for several dialogs didn't fit into their allotted space and were inconvenient to read.
This has been fixed.

1.3.4 Web client shows wrong path (in vm\inet\temp\pvcs) for client-side related error messages [DEF179189]

This has been fixed.

1.3.5 Web client Show Differences dialog: enter revision fields manually [ENH226246]

Users can now also manually input revision information without having to use an additional selection window.

1.3.6 Web client only shows "This browser has no Java Runtime Environment (JRE)" when the browser is blocking Java [DEF267153, ENH268623]

A new message was added to hint at the various root causes for the message.

1.3.7 Better cross browser support for web client [DEF265383]

This has been fixed.

1.3.8 Web client shows incorrect error message re-adding an existing versioned file where the archive is gone [DEF263563]

This has been fixed.

• Windows:
   
  1. Make sure the installed Version Manager release is either 8.5.0.0, 8.5.0.1, 8.5.1.0 or 8.5.2.0. This patch should not be deployed on any other VM release.
     
     
  2. Shut down all Version Manager applications using the installation being patched. This includes the Serena VM Web Application Server (File Server / VM I-Net / WebDAV), all workstations using a network installation and any IDE that has been integrated with Version Manager.
     
     Users of SCC-based IDEs should make sure the PCLIOutProc.exe process has shut down to avoid having to reboot their Operating System after installing the patch. If this process is still running after the SCC-based IDE has been closed (it can linger for up to 10 minutes), use Task Manager to kill the process.
      
  3. If the Serena VM Web Application Server is running as a Windows Service and you are running VM 8.5.0.x or 8.5.1.0, that service should be removed as it will not be compatible with the 8.5.3.0 configuration. Removing the service is not required if you are running VM 8.5.2.0, though you will not get the fix for defect DEF254142 if you don't.
     
     Prior to removing the service, it is advisable to check if the current service has been modified from its default so similar changes can be made after the new service has been installed.
     
     - Check as which UserID the VM Web Application Server service is running. This can be done from Settings / Control Panel, Administrative Tools, Services. Look up the Serena VM Web Application Server and check the Log On As setting. Write down the UserID being used if this is something other than the default value Local System Account.
     
     - Check if the Min/Max Java Heapsize parameters were changed. Do this by running regedit and opening the key  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serena VM Web Application Server\Parameters. In the Data column, look for the values -Xms... and -Xmx... and write them down if they are different from the default ones, which are -Xms64m and -Xmx512m. There is no need to write down values that are lower than the default ones.
     
     After checking for modified values, the existing service can be removed by running the Version Manager Application Server Admin utility (a.k.a. VPADMIN.EXE) and pressing the Remove NT Service button.
      
  4. Login to the system as a user with sufficient privileges to update the 8.5.0 installation files. Ideally this is the same user who installed VM 8.5.0.
      
  5. Download the file vm8530w32.exe and execute it to launch the installer.
      
  6. If the Apache Tomcat configuration file server.xml in your current VM installation contains manual edits, the installer will show a message similar to:
      
     
     
     In order to preserve your changes, they will have to be reapplied to the new server.xml file. To aid in this process, the directory VM_Install_Dir\vm\common\tomcat\conf that holds the server.xml file also contains a copy of the old, manually changed file (server.xml.bak_8500).
     
     A copy of the original server.xml files that were shipped with prior 8.5.x releases will be saved as server.xml.org_8500, server.xml.org_8510 and server.xml.org_8520 respectively. You can run a vdiff command on the .bak file and the .org file for the previously installed VM release to see which changes were made, and implement similar changes in the new server.xml file.

     
     Example:
     
     C:\Program Files (x86)\Serena\vm\common\tomcat\conf>vdiff server.xml.org_8520 server.xml.bak_8530
Serena PVCS Version Manager (vdiff) v8.5.3.0 (Build 071) for Windows NT/80x86
Copyright (C) 1985-2015 Serena Software. All rights reserved.
   server.xml.org_8520 (06 Aug 2014 01:14:04)
           server.xml.bak_8530 (24 Jun 2015 16:55:52)
===================
      68      68  |         Define a non-SSL HTTP/1.1 Connector on port 8080
      69      69  |    -->
+             70  |    <Connector port="8180" protocol="HTTP/1.1"
-     70          |    <Connector port="8080" protocol="HTTP/1.1"
      71      71  |               maxThreads="150" minSpareThreads="25"
      72      72  |           enableLookups="false" redirectPort="8443" acceptCount="100"
===================
      80      80  |               redirectPort="8443" />
      81      81  |    -->
+             82  |    <Connector port="8190"
-     82          |    <Connector port="8090"
      83      83  |               maxThreads="150" minSpareThreads="25"
      84      84  |               enableLookups="false" redirectPort="8443" acceptCount="100"
=================== 

     Note: the file server.xml.bak_8530 only exist if the installer detected a manually modified server.xml file.
     
     After applying these changes to the new server.xml file (and preserving the server.xml file installed by 8.5.3.0 as server.xml.org), vdiff shows:
     
     Serena PVCS Version Manager (vdiff) v8.5.3.0 (Build 071) for Windows NT/80x86
Copyright (C) 1985-2015 Serena Software. All rights reserved.
   server.xml.org (01 Jun 2015 12:58:14)
           server.xml (25 Jun 2015 13:33:28)
===================
      69      69  |         Define a non-SSL HTTP/1.1 Connector on port 8080
      70      70  |    -->
+             71  |    <Connector port="8081" protocol="HTTP/1.1"
-     71          |    <Connector port="8080" protocol="HTTP/1.1"
      72      72  |               maxThreads="150" minSpareThreads="25"
      73      73  |           enableLookups="false" redirectPort="8443" acceptCount="100"
===================
      81      81  |               redirectPort="8443" />
      82      82  |    -->
+             83  |    <Connector port="8091"
-     83          |    <Connector port="8090"
      84      84  |               maxThreads="150" minSpareThreads="25"
      85      85  |               enableLookups="false" redirectPort="8443" acceptCount="100"
===================
      
  7. If the service had to be removed in step 3, re-launch the Version Manager Application Server Admin utility and press the Install NT Service button.
     
     If the old service was using a specific Log On As user and/or had a modified Min/Max Java Heap Size, reapply those changes using the information obtained during step 3.
      
  8. If the Serena VM Web Application Server was configured so VM I-Net Web Client users can access it via the Microsoft IIS Server, use the same Version Manager Application Server Admin utility to rewrite the servlets.
     
     Do this by going to the Servlets tab, selecting a single servlet and then clicking Modify, Save and Apply.
      
  9. Restart Version Manager.
      
• Linux/UNIX:
  
  
  1. Make sure the installed Version Manager release is either 8.5.0.0, 8.5.0.1, 8.5.1.0 or 8.5.2.0. This patch should not be deployed on any other VM release.
     
     
  2. Shut down all Version Manager applications. This includes the Serena VM Web Application Server (File Server / VM I-Net / WebDAV), all workstations using a network installation and any IDE that has been integrated with Version Manager.
      
  3. Login to the system as a user with sufficient privileges to update the 8.5.0 installation files. Unless setuid mode has been turned off in the 8.5.0 installation, this should be the same user that installed VM 8.5.0.
      
  4. Download the file vm8530_en_unixpatch.tar, untar the file into an empty temporary directory, and execute ./vminst to launch the installer.
      
  5. If the Apache Tomcat configuration file server.xml in your current VM installation contains manual edits, the installer will show a message similar to:
     
               -> Existing server.xml has been modified. Hence, it has been renamed and kept in /usr/serena/vm/common/tomcat/conf/server.xml.bak_8530 by installer.
     
     In order to preserve your changes, they will have to be reapplied to the new server.xml file. To aid in this process, the directory VM_Install_Dir/vm/common/tomcat/conf) that holds the server.xml file also contains a copy of the old, manually changed file (server.xml.bak_8500).
     
     A copy of the original server.xml files that were shipped with prior 8.5.x releases will be saved as server.xml.org_8500 and server.xml.org_8520 respectively. You can run a vdiff command on the .bak file and the .org file for the previously installed VM release to see which changes were made, and implement similar changes in the new server.xml file.
     

     
     Example:
     
     Serena PVCS Version Manager (vdiff) v8.5.3.0 (Build 071) for Linux/80x86
Copyright (C) 1985-2015 Serena Software. All rights reserved.
   server.xml.org_8520 (06 Aug 2014 01:14:04)
           server.xml.bak_8530 (25 Jun 2015 13:51:34)
===================
      68      68  |         Define a non-SSL HTTP/1.1 Connector on port 8080
      69      69  |    -->
+             70  |    <Connector port="8180" protocol="HTTP/1.1"
-     70          |    <Connector port="8080" protocol="HTTP/1.1"
      71      71  |               maxThreads="150" minSpareThreads="25"
      72      72  |           enableLookups="false" redirectPort="8443" acceptCount="100"
===================
      80      80  |               redirectPort="8443" />
      81      81  |    -->
+             82  |    <Connector port="8190"
-     82          |    <Connector port="8090"
      83      83  |               maxThreads="150" minSpareThreads="25"
      84      84  |               enableLookups="false" redirectPort="8443" acceptCount="100"
===================


     
     Note: the file server.xml.bak_8530 only exist if the installer detected a manually modified server.xml file.

     
     After applying these changes to the new server.xml file (and preserving the server.xml file installed by 8.5.3.0 as server.xml.org), vdiff shows:
     
     Serena PVCS Version Manager (vdiff) v8.5.3.0 (Build 071) for Linux/80x86
Copyright (C) 1985-2015 Serena Software. All rights reserved.
   server.xml.org (01 Jun 2015 12:58:14)
           server.xml (25 Jun 2015 14:00:16)
===================
      69      69  |         Define a non-SSL HTTP/1.1 Connector on port 8080
      70      70  |    -->
+             71  |    <Connector port="8180" protocol="HTTP/1.1"
-     71          |    <Connector port="8080" protocol="HTTP/1.1"
      72      72  |               maxThreads="150" minSpareThreads="25"
      73      73  |           enableLookups="false" redirectPort="8443" acceptCount="100"
===================
      81      81  |               redirectPort="8443" />
      82      82  |    -->
+             83  |    <Connector port="8190"
-     83          |    <Connector port="8090"
      84      84  |               maxThreads="150" minSpareThreads="25"
      85      85  |               enableLookups="false" redirectPort="8443" acceptCount="100"
===================
      
  6. Restart Version Manager.
      

• Windows:
  
  
  1. Shut down all Version Manager applications. This includes the VM Web Application Server (File Server / VM I-Net / WebDAV) and all workstations using a network installation.
      
  2. If the system is running the Serena VM Web Application Server as a Windows Service then the service should be removed as it will not be compatible with the configuration used by VM release 8.5.0.x.
     
     Prior to removing the service, it is advisable to check if the current service has been modified from its default so similar changes can be made after the new service has been installed.
     
     - Check as which UserID the VM Web Application Server service is running. This can be done from Settings / Control Panel, Administrative Tools, Services. Look up the Serena VM Web Application Server and check the Log On As setting. Write down the UserID being used if this is something other than the default value Local System Account.
     
     - Check if the Min/Max Java Heapsize parameters were changed. Do this by running regedit and opening the key  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serena VM Web Application Server\Parameters. In the Data column, look for the values -Xms... and -Xmx... and write them down if they are different from the default ones, which are -Xms64m and -Xmx512m. There is no need to write down values that are lower than the default ones.
     
     After checking for modified values, the existing service can be removed by running the Version Manager Application Server Admin utility (a.k.a. VPADMIN.EXE) and pressing the Remove NT Service button.
      
  3. Login to the system as a user with sufficient privileges to update the 8.5.3.0 installation files. Ideally this is the same user who installed VM 8.5.3.0.
      
  4. Go to Add/Remove programs and uninstall Serena PVCS Version Manager 8.5.3. This will roll back the patch by putting the preserved files from the previously installed 8.5.0.x release back in place.
      
  5. If the service had to be removed in step 2, re-launch the Version Manager Application Server Admin utility and press the Install NT Service button.
     
     If the old service was using a specific Log On As user and/or had a modified Min/Max Java Heap Size, reapply those changes.
      
  6. After the patch rollback has completed, restart Version Manager.
      
• Linux/UNIX:
  
  
  1. Shut down all Version Manager applications. This includes the VM Web Application Server (File Server / VM I-Net / WebDAV) and all workstations using a network installation.
      
  2. Login to the system as a user with sufficient privileges to update the 8.5.2.0 installation files. Unless setuid mode has been turned off in the 8.5.0 installation, this should be the same user that installed VM 8.5.2.0.

      
  3. Go to the directory VM_Install_Dir/patch_backout and execute ./VM8.5.3.0_backout.sh to launch the uninstaller. This will roll back the patch by putting the preserved files from the previously installed 8.5.x release back in place.
      
  4. After the patch rollback has completed, restart Version Manager.