This file lists the defects fixed, enhancements made, and behaviors changed in each release of Version Manager. For information on installing and using the current release of Version Manager, see the <Install_Directory>\vm\readmevm.html file.
NOTES:
Each service pack contains all previous defect fixes released since the last full Version Manager release, so it is not necessary to install the previous service packs.
Items marked with a "Δ" (Delta) symbol include BEHAVIOR CHANGES more extensive than simply restoring function to an existing feature. (Starting with 8.1.4.2)
For additional information on using a new or modified feature listed below, see the relevant Version Manager PDF/manual, Help system, or readme file as indicated below.
This has been fixed.
This has been implemented.
If you have modified the settings for File Type [undefined], the directives written to the cfg file are based on the assumption that [undefined] is not modified by the user. If the user modifies these settings it could lead to workfile corruption.
This has been fixed.
When used in a version label, the characters would be displayed as "???" or cause an error to be thrown. The characters are: č, ě, ř (c, e, and r with a caron). In Windows CP1250 Latin, these are the High ASCII characters 200, 227, and 236.
BEHAVIOR CHANGE: This has been fixed. Windows CP1252 Latin (Western Eurpean Languages) does not contain these characters. To use these characters, you must change the region and language settings of your system to one that uses Code Page 1250, such as Romanian.
If errors are encountered during a get command with the -q option, then the -q option may be disabled for subsequent "get -q" operations.
This has been fixed.
This has been fixed
This has been fixed.
This has been fixed.
With PowerBuilder, Crystal Reports, and Version Manager installed, the Version Manager Desktop client does not work correctly and the SCC component will not initialize. These same DLLs could also interfere with CLI and PCLI.
This has been fixed. Version Manager now loads the specific version of the DLLs it installs rather than depending upon the DLL search-order logic within Windows.
NOTE: If you encounter a conflict with another third-party DLL, try adding the name of the DLL to the ISLV.INI file. If there is not already a [THIRDPARTY] section in the ISLV.INI file, create one and list the conflicting DLL's under it as follows:
[THIRDPARTY]
PVCS.VM.THIRDPARTYDLLS=libeay32.dll:ssleay32.dll
Any DLL names should:
Be separated by the delimiter colon ( : )
Contain only the filename, not the full file path.
It only occurs if the user has ACDBs at multiple non-root levels and they want to create new ACDBs during the copy operation. This has been fixed.
This has been fixed.
This has been fixed.
Having an embedded ACD can also cause this problem. This has been fixed.
If the File Server contains a Path Map where the Project Database location is set to the root of a drive, attempts to launch a client on this File Server (GUI, PCLI, CLI) will cause those clients to crash.
This has been fixed.
This has been fixed.
The PDB cache lifespan setting of "0 seconds" on the File Server Options page was intended to allow you to turn off the PDB cache. With the cache disabled like this, the list was supposed to be computed at the time of each request. Instead, the PDB cache rebuild thread runs continuously, causing a 100% CPU load.
This has been fixed.
This has been fixed.
In the case of split archives, this can result in empty archives remaining on the server. This has been fixed.
When the login source is set to VCSID, VLOGIN (in that order), and you DON'T have a VCSID variable defined, VM is supposed to ignore the VCSID login source and just use VLOGIN.
This works well for all operations, except Show History / PCLI vlog involving a version label. For those operations, every other file(!) in the report fails with the error:
"Error: <EntityPath>: You have encountered an internal processing error: 50 (PVCS_E_NO_USER_ID: Unable to obtain the user ID.)"
This has been fixed.
Entering a hostname will work, but if you try to specify a port (ie. 27000@abc-flexlm), then it will fail to connect.
This has been fixed.
This has been fixed.
This has been done.
Merge cannot be performed using the merge tool tkdiff merge. It displays the error: "*.tmp is not a part of revision control system."
This has been fixed.
When running in setuid mode, non-pvcs users (= users other than the owner of the executables) can corrupt archives when they are not a member of the group that owns the vcs executable, given a normal umask setting (002 or 022).
This has been fixed.
This has been fixed.
When assigning a promotion group to revisions based on a label comprised of numbers, VM returns the message that it "Could not find a revision named 123456 in the archive <archive path>" Where "123456" is the selected version label.
This has been fixed.
When issuing a PCLI list command against an archive that has an access list but the user running it is not part of that list, they will get a java.lang.nullpointerexception.
This had been fixed. A "No Access" error message will now be displayed as expected.
This has been fixed.
This has been fixed. A message now appears warning that if no privilege set is assigned the effective privilege set will be Unlimited.
When a promotion model is in effect, a checkout operation uses different revision lookup logic than a get operation.
BEHAVIOR CHANGE: Force revision lookup options have been added so that a checkout operation can be made to use the same revision lookup logic as a get operation. These options can be selected from the Get and Checkout dialogs at run time. The default configuration of those dialogs can be specified in the user options and/or configured by the administrator in the Promotion section of the Project Configuration dialog. An -FG and -FR option have been added to the Get command in CLI and PCLI. The relevant sections of the Version Manager documentation have been updated; refer to them for implementation details.
Single sign-on functionality is now restored for project databases and projects accessed from the Desktop Client.
BEHAVIOR CHANGE: The administrator can configure Version Manger projects and project databases to recognize a user who has already logged in to Version Manager. When single sign-on is enabled, a user can login once and access all single sign-on enabled projects without logging in again.
NOTE Your Version Manager user ID and password combination must match across the project databases and projects on which you wish to use single sign-on.
Single sign-on is supported only in the Desktop Client.
If an existing PDB visible in the Desktop Client has SSO enabled, and if we create a new PDB using the Desktop Client, by default it shows the "Enable Single sign-on" SSO option is selected in the project configure dialog. If SSO is not enabled for the existing PDB, it works as expected: creation of new PDB shows the default option as "Enable Single sign-on" DISABLED.
This has been fixed.
If a subproject contains an ACDB with VLOGIN and the user name and password are the same (ie UserID = "Bob" and PW = "Bob") but the UserID is different than that in the root project, then when you navigate into a subproject, a stack overflow exception will be thrown. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When attempting ti un-install Version Manager, the user will be prompted with a message "PCLIOutProc is not responding".
This has ben fixed.
Users should be able to manage the memory heap Xmx and Xms settings for their workstation. The PCLI, GUI and web clients all allow this capability.
This feature has been added.
Java based clients use the following memory heap parameters:
-Xms Minimum heap size JVM parameter for loading JVM.
-Xmx Maximum heap size JVM parameter for loading JVM. If heap value grows above this value application will throw "Out of memory" error.
BEHAVIOR CHANGE: The feature is implemented as follows for the various IDE clients:
SCC Clients
In ISLV.ini file add a section and key value pair in the following format:
[CPCLI]
JAVAARGS=-Xms128m -Xmx512m
Visual Studio RIDE
In ISLV.ini file add a section and key value pair in the following format:
[SVE]
sve.dotnet.jvmloader.jvm.initialHeapSize=<value>
sve.dotnet.jvmloader.jvm.maxHeapSize=<value>
Eclipse RIDE and SCC
In the eclipse.ini file located in the eclipse folder, add a section in the following format:
-vmargs
-Xms40m
-Xmx256m
Here 40m and 256m corresponds to 40MB (min Heapsize) and 256MB (max Heapsize).
In Eclipse, the default options set for Label under Windows | Preferences | Team | Serena | Checkin, do not get picked up when performing Compare Workspace, Synchronize, or Commit To Repository actions. It does when performing Check In.
BEHAVIOR CHANGE: A Commit dialog now appears in the above mentioned scenarios. It is similar in function to the Checkin dialog and provides access to the same options.
For a few scenarios error codes are displayed instead of Error messages in the Serena Output console; for example, if the user cancels an operation.
This has been fixed.
This has been fixed.
This has been fixed.
When trying to perform merge using the SCC integration, the Merge Tool is adding the project name twice to the path. This results in setting path to the workfile as invalid and resulting in an error like: "Error: Unable to access the following file for reading: E:\vs\WebApplication2\WebApplication2\Default.aspx".
This has been fixed.
User checks out revision, whether tip or non-tip, from the History view but cannot check in file from the same view. Checks in file from the Solution Explorer but the changes made to the modified file are lost. Also when looking at the contents of a file through the History View and when looking at the file opened through the Solution Explorer, the contents are not identical.
This has been fixed.
This has been fixed.
This has been fixed.
When the user eventually adds a workfile to a previously empty folder, it could not be added to source control without first deleting the empty folder from the Visual Studio project. This has been fixed.
BEHAVIOR CHANGE: A previously empty folder will now be added to source control when the user adds files to it. Until then, it will not be added to source control.
This has been fixed.
The Next Difference button stops at the next difference in the file pane that is currently selected. By default the pane on the left is selected which contains the file that is currently on the tip. If you click the Next Difference button the focus does not go to the next difference because all the Add changes are referenced against your local workfile. You will need to switch focus between the two panes to be able to use the next difference button to see all the differences.
This has been fixed.
This has been fixed. Rather than crashing, a message now appears stating that the name contains disallowed characters.
This has been fixed.
For a newly added file (no content, file size of 0KB), merge operation on empty file throws an unhandled exception. This has been fixed.
Viewing locally modified file from compare workspace shows the repository file instead of the local file. This has been fixed.
This has been fixed.
This has been fixed.
If the Version Manager Admin is attempting to edit the configuration at the same time that a user logs in via the Web Client, the changes configuration changes may not be retained.
This had been fixed.
Attempting to do so resulted in the error: "Empty Selection Set - Browse to select directory or files." This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
The Version Manager Web client applet may not install on FireFox and Mozilla browsers if the server is running IIS 6 on Windows 2003. You can avoid this issue by defining a MIME type for .xpi files.
This has been fixed. The MIME type work around is no longer needed.
Get with default revision fails with error: "Can not locate specified revision label" even though no label was specified. The problem shows up whenever the PDB explicitly sets "DefaultVersion" to an empty value, although "BranchVersion" and "BaseVersion" can also wreak havoc.
This has been fixed.
This has been fixed.
If an inet client is doing a get on a PDB with a VLOGIN login source and the client has no password in the access database, and another process assigns a password to that userid, then the daemon server processing the inet client's requests can crash. New daemon servers will get created, but they also will crash.
This has been fixed.
This has been fixed.
The "View" and "Edit" functions no longer work if you click the "View / Edit file" icon next to a file. The "View as html" function still works, but "View" and "Edit" leave the dialog window open when you click OK.
This has been fixed.
The conversion code may not be smart enough to take the current locale into account when reading checkin dates from VSS.
This has been fixed.
After performing a Get operation, the Details information indicates that the revision was "Checked out". This led some users to believe they had accidentally executed a Checkout operation.
BEHAVIOR CHANGE: This has been fixed. To avoid confusion, Get and Checkout operations now both report which revision number was "Fetched".
When you use the SCC Integration from PowerBuilder, your first attempt to assign a version label during check-in fails to assign the label. The new revision is checked in, but the label is not applied and has to be manually applied afterward. Subsequent check-in operations succeed in applying a label.
This has been fixed.
If you click the browse button next to Add Workfiles From in the Add Workfiles dialog box and then click Cancel in the file browser that opens (choosing to keep the default location), the Add Workfiles operation fails with the following message after you click OK:
Empty Selection Set – Browse to select directory or files
This has been fixed.
*.255 [DEF162200]In certain archives with trunk tip revisions greater than *.255, attempts to assign a floating label to a branch fail with the following misleading error message:
Could not access the file archivePath, because you do not have the appropriate privileges.
This has been fixed.
A number of security vulnerabilities were identified in the Apache Tomcat 5.0.28 application engine that is running the Version Manager Web Application Server used by File Server, VM I-Net, and WebDAV.
These issues have been addressed by replacing the application engine with Apache Tomcat release 6.0.20.
Attempts to use this API return PVCS_E_INVALID_PARAMETER when the application is using the DTK from Version Manager release 8.2.0.1 or 8.2.1.0.
This has been fixed.
The PvcsVersionToRevision() call must be passed the size of the buffer used to store the revision number and version label information. Because this size is declared as an unsigned short data type, the call cannot succeed if the buffer must be larger than 65535 bytes, which causes it to return PVCS_E_BUFFER_OVERFLOW.
This has been fixed. The buflen parameter is now declared as an unsigned integer, which supports buffers larger than 65535 bytes.
Although Version Manager 8.2.1 supports Windows 2008, it does not support the IIS 7 Web server. Attempts to use VPADMIN to configure Web Client access through IIS fails.
This has been fixed. As of Version Manager release 8.2.1.1, the use of IIS 7 is officially supported and VPADMIN can be used to enable it.
A Version Manager security violation has been found that allows a user to perform actions on an archive based on the user's base privileges, even though the archive has an access list (of which the user is a member) that does not include the privilege for the action performed.
This issue arises only when both privileges are restricted to a promotion group. In that scenario, user restrictions on promotion groups have preference over access list restrictions on promotion groups. The issue exists in all Version Manager releases as of version 8.1.1.
This has been fixed.
The LDAP login debug output written to the file referenced by the PVCS_LDAP_DEBUG_FILE environment variable is not flushed, which complicates the debugging of running server processes.
This has been fixed.
In the File Server Configuration dialog box, the tooltips incorrectly reference operations being performed on an LDAP server if the user's locale is not set to English.
This has been fixed.
If the server running Mover has Version Manager 8.2.0.0–8.2.1.0 installed on it, deployments sometimes fail, especially with File Server–based project databases. This is triggered by the modified default location of the ISLV.INI file, which changed in Version Manager 8.2.0.0.
This issue has been resolved. The primary fix for this issue is available in Mover patch 2.3.0.04, but Version Manager itself has been improved as well to better deal with unpatched Mover releases.
A layout problem sometimes prevents users of Firefox 3.0 from selecting the Include files in subprojects option when a promotion model is in effect, because this can cause the option to get obscured in the dialog box.
This has been fixed.
A layout problem sometimes prevents users of Firefox 3.0 from clicking the OK or Cancel buttons in the Advanced Filter dialog box when a promotion model is in effect, because this can cause the buttons to get obscured in the dialog box.
This has been fixed.
The Version Manager Web Server sometimes enters a state in which users can no longer log in. Users attempting to log in to the VM I-Net Web client sometimes get an error message saying that "The resource is locked by session xxxx", or the dialog box hangs with the OK button locked in the Wait state.
This has been fixed.
The View As HTML option does not work correctly for some file types in common use today, particularly the docx, xlsx, and pptx extensions used by Office 2007. For example, rather than viewing the file in the browser as expected, the user might be asked to open a Zip file because Office 2007 files are compressed XML files.
This has been fixed. The new file types have been added to the default mime-type list, and the list itself has been externalized to a file (vm/common/pvcsprop/pvcs/vm/mimetypemapper.properties), enabling administrators to add missing file types in the future.
If a default version label is defined and a check-in is performed to a new line of development (for example, 1.* ‑‑> 2.*), the CLI Put command reassigns the label, whereas the PCLI and the desktop client do not.
This has been fixed. The CLI Put command no longer attempts to move the label.
Under certain circumstances, the File Server can crash or become unresponsive on Win32 platforms. This generally happens when someone is performing a mass Get while the File Server Background Processor is running.
In the vm\common\tomcat\logs\tomcat.log file, the following indication can be found:
java.lang.Exception: Unknown Exception at line 600 in PVNMSystem.cpp
at pvcs.io.file.PvcsFileDirect.stat(Native Method)
…
This has been fixed.
If a workspace other than the default workspace is selected when you share projects to the repository, the selected-workspace settings are ignored.
This has been fixed.
When adding a work file using the RIDE interface to the Eclipse IDE, the default promotion group is not assigned to the initial revision.
This has been fixed.
This has been fixed.
This has been fixed.
When a Project Database has been configured to remove locks on unchanged revisions, Version Manager removes the lock on an unchanged revision and does not increment the tip revision number when the user answers No in the Confirm Check In Unmodified Workfile dialog box ("Workfile … unchanged, check in anyway?"), or when the user selects Don't check in for the If Workfile Unchanged or Older field in the Check In dialog box, and the file is unchanged or older.
As Version Manager goes through an Unlock scenario at that point, the Pre Unlock and Post Unlock triggers should get executed; however, this does not happen in the 8.2.1 release.
This has been fixed.
In some project databases with numerous subprojects that are almost all configured with separate Access Control Database (ACD) files, the desktop client sometimes locks up when a subproject is selected that does not contain the user whose credentials were used to log in to the project database itself.
This has been fixed.
This has been fixed. The license is now checked out for the user ID under which the Remote Build Server is running.
This has been fixed.
Using the desktop GUI, you can enter a new password for a project for which your old password has expired. However, using the Web client, there is no way to regain access to a project for which the password has expired.
When you import a Version Manager project into Eclipse, the default revision settings associated with the workspace are not imported; instead, the latest revisions of all files are imported.
Project labels on shared files in Visual SourceSafe are not converted when migrating from SourceSafe to Version Manager.
The Web client should check whether you have a Sun JRE installed, but it does not.
This has been fixed.
When you use the -p option with the PCLI get command, a copy of the file is created in the workfile location. The revision should only be output to stdout.
This has been fixed.
If the temporary file location in the TEMP variable has a space in it, attempting to show differences from the Version Manager desktop GUI fails with the error "Configuration file does not exist."
Installation fails on non-English language Windows systems with an error regarding security settings and invalid users.
When attempting to use the Web client, the Java Runtime Engine (JRE) displays a warning message that the certificate on the UTF8Encode applet from Serena Software has expired (in March 2009).
NLSPATH environment variables for other software applications may conflict with Version Manager and cause it to crash. This has been fixed.
This may occur when there is a promotion model active and module associations are enabled. As a result, it may be impossible to click the OK or Cancel buttons.
Check-in dates are displayed incorrectly on machines with a Brazilian locale setting.
This occurred because the File Server client transmits too much data, or in other words is too chatty.
This occurred in the Web client.
The file icons should display a lock icon to indicate that other users have them checked out.
After making changes to the Version Manager installation using Add / Remove Programs in the control panel, an error displays that the diffmerge.properties file could not be found. This occurs with the Web client and desktop GUI.
The Web client check-in dialog box does not give you an option to keep workfiles writable. This is inconsistent with options in the desktop GUI. It should be possible to keep a writable workfile, and the options should be consistent.
Firefox 3.0 is now supported.
Rich integration to Visual Studio 2008 is now supported.
Apache 2.2.x is now a supported Web server on Linux and UNIX platforms.
The Visual SourceSafe migration tool applies the current date to all revisions that are migrated.
Windows Server 2008 is now a supported server platform.
Internet Explorer 8 is now a supported browser for the Version Manager Web Client.
You can now use third party merge tools with Version Manager that support additional character sets.
When you display the Manage Promotion Groups dialog box from the Visual Studio source control options, the Promote From field is truncated.
In the Japanese edition of Version Manager, you cannot click the OK or Help buttons in the SCC integration.
In the Japanese edition of Version Manager, an exception occurs when you run the journal file.
In 8.2.0.0, having multiple items selected would run the tool multiple times, passing a single selection at a time. This broke scripts that were expected to be executed just once, while being passed a comma separated list of selected items.
A new option is now available in the Tool Configuration dialog that allows you to select the desired behavior when multiple selections are present. By default this option is set to use the pre-8.2.0.0 behavior of running the tool once, and passing it a comma separated list.
This defect was introduced in Version Manager 8.2. This has been fixed.
This defect was introduced in Version Manager 8.2. This has been fixed.
This has been fixed.
Version Manager server process memory usage keeps growing steadily, to the extent that the process needs to get restarted.
A number of memory leaks have been eliminated. The server no longer needs to be restarted as frequently.
Prior to 8.2.0.1, get and check out operations behaved differently when looking up default revisions. By default, get operations looked up the tip revision of the trunk, and checkout operations looked up the revision associated with the lowest level promotion group.
This has been addressed by providing an option to lookup the revision. See the document on changes to address promotion group and default revision behavior issues that has been released along with this patch.
If the SourceBridge setting "Show Association Dialog on Checkout/Checkin" is selected, the Issue Association dialog box does not appear while checking out / in in both the desktop and Web clients. This has been fixed.
This has been fixed.
This has been fixed.
SCC: When using the SCC integration, Rational Application Developer and Powerbuilder do not stop the javaw.exe, eclipse.exe or pclioutproc.exe processes [DEF151876]
Closing an instance of Rational Application Developer or Powerbuilder that has a workspace connected to the Version Manager repository via the SCC integration does not terminate the javaw.exe, eclipse.exe and pclioutproc.exe processes.
This has been fixed.
.Net Rich Integration: Serena Business Mashup details are not displayed in the Issue window [DEF153908]
This has been fixed.
VS2005 RIDE: Version control history not recorded in Business Mashups item [DEF156030]
Version control history is not being recorded in the Serena Business Mashups item that was associated with the check-in.
This has been fixed.
Web client does not find pvcsmerge.exe in its default location [DEF153827]
Users who only have the Version Manager Web client installed will get a java.lang.RuntimeException in the applet console when they try to run a difference report. This has been fixed.
Version Manager 8.2.0.0 no longer detects applet mismatch , resulting in random failures [DEF154191]
When a new version of the Web cliente applet loads an old native library version, there is no message that tells you that you need to download and install the latest version of the Web client. As a result, a java.lang.UnsatisfiedLinkError message appears when you attempt to Check out, Check in, and Get files. This has been fixed.
Unix: Setuid mode does not work out of the box on Linux & Solaris [DEF153339]
This has been fixed.
Hotspot error when running vss2vm utility [DEF155299]
Conversion of Visual SourceSafe projects to Version Manager using the vss2vm utility fails with nested directory structures. An unrecoverable stack overflow error occurs. This has been fixed.
No error reported in deployment log when Version Manager user doesn't have add label permission [DEF149541]
This has been fixed.
The Event Trigger parameter __EventFQPWorkfile__ (variable EVENTFQPWORKFILE) does not contain the correct path in Pre and Post Create Archive triggers during Add Workfiles operations.
This has been fixed.
This has been fixed.
Version Manager ignores the "NODELETEWORK" (and "DELETEWORK") directives in the project configuration file. Instead, the Check In dialog uses the settings in the islv.ini file to control what is displayed as a default. This has been fixed.
BEHAVIOR CHANGE: A new control has been added to the Workfile | Attributes page on the General tab of the Project Configuration dialog so that the administrator can specify which After Check In option is the default and which options the user gets to select from at check in.
This has been fixed.
This has been fixed.
This has been fixed.
BEHAVIOR CHANGE: A -s option has been added to the vjournal command so the user can specify a delimiter character for use in parsing filenames. Use this when filenames may contain the default delimiter character of a comma (,).
The -b option of the VMRG command causes garbled output. The -b option is supposed to do the following: Ignores white space at the beginning and end of the line during the comparison process (with this option, white space between words is not ignored). White space characters are spaces, tabs, carriage returns, line feeds, and form feeds.
BEHAVIOR CHANGE: The -b option has been removed from the VMRG command so as to avoid undesirable and unpredictable results.
When trying to split an archive from a directory where the current user lacks write privileges, the vsplit command would crash. This is because a temp file must be created in the current directory. This has been fixed. The user will now receive an error message stating that cannot create the temp file.
BEHAVIOR CHANGE: You can now use -d with -z to delete a directory. Since this is dangerous, you will be prompted unless you pass the new -y option.
This has been fixed.
This feature has been added. You can view the delete and rename actions in the file vtransfer.vcs, which is kept at the root of the Path Map. You can also view this information using Actions -> Show Journals and selecting the VTransfer option.
Using the vtransfer command with the combination of the -r -z options to move archives from a parent to a child directory location results in the archives being recursively deleted. This has been fixed. The command no longer accepts a target directory that is a child of the source directory.
When using "vtransfer -i" to import a split archive into a File Server, the split archive location will not be updated if the path you import it into does not perfectly match the one the file was exported from.
This has been fixed.
Options now work as documented.
BEHAVIOR CHANGE: The vtransfer command options -c, -i, and -r now prompt to overwrite if the file already exists.
This has been fixed.
A get with a wildcard fails if a non archive file is encountered and a target dir is set. This has been fixed to ensure that the calculated logfile is a valid archive prior to calculating the workfile name and path. This avoids the invalid warning condition that caused the command to exit prematurely.
After upgrading to VM 8.1.4.x, File Server clients may crash if more than 50 path maps are defined on the server. This has been fixed.
Copy/Import of split archives would fail with a stack trace if an archive or archive path was missing or corrupted.
This has been fixed. An "Archive does not exist" error will now be displayed under such circumstances.
The fields on the Advanced tab of the Create Project Database dialog box did not allow keyboard entry (you had to invoke the browse dialog). This has been fixed. You can now type directly into the fields.
In some circumstances it was possible for a user without the Create Project privilege to create a project. This has been fixed.
Customer wants the default Version Label automatically assigned to the initial revision on create archive.
BEHAVIOR CHANGE:
Desktop Client & Web Client: During AddFiles if there is a default version label, Version Manager will prepopulate the Version Label field with it and enable the Float label with tip checkbox.
PCLI Checkin: To use the default label, omit the -v option. To not assign the default label, use the -v option with no label specified.
Actions | Show Journal does not work if the journal files are located on a File Server and the path to them is accessible only through that File Server.
This has been fixed.
In certain circumstances, the advanced filter can result in 100% CPU usage.
This has been fixed.
This has been fixed.
Selecting View | Refresh or browsing to a different project did not always refresh the client with the latest changes that someone else has made to the workspace information.
This has been fixed.
This has been fixed.
This enhancement has been made.
This has been fixed. Performing a Refresh or changing the column sort order now correctly sorts on the updated Check In dates.
This has been fixed. Performing a Refresh or changing the column sort order now correctly sorts on the updated Locked By users.
When you try to save information, the information is not correctly stored in the following scenarios:
1. If you select keyword expansion option in "Configure Project" dialog box, the backward Slash (\) is replaced with a forward Slash (/) on reopening the option.
2. In General module | semaphore, if you enter 5.000 in "Number of Retries" field and save the information, the number is changed to 3.000 on reopening.
3. Changes are not saved in "Cobol Renumbering" when the option is checked in Configure project | File types.
This has been fixed.
This has been fixed. If a Client Name resembles a UNC path, VM no longer tries to access paths using this Client Name on the network.
If you remove a file from source control and delete its archive from the file server, you will get an error upon trying to re-add the workfile to source control unless you first restart the VM client where the file was deleted from the project (and web server if using the web client). This has been fixed.
Selecting refresh now from the PDB cache lifespan drop-down menu on the Server Options page of the Version Manager File Server admin utility does not remove deleted project databases from the project database cache.
This has been fixed.
If a workfile is being checked into an archive that doesn't have GENERATEDELTA set, the "lines deleted/added/moved:" statistics that get recorded into the archive is a copy of however many lines were deleted/added/moved in the last (and different!) archive that did have GENERATEDELTA set (during the current VM GUI session). This has been fixed. An archive with NOGENERATEDELTA set now always records 0/0/0 for "lines deleted/added/moved".
This has been fixed.
BEHAVIOR CHANGE: A new checkbox, Include Get Operation, has been added to the Journal File page of the Configure Project Database dialog box. Select this new checkbox to include non-locking Get operations in the journal report. By default, they are not included, so as to maintain the previous behavior.
This has been fixed.
There is no mechanism to deal with multiple LDAP domains.
BEHAVIOR CHANGE: Version Manager now supports multiple LDAP servers, each of which can have its own Base User Context and User Naming Attribute. Version Manager will search all available LDAP servers until it finds a match for the entered user name, and then verifies if the password matches. Version Manager purposefully does not try subsequent LDAP servers if the user name matched on an LDAP server, but the password did not. As such, the requirement is that user names need to be unique among all LDAP servers used in the configuration.
If a project database has:
- ArchiveSuffix +-arc
- ArchiveSuffix . +.-arc
at the root of the project database, and:
- ARCHIVESUFFIX .? = +_v
at a subproject level, Version Manager will corrupt memory. This can lead to a crash.
This has been fixed.
The title bar for each of the panes showed the file name as /tmp/_1pziob19.tmp or some other random tempfile name. There was no way of telling which revision is the newer one. This has been fixed.
BEHAVIOR CHANGE: You can now configure Version Manager to use the third-party Diff/Merge tools of your choice. Besides allowing for greater choice, this allows an effective and easy means of avoiding any aspects of the PVCS Diff/Merge tools that are not suitable to your needs.
This has been fixed. Version Manager is now supported for Client platforms using the HP-UX Aries PA-RISC emulator.
This has been fixed.
The colon is an illegal character for version labels, since it is used by the CLI commands as a revision separator. The PCLI label command allows version labels containing colons to be added, using either the "Label" or the "RenameLabel" command. This makes it impossible to operate on these labels using CLI commands. This has been fixed.
BEHAVIOR CHANGE: PCLI commands can no longer create a label containing a colon character (:). This was always blocked in all other interfaces and was never intended to be possible.
PCLI commands send some non-error information to StdErr and some error information to StdOut. This has been fixed so that each type of information is sent to the expected destination.
BEHAVIOR CHANGE: All PCLI commands have been modified so as to send information to the correct destination: StdErr or StdOut. In addition, some commands previously output only the entity name. They now output the full entity path.
This has been fixed.
This has been fixed.
This has been fixed as follows:
Modified ImportPDB so that it will not fail when importing an 'old' export which has a workspace with trailing whitespace.
Also modified CreateWorkspace so that it strips off whitespace from the start and end of the name to avoid the further creation of troublesome workspace names.
This has been fixed.
This has been fixed.
This has been fixed. PCLI based event triggers that are executed from a VM I-Net server are now able to reuse the same license that was checked out for the user calling the event trigger
BEHAVIOR CHANGE: Two command options have been added to the List command so that you can format its output as XML, -fx and -nx. -fx includes an XML header tag in the output, -nx does not. See the PCLI User's Guide and Reference for more information.
BEHAVIOR CHANGE: The -g option will now climb the promotion model if used with the new -c option.
This has been fixed.
Test -i Command works for = and != comparisons. When you enter the command using < <= > or >=, the -i option is ignored. This has been fixed.
This has been fixed. The Label command now shows the fully entity path and the revision number for files that the label was applied to.
From the command line there was no way to set the default workspace. A command has been added to allow this. See the Serena PVCS Version Manager PCLI User's Guide and Reference for complete information on using the new command.
BEHAVIOR CHANGE: SetDefaultWorkspace allows an administrator to set the default public workspace for users and for users to set their own default public or private workspace. It can also display the workspace currently in effect for the user.
If quotes are missing around an argument, PCLI does not return any explicit error message, which makes it hard to spot the problem when you've got lines of programme. Instead, it just hangs.
This has been fixed.
This has been fixed. You can now use -v< label>* to delete all revisions between the specified label and the tip.
This has been fixed.
A script that invokes the ImportPDB command on multiple project databases may fail if the same project name exists in some of the project databases.
This has been fixed.
This has been fixed.
This has been fixed. Users can now update the workfile location in their private workspaces without having the Modify Project Privilege.
Running several PCLI scripts in parallel may result in contention for write access to the change.log file.
This has been fixed.
Power Builder 11 is now supported by Version manager 8.2.
The PvcsMerge tool on UNIX/Linux (Desktop Client and I-Net) does not label the revision panes. This has been fixed.
As of Version Manager 8.0.0.2, the RSE (Redirect Standard Error) executable no longer works with batch files that are being passed arguments. This has been fixed.
Users who did not have rights to update the Root workspace were allowed to set the workfile location for an individual workfile during an Add Workfile operation by clicking on the Advanced tab and selecting the Use workfile's current location option. However, the same user was not allowed to update the workfile location of the versioned file after it was added to Version Manager. This was seen as a discrepancy in the user's rights which could result in versioned files being copied to an incorrect/undesired location on check out/get. This has been fixed.
BEHAVIOR CHANGE: When adding files using a public workspace, users must now have the MODIFY_PROJECT privilege to select the Use workfiles's current location radio button.
In the PCLI client, an error message will be displayed prior to command execution if the privilege check fails:
The user UserName does not have permission to set the workfile location for project ProjectName in workspace WorkspaceName. Specify an alternative workspace or use the '-c' or '-co' option.
When creating a project, Version Manager automatically creates a directory with a unique name and a pvcsproj.ser file. Since those created directories are always 11 characters (Pxxxxxx.prj), if end users try to add work files under more than a 21 deep directory structure, it would fail because the total path length of the directory for the ser file exceeds the Windows path length limitation (256 chars).
This has been fixed as follows:
BEHAVIOR CHANGE: The suffix (.prj) will not be included in new project directories. The project directory creation process will first attempt to create a 3-character Pxx format directory name. If after 50 attempts it cannot generate a unique 3-character directory name, it will then attempt to generate a 7-character name Pxxxxxx.
NOTE There are two cases where this change does not apply. The first is for Version Manager 5.3 projects which will remain in the old format. The other is the process of moving a project where the target directory of the move already has an existing directory name as the source location. In this case, the new target directory to be created will remain in the old format.
SourceBridge may prompt for login even after being disabled. This has been fixed. Provided "Cleanup associations on undo checkout" is not selected in the SourceBridge Settings for the Project Database, the I-Net client no longer prompts for a Tracker / TeamTrack login.
This has been fixed.
BEHAVIOR CHANGE: It is now possible to delete or rename a blank version label via the desktop client, CLI, and PCLI.
This has been fixed.
If a project is imported from Version Manager using VLOGIN into Eclipse RIDE and then the password of the VM user is changed or removed, the user is prompted to authenticate each time Eclipse is restarted. This has been fixed.
Version Manager was enhanced so that it is possible to run it on Eclipse 3.1.1.
This has been fixed.
If requesting a file history would invoke a password prompt, Eclipse would hang rather than display the prompt. This was a threading issue and has been fixed. In addition, a new field was added to give users more control over login behavior.
BEHAVIOR CHANGE: A new checkbox, Remember password, has been added everyplace the Password field appears. To persist your password across sessions, select the Remember password checkbox, else you will have to login at the beginning of each session.
When in the Conflicts mode of the Compare Workspaces view, the Resolve All Changes button should be disabled as it can do nothing in that mode. This has been fixed by disabling the button in Conflict mode.
This has been fixed.
Special HTML characters like @ and & do not work correctly in passwords.
This has been fixed.
When doing a get and choosing "Prompt if workfile is unchanged", the prompt does not identify which file it is referring to. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. NOTE some features are not supported in VS Ride 2005, Eclipse and Visual Basic 6.0 SCC.
This has been fixed.
When Microsoft Windows locale is set to United Kingdom English, in few instances, error codes are displayed instead of error messages. This has been fixed.
When a solution is opened from source control in VS2005 RICH, projects referenced in the solution are automatically placed into sub folders below the solution file. A problem arises when projects were not originally under the solution file. In this scenario, VS2005 will display a warning that some projects could not be loaded because they could not be located. This has been fixed.
The solution explorer tree does not display the latest file status for check-in and checkout files. This has been fixed.
When a file is checked in with the "Update after keyword expansion" checkbox enabled, the keyword still displays an old revision. This has been fixed.
The "Apply to all remaining files" checkbox on the Confirm Check In Unmodified Workfile dialog is ignored.
This has been fixed.
This has been fixed. You can now check in a directly modified code-behind file.
This has been fixed.
BEHAVIOR CHANGE: Added the ability to work while offline. If you attempt to login into a project database while the system hosting the project database is unavailable, a Work Offline button appears at the bottom of the Log In dialog. Click the button to initiate an offline session. See the IDE Client Implementation Guide for details.
This has been fixed.
This has been fixed. The workspace settings are now properly persisted in the local workspace manager rather than returning to the user default after a restart.
Adding a solution to source control that contains a NetCOBOL project throws an error:
Exception of type SystemStackOverflowException was thrown
This has been fixed.
Overwriting a project file by Force Updating from Compare Workspaces removes the file from the SCC bindings in the Solution file. The result is that the project will not be loaded when the solution is opened from source control.
This has been fixed.
This has been fixed.
The check-in option Update local file after keyword expansion was implemented with inverted logic. This has been fixed.
If the login source of a Version Manager Project Database (PDB) is set to "HOST", and the account has a password, attempts to connect to the PDB through a File Server Path Map that has "Access Control Database" security enabled fails. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
The column sort order was not maintained after invoking an action, such as a Get or Check Out. This has been fixed.
If an embedded configuration file contains a promotion group, the project configuration file seems to be ignored. This can be seen by the Access List creation attribute not being placed on the file when a new workfile is added to source control. This has been fixed.
If an "&" character was used in any field on the Servlets tab of the Version Manager Application Server Admin, an "Error: 500" will be returned.
After doing a get on a file with a & character in the file name, clicking on the ... button next to the revision field to select a version label would produce an Error 500. After this has happened, the same operation would fail for every file regardless of the name. This has been fixed.
When trying to perform the action Merge "Revisions in different versioned files" using a file that resides at the root of a project database, attempts to select the file and revision using the ellipsis button in "Branch 1" or "Branch 2" will yield: "HTTP Status 500 ".
This has been fixed.
If the project database root directory name included a "&" character, the web server would give the following error: HTTP Status 404. This has been fixed.
In some configurations, when a user logs back into a servlet after it has timed out, attempts to perform a Get or Put operation can fail with the error:
java.lang.UnsatisfiedLinkError: pvcs.io.file.PvcsFileDirect.stat()
This has been fixed.
If the LDAP configuration for a project database is setup to follow referrals, an attempt to login can crash the Version Manager server when the referral logic has to kick in, for example because the UserID is unknown due to a typo.
This has been fixed.
Under certain circumstances, accessing both the LDAP Servers and the LDAP Configuration options in the Configure Project dialog could result in a loss of the list of LDAP Servers. This has been fixed as part of a renewed LDAP server configuration system..
When attempting to do a Get to a workpath that was currently not accessible, the incorrect workpath would be displayed in the error message. This has been fixed.
BEHAVIOR CHANGE: An option was added to the Web Client, Add Workfiles dialog to allow keeping revisions locked when adding them to source control.
This has been fixed.
When accessing a WebDAV folder on the file server and on refreshing the view, a memory leak is noticed. This has been fixed.
In Japanese edition of Version Manager, the Serena Business Mashups item ID information did not appear as a version label after checking in. This has been fixed. NOTE You require Serena TeamTrack 6.6.1.13 or Serena Business Mashups 2009 R1 editions or later to view this fix.
This has been fixed.
If a project was checked-in with different description for each work file, the check-in comments were unavailable in Team Track revision history window. This has been fixed. NOTE You require Serena TeamTrack 6.6.1.13 or Serena Business Mashups 2009 R1 editions or later to view this fix.
The Version Manager Web Server leaves a large amount of temporary files in the vm\inet\temp directory. This has been fixed. The directory now gets cleaned up at startup.
This has been fixed.
Users need the ability to immediately remove a stale login session, else the old session may remain open and consume a license until it times out.
BEHAVIOR CHANGE: To allow the user to close his stale login sessions, the following checkbox has been added to the login page: Automatically close all other sessions for your user ID on this server.
In some circumstances, when users switch from a subproject to another subproject or if the user tries to log into another servlet in the same server, all icons are grayed out. The solution was to restart the Apache TomCat. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. View files are now stored in the temporary file location (Microsoft Windows - C:\DOCUME~1\user\LOCALS~1\Temp\pvcs and in Linux - /tmp/pvcs)
This has been fixed. Temporary files are removed on restarting the server.
This has been fixed.
In the case of a private workspace and a user without SUPERUSER or UNLIMITED privileges, the link to the workfile location will not be displayed.
This has been fixed.
To add workfiles recursively the user was required to have the Create Project privilege even if the user had no intention of creating projects because the projects already existed. This has been fixed.
When doing a get or check out of a file to a workfile location where there is an existing workfile, the new workfile would overwrite the existing workfile, but would not inherit the folder's permissions. This has been fixed.
This has been fixed. Version Manager no longer throws an exception and stops working if it cannot create the initial ISLV.INI file (Windows) or islvrc file (UNIX) when trying to open a project database.
From the command line there was no way to set such workspace attributes as the default version. A command has been added to allow this. Use the -H option for information on using the new command. (An updated PCLI guide will be included in the 8.2 release.)
BEHAVIOR CHANGE: SetWorkspaceAttributes allows you to set the default version, base version, branch version, and default lowest level promotion group for the current workspace. You can clear the value in effect for the target workspace (to inherit one from a higher workspace or project entity). You can also display the values in effect for the specified project and workspace, including values inherited from higher level projects/workspaces.
Running CLI commands with wildcard characters contained in quoted strings (single or double quotes) on Solaris 10 results in a segmentation fault for certain directories. The same command without the single quotes works fine, but that would not be a workaround for path names that have spaces. This has been fixed.
If you have Remove lock on unchanged revision set in your VM project database, and you check in files associated with TeamTrack items through SouceBridge, Version Manager will label unchanged files with a TeamTrack item label. This has been fixed so that only items that are being checked in receive the label.
When adding workfiles and selecting the option to "Don't check in work file" the SourceBridge association can hang. Since no revisions exist in this situation, it is impossible for SourceBridge to associate a record. This has been fixed.
On UNIX with 8.1.4 or 8.1.4.1 installed in setsuid mode, running CLI commands like "get" as a user other than the setuid user may fail if the WORKDIR CFG file directive points to a directory that is not writeable by group (if a member of the group) or other. This defect was introduced in 8.1.4. It has been fixed.
Version Manager was enhanced so that it is possible to run it on Windows Vista.
If you tried to execute View or Edit a file that did not have a Windows file type association, an exception would be shown saying "pvcsexec.exe has stopped working". This has been fixed.
This defect was introduced in Version Manager 8.1.4.1. This has been fixed.
This has been fixed.
The customer is able to successfully generate a web service only once. Any attempts after that result in an error:
"IWAB0443E Error parsing webservices.xml: org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources."
This has been fixed.
This has been fixed.
If the user has a default workspace set for the project database, it is used regardless of what workspace they select while importing the project. This has been fixed.
BEHAVIOR CHANGE: The workspace the user selects during the project import will be used.
After installing VS2005 SP1, archive actions return assertion failure errors. This has been fixed.
The user is manually creating a folder on disk under the solution and adding solution items from that folder. When the solution is added to source control, the physical solution folder gets added to VM the same as project folders. When opening from source control, the solution files are retrieved first and then each project folder is opened individually. Since the folder containing the solution items in VM is not a project folder, it is overlooked. This has been fixed
This has been fixed.
A sufficiently knowledgeable person may be able to spoof or impersonate a login to the Web client if HOST ID is the login source. This hotfix increases the security of the HOST ID login source and the Web client. Details have been omitted from this description to limit exposure and reduce risk to those who have not upgraded.
The VM Web Server would randomly crash on UNIX, referencing pvcs.vm.vms.AccessDatabase.PvcsLogin() in the crash dumps. This has been fixed.
If you close the browser without first logging out of Version Manager, the license is held until the servlet timeout period passes. This has been fixed.
BEHAVIOR CHANGE: If you close the browser or use the same browser instance to open a different URL, the license is released immediately or within a few seconds, depending upon the browser used.
BEHAVIOR CHANGE: The password length limit has been removed.
Check-in time is GMT rather than the "Mexico City-New" timezone the server box is set to. This has been fixed.
This has been fixed. You no longer must be an Admin in order to install the Version Manager Web client to Internet Explorer 7 on a Windows Vista system.
Jobs are saved under the user account folder corresponding to the OS user running the VM Web Application server (instead of the VM user id). To Builder, it looks as though the job was created as "system" if the VM Web Application server is running as a service as LocalSystem. As a result, a user won't be able to update or execute the jobs created in the VM Web client, no matter if using the VM Builder integration (once they leave the wizard) or Builder Web Client. This has been fixed.
The Builder integration wizard prompts the user for a Search Path and Build Job name. However, unlike the Desktop client, it does not prevent the user from progressing through the wizard without choosing a search path. The result is a malformed build job. This has been fixed.
When executing a build using the VM/Builder integration, the step of fetching revision information using the VMMBI_GetRevInfo.pcli script will fail when encountering an archive that has no revisions. This has been fixed.
If you select a remote build machine instead of My Computer, the resulting job is not created correctly. The MachineName of the machine selected shows My Computer. This leads (I think) to Builder Web Client showing only one machine in the job (My Computer) and it having no activities. This has been fixed.
This has been fixed.
When creating a new build job through the Builder wizard in VM, the parameters in the task for the build job are not saved correctly. The <Command> portion is correct, but the other parameters where the build job is derived from do not have the information necessary to reconstruct the commands in the Builder Web client. This has been fixed.
BEHAVIOR CHANGE: Changed the "options" command patterns field to include the integration parameters for the associated buildmake and OM tasks. This was done because it was possible not to have any OM command pattern options which triggered the Openmake Web client to reset all of the build job parameters back to their defaults if the build job is changed from the Web client.
The VSS2VM tool doesn't run in the Japanese locale, throwing an EXCEPTION_ACCESS_VIOLATION error. Attempts to run the converter in the English locale as a workaround fail if a filename or a label has a DBCS character containing 0x5C.
This has been fixed. You can now run VSS2VM in the Japanese locale.
This issue occurs only if an archive is empty, that is the archive contains no revisions.
This has been fixed.
Manually refreshing the Desktop client (View | Refresh) can be very slow. Although it is not hung, one could easily assume that it is due to the slow progress.
This has been fixed.
This issue results in the following error: "[Info] No journal information exists matching the requested specification".
This has been fixed.
Patch installer does not detect whether the executables it is replacing were running in setuid mode.
This has been fixed.
When the Builder 6.3.1 to 6.41.1 patch and build job conversion is performed, a space is added to the end of each environment variable. When the Version Manager integration loads one of these converted build jobs, it fails to populate the integration dialogs with the information stored in the environment variables. To the user, it appears that the build job information has been lost. If the user goes through the dialogs and saves the build job, all of the original build job information is lost. However, if the spaces are manually removed from the build job, the VM integration correctly populates the dialogs.
This has been fixed.
A build based on the promotion model requires that the target promotion group be on the TGT file. Else the integration refuses to start the build definition and an error is returned: "No targets found with: group name".
This has been fixed.
The integration was looking for a TGT file revision to use to get the project name from. It was doing an exact match for a promotion group. Instead it needed to chase the promotion chain to find a revision. For example if the promotion model is dev, qa, prod and the TGT archive does not have the "dev" promotion group assigned but does have "qa" assigned and the user specifies that they want to build at the "dev" level, then the integration would first look for a revision at "dev" and when that is not found it would then look for "qa" which it does find.
Certain combinations of filter options could produce incorrect results.
This has been fixed.
Customer request to make workspace information available. The follow event information has been added: EventWorkspaceBase; EventWorkspaceBranch; EventWorkspaceName; EventWorkspacePromoGrp; EventWorkspaceVersion. See the Serena Version Manager Administrator's Guide for more information.
Open (Serena-SB | Open from Serena Team Provider) fails if subproject/folder name is more than 60 characters long.
Error Message:
Failed to open Project VTPTerminierungWAR - Error Code: SCC_E_OPENNOTPERFORMED
This has been fixed.
IDE's hang onto license longer than desired after being closed.
This has been fixed.
Add SCC and Rich Integration support for Rational Application Developer 7.
This feature has been added.
IMPORTANT! See Integrating with IBM Rational Application Developer 7 in the Install_Info.html readme file for information on installing this integration.
When checking in multiple files, the Use for all checkbox is not honored if one or more of the checked out revisions are non-tip revisions.
This has been fixed.
This has been fixed.
The integration correctly handles projects outside of the solution if the projects and solution are added to source control at the same time. However, it does not work correctly if the project was added to the solution after the solution was controlled. In this case, Open from Source Control will fail for the added project.
This has been fixed
Selecting the Servlets tab of the Version Manager Application Server Admin may sometimes result in the error:
"Unable to open properties file C:\Program Files\Serena\vm\inetprops\PVCS Servlets.properties".
This has been fixed.
At startup, it does not log on automatically. Instead the Login page appears with the Username field grayed out and a field to put a password in.
This has been fixed.
This has been fixed.
In some circumstances, using vtransfer -r to make a case-only name change to an archive could result in the deletion of the archive. This has been fixed.
This has been fixed.
The customer wants to see those files where the promotion group and the label are pointing to the SAME revision. At present, the filter cannot provide this information, since the invert option ("Show files not matched by this filter") also shows files that don't have the label and/or group at all.
The filter has been enhanced to support the customer use case.
Customer's build hangs when a PCLI Get command randomly locks up after an otherwise successfully completion.
This was an issue with licensing. This has been fixed.
Done.
If a copy project operation fails due to exceeding the path-length limits of the operating system, the error message did not state which specific projects exceeded the O/S limits. This feature has been added.
Various operations in setuid mode would fail for invalid reasons. This has been fixed.
This has been fixed.
Completed.
The combination of enabling case sensitive client path and creating a UNC style client path from Windows on a UNIX file server, can result in backslash (\) characters in the UNXI-based project database. This has been fixed.
This has been fixed.
In some obscure circumstances, Path Map security on the File Server might be ignored. This has been fixed. For reasons of security, details of this issue will not be published.
For increased File Server security, Serena recommends upgrading the clients as well as the File Server to release 8.1.4.
To mitigate this issue on older releases and to maximize security on 8.1.4:
Ensure that utility access is restricted. (On the Options page of the File Server Admin, change Enable Utilities to LocalOnly or to Off.)
Limit login access to the system that is running the Version Manager File Server so that only Version Manager administrators can login to the operating system.
Both the AddUser and DeleteUser commands are equipped with the -pp option to specify a project. According to the manual, the function of this option is that it:
"Specifies the project or folder to which the user will be granted access"
When you run the command with the -pp option that command completes successfully, but the user is added to the ACD defined at PDB root level, not the one associated with the specified project level. This has been fixed.
Show History returns "Unknown Exception at line 2446 in VMNMArchiveFile" instead of the expected message of: "No history exists matching the requested specifications". This has been fixed.
The data in the Folder Name field is unreadable. One can type correct data in there, it is still unreadable, but it works. This has been fixed.
Command line users may occasional see the confusing message "DTK after clearing cache mkfile returned -1". This has been fixed.
The History pane has been enhanced so that it can display revisions using a tree structure so that the hierarchy of branched revisions can be shown.
Added Force Branch option at check in.
Migration of Visual Studio 2005 web projects from the SCC integration to the rich integration fails. This has been fixed.
Added a configuration option to the desktop client so that the administrator can require users of the rich integration to Visual Studio 2005 to check out files in order to edit them.
Customer is trying to authenticate to TeamTrack by selecting the TeamTrack Login icon (not by launching TeamTrack from within the IDE - which works fine) and is getting "Invalid User" in the issues pane. Everything looks set up properly. This has been fixed.
This support has been added.
If one archive is renamed, moved, or deleted all files will appear as incoming changes when compare workspaces is run. This has been fixed.
A user may log out and not be able to log back in from the same system with the same ID until the web server is restarted. When attempted, the login dialog would hang (with the OK button showing Wait). This happened intermittently. This has been fixed.
If you run a PCLI or CLI command from an Event Trigger, that command will cause a second license to get consumed. This has been fixed.
This causes problems for sites that needs to access the server from both sides of a firewall, where the server has distinctly different names depending on what side you look from. This has been fixed.
If the top level project contains no files
and you do a recursive get based on a label
and you specify a non-default "Copy to" location,
then the first sub project will be placed in the specified location, but any others will be placed in the default location.
This has been fixed.
This has been fixed.
If a subproject has an access control database, LDAP authentication may not work correctly. This has been fixed.
If HostID is the login source and a subproject has a different password than the project database, you will lose access to the project database level once you log into the subproject. This has been fixed.
If the option to Ignore Ctrl-Z is enabled, the last line of the file will not be displayed by the Merge Tool. This has been fixed.
When accessing TeamTrack through the Eclipse RIDE interface, concurrent licenses are not released by the license manager after the TeamTrack window or the IDE itself is closed. This has been fixed.
If the path to an archive, or the archive name itself, contains double-byte characters, attempting to unsplit the archive will result in data loss. This has been fixed.
Under some circumstances, history reports on Windows sometimes fail. On UNIX, they sometimes crash. This has been fixed.
PCLI VLOG -bv can be used to find out what revision a version label is assigned to. If no label is specified the system should report on the default version label, but it does not--it gives a report showing all version labels on all revisions. This has been fixed.
This has been fixed. Version Manager now works with full length multi-byte paths in Windows.
Filters, such as "Locked by" sometimes do not accurately reflect the current state of the archives. This has been fixed.
The advanced filter would confuse a label that contained a comma for two separate labels. This has been fixed. It is now possible to filter on a label that contains a comma by setting the delimiter character to a semi colon (or the other way around).
If the case of the user id in the access control database differs from the case of the user id for the host login source (i.e. admin vs. Admin), the user can do everything with a file (lock, unlock, etc.) except a check in. A check in results in "Could not complete action because the revision is not currently locked by this user." This has been fixed.
A Windows web client hitting a UNIX/Linux server will receive the incorrect End of Line character if the archives are split. This has been fixed.
SSL connections fail after restart, but will work if restarted multiple times. This was a defect in Tomcat. This has been fixed.
This has been fixed.
The underlying cause of the error has been fixed, also the error messaging has been improved to better identify the true cause of certain errors.
An error similar to the following would be returned and the operation would fail:
ChangeMan Version Manager could not create the semaphore "//FS/...../archive-arc" for this project....
A file that has been branched multiple times and that has had an interim branch renamed will fail with an "unable to build branch" error. This has been fixed.
If your project database used LDAP as a login source, an attempt to access any of these security dialogs:
- Admin | Security | Users
- Admin | Security | Privilege Sets
- Admin | Security | Access List Groups
- Admin | Security | Show Report
Would result in an error similar to the following:
12:03:40 Apr.14.06 [Error] You have encountered an internal processing error: 50 (PVCS_E_NO_USER_ID: Unable to obtain the user ID.)
If a Version Manager client is configured to access a Version Manager file server that is unavailable, the client will hang. This has been fixed.
SCC and rich integration support has been added for Visual Studio 2005.
NOTE This new integration resolves most limitations and issues associated with the Visual Studio .NET 2003 integration--but only for Visual Studio 2005. The integration to Visual Studio 2005 is a separate install from the integration to Visual Studio .NET 2003, so it cannot resolve any issues in the Visual Studio .NET 2003 integration.
This feature was added to the rich integration to Visual Studio 2005.
In Visual Studio 2005, the results text distinguishes between get and check out operations.
When adding large solutions to source control, the solution is added to Version Manager correctly, but the IDE becomes unresponsive. Once the IDE has been killed and relaunched, the solution is under source control context. This has been fixed.
Adding web projects to source control resulted in the following error:
"Unable to create a session for VMPro - Failing ClientAPI unable to createSession Possible UVE_Lib definition Error"
This feature is supported in the integration to Visual Studio 2005.
This is fixed in the integration to Visual Studio 2005.
When attempting to open a solution from source control, the user may receive the following error:
"Unable to create session for \\CEI\InformationTechnology - Failing ClientAPI unable to createSession Possible UVE_Lib defintion error"
This was seen on systems with Crystal Reports 10 and also sometimes if a web project had been loaded first. This has been fixed.
Open From Version Manager produces the following error if the root folder contains both the project and solution file:
"System.NullReferenceException: Object reference not set to an instance of an object"
Having both the solution and project files in the root directory is not a supported configuration.
The new integration to Visual Studio 2005 will: Catch the exception, add a logging message to indicate the error, and skip the solution/project file. This allows the remaining solutions to be opened.
This is fixed in the integration to Visual Studio 2005.
This is supported in the integration to Visual Studio 2005.
This is fixed in the integration to Visual Studio 2005.
End-of-Line translation is now performed correctly.
This patch includes several hotfixes that have previously been released. Since the patch installer does not remove content from the Install_Dir\vm\common\lib\patch directory, any pre-existing patch files will still be present after installing this patch. This could have adverse impact because the "old" content in the patch directory will be used instead of the "new" content in the vm.jar that was shipped with this patch.
To avoid potential conflicts, remove any files in the Install_Dir\vm\common\lib\patch directory before installing the 8.1.2.2 patch. If you have any patches newer than 8.1.2.2, re-install them after installing 8.1.2.2.
If a file with a double-byte name is added from a Windows-based system, the UNIX Version Manager client will hang when it tries to access it because it uses a different and incompatible code page. This has been fixed for the PCLI, Desktop client, and Web client.
However, some CLI operations (such as Get and Put) will continue to fail if the workfile name in the archive contains a character incompatible with the client code page. To work around this issue, use the "archive(workfile)" syntax to explicitly pass a workfile name that is valid in the client's code page.
Intermittently, and on a non-reproducible basis, the contents of a random archive would be replaced by the contents of another. This has been fixed.
When File Server archives are updated (either unsplit or the meta-data part of a split archive), the updated archive remains in the ARCHIVEWORK directory and is not moved over to the FS_TMP directory. Because of this, the cleanup routine will not be able to cleanup these temporary files. This has been fixed.
Quoting a command string containing brackets [] was not sufficient to make it work correctly. This has been fixed.
If a PCLI command runs into an internal error, instead of printing that error the application will crash. This has been fixed.
Customer would like Version Manager to warn if the project structure gets too deep when creating a new project so it won't hit the Windows limitation of 256 bytes. This feature has been added.
When running an EventTrigger on Linux kernel 2.4.20 or beyond, the following error appears:
You have encountered an internal processing error: 106 (PVCS_E_TRIGGER_FAILED: The event trigger failed.)
If the trigger is of the Pre* type, the operation will subsequently fail. This has been fixed.
On some Linux platforms, a non-expected error message is displayed while opening a History Report or Journal Report, even though the report is shown correctly. Likewise, external PCLI commands (run -e) execute correctly but return an error code indicating failure. This has been fixed.
If an archive has been deleted or corrupted outside of the interface, all files will be erroneously marked for removal at the next synchronization. This has been fixed.
Several processes continue to run when the user attempts to close the IDE. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
The Show Issue report title is replaced with the title of an issue from the list. This has been fixed.
Intermittently lose the ability to see existing version labels and promotion groups.
We were not able to reproduce this issue in house, but are reasonably sure we have resolved the cause. If anyone continues to experience this issue, we would like to hear more about your configuration, usage, etc.
Adding a large number of files while associating issues using TrackerLink may throw a General Exception when the login authentication method is LDAP. This has been fixed.
This has been fixed.
Some text may still appear a bit smaller than expected, but for the most part this issue has been fixed.
In order to make sure that Version Manager got project information (such as configuration file locations) from the Version Manager File Server, you had to make sure that the location was not also mapped by an entry in the nfsmap file. This has been fixed.
Error messages for a variety of circumstances have been made more specific and helpful. Some specific instances include:
DEF81501: vsplit does not report cause for failure when File Server authentication fails.
DEF81504: VTRANSFER error message "Move Failed!" is much too generic.
DEF82350: Error due to lack of permissions on ACDB does not get reported as such.
INT82352: Inability to create semaphore files should be reported as such.
ENH78863: You have encountered an internal processing error 117.
DEF78667: Fatal permission problems on %TEMP% and %FS_TMP% shall be identified as such.
DEF80554: Wrong error message when AIX user unable to write to /tmp/pvcs and /tmp/pvcsfs.
If you login to a project database using LDAP and then log out without closing the GUI, upon logging back in you do not need to supply a password in order for the login to succeed. This has been fixed so that the LDAP password is required when you log back in.
Open VM with the option 'open any previously opened project databases'. Log in to one pdb. Highlight a file in the versioned file pane. Then click on the plus sign (+) next to the name of another pdb on your list. If this pdb has as its login source "host id" and needs a password, this action hangs the whole of VM - you can only exit using Task Manager. This has been fixed.
Unix client gets "java.lang.IllegalArgumentException" with PCLI put command if past revision contains specific Japanese character. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Other than the scroll bar, this has been fixed. The scroll bar still may not behave correctly on large files. Use the Next, Previous, and Go to line features instead.
This has been fixed.
This has been fixed.
Attempts to manually launch the Diff/Merge tool via the executable (pvcsmerge.exe) fail with a licensing error.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This feature has been added.
This has been fixed.
This has been done.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This change has been made.
This has been fixed.
This has been fixed.
This feature has been added.
This feature has been added.
This feature has been added.
This has been fixed.
This has been fixed.
The Desktop Client would lock up after displaying the login dialog for a second project database. This has been fixed.
In the .NET IDE, if you add a project from Version Manager and specify the local workspace used by the current solution, files with names similar to those in the current project may fail to open. You must then reopen the project from source control to another location so that you can clean things up. This has been fixed.
This has been fixed.
This has been fixed.
Running the operation twice would complete the process. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
If ARCHIVEWORK and WORKDIR are defined in the configuration file as "", which resolves to current directory, all file actions fail. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This affects both the Web server and the File server.
This was fixed in a previous release cycle, but was reintroduced before GA. This has been fixed.
This feature has been added.
This has been fixed.
This has been fixed.
This feature has been added.
This has been fixed.
Login to a PDB located on a file server may fail if the user name contains high ASCII or Asian characters. This has been fixed.
This has been fixed.
This has been fixed.
CLI commands using an @list may not execute correctly or may fail with a protection fault. This has been fixed.
The fix for this defect was omitted from the previous patch. This has been fixed.
The closing "$" character may not be properly detected, resulting in the loss of file data up to the next "$" character or the end of the file, which ever comes first. This has been fixed.
NOTE As part of this fix, the syntax for fixed length keyword expansion has changed. This change is not yet reflected in the documentation, but is included below:
If the content of a keyword contains a "$" character, you must use the new syntax:
$Keyword::$123456::$
Where:
Keyword is the keyword.
123456 is the length delimiter. The length is determined by the number of characters. Any characters can be used as the length delimiter.
::$ marks the beginning and the end of the length delimiter character string.
If the content of a fixed length keyword does not contain a "$" character, you may use either the new syntax or the original syntax, which follows:
$Keyword::123456$
There is a Copy button to allow you to copy the results of an operation to the Clipboard. This button does not work if you are using a workstation installation installed from a UNC path. This has been fixed.
If you assign a version label or promotion group that matches a revision number to a different revision, you can no longer access the revision with the matching number using the desktop client, the web client, or the PCLI. For example, if you apply the label "1.5" to revision number 1.7, it is longer be possible to access revision 1.5, because attempts to access revision 1.5 yield revision 1.7.
This has been resolved. Whenever the Revision field or corresponding PCLI option (-r) has a value that looks like a revision number (like 1.5 or 1.4.2.1), Version Manager tries to get a matching revision number and not check whether there is a label or group by that name. If you need to use the Revision field or corresponding PCLI option to access a version label or promotion group that looks like a revision number, precede that label or group with a backslash (\).
Caution: In dialog boxes where you pick a label or group from a list, this release of Version Manager does not automatically precede the label or group with a backslash when the label or group looks like a revision number.
To avoid confusion, we strongly recommend never using labels or groups that look like revision numbers.
This has been fixed. See DEF78155.
This has been fixed.
This has been fixed.
If you execute vsplit -u from the directory containing the metadata archive, the archive may be deleted.
This has been fixed.
This has been fixed.
Under some circumstances it was possible to see LDAP passwords. This has been fixed. In the interest of security, the details of this defect will not be described here.
This has been fixed.
In certain circumstances, unsplitting a split archive will cause the metadata of the new unsplit archive to reflect the information stored in the delta.d file.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Using the Version Manager web client with an Apache 1.3.x server configured to use EAPI produces an error when you try to start the Apache server. This has been fixed.
If a default version label is defined, the History Report ignores the specified revision and always checks the Default Version against the tip revision. This has been fixed.
Following the otherwise successful completion of a command or script, PCLI prints:
Exception in thread "main" java.util.ConcurrentModificationException
at java.util.Hashtable$Enumerator.next(Hashtable.java:976)
at pvcs.vm.VmFlexFactory.checkinAllLicenses(VmFlexFactory.java:52)
at pvcs.cmd.CmdProcessor.pcliMain(CmdProcessor.java:202)
at pvcs.cmd.CmdProcessor.main(CmdProcessor.java:174)
This issue has been resolved.
When the Version Manager desktop client opens on a remote X Windows display, screen updates can take a very long time.
This has been fixed.
After you perform certain operations in the project pane of the Version Manager desktop client, the project pane occasionally collapses, requiring you to browse back to your original project.
This has been fixed.
The default semaphore suffix used by vsplit (??$) results in a failure when you try to split an archive that has a dollar sign ($) in the file-name suffix.
This has been fixed. The vsplit command now supports the -C option, which you can use to pass the command a configuration file that redefines the semaphore suffix to be used (for example, SemSuffix = +-sem). For more information, see the SemSuffix directive in the Serena PVCS Version Manager Command-Line Reference Guide.
When an event trigger executed from a UNIX client tries to access a file on a File Server (for example, through a CLI command), that trigger fails with a SOAP FAULT message.
This has been fixed.
The description of the different types of configuration files is somewhat confusing.
This has been fixed.
This has been fixed.
If TRANSLATE is on, the "unchanged" prompt does not appear on Unix. This has been fixed.
When vtransfer -r is used only to change the case of the name of an archive, it can result in the loss of the archive.
This has been fixed.
A UNIX File Server configured to be case-insensitive sometimes treats an archve in a case-sensitive manner. Such archives are temporarily unavailable to the Version Manager clients.
This has been fixed.
The Version Manager Web Application Server process used to provide the File Server, the Version Manager Web Server, and WebDAV services sometimes shuts down on Windows systems when someone logs off from that system's console.
This has been fixed.
Attempts to run vsplit or vsql against a DBCS (double-byte character set) archive on a File Server locks up those commands. This has been fixed.
In Version Manager 8.0.2.x, the Visual SourceSafe convertor fails with the message "ERROR: PVCS_E_ACCESS_DENIED". This has been fixed.
A user without rights to create a project in Version Manager in other environments is able to create a project in Eclipse/WSAD environment. This has been fixed.
This has been fixed.
This has been fixed. For details, see the online help for the new promotion dialog boxes.
When an https: connection string is specified to connect to the File Server, the IDE integration prefixes that string with http:. This makes it impossible for the IDE integration to connect to the File Server via HTTPS.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Some of the default configurations in the Tomcat server used by Version Manager can expose potential vulnerablilities.
This has been fixed by switching to Tomcat 5 and by modifying and removing vulnerable configurations.
Under certain circumstances (generally involving users logging off), the temporary files stored in the File Server client cache directory are not cleaned up on exit. This issue is being addressed by a new feature that automatically cleans up old files whenever a Version Manager session first contacts the File Server.
You can exert some control over this feature by adding entries to your islv.ini file.
NOTE: Time values are in seconds by default, but you can specify minutes or hours using the <n>m or <n>h syntax.
New settings of interest are as follows (shown with the default values that will be used if the entry is absent):
[PVCSGUI_6.5]
pvcs.fileserver.cache.cleanup.frequency=12h
Wait at least 12 hours following a cleanup operation before attempting to clean up the cache directory again.
pvcs.fileserver.cache.cleanup.age=24h
Clean up all files that are at least 24 hours old.
pvcs.fileserver.cache.cleanup.mode=m
Determine the age of the file based on its modification time ('m'). Can also be set to 'a' (file access time) or 'c' (file creation time). The default is highly recommended as some file systems could exhibit bad behavior with the other options.
NOTE: The location of the File Server client cache directory is determined by the environment variable FS_TMP or, if FS_TMP is not defined, FS_TEMP. If neither is defined, the directory defaults to %TMP%\pvcsfs or, if TMP is not defined, %TEMP%\pvcsfs.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed for the Solaris platform.
This has been fixed.
This has been fixed.
When using the browse capability for local file systems or when trying to open a project database, some users receive the following error: "There is no disk in the drive. Please insert a disk into drive A:."
This has been fixed.
Clicking the file browse button in any Version Manager web client dialog box can cause an error message to appear in the Java Console referring to an A: drive security problem. In that case, the browse dialog box does not open.
This has been fixed.
The job fails with one or more of the following messages:
VMMBI6200: verify_gets: Error: The get for: '<file_name> failed', the work file time does not match:
If the current time is within Daylight Saving Time, the error message is produced for those Version Manager workfiles that have a "last modified date" outside of Daylight Saving Time. Likewise, if the current time is outside of Daylight Saving Time, the error message is produced for those files within Daylight Saving Time.
The failure occurs only when the build directory is located on a FAT or FAT32 disk volume. It does not occur on NTFS volumes.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. Wheel mice now work correctly in the desktop client, and they work in any web client that uses version 1.4.1 or higher of the Jave Runtime Environment (JRE).
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
There is no good way to obtain the entity path for the versioned file for which an event trigger is executed.
This has been fixed. There is a new event parameter, EVENT_ENTITY_PATH, for all the event types, and the EVENT_WORKFILE parameter is enabled for the events Lock, Unlock, Promote, and Create Archive.
If a user is a member of an access list group, and that group is specifed in an archive after an empty access list group, the user cannot see the revisions even if the user has unlimited privileges.
This has been fixed.
CLI commands on UNIX interpret the SemaphoreDelay as a value expressed in seconds rather than tenths of a second. This has been fixed.
This has been fixed.
A certain combination of ACD privileges can make a user UNLIMITED. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
If a specific port is specified for the license server during installation, Version Manager adds an extra @ character in islv.ini.
This has been fixed.
This has been fixed. The AddUser command now has a new -ps option for specifying a custom privilege set.
The following example creates a new user with Developer and PromoteToQA privileges:
AddUser -ps"Developer,PromoteToQA" Simba
The -ps option is not required. If you specify the option, you must include an argument specifying a list of one or more privileges. Use commas to separate multiple privileges. If the argument contains spaces, enclose it within double quotation marks.
If you do not specify the option, the new user will have the Unlimited privilege set.
If the default font size used by Version Manager is too small in the your UNIX environment, you can increase the font size through the pvcs.fontSize property; however, some dialog boxes do not reflect the change.
This has been fixed.
This has been fixed.
This has been fixed.
If you are a member of multiple privilege sets and one of these privilege sets is restricted to a promotion group, attempts to view the Granted Privileges on an archive (right-click | Properties) generates a Java exception (Windows) or causes a crash of the desktop client (UNIX).
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. The command now returns –1 if the import fails.
This problem occurs when your Access Control Database has a file-name extension of .acd.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
In a heterogeneous environment where the Client Name of a Path Map is specified as "windows style", a UNIX client cannot read the pvcsldap.ini file from the File Server.
This has been fixed.
If you check in an unchanged file, and the option to not check in an unchanged file is enabled, the file is unlocked as expected, but a prompt asks whether you want to merge the branch to the tip (even though there may be no branch revision).
This has been fixed.
This has been fixed.
This has been fixed.
When you delete a file from your workspace, you get the option of deleting the file from the Source Control Tool; however, if you do not delete the file from the project at that time, you do not get the option again when you run synchronize.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Using the Diff/Merge tool from the Version Manager web client on UNIX shows the revision contents in DOS style, even if the archive being examined has the TRANSLATE archive attribute enabled. If you compare a revision against a checked-out workfile that has TRANSLATE enabled, the Diff/Merge tools reports all lines as being different.
This has been fixed.
This has been fixed.
This has been fixed.
When the user ID is the same throughout the PDB but the password is different among projects or subprojects, the login dialog box does not appear when the user selects the plus sign (without selecting the folder) to expand a project or subproject tree.
This has been fixed.
This has been fixed.
This has been fixed.
If a version label starts with a digit, the PCLI isDifferent command fails, and the error message displays the wrong version label.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When the $(Command) alias is used in configuration files, it incorrectly identifies PCLI as "VMGUI" on UNIX and Linux platforms.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Access to a File Server PDB is denied when you log in using a DBCS (double-byte character system) ID. This has been fixed.
If your ARCHIVEWORK and WORKDIR directories point to a slow drive, such as a network volume, attempts to update an archive on the File Server may corrupt the archive. Because ARCHIVEWORK and WORKDIR default to the current directory for command-line interface (CLI) operations, you could trigger this result just by running a CLI command when the current directory is a mapped network drive, or even by using a local drive on a busy system.
This has been fixed.
This has been fixed.
The security report (Admin | Security | Show Report) shows the passwords stored in the ACD if the user running the report is a SUPERUSER. Because it is fairly easy for an UNLIMITED user to become a SUPERUSER, we need a way to disable this feature.
This has been fixed. By default, the Security Report no longer shows passwords, even if the user running the report is a SUPERUSER.
To allow a SUPERUSER to see passwords (as they could prior to this change), there must be a file called:
VM_Install_Dir/vm/common/pvcsprop/pvcs/vm/security.properties
with these contents:
vm.showpasswords=enabled
New revisions are not created when you check in files from Interdev. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When the File Server and the Version Manager web server are running in the same instance of Tomcat, journal files and reference directories are sometimes modified with information pertaining to delta.d file changes. This has been fixed.
The setting of the %TEMP%, %FS_TEMP%, and %FS_TMP% directory environment variables can cause heap corruption that leads to Java "unknown exception" and other failures. This has been fixed.
These occur if there is no diskspace left on the Temp directory defined under File Server Administrator | Options. This has been fixed.
If temporary directories are not specified, temporary archive files get created in the product installation directory. This has been fixed.
This has been fixed.
This has been fixed.
With LDAP authentication in place, users sometimes receive an error stating that they lack the privileges to access files. This has been fixed.
This has been fixed.
The documentation suggests that a read-only network share is a valid location for the servers.ini file; however, this configuration causes error conditions.
This has been fixed; the product now supports this documented configuration.
If the chosen or default device-specific temp directory is invalid because the specified name already exists as a file name, attempts to update files through the Version Manager File Server result in these files being replaced by 0-byte files.
This has been fixed; an appropriate warning now appears.
When you run the vsplit command, the .??$ semaphore file that gets created for the archive does not get removed. This has been fixed.
This has been fixed. The section on licensing workstation installs has been removed; the subject is covered correctly in another part of the guide.
This has been fixed.
The default location for the new pvcsldap.ini file is the Version Manager installation directory, which causes problems when the Version Manager installation is local.
This has been fixed; the default location is now the root of the PDB.
If the case of the login ID returned by the HOST login source changes (for example, as a result of the customer switching domains) in a case-insensitive PDB, the private workspaces for the users are permanently deleted. This has been fixed.
To preserve path names with spaces in an @list, you normally need to enclose the invidual path names within quotation marks; however, the vsplit command silently ignores quoted path names. This has been fixed.
The file server client does not honor the total cache file size limit. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
If you are using version 4.0 or 4.0.1 of Collage and you try to interface Version Manager and Collage, the files are not uploaded to Collage. This has been fixed.
This has been fixed.
This has been fixed.
From within an IDE, performing a Show History operation on revisions locked by a specific user returns all users. This has been fixed.
If a user that does not have version label permissions within WSAD connects to a Version Manager Project Database and attempts to label a file from within WSAD, the operation seems to proceed with no errors; however, viewing the file in Version Manager reveals that it does not contain the version label. This has been fixed.
Populating your Access Control Database by adding authenticated LDAP users using the auto-create feature doesn't work if you are using the Version Manager web client. This has been fixed.
This has been fixed.
The documentation incorrectly refers to a Tracker project rather than a Tracker server in connection with configuring servlets. This has been fixed.
This has been fixed.
Though we are shipping mod_jk 1.2.1 for Apache 1.3, a customer noticed that we are still shipping the 1.2.0 release for Apache 2.0 on Solaris. This has been fixed.
If you run VSPLIT on archives stored on the File Server, and the archives contain an AccessList at the time of the split, attempts to retrieve revisions from the archives will fail. This has been fixed.
When you use Version Manager Server 7.5.1.0 on Windows with a client on Solaris, the execuatlable bits of a read-only workfile are lost after a check-in. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
UNIX: Any attempt to start the Version Manager web server with daemons enabled produces an error.
This has been fixed.
When a sufficiently large promotion model is being edited in the desktop client, it gets deleted from the CFG file. This has been fixed.
This has been fixed.
When not utilizing File Server, Version Manager should recognize a split archive and display a useful message stating that the archive is split and must be referenced through a file server. This has been implemented.
Changes made to web.xml are not read until the server is restarted, and may cause incorrect operation of the server. This has been fixed.
Licenses allocated to Version Manager web-client user sessions are never returned to the license pool; the license should be returned to the pool five minutes after the user logs out from the web client.
This has been fixed.
The client appears to work but applet operations fail. This has been fixed.
When the customer performs simultaneous Show History operations on multiple PDBs (in multiple browser windows), Version Manager hangs. This has been fixed.
This has been fixed.
On a multiple-file check-in or add, the Use Change Description for all check box is not selected by default. This has been fixed.
If you set up a post-put event trigger, configure the PDB to remove the lock on an unchanged file, check out a file without changing it, check in the file with "Prompt" selected for unchanged workfiles and with "Keep read-only workfile" selected, and reply "no" when asked if you want to check in an unchanged file, an event trigger fires even though no check-in occurred. This has been fixed.
This has been fixed.
If you perform an action that results in an error in the desktop client, the Details window takes about five seconds to auto-expand. This has been fixed.
The documentation for the pcli list -ca command contains errors (:= should be =). This has been fixed.
If the selected workfile location does not match the project's default location, selecting "Don't check in workfile" changes the default workfile location. This has been fixed.
The comma should remain the default delimiter. This has been fixed.
The PCLI manual contains references to PCLI PR and PCLI ID (without the underscore). This has been fixed.
In the Add Workfiles dialog box, clicking the Browse button sometimes displays a path with an extra \*.*. This has been fixed.
This has been fixed.
When checking if the allusers.ser data in memory is out of date compared with the persistent data, the code looks for the file in the wrong directory. This has been fixed.
If you modify an existing user to have an expiration date of today (or any date before today), a blank dialog box appears and cannot be dismissed except through the Windows Task Manager. This has been fixed.
The IsDifferent command always performs the comparison against the tip rather than the default revision. This has been fixed.
When you enter a new user name in the Switch User dialog box, the user name in the status bar is sometimes repainted incorrectly. This has been fixed.
The -v option should be treated as a label and accept numeric characters without requiring escape characters. This has been fixed.
This has been fixed.
This has been fixed.
The PCLI commands ImportArchives and AddFiles do not observe the Run options -y, -n and -np. Instead of accepting the Yes, No, and No Prompt options being passed through Run, the functions still pass the question to the user.
This has been fixed.
This has been fixed.
If you try to update an ACD file (for example, add a user) and the ACD file is flagged by the operating system as being in use (for example, because another process is reading the file), the ACD file is deleted and must be restored from backup. This has been fixed.
During import, , a corrupt archive will generate the error "Unexpected error: java.lang.NullPointerException" and halt the process. This has been fixed.
This has been fixed.
On a branch, checking in a file creates a new revision even with a "remove lock if unchanged" option selected ("Don't check in" or "Prompt" when the file is unchanged). This has been fixed.
This has been fixed.
You can no longer highlight a project by selecting the Project Database root on the left side (Project Pane) and then typing the first letter of the project you want to work on. This has been fixed.
"Show Journal" doesn't display the proper journal information when the "Date Range" is set from the morning of the current day to the night of current day, even though actions have taken place on the versioned file during the current day. This has been fixed.
If you run two exports within a few seconds of each other, duplicate IDs can occur. This should be avoided, and a note has been added to the documentation.
When archive operations are performed between midnight and 1:00 AM during Daylight Savings Time, the date incorrectly specifies the previous day. This has been fixed.
This has been fixed.
The -a option of the Readline command should be able to assign the individual words in a line of input to elements of an array; however, all words are placed into the first array element. This has been fixed.
The Version Manager product link is out of date in the installation guide. This has been fixed.
When you edit a large promotion model in the desktop client, the model gets deleted from the configuration file. This has been fixed.
The installation does not allow you to select a Program Folder for all users on the machine; it lets you select a Program Folder only for the current user. This has been fixed.
When you access a project database through a file server, the journal files do not get created or updated with your last action. This has been fixed.
The vtransfer command option -f to fix a RevLib path does not work. This has been fixed.
When accessing a project database through a file server, you may get lock errors after attempting to check in files. This has been fixed.
In the desktop client and web client, long label names are not allowed to fill up the available space in the Filter Selection list, and so get unnecessarily truncated. This has been fixed.
This has been fixed.
For Eclipse-based IDEs, the Serena menu and the source-control glyphs are not enabled by default. The information is saved in the user workspace, so you have to enable the menu and glyphs for each new workspace you create. This has been fixed.
When the TD plug-in is installed, it should create the following registry key:
HKEY_LOCAL_MACHINE->SOFTWARE->Mercury Interactive->Version Manager->Test Type
The value of the string should contain the test types for TD, separated by commas.
This has been fixed.
An "Unable to get file" error occurs during a Get that includes Get latest version of... or Refresh Project View. This has been fixed.
In the desktop client and web client, long label names are not allowed to fill up the available space in the Filter Selection list, and so get unnecessarily truncated. This has been fixed.
On a multiple-file check-in or add, the Use Change Description for all check box is not selected by default. This has been fixed.
This has been fixed.
You do not receive a prompt to enter different passwords to enter subprojects with a different password for the same User ID. This has been fixed.
On check-in of an unmodified workfile, the "modified" date is changed if an UnconditionalPrePut event trigger is defined for that project. This has been fixed.
This has been fixed.
If you are using a Netscape browser and you resize the results window during a checkout, the action is aborted and the results information is lost. This has been fixed.
The VMINET.HTML page, the vminet_install.html page, and the sample project database servlet page come up blank when you try to access them in your web browser. This has been fixed.
End Release Notes
Copyright © 2003–2010 Serena Software, Inc. All rights reserved.