Serena PVCS Version Manager Release Notes

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.

1.0 Defects Fixed in Version Manager 8.2.0.0

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

1.2 IDE Client Defects Fixed

1.3 Version Manager Web Client Defects Fixed

2.0 Defects Fixed in Version Manager 8.1.4.2

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

2.2 IDE Client Defects Fixed

2.3 Version Manager Web Client Defects Fixed

2.4 Serena Builder Defects Fixed

2.5 vss2vm Converter Defects Fixed

3.0 Defects Fixed in Version Manager 8.1.4.1

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

3.2 IDE Client Defects Fixed

3.3 Version Manager Web Client Defects Fixed

4.0 Defects Fixed in Version Manager 8.1.4.0

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

4.2 IDE Client Defects Fixed

4.3 Version Manager Web Client Defects Fixed

5.0 Defects Fixed in Version Manager 8.1.3.2

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

5.2 IDE Client Defects Fixed

6.0 Defects Fixed in Version Manager 8.1.3.1

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

6.2 Version Manager Web Client Defects Fixed

7.0 Defects Fixed in Version Manager 8.1.3

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

7.2 IDE Client Defects Fixed

7.3 Version Manager Web Client Defects Fixed

8.0 Defects Fixed in Version Manager 8.1.2.2

8.1 Old Files will Remain in Patch Directory

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

8.3 IDE Client Defects Fixed

8.4 Version Manager Web Client Defects Fixed

9.0 Defects Fixed in Version Manager 8.1.2

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

9.2 IDE Client Defects Fixed

9.3 Version Manager Web Client Defects Fixed

9.4 Meritage Defects Fixed

10.0 Defects Fixed in Version Manager 8.1.1.3

10.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

11.0 Defects Fixed in Version Manager 8.1.1.2

11.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

12.0 Defects Fixed in Version Manager 8.1.1

12.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

12.2 IDE Client Defects Fixed

12.3 Version Manager Web Client Defects Fixed

13.0 Defects Fixed in Version Manager 8.1.0

13.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

13.2 IDE Client Defects Fixed

13.3 Version Manager Web Client Defects Fixed

14.0 Defects Fixed in Version Manager 8.0.2.6

14.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

14.2 IDE Client Defects Fixed

14.3 Version Manager Web Client Defects Fixed

15.0 Defects Fixed in Version Manager 8.0.2.5

15.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

15.2 Version Manager Web Client Defects Fixed

16.0 Defects Fixed in Version Manager 8.0.2.4

16.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

17.0 Defects Fixed in Version Manager 8.0.2.3

17.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

17.2 Version Manager Web Client Defects Fixed

18.0 Defects Fixed in Version Manager 8.0.2.2

18.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

19.0 Defects Fixed in Version Manager 8.0.2.1

19.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

20.0 Defects Fixed in Version Manager 8.0.2.0

20.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

20.2 IDE Client Defects Fixed

20.3 Version Manager Web Client Defects Fixed

21.0 Defects Fixed in Version Manager 8.0.0.9

21.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

21.2 IDE Client Defects Fixed

21.3 Version Manager Web Client Defects Fixed

22.0 Defects Fixed in Version Manager 8.0.0.8

22.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

22.2 IDE Client Defects Fixed

22.3 Version Manager Web Client Defects Fixed

23.0 Defects Fixed in Version Manager 8.0.0.7

23.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

24.0 Defects Fixed in Version Manager 8.0.0.6

24.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

24.2 Version Manager Web Client Defects Fixed

25.0 Defects Fixed in Version Manager 8.0.0.5

25.1 IDE Client Defects Fixed

26.0 Defects Fixed in Version Manager 8.0.0.4

26.1 Version Manager Web Client Defects Fixed

27.0 Defects Fixed in Version Manager 8.0.0.3

27.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

27.2 IDE Client Defects Fixed

27.3 Version Manager Web Client Defects Fixed

28.0 Defects Fixed in Version Manager 8.0.0.2

28.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

28.2 Version Manager Web Client Defects Fixed

29.0 Defects Fixed in Version Manager 8.0.0.1

29.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

29.2 Version Manager Web Client Defects Fixed

30.0 Defects Fixed in Version Manager 8.0.0.0

30.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

30.2 IDE Client Defects Fixed

30.3 Version Manager Web Client Defects Fixed

31.0 Defects Fixed in Version Manager 7.5.2.2

31.1 Development Interface Defects Fixed

32.0 Defects Fixed in Version Manager 7.5.2.1

32.1 GUI, CLI, PCLI, and DTK Defects Fixed

32.2 Development Interface Defects Fixed

33.0 Defects Fixed in Version Manager 7.5.2.0

34.0 Defects Fixed in Version Manager 7.5.1.5

34.1 GUI, CLI, PCLI, and DTK Defects Fixed

35.0 Defects Fixed in Version Manager 7.5.1.4

35.1 GUI, CLI, PCLI, and DTK Defects Fixed

36.0 Defects Fixed in Version Manager 7.5.1.3

36.1 Version Manager Defects Fixed

36.2 Development Interface Defects Fixed

37.0 Defects Fixed in Version Manager 7.5.1.2

37.1 Version Manager GUI, CLI, PCLI, and DTK Defects Fixed

37.2 Development Interface Defects Fixed

37.3 VM I-Net Defects Fixed

38.0 Defects Fixed in Version Manager 7.5.1.0

38.1 Version Manager GUI, CLI, PCLI, and DTK Defects Fixed

38.2 VM I-Net Defects Fixed

39.0 Defects Fixed in Version Manager 7.5.0.1

40.0 Defects Fixed in Version Manager 7.5.0.0

40.1 Version Manager GUI, CLI, PCLI, and DTK Defects Fixed

40.2 Development Interface Defects Fixed

40.3 VM I-Net Defects Fixed

1.0 Defects Fixed in Version Manager 8.2.0.0

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

1.1.1 Access Control List: Unable to Remove if Maximum Size Has Been Reached [DEF123143]

1.1.2 "After Check In" Options Override Configuration Settings [DEF38782] Δ

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.

1.1.3 AIX: PVCS_LDAP_DEBUG Does not Work [DEF115565]

1.1.4 Cannot Add or Remove Floating Labels on a Branch if the Trunk Revision Number Is >= 1.2560 [DEF72045]

1.1.5 CLI: ident: Does Not Work with File Server Path Maps [DEF79960]

1.1.6 CLI: vjournal: New Option to Specify File Delimiter Character [DEF123285] Δ

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

1.1.7 CLI: VMRG: -b Produces Garbled Output [DEF31733] Δ

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.

1.1.8 CLI: vsplit: Crashes if Directory Not Writable [DEF105128]

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.

1.1.9 CLI: vtransfer: Add Ability to Recursively Delete a Directory of Archives [ENH146175] Δ

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.

1.1.10 CLI: vtransfer: -c (Copy a File or Directory of Files) Option Does Not Work for Unsplit Archives [DEF111921]

1.1.11 CLI: vtransfer: : No Log File Available for Renamed or Archived Journal Files [ENH112202]

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.

1.1.12 CLI: vtransfer: -r -z Results in Recursive Delete [DEF143164]

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.

1.1.13 CLI: vtransfer: -i Option Does Not Always Update Split Archive Location [DEF81586]

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.

1.1.14 CLI: vtransfer: -m, -xo, and -xe Options Not Working [DEF113377; DEF146174]

1.1.15 CLI: vtransfer: -c, -i, and -r Should Prompt to Overwrite Existing Files [ENH130091] Δ

BEHAVIOR CHANGE: The vtransfer command options -c, -i, and -r now prompt to overwrite if the file already exists.

1.1.16 CLI: vtransfer: Fails if -id Option Comes after -x Option [DEF76080]

1.1.17 CLI: Wildcard Get May Fail [DEF31107]

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.

1.1.18 Clients Crash if File Server Has more than 50 Path Maps [DEF143935; DEF137890]

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.

1.1.19 Copy/Import Archives: "Error, Unsupported JNI RevLib operation" [DEF99170]

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.

1.1.20 Create Project Database: Cannot Type Path to Configuration File or Access Control File [DEF30638]

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.

1.1.21 Create Project Privilege: Possible to Create Project Without It [DEF27772]

In some circumstances it was possible for a user without the Create Project privilege to create a project. This has been fixed.

1.1.22 Default Version Label Not Assigned when Add New Workfile [DEF72109] Δ

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.

1.1.23 Desktop Client: "Actions | Show Journal" May Not Work on File Server [DEF129851]

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.

1.1.24 Desktop Client: Add Workfile Operation May Fail if "Don't Check in workfile" Is Selected [DEF124190]

1.1.25 Desktop Client: Advanced Filter Can Result in 100% CPU Usage [DEF104395]

In certain circumstances, the advanced filter can result in 100% CPU usage.
This has been fixed.

1.1.26 Desktop Client: Double-Clicking Does Not Open View/Edit from Version Labels or Promotion Groups Panes [DEF28901]

1.1.27 Desktop Client May Not Refresh Workspace Information [DEF133170]

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.

1.1.28 Desktop Client: Position of Horizontal and Vertical Separators May Not Be Retained Between Sessions [DEF31277]

1.1.29 Desktop Client: Project Tree Should Automatically Scroll to Keep Expanded Project in View [ENH78635]

1.1.30 Desktop Client: Sorting by "Date" Is Not Refreshed after Check In [DEF71525; DEF37378]

This has been fixed. Performing a Refresh or changing the column sort order now correctly sorts on the updated Check In dates.

1.1.31 Desktop Client: Sorting by "Locked By" Is Not Refreshed after Check Out [DEF100302]

This has been fixed. Performing a Refresh or changing the column sort order now correctly sorts on the updated Locked By users.

1.1.32 Desktop Client: Unable to Retain Saved information in "Configure Project" and "Semaphore" Windows [DEF147619]

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.

1.1.33 File Server: May Unnecessarily Search the Network for UNC Paths, Causing Delays [DEF133908]

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.

1.1.34 File Server: Must Restart in Order to Re-Add a File to Source Control [DEF112442]

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.

1.1.35 File Server: "refresh now" Does Not Remove Deleted Project Databases from Cache [DEF102492]

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.

1.1.36 History Report: Line Counting Statistics Not Displayed Correctly [DEF29978]

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

1.1.37 Internal Error 4 if a Privilege Set Name Contains a Dash (-) Character [DEF39256]

1.1.38 Journal Report: New Option to Include Non-Locking Gets [ENH87218] Δ

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.

1.1.39 JRE, 1.6.0 Update 10: VM I-Net has problems with the "Recursive" operations [DEF151870]

1.1.40 Memory Errors Caused by Certain Archive Suffix Directives [DEF137714]

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.

1.1.41 Merge Tool on UNIX: Cannot Tell which Revision/File Is in which Pane [DEF27987]

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.

1.1.42 Merge and Diff Tool Limitations [ENH80752; ENH19150, and 36 others] Δ

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.

1.1.43 Need support for Version Manager on HP-UX with Itanium CPU architecture [ENH75417]

This has been fixed. Version Manager is now supported for Client platforms using the HP-UX Aries PA-RISC emulator.

1.1.44 PCLI: A Warning Message Must Be Displayed in Version Manager Desktop If LDAPINFOFILE Directive is Wrongly Configured [DEF75227]

1.1.45 PCLI Allows Creation of Version Labels Containing Illegal Colon Character (:) [DEF37875] Δ

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.

1.1.46 PCLI: Commands Send Output to StdErr Rather than StdOut [DEF90937] Δ

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.

1.1.47 PCLI: Delete Command Gives Exception if Try to Delete Root [DEF87807]

1.1.48 PCLI: ImportPdb Command Fails if File Name Contains Equals Sign (=) Character [DEF78914]

1.1.49 PCLI: ImportPdb Command Fails if Worksapce Name Ends with a Blank Space ( ) Character [DEF76503]

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.

1.1.50 PCLI: ImportPDB Command Fails on Large Project Databases [DEF39833]

1.1.51 PCLI: IsDifferent Command Fails with Floating Default Versions [DEF86630]

1.1.52 PCLI: Licensing (EVENTTOKEN) Does Not Work Correctly [DEF129400]

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

1.1.53 PCLI: List Command: Add Ability to Output to XML [ENH109377] Δ

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.

1.1.54 PCLI: ListRevision Command: Add Ability to Climb Promotion Model [ENH73478] Δ

BEHAVIOR CHANGE: The -g option will now climb the promotion model if used with the new -c option.

1.1.55 PCLI: test -I Command Must Accept< <= > and >= Values [ENH147394]

Test -i Command works for = and != comparisons. When you enter the command using < <= > or >=, the -i option is ignored. This has been fixed.

1.1.56 PCLI: Label Command needs to show Entity Path and Revision Output [ENH139259]

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.

1.1.57 PCLI: No Way to Set Default Workspace [DEF38921] Δ

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.

1.1.58 PCLI: Poor Syntax Error Reporting [DEF30605]

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.

1.1.59 PCLI Vdel Command with -v< label>* Option Results in ERROR: String index out of range [DEF114693]

This has been fixed. You can now use -v< label>* to delete all revisions between the specified label and the tip.

1.1.60 PCLI: ImportPDB Command Fails if Workspace Name Contains a Colon (:) [DEF79339]

1.1.61 PCLI: ImportPDB Command Fails in Script if Same Project Name Exists in Multiple Project Databases [DEF41346]

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.

1.1.62 PCLI: Run: -xe and -ae Options Not Working Correctly [DEF31875]

1.1.63 PCLI: SetWorkfileLocation Command Required Modify Project Privilege to Update Workfile Location in Private Workspace [DEF40962]

This has been fixed. Users can now update the workfile location in their private workspaces without having the Modify Project Privilege.

1.1.64 PCLI: Script Error: [Warning] Timeout waiting for path "Path\change.log" [DEF104822]

Running several PCLI scripts in parallel may result in contention for write access to the change.log file.
This has been fixed.

1.1.65 PowerBuilder 11: Version Manager Must support for PowerBuilder 11 [ENH129799]

1.1.66 Red Hat Linux 4.0: PVCS Merge Tool Does Not Label the Revision Panes on Desktop Client and I-Net [DEF128513]

The PvcsMerge tool on UNIX/Linux (Desktop Client and I-Net) does not label the revision panes. This has been fixed.

1.1.67 RSE (Redirect Standard Error) Executable No Longer Works [DEF87236]

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.

1.1.68 Set Workfile Location Permission Discrepancy [DEF75064] Δ

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.

1.1.69 Shorten The Project Path Version Manager Uses Internally [ENH96656; EP05372] Δ

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

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.

1.1.70 SourceBridge: May Be Unable to Fully Disable the Integration [DEF107936]

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.

1.1.71 "v" and "w" Alphabets Are Misinterpreted in Danish and Norwegian Language Editions [DEF38705]

1.1.72 Version Label: Unable to Delete or Rename a Blank Version Label [DEF138482; DEF30661] Δ

BEHAVIOR CHANGE: It is now possible to delete or rename a blank version label via the desktop client, CLI, and PCLI.

1.2 IDE Client Defects Fixed

1.2.1 Eclipse 3.1.1 and RAD 6.0: When FS and Client is Disconnected, Eclipse and RAD Crashes Without Saving the Changes [DEF114021]

1.2.2 Eclipse 3.1.1: User Authentication Is Required Each Time Eclipse 3.1.1 is Started [DEF91844]

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.

1.2.3 Eclipse 3.1: Version manager Integration with Eclipse 3.1 [ENH115846]

1.2.4 Eclipse RIDE: Accented Characters are Not Displayed when "Compare Revisions" Option is Used in VS2003 [DEF123473]

1.2.5 Eclipse RIDE: "Team | History" Causes Hang if Password Is Required [DEF107736] Δ

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.

1.2.6 Eclipse RIDE: Disable the "Resolve All Changes" Button in Conflicts Mode [DEF89387]

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.

1.2.7 Eclipse RIDE: Finding Related Issues Fails if File Name or Path Includes a Space [DEF128800]

1.2.8 Eclipse RIDE: HTML Characters Do Not Work in Passwords [DEF130113]

Special HTML characters like @ and & do not work correctly in passwords.
This has been fixed.

1.2.9 Eclipse RIDE: Prompt if Workfile is Unchanged Does Not Include File Name [DEF113452]

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.

1.2.10 Eclipse RIDE: Report Project Does Not Work With Rich Integration for .NET [ENH86092]

1.2.11 Eclipse Ride integration with Web Sphere Developer for zSeries: Reopening of Workbench Causes Lack of Memory Space [ENH128913]

1.2.12 Microsoft Vista: Support for VS Ride 2005, Eclipse, Visual Studio 2005 SCC, Visual Basic 6.0 SCC, WebDAV, Version Manager INET, Version Manager Desktop Client, PCLI, File Server [ENH103043]

This has been fixed. NOTE some features are not supported in VS Ride 2005, Eclipse and Visual Basic 6.0 SCC.

1.2.13 VS 2003 & 2005: Keyword Expansion Not Enabled by Default for CS Files [ENH76493]

1.2.14 VS 2003: Non U.S. Locale Displays Error Codes Instead of Error Messages [DEF89537]

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.

1.2.15 VS2005: Projects Are Not Moved Into Correct Folders When a Solution is Opened from Source Control [DEF132775]

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.

1.2.16 VS2005: Solution Explorer Tree Does Not Display the Latest File Status for New Projects [DEF101400]

The solution explorer tree does not display the latest file status for check-in and checkout files. This has been fixed.

1.2.17 VS2005: "Update after keyword expansion" Checkbox Does Not Work [DEF105966]

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.

1.2.18 VS2005 RIDE: Check In: "Apply to all remaining files" Checkbox Is Ignored [DEF111917]

The "Apply to all remaining files" checkbox on the Confirm Check In Unmodified Workfile dialog is ignored.
This has been fixed.

1.2.19 VS2005 RIDE: Can't Check In Code-Behind Files if Parent Not Modified [DEF106338]

1.2.20 VS2005 RIDE: Cannot Add SQL and VSTS Projects to Source Control [DEF104294]

1.2.21 VS2005 RIDE: Cannot Work Offline [DEF144498] Δ

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.

1.2.22 VS2005 RIDE: Offline Sessions Time Out Quickly [DEF137874]

1.2.23 VS2005 RIDE: Incorrect Workspace Settings Sometimes Used [DEF99277]

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.

1.2.24 VS2005 RIDE: NetCOBOL Projects Cause Error [ENH81312]

Adding a solution to source control that contains a NetCOBOL project throws an error:

1.2.25 VS2005 RIDE: Solution File Can Lose SCC Bindings for Project when Force Update [DEF112428]

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.

1.2.26 VS2005 RIDE: Strange Codes Appear when Working with Renamed Files [DEF113711]

1.2.27 VS2005 RIDE: "Update local file after keyword expansion" Option Logic Is Inverted [DEF112209]

The check-in option Update local file after keyword expansion was implemented with inverted logic. This has been fixed.

1.2.28 WSAD: Cannot use Path Map security on File Server [DEF22188]

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.

1.3 Version Manager Web Client Defects Fixed

1.3.1 Cannot Open Files with Left-Bracket "(" in File Name [DEF111860]

1.3.2 Cannot use Comma (,) in File Names [DEF41445; DEF31864; DEF41390]

1.3.3 Check In of Single File Does Not Work from Non-Default Location [DEF93939]

1.3.4 Column Sort Order Lost After Action [DEF107408]

The column sort order was not maintained after invoking an action, such as a Get or Check Out. This has been fixed.

1.3.5 Error 500 if any Field on the Servlets Tab Includes an "&" Character [DEF41531]

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.

1.3.6 Error 500 if File Name Includes the "&" Character [DEF86240]

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.

1.3.7 Error 500 Merging Revisions [DEF114065]

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.

1.3.8 Error if Project Database Root Directory Contains the "&" Character [DEF77489]

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.

1.3.9 LDAP Referrals May Crash Server at Login [DEF137487]

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.

1.3.10 Current LDAP Server Configuration Settings Must Be Retained [DEF91421]

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

1.3.11 Incorrect Path in Error Message on Get [DEF94663]

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.

1.3.12 No Option to Keep Revision Locked when Adding Workfiles [DEF31400] Δ

BEHAVIOR CHANGE: An option was added to the Web Client, Add Workfiles dialog to allow keeping revisions locked when adding them to source control.

1.3.13 "Previous" Link Returns to First Page Rather than to Previous Page [DEF127369]

1.3.14 Refresh View of a WebDAV Folder on the File Server Causes Memory Leak While Using Apache TomCat [DEF148273]

When accessing a WebDAV folder on the file server and on refreshing the view, a memory leak is noticed. This has been fixed.

1.3.15 Serena Business Mashups Integration: Item ID Information not Displayed in the Japanese Edition of the Version Manager [DEF150271]

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.

1.3.16 Version Manager Web Server Sometimes Crashes with PID Errors [DEF130918]

1.3.17 Team Track integration: Check-in comments not logged in the Team Track revision history for modified files [DEF150270]

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.

1.3.18 Version Manager Web Server Temp Files Are not Cleaned Up [DEF41182]

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.

1.3.19 Unable to Add a Work file with Filename As "Admin" Without Any Extension If the Project Database Already Has a "Admin" folder [DEF91649]

1.3.20 User Needs Ability to Close their Stale Login Sessions [ENH130001] Δ

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.

1.3.21 Version Manager I-NET: Buttons are Grayed Out in the Browser Interface [DEF139116]

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.

1.3.22 Version Manager I-NET: Checked In Comments Are Not logged in the Team Track Revision History for Modified Files [DEF150270]

1.3.23 Version Manager I-NET: Logoff Results in a Extra Browser Window Pop-up and Code Display On Internet Explorer and Fire Fox [DEF133332]

1.3.24 Version Manager I-NET: View Files Are Copied To Work File Location [DEF127993]

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)

1.3.25 Version Manager I-NET Installer: Temporary Files Must be Removed At Preset Timings [DEF133559]

1.3.26 "View as HTML" Option not Working for Some File Types [DEF39332; DEF80909]

1.3.27 Workfile Location Link Is Missing [DEF96124]

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.

2.0 Defects Fixed in Version Manager 8.1.4.2

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

2.1.1 Add Workfiles Recursively Requires Create Project Privilege [DEF75069; DEF124063]

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.

2.1.2 Folder Permissions Not Inherited when Overwriting Workfile [DEF125893]

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.

2.1.3 If Unable to Write to ISLV.INI file: [Error] java.lang.ExceptionInInitializerError [DEF127651]

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.

2.1.4 PCLI: No Way to Set Workspace Attributes [ENH73423] Δ

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.

2.1.5 Solaris 10: Running vlog '*' Results in Segmentation Fault [DEF125262]

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.

2.1.6 SourceBridge Version Label Is Assigned Even if File Is Not Checked In [DEF115044; 116494]

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.

2.1.7 SourceBridge: Hangs when Adding Workfiles if "Don't check in work file" Option is Selected [DEF116223]

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.

2.1.8 UNIX: Workdir Must Be Writeable by Group or Other Even with Setuid [DEF129831]

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.

2.1.9 Vista: Initial Work to Make Version Manager Run on Windows Vista [ENH105516]

2.1.10 Vista: Failure when trying to View/Edit a File without a known File Type Association on Windows Vista [ENH126622]

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.

2.1.11 vtransfer -c (Copy) and vtransfer -x (Export) Does Not Work for Unsplit Archives [DEF127130]

2.2 IDE Client Defects Fixed

2.2.1 Eclipse 3.1.x: File Server Temp Files Not Cleaned Up when Closing Eclipse [DEF127456]

2.2.2 Eclipse RIDE: Does Not Support Dynamic Generation of Web Services [DEF115817]

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.

2.2.3 Eclipse RIDE: Compare Workspaces: "Force Update" Does Not Work Correctly on Locally Deleted Folder [DEF78224]

2.2.4 Eclipse RIDE: Forced to Use the Default Workspace [TECH03638; DEF92798; DEF127349] Δ

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.

2.2.5 VS2005 RIDE: Assertion Failure Errors [DEF123425; TECH04973; DEF123529; L3RD00124]

After installing VS2005 SP1, archive actions return assertion failure errors. This has been fixed.

2.2.6 VS2005 RIDE: Manually Added Folders Not Gotten from Source Control [DEF114114]

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

2.2.7 VS2005 RIDE: History View: Cannot View a Revision by Double-Clicking It [DEF116385]

2.3 Version Manager Web Client Defects Fixed

2.3.1 Web Client Security [DEF114862]

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.

2.3.2 Version Manager Web Server on UNIX (Solaris) Randomly Crashes [DEF123172]

The VM Web Server would randomly crash on UNIX, referencing pvcs.vm.vms.AccessDatabase.PvcsLogin() in the crash dumps. This has been fixed.

2.3.3 Closing the Browser Does Not Logout [DEF124417] Δ

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.

2.3.4 LDAP Password Length Limit of 29 Characters [112809] Δ

2.3.5 "Mexico City-New" Timezone Not Working Correctly [DEF112438]

Check-in time is GMT rather than the "Mexico City-New" timezone the server box is set to. This has been fixed.

2.3.6 Vista: Only Admin Can Install Web Client to Internet Explorer 7 [ENH127090]

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.

2.4 Serena Builder Defects Fixed

2.4.1 Build Jobs Created from VM Web Client Are Not Accessible Once Saved. [DEF123717]

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.

2.4.2 Build Job Wizard Does Not Enforce Selection of Search Path in VM Web Client [DEF123719]

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.

2.4.3 Integration Fails if VMMBI_GetRevInfo.pcli Script Hits Empty Archives [DEF127003]

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.

2.4.4 Remote Build Jobs created via VM's Builder Integration are invalid [DEF123851]

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.

2.4.5 Unable to Edit a Job Created in Builder Web Client from VM [DEF123848]

2.4.6 Wizard Stores Build Job Information Incorrectly [DEF115323] Δ

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.

2.5 vss2vm Converter Defects Fixed

2.5.1 VM8124(J): VSS2VM Tool Does Not Run in a Japanese Locale [DEF113620; DEF113621; TECH04688; DEF85046]

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.

3.0 Defects Fixed in Version Manager 8.1.4.1

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

3.1.1 Copy on File Server Results in Hang, Open Threads, or Errors [DEF107376; DEF114687]

This issue occurs only if an archive is empty, that is the archive contains no revisions.
This has been fixed.

3.1.2 Manual Refresh of Desktop Client Is Slow, Looks Like a Hang [DEF107434]

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.

3.1.3 UNIX/Linux: Cannot Generate Journal Report on File Server Projects [DEF107995]

This issue results in the following error: "[Info] No journal information exists matching the requested specification".
This has been fixed.

3.1.4 UNIX: Patch Installer Disables Setuid Mode for CLI [DEF111151]

Patch installer does not detect whether the executables it is replacing were running in setuid mode.
This has been fixed.

3.1.5 Serena Builder: Dialog Fails to Populate; Build Job Information Appears to Be Lost [DEF114382]

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.

3.1.6 Serena Builder: Target Promotion Group Required for TGT File [DEF77304]

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.

3.1.7 Advanced Filter May Not Work Correctly in Some Instances [DEF114741; DEF114921; DEF114980]

Certain combinations of filter options could produce incorrect results.
This has been fixed.

3.1.8 Event Triggers: Add Event Information for Workspace Related Values [ENH74447]

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.

3.2 IDE Client Defects Fixed

3.2.1 Eclipse SCC (Old) Integration: Cannot Open Projects with Long Names [DEF108328]

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.

3.2.2 SCC IDE Clients Hang Onto License [DEF108796]

IDE's hang onto license longer than desired after being closed.
This has been fixed.

3.2.3 Add Support for Rational Application Developer 7 [ENH108819; ENH108146; ENH107802]

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.

3.2.4 VS 2005 Rich Integration: "Use for all" Checkbox Is Not Honored for Non-Tip Revisions [DEF113667]

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.

3.2.5 VS 2005 Rich Integration: Business Intelligent Projects (SQL) Not Added to Source Control [DEF114620]

3.2.6 VS 2005 Rich Integration: Projects Added from Outside of Solution May Not Open from Source Control [DEF114695]

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

3.3 Version Manager Web Client Defects Fixed

3.3.1 Error: "Unable to open properties file C:\Program Files\Serena\vm\inetprops\PVCS Servlets.properties" [DEF74410; DEF78587]

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.

3.3.2 Linux: HostID Does Not Work with FireFox [DEF106074]

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.

3.3.3 Server Slowly Uses Up More and More Memory, then Stops Working [DEF112701]

4.0 Defects Fixed in Version Manager 8.1.4.0

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

4.1.1 Archive Deleted when Using vtransfer -r to Make a Case-Only Name Change [DEF101649]

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.

4.1.2 Unable to Migrate Version Manager 5.3/6.0 Files to 8.x Projects

4.1.3 Improve Advanced Filter [ENH102672; ENH74096; ENH85616]

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.

4.1.4 PCLI: Random Lockup [DEF106149]

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.

4.1.5 Add Support for Builder 6.4.1 [ENH106267]

4.1.6 O/S Length Limit: Add Project Name to Copy Project Failure Message [ENH107838]

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.

4.1.7 Problems with Create and Copy in setuid Mode [DEF110574]

Various operations in setuid mode would fail for invalid reasons. This has been fixed.

4.1.8 Patch Installer Not Correctly Validating Target Platform [DEF110761]

4.1.9 Changes to Support New Start and End of DST [DEF87528]

4.1.10 UNIX: Case Sensitive Mode Leads to Backslash (\) in Paths [ENH90111]

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.

4.1.11 LDAP Path Map Authentication on File Server Does Not Work [DEF99793]

4.1.12 Security Vulnerability when Using File Server with Secured Path Maps [DEF112435; DEF112436; DEF113143]

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.

4.1.13 PCLI AddUser/DeleteUser Command Does Not Use the Access Control Database Defined at Project Level [DEF108334]

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:

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.

4.1.14 Show History Returning" "Unknown Exception at line 2446 in VMNMArchiveFile" [DEF112763]

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.

4.1.15 vss2vm: Defects Fixed in the Visual SourceSafe to Version Manager Conversion Utility

4.1.16 UNIX: Folder Name Field Garbled, Unreadable, on Open Project Database Dialog [DEF111253]

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.

4.1.17 Hide User Visible Debug Message "DTK after clearing cache mkfile returned -1" [DEF111916]

Command line users may occasional see the confusing message "DTK after clearing cache mkfile returned -1". This has been fixed.

4.2 IDE Client Defects Fixed

4.2.1 Visual Studio 2005 RIDE: Display Branches in History Pane [ENH103565]

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.

4.2.2 Visual Studio 2005 RIDE: Support Branching of Files [ENH102647; ENH103566]

4.2.3 Visual Studio 2005 RIDE: Cannot Migrate 2005 Web Projects [DEF103314; DEF103425]

Migration of Visual Studio 2005 web projects from the SCC integration to the rich integration fails. This has been fixed.

4.2.4 VS2005 RIDE: Added Ability to Enforce Pessimistic Locking [ENH103568; ENH92721]

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.

4.2.5 VS2005 RIDE: Cannot Connect to TeamTrack with TeamTrack Login Icon [DEF106667]

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.

4.2.6 Add Support for Eclipse 3.2 [ENH95328]

4.2.7 Eclipse RIDE: Renaming One Archive Causes all Files to Appear as Incoming Changes [DEF98927]

If one archive is renamed, moved, or deleted all files will appear as incoming changes when compare workspaces is run. This has been fixed.

4.3 Version Manager Web Client Defects Fixed

4.3.1 A Given User on a Given System Is Unable to Log Back In [DEF101311; DEF102547]

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.

4.3.2 Double License Usage Running PCLI- and CLI-Based Triggers [DEF102814]

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.

4.3.3 vminet.html Includes Full URLs Rather than Relative Paths [DEF103262]

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.

4.3.4 Recursive Get by Label to "Copy to" Location May Place some Files in Default Location [DEF91065]

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.

5.0 Defects Fixed in Version Manager 8.1.3.2

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

5.1.1 Solaris 10: Version Manager Does Not Work in Setuid Mode [DEF103853]

5.1.2 LDAP Authentication Does Not Work Correctly on Subprojects with Passwords [DEF103577]

If a subproject has an access control database, LDAP authentication may not work correctly. This has been fixed.

5.1.3 HostID Does Not Work Correctly on Subprojects with Different Passwords for the Same User [DEF100920; TECH03489]

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.

5.1.4 Merge Tool: Option to Ignore Ctrl-Z Causes Incorrect Display [DEF101565]

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.

5.2 IDE Client Defects Fixed

5.2.1 Eclipse RIDE: Concurrent Licenses Are Not Released [DEF86396; TECH03418]

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.

6.0 Defects Fixed in Version Manager 8.1.3.1

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

6.1.1 Running vsplit -u on Archive Paths that Contain Double-Byte Characters Causes Data Loss [DEF102167; DEF100974]

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.

6.1.2 Show History Returns "Unknown Exception at line 2446 in VMNMArchiveFile" [DEF73412]

Under some circumstances, history reports on Windows sometimes fail. On UNIX, they sometimes crash. This has been fixed.

6.1.3 PCLI VLOG -bv Does Not Report the Default Label [DEF90649]

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.

6.1.4 Version Manager Did Not Support Windows Paths >=128 Multi-Byte Characters [DEF96024]

This has been fixed. Version Manager now works with full length multi-byte paths in Windows.

6.1.5 Desktop Client Filter Does Not Reflecting Archive Updates [DEF99052]

Filters, such as "Locked by" sometimes do not accurately reflect the current state of the archives. This has been fixed.

6.1.6 Advanced Filter Did Not Recognize the Specified Delimiter Character [DEF102146]

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

6.2 Version Manager Web Client Defects Fixed

6.2.1 NoCase=VCSID Ignored at Check In [DEF101026]

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.

6.2.2 Translate EOL Does Not Work Correctly with Split Archives and the Web Client [DEF102145; DEF96539]

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.

6.2.3 SSL Connections Fail after Restart [DEF100843; DEF102171]

SSL connections fail after restart, but will work if restarted multiple times. This was a defect in Tomcat. This has been fixed.

6.2.4 Filtering by Wildcard Filename: Entering Invalid Filter Pattern Causes Unhelpful Error [DEF87693]

7.0 Defects Fixed in Version Manager 8.1.3

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

7.1.1 Erroneous IDENT Command Error: error, unable to write file "<stdout>" (disk full?) [DEF93920]

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.

7.1.2 Double-Byte Characters in UserID Cause Check In and Check Out Operations to Fail [DEF94954]

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

7.1.3 Vss2Vm: Conversion Fails on Branched Files that Have Been Renamed [DEF95091]

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.

7.1.4 "Internal Processing Error 50" when Accessing Admin | Security Dialogs with LDAP in Effect [DEF93024]

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

7.1.5 Version Manager Clients Hang if They Reference a File Server that Is Unavailable [DEF96284; DEF99551]

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.

7.2 IDE Client Defects Fixed

7.2.1 Visual Studio: Request for Support of Visual Studio 2005 [ENH94374 ENH87128]

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.

7.2.2 Visual Studio RIDE: Glyphs for IDE Objects Should Reflect Files Checked Out by Other Users [ENH22103]

7.2.3 Visual Studio RIDE: Results for Get Operation States that Check Out Succeeded [DEF75089]

In Visual Studio 2005, the results text distinguishes between get and check out operations.

7.2.4 Visual Studio RIDE: IDE Hangs when Adding Large Solutions to Source Control [DEF88679; DEF88851]

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.

7.2.5 Visual Studio RIDE: Unable to Add Web Projects to Source Control [DEF88919]

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"

7.2.6 Visual Studio RIDE: Request for Ability to Make Workfile Writable on a Get Operation [ENH89586]

7.2.7 Visual Studio RIDE: Synchronize Put Remotely Added Web Project Files in Incorrect Directory [DEF88987]

7.2.8 Visual Studio RIDE: Error when Attempting to Open Solution From Version Manager [DEF89116]

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.

7.2.9 Visual Studio RIDE: Open from Version Manager: "System.NullReferenceException:" [DEF81268]

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.

7.2.10 Visual Studio RIDE: Force Update Does Not Update Local File in Web Projects [DEF87075]

7.2.11 Visual Studio RIDE: Request for Ability to Share a Source Controlled Project with Multiple Solutions [ENH87078]

7.2.12 Visual Studio RIDE: Does Not Indicate Progress or Activity when Processing Large Tasks [DEF88139]

7.3 Version Manager Web Client Defects Fixed

7.3.1 Windows Web Client Receives Improper End-of-Line Translation from UNIX/Linux Servers if Archives Are Split [DEF99423]

8.0 Defects Fixed in Version Manager 8.1.2.2

8.1 Old Files will Remain in Patch Directory

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.

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

8.2.1 UNIX Client Fails with Double-Byte File Names [TECH02291; DEF83829]

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.

8.2.2 Content of an Archive Replaced with that of Another [TECH02854; DEF71836]

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.

8.2.3 pvcsfs (FS_TMP) Cleanup Routine Cannot Remove Temp Files of Updated Archives [DEF85061]

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.

8.2.4 PCLI Does Not Handle Brackets [] Correctly [DEF87594]

Quoting a command string containing brackets [] was not sufficient to make it work correctly. This has been fixed.

8.2.5 HP-UX: PCLI "Unresolved symbol: PvcsGetErrorMessage2" [TECH02921; DEF94577]

If a PCLI command runs into an internal error, instead of printing that error the application will crash. This has been fixed.

8.2.6 Want Structure Depth Warning [TECH02249]

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.

8.2.7 Linux 2.4.20+: Internal Processing Error:106 [DEF94914]

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.

8.2.8 Linux: "Command not found" Errors for History Report and External Commands [DEF89569]

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.

8.3 IDE Client Defects Fixed

8.3.1 Eclipse: Synchronize Project Lists all Files in Project for Removal [TECH02630; DEF91574]

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.

8.3.2 Eclipse: Processes Continue to Run when Exit IDE [TECH02479; DEF87410]

Several processes continue to run when the user attempts to close the IDE. This has been fixed.

8.3.3 Eclipse: LDAP Authentication Does Not Work [TECH02933; DEF94713]

8.3.4 Eclipse RIDE: Cannot Connect to Project if Directory Name Different than Project Name [TECH02301; DEF88682]

8.3.5 Eclipse RIDE: Refactoring/Renaming Folders Does Not Work as Expected [TECH02577; DEF91236]

8.3.6 Eclipse RIDE: "Show Issue" Report Title Is Wrong [DEF85576]

The Show Issue report title is replaced with the title of an issue from the list. This has been fixed.

8.4 Version Manager Web Client Defects Fixed

8.4.1 Lose Access to Labels and Promotion Groups [TECH02409; DEF89553]

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.

8.4.2 Exception when Adding Files and Associating with TrackerLink with LDAP Login Source [TECH02410; DEF89582]

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.

8.4.3 configure_inet Script Returns "Bad string" on Solaris 10 [DEF92966]

9.0 Defects Fixed in Version Manager 8.1.2

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

9.1.1 Font Problems Can Occur in the Desktop Client on UNIX [DEF38783]

Some text may still appear a bit smaller than expected, but for the most part this issue has been fixed.

9.1.2 Version Manager Gets Project Information from the nfsmap File First, Then the File Server [DEF72358]

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.

9.1.3 Unhelpful Error Messages [INT31101]

Error messages for a variety of circumstances have been made more specific and helpful. Some specific instances include:

9.1.4 LDAP Password Is Cached and Reused [DEF80234]

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.

9.1.5 Version Manager hangs when you open a project database [DEF40983]

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.

9.1.6 java.lang.IllegalArgumentException with PCLI [DEF77699]

Unix client gets "java.lang.IllegalArgumentException" with PCLI put command if past revision contains specific Japanese character. This has been fixed.

9.1.7 DBCS on Korean fails during Keyword Expansion [DEF76944]

9.1.8 DTK: PvcsGetRevisionInfoVB Returns BUFFER OVERFLOW when Total Length of Path Related Strings Exceed 255 [DEF41413]

9.1.9 Improve/Simplify SETUID Logging for Security Auditing [DEF84055]

9.1.10 Diff/Merge Tool Does Not Handle Large Files (over 80,000 lines) [DEF37895]

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.

9.1.11 Diff/Merge Tool Cannot Handle Text File with ASCII 0x1A (Ctrl-Z) [DEF77126]

9.1.12 Diff/Merge: "Show Only Differences" Mode is Broken [DEF85645]

9.1.13 Fixed Length Keywords Defined with "x" Characters Instead of Spaces Don't Work [DEF80211]

9.1.14 Archive Directories and Project Meta-Data Files Not Using SETGID Group (setuid) [DEF38947]

9.1.15 PCLI java.lang.NullPointerException [DEF41114]

9.1.16 Allow Printing of PCLI Debug Information [ENH31856]

9.1.17 Builder/VM Integration Does Not Properly Support UNC Paths Coming from Unix Machines [DEF87369]

9.1.18 Improve File Server Performance in Certain Scenarios [DEF85209]

9.1.19 Source Bridge and $log$ Adds Extra Lines During Checkin of Multiple Files [DEF85540]

9.1.20 Too Many Project Databases Are Listed when Trying to Open a PDB through File Server [ENH40947]

9.1.21 Security Fix [DEF85953 5071718]

9.1.22 Enable Utilities Option Ignored by vtransfer [DEF86082]

9.1.23 vtransfer -d Always Reports Successful Deletion, Even if it Failed [DEF78664]

9.1.24 Timestamp is Sometimes Incorrect on Desktop Client [DEF38895]

9.1.25 On Windows Cannot Redirect Dbug Output of pvcsvmntc -d to a Text File. [DEF78971]

9.1.26 File Server Background Thread Sometimes Uses 100% of CPU and Generates Multi-GB Logfile [DEF84742]

9.1.27 Increase Maximum Promotion Model from 16k to 65k [ENH78578]

9.1.28 Open Project Database Dialog May Be Empty by Default [DEF37282]

9.1.29 DTK PvcsIsArchive Fails with Archive on a File Server [DEF40972]

9.1.30 vtransfer -r Should Allow Renaming a Directory [ENH22544]

9.1.31 Retain Shared Archives While Copying PDB's [INT86829]

9.1.32 Retain Workspace Settings While Copying PDB's [ENH79841]

9.1.33 SplitOnCreate Not Retained When Subsequent Configuration Changes Are Made [DEF78378]

9.1.34 Access Denied to PDBs if ldapinfo.ini File Is Read-Only [DEF81406]

9.1.35 Desktop Client Locks Up when Logging In to Second Project Database [DEF86916]

The Desktop Client would lock up after displaying the login dialog for a second project database. This has been fixed.

9.2 IDE Client Defects Fixed

9.2.1 .NET: Overwriting a Local Workspace Causes Failures [DEF77331]

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.

9.2.2 Eclipse: "Commit to Repository" Action Deletes Local Files that Should Not Be Deleted [DEF82433]

9.2.3 .NET: There Are a Number of Problems with the Current Logger [DEF80629 INT77485]

9.2.4 Eclipse Refactoring Error: “Cannot proceed due to the following problems. File Filename has been modified since the beginning of the operation.” [DEF75562]

9.2.5 Projects Imported into Eclipse using RIDE under UK Regional Settings Don't Work [DEF84346]

9.2.6 Windows CE Platform Manager Breaks SCC Admin Tool [DEF78259]

9.2.7 .NET: Improve Message when Auto Merge Fails Due to Conflict [ENH87456]

9.2.8 Eclipse 3.1.1: Unable to Associate Files with TeamTrack Issues [DEF88386]

9.3 Version Manager Web Client Defects Fixed

9.3.1 $Workfile$ Expands with the Full Workfile Path when Checking In from Unix Web Client [DEF79488]

9.3.2 Users Can Set Default Promotion Group Even when Disabled in GUI [DEF31742]

9.3.3 Any File Action in Web Client Returns XML RPC Error: java.lang.Exception [DEF73386]

If ARCHIVEWORK and WORKDIR are defined in the configuration file as "", which resolves to current directory, all file actions fail. This has been fixed.

9.3.4 Web Client Hangs Onto Licenses Too Long [DEF81660]

9.3.5 Checkin Fails if Unlocking Unchanged Files when Using Associations [DEF81755]

9.3.6 Checkin Consumes Two TeamTrack Licenses if Associated with TeamTrack Issue [DEF83948]

9.3.7 Improve DaemonServer Initialization with Regard to ARCHIVEWORK and WORKDIR Directives [DEF78571 DEF85206]

9.3.8 SourceBridge Cannot See Files in Sub Directories on a Recursive Add[DEF83544]

This was fixed in a previous release cycle, but was reintroduced before GA. This has been fixed.

9.3.9 Logfile Listing Web Client User Information [ENH82564]

9.3.10 Cannot View History or Reports in Web Client Using Apache [DEF83747]

9.3.11 Web Client Does Not Release License when Client Is Closed. [DEF22517]

9.3.12 Allow HostID Login Source [DEF40954]

9.4 Meritage Defects Fixed

9.4.1 Meritage Users Are Unable to Open Files from Repository Via SSL [DEF83144]

10.0 Defects Fixed in Version Manager 8.1.1.3

10.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

10.1.1 User Names Containing High ASCII or Asian Characters Not Recognized by File Server [DEF84933]

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.

10.1.2 PCLI Put Command May Fail if File Name Contains Asian Characters [DEF85003]

10.1.3 Semaphores Left Open on File Server [DEF84768]

11.0 Defects Fixed in Version Manager 8.1.1.2

11.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

11.1.1 CLI @list May Fail [DEF84663]

CLI commands using an @list may not execute correctly or may fail with a protection fault. This has been fixed.

11.1.2 Logging of Put Command Corrupts Journal File [DEF81137 DEF84671]

The fix for this defect was omitted from the previous patch. This has been fixed.

11.1.3 Fixed Length Keywords Can Corrupt Files [DEF83081]

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:

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:

12.0 Defects Fixed in Version Manager 8.1.1

12.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

12.1.1 The Copy Button for Results Does Not Work with Workstation Installs from UNC Paths [DEF38931]

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.

12.1.2 Version Labels or Promotion Groups That Match Revision Numbers Cause Version Manager to Use the Wrong Revision [DEF76128, SCR14516]

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.

12.1.3 File Server client cache files do not get cleaned up [INT80382]

12.1.4 PCLI ExportPDB fails with OutOfMemory error when the PDB is very large [DEF74450]

12.1.5 PCLI vlog ignores revision range when Default VL is defined in the active workspace [DEF76818 ]

12.1.6 Lost archive after unsplit operation [DEF78461]

If you execute vsplit -u from the directory containing the metadata archive, the archive may be deleted.

12.1.7 Mass operations randomly fail on File Server PDB [DEF75470]

12.1.8 LDAP Passwords Visible Under Some Circumstances [DEF78374]

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.

12.1.9 Logging of put command corrupts journal file [DEF81137]

12.1.10 Unsplitting an archive can cause loss of metadata [DEF81107]

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.

12.2 IDE Client Defects Fixed

12.2.1 .NET: Compare Workspaces View Does Not Refresh After Forcing Update [76675]

12.2.2 Eclipse: "Open from Team Provider" results in two login prompts [DEF74657]

12.2.3 Browsing to a version label containing a space causes Get to fail [DEF73999]

12.3 Version Manager Web Client Defects Fixed

12.3.1 Cannot use Version Manager on AIX with an EAPI version of Apache 1.3 [DEF38984]

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.

13.0 Defects Fixed in Version Manager 8.1.0

13.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

13.1.1 History Report Ignores Specified Label and Uses Default [DEF40760]

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.

13.1.2 PCLI generates licensing exception on exit [DEF74068]

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)

13.1.3 UNIX: Screen updates are very slow with remote X displays [38142]

When the Version Manager desktop client opens on a remote X Windows display, screen updates can take a very long time.

13.1.4 Project tree view occasionally collapses [38949, 41229]

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.

13.1.5 vsplit command fails on an archive named fileName.$$$-arc [40936]

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 ChangeMan Version Manager Command-Line Reference Guide.

13.1.6 File server returns an error when an event trigger is called from a UNIX client [40937]

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.

13.1.7 Long convoluted sentence in the admin guide [71355]

The description of the different types of configuration files is somewhat confusing.

13.1.8 Differencing tool reports some binary files as being the same when they are not [31714]

13.1.9 UNIX: TRANSLATE prevents "unchanged" prompt from appearing [38934]

If TRANSLATE is on, the "unchanged" prompt does not appear on Unix. This has been fixed.

13.1.10 VTRANSFER -r (UNIX): Changing the case of a file name on a case-insensitive File Server results in loss of the archive [72245]

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.

13.1.11 UNIX: Unexpected File Server case-sensitivity sometimes causes archives not to appear [72892, 73070]

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.

13.1.12 Version Manager Web Application Server seemingly shuts down at random [74459]

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.

13.1.13 DBCS File Server: VSQL and VSPLIT Use 100% of the CPU [75544]

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.

13.1.14 Vss2VM converter no longer works in 8.0.2.x [72539]

In Version Manager 8.0.2.x, the Visual SourceSafe convertor fails with the message "ERROR: PVCS_E_ACCESS_DENIED". This has been fixed.

13.2 IDE Client Defects Fixed

13.2.1 Eclipse: PVCS Eclipse Plug-in Bypasses Access Control Database for Project Creation [DEF75558]

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.

13.2.2 Error occurs when an @ sign is used in the Description field to specify a message file [22203]

13.2.3 No method to promote a revision to the next promotion group or to manage promotion groups [22048]

This has been fixed. For details, see the online help for the new promotion dialog boxes.

13.2.4 Configuring File Server to allow HTTPS (SSL) connections results in corrupted connection string [22172]

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.

13.3 Version Manager Web Client Defects Fixed

13.3.1 Check-out by version label fails if the label contains a space [40565]

13.3.2 Cannot view or edit a file from the Revision pane if the file name contains a single quotation mark [40977]

13.3.3 Cannot view or edit a file if the file name contains an ampersand (&) [40978]

13.3.4 Version Manager Web Server does not read embedded master configuration files [73141]

13.3.5 Tomcat exposes potential vulnerabilities [74087]

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.

14.0 Defects Fixed in Version Manager 8.0.2.6

14.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

14.1.1 File Server client cache files do not get cleaned up [DEF78155]

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.

14.2 IDE Client Defects Fixed

14.2.1 Eclipse: "Open from Team Provider" results in two login prompts [DEF74657]

14.3 Version Manager Web Client Defects Fixed

14.3.1 Browsing to a version label containing a space causes Get to fail [DEF73999]

15.0 Defects Fixed in Version Manager 8.0.2.5

15.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

15.1.1 DBCS File Server: VSQL plus VSPLIT uses 100% of the CPU [5017302]

15.2 Version Manager Web Client Defects Fixed

15.2.1 "Could not find revision..." error after vsplit on systems with double-byte characters [5018835, 5016685, 5008960, 5024728, 5029458]

16.0 Defects Fixed in Version Manager 8.0.2.4

16.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

16.1.1 Version Manager fails to connect to LDAP using SSL [1467218]

17.0 Defects Fixed in Version Manager 8.0.2.3

17.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

17.1.1 Four authentication requests are sent when a user successfully logs in using LDAP authentication [27732]

17.1.2 Cannot log in to two project databases simultaneously with named licenses [22612]

17.1.3 Users receive an A: drive error while browsing the local file system [37293]

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:."

17.2 Version Manager Web Client Defects Fixed

17.2.1 Clicking on a file browse button sometimes causes a Java exception [22460]

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.

18.0 Defects Fixed in Version Manager 8.0.2.2

18.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

18.1.1 A Merant Build job created within the Version Manager to Merant Build integration fails [1469322]

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.

19.0 Defects Fixed in Version Manager 8.0.2.1

19.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

19.1.1 Tomcat uses an ever increasing amount of memory (over the -Xmx limit) [1049877]

20.0 Defects Fixed in Version Manager 8.0.2.0

20.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

20.1.1 PCLI maintains multiple TCP/IP connections to the license server for a single user ID and session [1048543]

20.1.2 Mouse wheel doesn't work in some Version Manager versions [4000040]

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

20.1.3 DTK: The PvcsGetLockInfoVB function always returns 0 when you specify a revision [1026680]

20.1.4 Solaris, Linux, and AIX: Pop-up menus disabled in the desktop client [1032845]

20.1.5 Cannot use versioned-file entity paths from Event Triggers during Add Workfiles [1031458]

20.1.6 Merge tool fails when you specify a revision using a numeric promotion group [4000789]

20.1.7 Event Triggers: Need a way to get an entity path for PCLI triggers [1035829]

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.

20.1.8 Cannot see revisions on archive with access list [1036428]

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.

20.1.9 CLI on UNIX: SemaphoreDelay interpreted in seconds [1037358]

CLI commands on UNIX interpret the SemaphoreDelay as a value expressed in seconds rather than tenths of a second. This has been fixed.

20.1.10 Cannot launch Diff/Merge on Red Hat Linux 7.3 [1037751]

20.1.11 Unexplained security privilege discrepancy occurs [1038002]

A certain combination of ACD privileges can make a user UNLIMITED. This has been fixed.

20.1.12 VSS2PVCS: Shared archives persist in default archive location [1038825]

20.1.13 Allow/Disallow tab should appear only when the file to be edited is a master config file [1039670]

20.1.14 PCLI List and GetWorkLocation (GWL) return incorrect relative WorkPath [1039753]

20.1.15 Version Manager adds an extra @ character in islv.ini if a specific port is configured for the license server [1048683]

If a specific port is specified for the license server during installation, Version Manager adds an extra @ character in islv.ini.

20.1.16 Need a way to specify custom privilege sets through the PCLI AddUser command [1027133]

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:

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.

20.1.17 UNIX: Some dialog boxes ignore the pvcs.fontSize property [1035341]

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.

20.1.18 CLI commands do not respect the LOCALE setting in ISLV.INI [1040425]

20.1.19 The CLI readdb command generates an error when LDAP is configured as the primary login source [1045454]

20.1.20 Under certain conditions, an error or crash occurs when you try to view Granted Privileges [1045459]

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

20.1.21 The Select Revision dialog box does not correctly handle project expansion [1046006]

20.1.22 User IDs of users with DBCS names auto-added through Version Manager are corrupted [1046364]

20.1.23 Mover / Version Manager integration on UNIX: Deployment option isn't enabled after a successful regdeploy operation [1048275]

20.1.24 Difference report does not work with certain version labels that start with a digit [1047204]

20.1.25 VSS2VM fails with a File Server path [1047252]

20.1.26 Single-user login functions properly only if the user has the SuperUser or Unlimited privilege set [1047564]

20.1.27 Cannot select a specific semaphore directory for a non–File Server PDB [1047813]

20.1.28 Admin | Import Archives on a File Server PDB shows non-archive files [1047809]

20.1.29 Journal file does not properly indicate a floating version label after an Add Workfile operation [1047975]

20.1.30 PCLI: ImportPDB does not return a non-zero exit code if the import fails [1048024]

20.1.31 Cannot log in with LDAP definitions set up through the File Server if ACD is named fileName.acd [1048027]

This problem occurs when your Access Control Database has a file-name extension of .acd.

20.1.32 CLI: vtransfer -r fails if the unsplit archive doesn't have a revision path specified [1048595]

20.1.33 Toolkit: PvcsGetRevision produces inconsistent results between versions 7.5 and 8.x [1048075]

20.1.34 VSPLIT option -xo incorrectly behaves the same as -xe [1048157]

20.1.35 Merge tool: Ignore Case Difference option not working [1048174]

20.1.36 PCLI Vlog options should support the DefaultVersion directive when no revision is specified [1048324]

20.1.37 GET generates an error if performed on an archive directory to which access is denied from an accessDB in the File Server PathMap [1048382]

20.1.38 PCLI: The put -v option does not work when the -u option is also specified [1048404]

20.1.39 After checking granted privileges and getting an error message, you can no longer see all revision information [1048563]

20.1.40 PCLI: Unhelpful error message when workspace doesn't exist [1048600]

20.1.41 Trunk revisions display doesn't expand automatically [1039910]

20.1.42 Version Manager Application Configuration dialog box displays no information when the pvcsservlets.properties file is in use [1048899]

20.1.43 vlog -d does not account for Daylight Savings Time [1048542]

20.1.44 Cannot read LDAPINFOFILE file from the File Server in a heterogeneous environment [DEF75225]

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.

20.2 IDE Client Defects Fixed

20.2.1 WSAD: Unlocking an unchanged file triggers a prompt to merge branch to tip [1047106]

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

20.2.2 WSAD: Users not in ACD cannot cancel the login dialog to access projects not under SCC [1042019]

20.2.3 WSAD: When you load a workbench with deleted repository projects, the error messages are insufficiently descriptive [1046059]

20.2.4 WSAD: IDE does not ask more than once to remove deleted file from repository [1046718]

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.

20.3 Version Manager Web Client Defects Fixed

20.3.1 As Non-Super User, an error occurs when you try to view Granted Privileges [DEF40951]

20.3.2 Keyword Expansion Not Performed on Workfile After Check In [DEF40136]

20.3.3 If a user who is not a superuser tries to add a workfile to a 6.0 folder, an error occurs [1036535]

20.3.4 Users cannot modify private workspace settings [1037719]

20.3.5 Misleading error message occurs on Add Workfile if the reference directory does not exist [1047817]

20.3.6 Incorrectly interpreted ISLVINI environment variable causes a licensing error [1047852]

20.3.7 UNIX: Diff/Merge tool does not use TRANSLATE [1048049]

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.

20.3.8 web.xml refers to http://java.sun.com/j2ee/dtds/web-app_2.2.dtd, which should end with 2_2.dtd rather than 2.2.dtd [1049156]

20.3.9 $Log$ does not work when you choose to keep the file locked after check-in using the Version Manager web client [1046823]

20.3.10 Problem Expanding Project Folders [1048344]

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.

21.0 Defects Fixed in Version Manager 8.0.0.9

21.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

21.1.1 Vcompres fails with large archives [1030515]

21.1.2 Check-in of a large workfile fails if the compress directive is set [1039662]

21.1.3 PCLI isDifferent command fails if a version label starts with a digit [1048534]

If a version label starts with a digit, the PCLI isDifferent command fails, and the error message displays the wrong version label.

21.1.4 UNIX: No .islvtk file is created, which results in numerous calls to the license server [1048540]

21.1.5 Advanced filtering by two version labels does not work when there is a floating label on a branch [1048462]

21.1.6 UNIX: You cannot log in using LDAP if LDAP was configured using a Windows desktop client [1048811]

21.1.7 AIX and Linux: LDAP debugging (PVCS_LDAP_DEBUG) does not work [1048813]

21.1.8 Get operation fails on archives with large compressed deltas [1048901]

21.1.9 $(Command) does not differentiate between the desktop client and PCLI on UNIX/Linux

When the $(Command) alias is used in configuration files, it incorrectly identifies PCLI as "VMGUI" on UNIX and Linux platforms.

21.2 IDE Client Defects Fixed

21.2.1 WSAD 5 Plug-In: The Refactor | Rename operation does not complete successfully [1042493]

21.3 Version Manager Web Client Defects Fixed

21.3.1 HTTP 500 error occurs when the project name includes an ampersand (&) [1046912]

22.0 Defects Fixed in Version Manager 8.0.0.8

22.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

22.1.1 Reference directory fails and shows incorrect path if the path contains spaces [1047343]

22.1.2 Unable to log in to a File Server project using a DBCS ID [1048287]

Access to a File Server PDB is denied when you log in using a DBCS (double-byte character system) ID. This has been fixed.

22.1.3 File Server: Version Manager can corrupt archive files if ARCHIVEWORK and WORKDIR use a slow drive [1048300]

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.

22.1.4 The CLI and DTK applications fail to access files from the File Server when launched from the EventTrigger or Toolbar [1048448]

22.1.5 Admin: Security report needs a way never to show passwords [1040729]

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:

22.2 IDE Client Defects Fixed

22.2.1 Interdev: New revisions are not created on check-in [1047354]

New revisions are not created when you check in files from Interdev. This has been fixed.

22.3 Version Manager Web Client Defects Fixed

22.3.1 VM I-Net: History Report Ignores Time Input [DEF38918]

22.3.2 Solaris and HPUX: Version Manager Web Client hangs during pre-processing [1048807]

23.0 Defects Fixed in Version Manager 8.0.0.7

23.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

23.1.1 PCLI: Problems occur with the ListRevision (lr) command if the version label starts with a number [1046536]

24.0 Defects Fixed in Version Manager 8.0.0.6

24.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

24.1.1 Journal files and reference directories get randomly modified [1047770]

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.

24.1.2 FS_TEMP setting can cause "unknown exception" error [1047850]

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.

24.1.3 Zero-Byte Archives SER Files [1047876]

These occur if there is no diskspace left on the Temp directory defined under File Server Administrator | Options. This has been fixed.

24.2 Version Manager Web Client Defects Fixed

24.2.1 Temporary archives created in the product installation directory [1047572]

If temporary directories are not specified, temporary archive files get created in the product installation directory. This has been fixed.

24.2.2 You can no longer use $(Command) in your configuration file to identify the Version Manager web client [1047800]

25.0 Defects Fixed in Version Manager 8.0.0.5

25.1 IDE Client Defects Fixed

25.1.1 Visual Studio .NET: TrackerLink does not update InRev or OutRev [1044194]

26.0 Defects Fixed in Version Manager 8.0.0.4

26.1 Version Manager Web Client Defects Fixed

26.1.1 Intermittent "No Privilege" Error [1042661]

With LDAP authentication in place, users sometimes receive an error stating that they lack the privileges to access files. This has been fixed.

27.0 Defects Fixed in Version Manager 8.0.0.3

27.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

27.1.1 CLI commands that update archives using 8.3-format file names cause Version Manager to crash [1045357]

27.1.2 servers.ini cannot be on a read-only network share [1045001]

The documentation suggests that a read-only network share is a valid location for the servers.ini file; however, this configuration causes error conditions.

27.1.3 File Server: Invalid device-specific temp directories can corrupt archives and metadata [1045858]

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.

27.1.4 File Server: vsplit does not clean up semaphores [1045832]

When you run the vsplit command, the .??$ semaphore file that gets created for the archive does not get removed. This has been fixed.

27.1.5 The workstation installation section of the Version Manager Installation Guide contains an error [1045750]

This has been fixed. The section on licensing workstation installs has been removed; the subject is covered correctly in another part of the guide.

27.1.6 UNIX: The Copy button in the Results dialog box does not copy to the X primary selection [1040678]

27.1.7 pvcsldap.ini created in the wrong directory [1046061]

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.

27.1.8 Change in case of HOST login ID results in loss of private workspaces [1042443]

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.

27.1.9 vsplit cannot parse an @list with quoted path names [1046111]

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.

27.1.10 Local %TEMP% directory fills up with cache files [1046308]

The file server client does not honor the total cache file size limit. This has been fixed.

27.1.11 Korean: Last character gets removed from the archive location when you tab to the next field in edit mode [1038984]

27.1.12 Japanese Windows: Project Database name is corrupted when you use the IME input form [1040977]

27.1.13 VSS2PVCS conversion involves a labeling anomaly [1046344]

27.1.14 Version Manager / Collage integration: runvmcm -s command fails [1046978]

27.1.15 Version Manager / Collage integration: Integration between Version Manager and Collage does not work with current release of Collage [1046976]

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.

27.1.16 Trackerlink-generated version labels are moved to the wrong revision on checkout [1047449]

27.2 IDE Client Defects Fixed

27.2.1 Conflict created when you open a pre-existing workspace after applying the "Merant Integrations Patch for Version Manager 7.5.1.0..." [1045236]

27.2.2 Show History on revisions locked by a specific user returns all users [1037527]

From within an IDE, performing a Show History operation on revisions locked by a specific user returns all users. This has been fixed.

27.2.3 WSAD: Error not displayed when privileges are not available [1041137]

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.

27.3 Version Manager Web Client Defects Fixed

27.3.1 Auto-Create Users doesn't work with LDAP on Version Manager web client [1044614]

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.

27.3.2 UNIX: In Netscape on UNIX, the font size for captions is too large, which makes some text cut short or invisible [1026715]

27.3.3 Documentation regarding linking Version Manager and Tracker web clients contains an error [1045676]

The documentation incorrectly refers to a Tracker project rather than a Tracker server in connection with configuring servlets. This has been fixed.

27.3.4 useDaemons=true is reset by each new version or patch [1039784]

27.3.5 Still shipping mod_jk 1.2.0 for Apache 2 on Solaris [1045434]

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.

27.3.6 GET fails on a split archive if it contained an access list when VSPLIT was run [1046354]

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.

27.3.7 Solaris clients: Execuatable bits are missing from workfiles after check-in [1044750]

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.

28.0 Defects Fixed in Version Manager 8.0.0.2

28.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

28.1.1 Merge Tool's default font cannot display Japanese characters [1040591]

28.1.2 PCLI: The -nb (No Banner) option does not work on UNIX [1044740]

28.1.3 Manually entering an invalid workfile location renders the file browser unusable [1045308]

28.2 Version Manager Web Client Defects Fixed

28.2.1 Cannot run daemons on UNIX [1037809]

UNIX: Any attempt to start the Version Manager web server with daemons enabled produces an error.

29.0 Defects Fixed in Version Manager 8.0.0.1

29.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

29.1.1 Promotion model deleted during editing in the desktop client [1042881]

When a sufficiently large promotion model is being edited in the desktop client, it gets deleted from the CFG file. This has been fixed.

29.1.2 Environment variable LM_LICENSE_FILE prevents evaluation license from working [1044425]

29.1.3 Non–File Server PDBs should check for split archives and warn appropriately [1044305]

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.

29.2 Version Manager Web Client Defects Fixed

29.2.1 After web.xml is modified, users get errors in all PDBs [1039249 ]

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.

29.2.2 Concurrent licenses not returned to pool [1044247]

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.

29.2.3 Windows XP: Applet does not fully install on Internet Explorer 6 with Sun's JRE [1043914]

29.2.4 Resource locked by session during Show History [1043662]

When the customer performs simultaneous Show History operations on multiple PDBs (in multiple browser windows), Version Manager hangs. This has been fixed.

30.0 Defects Fixed in Version Manager 8.0.0.0

30.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

30.1.1 PCLI online help for the -nb option confusing and incorrect [1038900]

30.1.2 Need to persist comments across multiple-file actions by default [1037053]

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.

30.1.3 Post-put event trigger is called even if the file doesn't get checked in [1039530]

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.

30.1.4 pcli get -p does not work [1039613]

30.1.5 Error details appear much too slowly [1039145]

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.

30.1.6 pcli list -ca format error [1039676]

The documentation for the pcli list -ca command contains errors (:= should be =). This has been fixed.

30.1.7 Selecting "Don't check in workfile" changes the default workfile location [1038803]

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.

30.1.8 Filter by Version Label returns incorrect results [1039920 ]

30.1.9 PCLI variables incorrect in PCLI manual [1038997]

The PCLI manual contains references to PCLI PR and PCLI ID (without the underscore). This has been fixed.

30.1.10 When you browse from Add Workfiles, the path contains \*.*\*.* [1035507]

In the Add Workfiles dialog box, clicking the Browse button sometimes displays a path with an extra \*.*. This has been fixed.

30.1.11 DOC: Installation Guide link for System Requirements no longer valid [1039038]

30.1.12 Version Manager looks for allusers.ser in the wrong location [1039525]

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.

30.1.13 If the current date is used as an expiration date, the security dialog box locks up [1039618]

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.

30.1.14 pcli IsDifferent command does not use the default revision [1039162]

The IsDifferent command always performs the comparison against the tip rather than the default revision. This has been fixed.

30.1.15 User name in the status bar can become corrupt [1039828]

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.

30.1.16 In the PCLI, the -v option should accept numeric strings as a version label [1040225]

The -v option should be treated as a label and accept numeric characters without requiring escape characters. This has been fixed.

30.1.17 Incorrect nfsmap file information in the Administrator's Guide [1038249]

30.1.18 Tool configured with a path longer than 80 characters does not run [1040235]

30.1.19 PCLI ImportArchives and AddFiles do not respect Run options -y, -n, and -np [1041294]

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.

30.1.20 PCLI IsDifferent -v command crashes if the version label contains two or more dots [1040963]

30.1.21 ACD file is deleted when you try to update an ACD file that is in use [1040386]

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.

30.1.22 java.lang.NullPointerException during Import Archive [1041296]

During import, , a corrupt archive will generate the error "Unexpected error: java.lang.NullPointerException" and halt the process. This has been fixed.

30.1.23 Journal Report uses incorrect beginning date in date range [1005578]

30.1.24 PUT: Checking in with "remove lock if unchanged" option creates another revision [1006888]

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.

30.1.25 Import Archive dialog box sometimes does not display all files or folders [1037435]

30.1.26 "Hot key" access to projects in the project pane stopped working [1037750]

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.

30.1.27 "Show Journal" doesn't display the proper journal information [1036675]

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

30.1.28 Need to update documentation to warn about duplicate IDs during multiple runs of VSQL [1035176]

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.

30.1.29 Journal entry date recorded incorrectly between midnight and 1:00 AM during Daylight Savings Time [1035508]

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.

30.1.30 PCLI Vlog options should support the Default Version when no revision is specified [1036271]

30.1.31 PCLI: The -a option of the Readline command does not assign to an array [1037027]

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.

30.1.32 Installation guide refers to a web site that no longer exists [1037377]

The Version Manager product link is out of date in the installation guide. This has been fixed.

30.1.33 Promotion model deleted when you edit in the desktop client [1042881]

When you edit a large promotion model in the desktop client, the model gets deleted from the configuration file. This has been fixed.

30.1.34 Version Manager installation shows wrong Start Menu folders [1043085]

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.

30.1.35 Journal files are not created or updated when you use File Server [1043220]

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.

30.1.36 vtransfer -f (fix) option does not work [1043290]

The vtransfer command option -f to fix a RevLib path does not work. This has been fixed.

30.1.37 Locking problems with File Server [1043304]

When accessing a project database through a file server, you may get lock errors after attempting to check in files. This has been fixed.

30.1.38 Long label names unnecessarily truncated in Filter Selection list [1035519]

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.

30.2 IDE Client Defects Fixed

30.2.1 Eclipse 2: Patch to Eclipse plug-in returns "The chosen operation is not currently available" [1038771]

30.2.2 Eclipse/WSAD: Enhancement request to enable Merant menu and glyphs by default [1039523]

For Eclipse-based IDEs, the Merant 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.

30.2.3 TD: Setting test types to be placed under version control [1041223]

The value of the string should contain the test types for TD, separated by commas.

30.2.4 ID: Can't perform a "Get latest version" on a file unless a local copy already exists [1040799]

An "Unable to get file" error occurs during a Get that includes Get latest version of... or Refresh Project View. This has been fixed.

30.3 Version Manager Web Client Defects Fixed

30.3.1 Long label names unnecessarily truncated in Filter Selection list [1035519]

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.

30.3.2 Need to persist comments across multiple-file actions by default [1037053]

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.

30.3.3 Receive "internal processing error: 72" when using "@" in the Change Description [1039381]

30.3.4 Different passwords not allowed for the same user within a PDB [1039078]

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.

30.3.5 Timestamp changed when an UnconditionalPrePut event trigger is used [1039199]

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.

30.3.6 Consecutive spaces in version labels are collapsed into a single space [1040379]

30.3.7 Netscape reload problem [1023611]

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.

30.3.8 Web client does not load VMINET.HTML or the SampleDB [1043355]

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.

31.0 Defects Fixed in Version Manager 7.5.2.2

31.1 Development Interface Defects Fixed

31.1.1 WSAD5/Eclipse: Patch install on Windows XP causes Dev Int to fail to initialize on WSAD 5 [1042706]

32.0 Defects Fixed in Version Manager 7.5.2.1

32.1 GUI, CLI, PCLI, and DTK Defects Fixed

32.1.1 Version Manager DTK has memory leaks in several functions [1014880]

32.1.2 Attempting to associate an SCR when adding workfiles returns an error [1039423]

If you select a file in the default workfile location and attempt to associate an SCR, nothing appears to happen. If you click the button again, the following error is returned: Empty Selection Set: Browse to select directories or files. This has been fixed.

32.2 Development Interface Defects Fixed

32.2.1 ALL: Open files do not return an "in use" error on a GET with Version Manager 7.5.1.0 [1041718]

When an item under source control is opened by an external application, such as MS Word, and the user performs a GET function through the IDE, the GET fails. This is correct behavior; however, in Version Manager 7.5.1.0, no error is passed, and the user is not alerted to the failure. This has been fixed.

32.2.2 ECLIPSE: Unable to modify plugin.xml [1039689]

Creating a plug-in project in an Eclipse-based IDE creates a file named plugin.xml. If you try to modify a field in that file, a dialog box prompts you to check out the file (even if the file is already checked out). Clicking Yes or No does not dismiss the dialog box or provide a way to check in the modified file. Shutting down the IDE through the Task Manager is the only way to dismiss the dialog box.

32.2.3 WSAD: Menu options do not conform to Windows standards [1039838]

Menu items that spawn dialog boxes are not followed by an ellipsis. This has been fixed.

32.2.4 WSAD 5 Plug-In: Doesn't check out the .websettings file [1042198]

When you modify the properties for the Web Project, the .websettings file does not get checked out, and an error is generated. This has been fixed.

32.2.5 Eclipse 2 and WSAD 5: Enhancement request to be able to not check out the .classpath file [1039109]

The .classpath file stores the java class path for the application. This file can contain custom directory values that are specific to the current user workstation. The .classpath file is getting automatically checked out and can cause problems when a modified version is checked back in.

33.0 Defects Fixed in Version Manager 7.5.2.0

This release is primarily intended to provide compatibility with Merant® Mover^TM. If you wish to use Merant Mover with Version Manager, you must install this release or upgrade to Version Manager 8.

34.0 Defects Fixed in Version Manager 7.5.1.5

34.1 GUI, CLI, PCLI, and DTK Defects Fixed

34.1.1 LDAP connection to Microsoft Active Directory Server via SSL fails [1039896]

Version Manager may shut down when trying to connect to a Microsoft Active Directory Server via Secure Socket Layer. This has been fixed.

34.1.2 PCLI List Archive:LockInfo output format changed [1040524]

As of Version Manager 7.5.1.0, the PCLI List output format for the Archive:LockInfo attribute was inadvertently changed, which can adversely affect scripts parsing this output. With the 7.5.1.5 patch, the original format has been restored.

35.0 Defects Fixed in Version Manager 7.5.1.4

35.1 GUI, CLI, PCLI, and DTK Defects Fixed

35.1.1 Double-Clicking the Create or Duplicate User Buttons Prevents Login to the Project Database [1039798]

Double-clicking the Create or Duplicate buttons on the Create User or Duplicate User dialog boxes may corrupt the list of valid users and prevent login to the project database. This has been fixed.

NOTE: If you have experienced this problem prior to installing the 7.5.1.4 patch, you may now see the following message when opening the affected project database (PDB):

[Warning] A user with a blank (null) name was found in allusers.ser. Your access control database might have lost some users--restoring from backup is recommended.

In that case, it is recommended that you restore the related access control database file (e.g. access.db) from backup. The warning message when you open the PDB will persist until a user is added or removed, unless the allusers.ser file was also restored (from backup or from allusers.old).

35.1.2 Difference Results Depend on Order in which Files Are Selected [1039504]

The results produced by the difference tool can be affected by the order in which the files are selected. This has been fixed.

36.0 Defects Fixed in Version Manager 7.5.1.3

36.1 Version Manager Defects Fixed

36.1.1 Long Path to Configuration File Causes Version Manager to Fail [1039271]

A long path (over 200 characters) to a Version Manager configuration file may cause operations to fail. This has been fixed.

36.2 Development Interface Defects Fixed

36.2.1 Integration to SCC and Eclipse IDEs Fails on Windows NT [1039154]

The Development Interface does not work correctly with SCC and Eclipse IDEs on Windows NT systems. This has been fixed.

37.0 Defects Fixed in Version Manager 7.5.1.2

37.1 Version Manager GUI, CLI, PCLI, and DTK Defects Fixed

37.1.1 Unable to Add Files to Source Control if the Reference Directory Does Not Exist [1039015]

If a reference directory is defined for a project but that directory does not exist, you will not be able to add files to source control for that project. This has been fixed.

37.2 Development Interface Defects Fixed

37.2.1 Visual Studio .NET: Web Projects on Remote Servers Do Not Include Nested Project Structure [1038885]

Visual Studio .NET web projects located on remote servers end up with flat file structures when added to source control. This has been fixed.

37.3 VM I-Net Defects Fixed

37.3.1 Unable to Add Files to Source Control if the Reference Directory Does Not Exist [1039015]

If a reference directory is defined for a project but that directory does not exist, you will not be able to add files to source control for that project. This has been fixed.

38.0 Defects Fixed in Version Manager 7.5.1.0

38.1 Version Manager GUI, CLI, PCLI, and DTK Defects Fixed

38.1.1 PCLI Does Not Create Archives That Have German Characters in the File Name [1031395]

On Windows, if a CodePage other than 1252 is used, the German umlaut characters are not displayed correctly. This has been fixed.

NOTE: You can change or query your CodePage from a Command Prompt using the command chcp.

38.1.2 Double-Clicking a Project with No Permissions Locks the GUI [1023776]

If a user is not defined in the access control database for a project and that user double-clicks a project to open it, the GUI locks up and displays the error message: "Access to this project has been denied because your login account is invalid". This has been fixed.

38.1.3 Version Manager 7.5.0.0 Hangs When You Try to Rename a Promotion Group to an Existing Group [1037855]

If you enter the name of an existing promotion group in an attempt to rename that promotion group using Configure Project, the GUI gets stuck in a loop and locks up. This has been fixed.

38.1.4 No PCLI Option to Turn Off Header Banner [1003330]

There was no way to turn off the display of the Banner Header when running a PCLI command. This is now possible by passing PCLI the option -nb (No Banner), or by assigning a value to the environment variable PVCS_NO_BANNER. This new environment variable is honored by all Version Manager commands.

38.1.5 Certain Command-Line Executables Did Not Use the nfsmap File [222505]

The nfsmap file is not used by the command-line executables vcompress, vdel, vdiff, vsql, readdb, and makedb. This has been fixed.

38.1.6 Put Does Not Check the Workfile Name if the User has Locked an Archive and Checked Something Different In [1002176]

If you merely lock an archive, rather than doing a checkout with a lock, and then browse to a different file at check-in, Version Manager checks in the file without a warning. This has been fixed.

38.1.7 User Cannot Check In Multiple Files That Were Checked Out to Different Locations [1014389]

If you check out files in a project to different locations, either manually or by using different workspaces, you cannot check them in as a group; Version Manager defaults to the workfile location for the project and does not use the check-out location embedded in the archive. This has been fixed.

38.1.8 Pinned Files Return "specifies a version number, which is illegal" Error When Using Version Manager with VSS [1019336]

The command ss dir $/pinned returns a list of items in the project specified. When a file is pinned, the file name is returned with a semicolon and a number to append to it. This has been fixed.

38.1.9 No PCLI Command to Promote or Assign Promotion Group [1032167]

In previous versions of Version Manager, it was nearly impossible to promote a revision or assign a promotion group from within a PCLI script. The commands AssignGroup, ChangeGroup, DeleteGroup and PromoteGroup have been added to PCLI to fix this. See the readme file for a description and syntax of these commands.

38.1.10 Wrong Workfile Location Used When One User Checks Out the Same Revision Twice [1032683, 1036485]

If a file was checked out using the root workspace setting, then the user switched to a new workspace and checked the file out again, Version Manager produced two locks with workfiles in different locations. When checking in the file, Version Manager did not know which workspace was used to check out the archive and might check in the wrong version. This has been fixed.

38.1.11 Quotation Marks Around Name Used Literally in PCLI [1035591]

The PCLI DeleteUser and AddUser commands takes any quotation marks around a name, making it impossible to create or delete certain valid names. This has been fixed.

38.1.12 Journal File Entries for "modify change description" Truncated to 200 Bytes [1036160]

If you modify an existing change description, the journal file entry is limited to 200 characters. This produces errors when you run the journal report causing, in some cases, an "Unknown Exception" error. This has been fixed.

38.1.13 Typing Filename (base) in Add Workfiles From Field Will Create Project [1036310]

When a user types a file basename (a name without a path) in the From field of the Add Workfiles dialog box, Version Manager creates a project with the name of that file. This has been fixed.

38.1.14 Problem Converting Archives from VSS to Version Manager when Multiple Branches were Deleted [1036609, 1036626]

If branch revisions between the trunk and tip are deleted, the trunk is not able to attach itself to a branch. The VSS Converter tool is unable to build a branch. This has been fixed.

38.1.15 How to Disable the New Banner and Help Page Buttons, "What's New" and "What's Coming" [1037716]

Tracker and Version Manager automatically pop up marketing messages in the What's New and What's Coming topics after a fresh installation. It is possible to turn off these help messages. Contact Answerline for assistance.

38.1.16 Embedded Disallow Directives Appended to Every Configuration File [1020757]

When users made changes to the configuration files, disallow statements were appended to the configuration file. The customer would need to remove the disallow statements that were appended to the configuration file, but when a change was made, the disallow statements were appended again. This has been fixed.

38.1.17 Project Metadata Directory (P*.prj) Not Always Moved When the Project is Moved [1038161]

Version Manager on Windows platforms could fail a project move operation because the directory being moved was "in use", resulting in error messages such as: "Could not rename "\\server\share\...\old_dir\P2tkjy.prj" to "\\server\share\...\new_dir\P2tkjy.prj". This has been fixed.

38.2 VM I-Net Defects Fixed

38.2.1 Incorrect Setup of iPlanet 6.0 Files After Server Configuration Utility [1037641]

If iPlanet 6.0 files are set up incorrectly, users would receive Init links in the wrong file and partial tag definitions. This has been fixed.

38.2.2 File Does Not Exist <path>BKGRD.gif [1008398]

The web server error log recorded the error: "file does not exist <path>BKGRD.gif". This file was called by a number of pages and the log could grow very large affecting performance. This has been fixed.

38.2.3 VM I-Net Default Version Does Not Work for Diff if Floating Label [1037274]

VM I-Net would produce the error: "Could not find a revision assigned with the version label, 1.*, in the archive <path><file name-arc>" when users would try to run a diff report. This has been fixed.

38.2.4 VM I-Net Gets 404 Error When Trying to Get to a PDB [1035955]

When you use Apache with VM I-Net, the attempt to hit the servlet or "install program" generates a segmentation violation in the active Apache thread. It reports the error: "[warn] Loaded DSO <Pathname_to_mod_jk> uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI)"

38.2.5 VM I-Net Project Names Not Visible with Certain Display Settings [1036467]

If a user's workstation display settings were set to "high contrast black", the names of the projects were not visible with the black background. This has been fixed.

38.2.6 Regarding the mod_jk Connector [1037918]

A user may connect to the target machine and deliver several requests with invalid chunked coded body. VM I-Net now includes mod_jk 1.2.1, which no longer suffers from this problem.

38.2.7 pvcsstart.sh Script Does Not Unset Variables That Can Adversely Affect VM I-Net [1037776]

The tomcat.sh script did not calculate JAVACMD if the environment variable already existed. If a user already had this variable, VM I-Net would not use Merant's JVM. This has been fixed.

38.2.8 Remove Command in pvcsstart.sh Script is Lacking "Force" Option [1037797]

The remove command in the pvcsstart.sh script that clears Tomcat's work directory would require a response if any file in that directory is read-only. This has been fixed.

39.0 Defects Fixed in Version Manager 7.5.0.1

39.0.1 Test Connection Fails with Large LDAP Databases

When you test the connection to large LDAP databases, the test may fail and return a "Sizelimit Exceeded" error. This has been fixed.

40.0 Defects Fixed in Version Manager 7.5.0.0

40.1 Version Manager GUI, CLI, PCLI, and DTK Defects Fixed

40.1.1 Missing Journal File Results in Misleading Error Message [1018413]

If the path to the journal file is incorrect or if the journal file is missing, an error may appear which does not mention the journal file. This has been fixed.

40.1.2 Command-Line Strips Leading Slash (\) from Quoted UNC Paths [223966]

The command-line strips the leading slash from quoted UNC paths. This has been fixed. NOTE: This fix is still compatible with old scripts that use extra slashes in order to compensate for the previous behavior.

40.1.3 Incorrect VB Include File in DTK Installation [1035005]

40.1.4 PCLI: Java Exception for Empty @file List [1031370]

If you use PCLI to expand an empty @file list, it will produce a Java exception error. This has been fixed.

40.1.5 "PCLI list -caDefaultVersion" Does Not Work Correctly [1032655]

"PCLI list -caDefaultVersion" does not give the correct value if the default label is defined for the parent project. This has been fixed.

40.1.6 "VLOG -bn -d" Returns Confusing Results [1035459]

40.1.7 AIX: Dragging in Tool Tip Causes Core Dump [1035549]

An invalid tool tip sometimes appears when you resize panes. Attempting to drag this window causes a core dump. This has been fixed.

40.1.8 PCLI Fails to Pass Exit Code Back to the Environment [1036127]

40.1.9 Browsing for the "Copy To" Directory Fails if the Default Directory Does Not Exist [1035953]

If you browse for the directory to "Copy To" during a check-out or get operation and the default directory does not exist, the operation may fail. This has been fixed.

40.1.10 Cannot Save the Output of the Results Dialog Box [1026427]

There is not an easy way to save the output of the Results dialog box. This has been fixed. One can now copy the entire output or multi select individual items to be copied.

40.1.11 Installer Did Not Accept 14-Digit Serial Numbers [1035914]

40.1.12 PCLI: IF Command Fails with NullPointer Exception if Boolean Function Fails [1036184]

If the boolean function in the PCLI if command failed (without returning a value), a Null Pointer exception could result. This has been corrected.

40.1.13 PCLI: IsDifferent Command Does Not Remove tmp Files if Execution Fails [1036190]

Running the PCLI IsDifferent command used to result in many temporary files being created and left behind. This has been corrected.

40.1.14 Workstation Install Shows No Feature Selection List when Source Directories Are Read-Only [1036303]

If the source directory for a workstation installation was read-only, the VM install program did not correctly identify the options available for installation from that directory. This has been fixed: You can now write-protect the source directory for workstation installs.

40.1.15 Specifying Journal File Using Filename Only Does Not Work Correctly [1036363]

If you specified a journal file name while running a Journal Report from the VM GUI, VM would just look in the application binary directory for the journal files, not in each archive directory as it should have. Correct location for the Journal files are searched, and Journal reports now contain all the appropriate info.

40.1.16 PCLI: VMCopy Produces a Stack Trace When Called with No Parameters [1035964]

If PCLI VMCopy was called with no parameters, an exception was reported. This has been fixed.

40.1.17 Documentation Issue with Respect to Daemons Configuration [1036683]

40.1.18 Versioned File Pane Redrawn for Every Project with a CFG if File Filter Is Used [1036949]

If your project database has multiple configuration files and you use a recursive view in the VM GUI and also apply a filter to that view, the display is updated too frequently. This has been fixed.

40.2 Development Interface Defects Fixed

40.2.1 Cannot Install Eclipse Integration without Also Installing GUI [1035737]

Cannot not install the integration to Eclipse/WSAD by itself. This has been fixed.

40.3 VM I-Net Defects Fixed

40.3.1 I-Net Fails with Sun's JRE [1032636]

This has been fixed. NOTE: See the Version Manager readme file for information about using Sun's 1.4.0x JRE and Internet Explorer with TrackerLink.

40.3.2 Remember Password Option Locks Out Users in Some Cases [1034767]

40.3.3 readdb and makedb Not Using Compatible User ID Expiration Date Formats [1034777]

readdb outputs user ID expiration dates in a different format than that expected by makedb. This has been fixed.

40.3.4 Must Occasionally Clean Out \tomcat\work\localhost8080 Directory to Run VM I-Net [1034993]

From time to time, the \tomcat\work\localhost8080 directory must be cleaned out or VM I-Net will no load correctly. This has been fixed. The directory is now regenerated whenever VM I-Net Server is restarted.

40.3.5 "ERROR: 500 Internal Servlet Error" when Viewing Properties of Version Manager 3.2 or Older Archives [1035567]

Viewing file properties of archives created with Version Manager 3.2 or older will result in an error. This has been fixed.

40.3.6 If %TOMCAT_INSTALL% Is Set then VM I-Net will Not Serve Content Correctly [1036254]

If you set a value for TOMCAT_INSTALL or CLASSPATH in your environment, those values could interfere with the correct operation of VM I-Net. The VM I-Net startup scripts have been modified to prevent this problem from occurring.

Serena PVCS Version Manager Version 8.2 Release Notes Last updated on 20 November 2008

Table of Contents

1.0 Defects Fixed in Version Manager 8.2.0.0

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

1.2 IDE Client Defects Fixed

1.3 Version Manager Web Client Defects Fixed

2.0 Defects Fixed in Version Manager 8.1.4.2

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

2.2 IDE Client Defects Fixed

2.3 Version Manager Web Client Defects Fixed

2.4 Serena Builder Defects Fixed

2.5 vss2vm Converter Defects Fixed

3.0 Defects Fixed in Version Manager 8.1.4.1

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

3.2 IDE Client Defects Fixed

3.3 Version Manager Web Client Defects Fixed

4.0 Defects Fixed in Version Manager 8.1.4.0

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

4.2 IDE Client Defects Fixed

4.3 Version Manager Web Client Defects Fixed

5.0 Defects Fixed in Version Manager 8.1.3.2

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

5.2 IDE Client Defects Fixed

6.0 Defects Fixed in Version Manager 8.1.3.1

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

6.2 Version Manager Web Client Defects Fixed

7.0 Defects Fixed in Version Manager 8.1.3

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

7.2 IDE Client Defects Fixed

7.3 Version Manager Web Client Defects Fixed

8.0 Defects Fixed in Version Manager 8.1.2.2

8.1 Old Files will Remain in Patch Directory

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

8.3 IDE Client Defects Fixed

8.4 Version Manager Web Client Defects Fixed

9.0 Defects Fixed in Version Manager 8.1.2

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

9.2 IDE Client Defects Fixed

9.3 Version Manager Web Client Defects Fixed

9.4 Meritage Defects Fixed

10.0 Defects Fixed in Version Manager 8.1.1.3

10.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

11.0 Defects Fixed in Version Manager 8.1.1.2

11.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

12.0 Defects Fixed in Version Manager 8.1.1

12.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

12.2 IDE Client Defects Fixed

12.3 Version Manager Web Client Defects Fixed

13.0 Defects Fixed in Version Manager 8.1.0

13.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

13.2 IDE Client Defects Fixed

13.3 Version Manager Web Client Defects Fixed

14.0 Defects Fixed in Version Manager 8.0.2.6

14.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

14.2 IDE Client Defects Fixed

14.3 Version Manager Web Client Defects Fixed

15.0 Defects Fixed in Version Manager 8.0.2.5

15.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

15.2 Version Manager Web Client Defects Fixed

16.0 Defects Fixed in Version Manager 8.0.2.4

16.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

17.0 Defects Fixed in Version Manager 8.0.2.3

17.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

17.2 Version Manager Web Client Defects Fixed

18.0 Defects Fixed in Version Manager 8.0.2.2

18.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

19.0 Defects Fixed in Version Manager 8.0.2.1

19.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

20.0 Defects Fixed in Version Manager 8.0.2.0

20.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

20.2 IDE Client Defects Fixed

20.3 Version Manager Web Client Defects Fixed

21.0 Defects Fixed in Version Manager 8.0.0.9

21.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

21.2 IDE Client Defects Fixed

21.3 Version Manager Web Client Defects Fixed

22.0 Defects Fixed in Version Manager 8.0.0.8

22.1 Desktop Client, CLI, PCLI, and DTK Defects Fixed

22.2 IDE Client Defects Fixed

22.3 Version Manager Web Client Defects Fixed

Serena PVCS Version Manager
Version 8.2
Release Notes
Last updated on 20 November 2008