The readme contains information, not included in the manuals or online help, on installing and using the current release of Version Manager. Additional information is available in KnowledgeBase articles available via your browser.
The Version Manager readme consists of the following files:
Installation Information (installation_info.html)
Information on system requirements and important tips on correctly installing Version Manager. Read this before installing Version Manager.
Usage Cautions (usage_cautions.html)
Performance tips and workarounds to help you proactively avoid undesirable outcomes. Read this before using Version Manager or attempting to recover from a critical error.
Known Issues (this file)
Information on cosmetic defects, non-critical errors, and issues for which there are no preventative measures. Look here when you experience an error or other unexpected behavior not listed in the Usage Cautions file.
Release Notes (release_notesvm.html)
A list of the defects fixed, enhancements made, and behaviors changed in each release of Version Manager. Look here to see what has changed since you last upgraded.
This readme file is organized into distinct parts. Please read the parts that correspond to the Version Manager components you are using.
Part 1: Version Manager CLI, Desktop Client, and PCLI
Part 2: Version Manager IDE Client
Part 3: Version Manager Web Client
Part 4: Version Manager WebDAV Server
Part 5: Copyright/Disclaimers/Support
|
Part 1: Version Manager CLI, Desktop Client, and PCLI |
If you receive the following error:
"Failed to connect to LDAP server."
"You cannot access this project because your login account, UserName, is invalid ..."
See LDAP Connection/Authentication Fails in the Usage_Cautions.html readme file.
In Mover 2, you deploy "packages" rather than "deploy maps". As a result, the deploy command usage statement (output by the -h option) should refer to a "package id" rather than a "deploy map id".
As of Version Manager 6.8, the "Create Archive" privilege has been renamed to "Create Archive and Workfile" because this privilege now allows the user to add workfiles. In previous releases the "Create Archive" privilege had to be combined with the "Add or Remove Versioned Files" privilege in order to allow the same behavior with respect to adding workfiles. This changed behavior makes it possible to allow users to add workfiles without also allowing them to delete files.
Version Manager Administrators should be aware that users who may have had only the "Create Archive" privilege can now add workfiles. The behavior of the "Add or Remove Versioned Files" privilege has not changed.
The output messaging behavior in the Command-line Interface (CLI) has been changed so that all error messages are directed to stderr and all other types of messages are directed to stdout. This change provides for more consistent behavior, but may have an impact on existing scripts.
The default refresh interval is now 30 seconds, which means that changes made in one interface will be visible in another interface (or another instance) after 30 seconds. To refresh immediately from the Version Manager desktop client, choose View | Refresh from the Menu or press CTRL+R.
The Show History Report contains colons to use when you filter for reports on archives. The colons are used to separate the "owner", "author", and "locker" filter criteria. If you use scripts to parse the output of Show History Archive reports, you may need to update the scripts.
The Serena PVCS Version Manager Administrator's Guide indicates that multiple setup files can be specified with the runvmcm command. This does not work correctly at this time. If you specify more than one setup file, only the last one will be used.
To workaround this issue, define multiple transfers in a single setup file. See "Creating a Setup File" in the Collage chapter of the Serena PVCS Version Manager Administrator's Guide.
The output of the CLI and PCLI vlog commands have been changed to include the Split mode of an archive. You may need to update scripts that parse the output of these commands.
Paths specified in event triggers or custom tool definitions must be accessible by the client operating system. If you migrate an existing Project Database for use with a file server, you may need to change the definitions so that paths remain accessible to the OS.
For security reasons, only Version Manager executables can access paths served by the Version Manager File Server. If the directories mapped by the file server contain files other than archives and Project Database files, and if third-party applications need to access these files (or if the files are third-party applications), you need to provide another form of access for these files (such as a shared directory or a mapped drive).
NOTE: Any Version Manager executable used in your event trigger will work fine without a shared directory or mapped drive, as long as the executable itself--and any script containing it--can be found using regular (OS) file access.
The output from the -h option for CLI commands always shows options as all-uppercase; however, many options do not work if you use uppercase letters. To be safe, always use lowercase letters for CLI options.
If a user performs a makedb operation on a path for which the user is not authorized, two messages appear in the log:
Access to writing utility by user userName is granted
Error during authentication.
User userName is not authorized for path path.
The first message should appear only if the second message does not.
If a makedb operation fails because the destination is on a file server that disallows utilities, the user sees the confusing error text, "makedb: cannot create semaphore path."
If a default version label is defined for the Project Database, the Show History report does not work when you perform a Check tips against version/revision operation.
Simultaneous use of the desktop client (Version Manager or Tracker) and a Web client (Version Manager, Tracker, or TeamTrack) consumes two licenses if access is via a proxy server. The desktop application will license to the client hostname and the Web servers will license to the proxy server's hostname, so two licences are consumed.
Problem:
Deploy a promotion model at the root level of a Project Database (PDB).
Create a sub-project with a configuration file.
In the sub-project's configuration file, declare an additional promotion group below the main promotion model's bottom level.
Add a workfile to the sub-project.
Place the desktop client in recursive mode (View | Filter | Recursive).
Select the PDB level. The sub-project and versioned file appear in the right pane.
Select the versioned file directly in the right pane.
Right-click and select Check Out.
Open the drop-down list.
It shows the original bottom-level promotion group as defined by the top-level configuration.
Workaround:
After placing the desktop client in recursive mode (step 5 above), select the PDB level. The sub-project and versioned file appear in the right pane.
This time, select the sub-project.
Select the versioned file in the right pane.
Right-click and select Check Out.
Open the drop-down list.
This time, it displays the new bottom-level promotion group as defined by the sub-project configuration.
An error like this indicates that the SSO Trust Keys of the STS component on the SSO server do not match those of the client. See the Importing a Modified STS Trust Certificate from the SSO Server section of the Serena PVCS Version Manager Installation Guide.
If you open a project database (PDB) from a File Server and specify a configuration file with a name that doesn't have a ".cfg" extension, Version Manager does not recognize the configuration file.
If you set up TrackerLink to require associations for checkout, you should also require associations for check-in. Otherwise, the revision number of the checked in revision will not appear in the Tracker issue, and the issue information will not be added to the revision description. You should also select the "Clean up associations on undo checkout" check box from the Serena TrackerLink Settings dialog box (Admin | TrackerLink Settings).
If associations are not required on check-in, you can still complete associations during check-in by clicking the Associate Issues button on the Check In dialog box and clicking OK.
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.
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.
Chmod.exe is no longer part of the Version Manager installation. For similar functionality, use the MSDOS Attrib command.
For supported languages, Version Manager commands use internationalized strings that match your locale settings. These strings are stored in the message catalog file (pvcsvm.cat). By default, the catalog file is located in the bin directory of your Version Manager installation location (for example, C:\Program Files\Serena\vm\common\bin\win32). If command prompts and messages are displayed in English (rather than matching the language of your locale settings), your language is not supported, or the NLSPATH is incorrect.
To set the NLSPATH variable:
From the Windows Start menu, select Control Panel | System. The System Properties dialog box appears.
Select the Advanced tab.
Click the Environment Variables button. The Environment Variables dialog box appears.
Click the New button. The New Variable dialog box appears.
Enter NLSPATH in the Variable name field.
Enter the location of the pvcsvm.cat file in the Variable value field.
Click the OK button on each dialog box.
In the PVCS Version Manager desktop client, to save the Admin | Make Secure configuration settings, you must use the PVCS Version Manager Run as administrator option.
Attempting to change the case of a file name on a case-insensitive File Server fails to rename the archive.
In some situations, the Helper application may not start correctly unless you enter a full path.
Under the View | Options Application tab, you should enter full paths for the following applications:
The editor that Version Manager will use to display and edit your workfiles and to display reports
Adobe Acrobat Reader, used for viewing online manuals
An HTML browser, used for displaying reports and online help
Using Exceed 7.1 in Multiple Window mode causes inconsistent behavior in Version Manager when you click tabs in a dialog box with multiple tabs. The dialog box may move to the upper left corner of the screen. This problem does not happen in Single Window Mode.
Earlier versions of Exceed may cause problems with random shut downs and other unexpected behavior. This is an Exceed issue. Upgrading to Exceed 7.1 should resolve these issues.
If you use Exceed, you must configure it NOT to use font substitution. If font substitution is enabled, many dialog controls will not display correctly. Some may be unusable.
When you install Exceed, it enables font substitution by default. This may also apply to other X server software.
To disable font substitution in Exceed:
Launch Xconfig.
Select Font Management.
Select the Advanced Settings tab.
Deselect the Automatic Font Substitution checkbox.
NOTE The following two steps are optional, but recommended.
Select the Local Fonts First checkbox.
Select the Optimize for Java VM checkbox.
NOTE The procedure above is for Exceed 10. For other versions or for other X server software, consult the product's documentation.
Launching the Diff/Merge tool may cause an error message about missing fonts to appear in the Linux console. This is an erroneous message; The Diff/Merge operation will work correctly.
See "Setting Up Your UNIX Environment for Version Manager" in Chapter 4 of the Serena PVCS Version Manager Installation Guide.
When you try to select a file server or local location from the Open Server Configuration File dialog box, the drop-down list may draw incorrectly and appear to be empty. You can prevent future occurrences of this behavior by changing your locale settings from UTF8 to ISO-8859-1.
To do so, run the following commands:
export LANG=en_US
export LC_ALL=en_US
When referencing a variable's elements in PCLI, do not use leading or trailing spaces. For example:
$FOO[ 3 ] should be changed to $FOO[3]
You cannot use wildcard characters at the top level of workspace paths. For example, if you enter the following, the PCLI does not list the names of any public or private workspaces:
pcli list /@/*
However, this command lists all private workspaces of AdamJ, provided you are logged in to the project database as AdamJ:
pcli list /@/AdamJ/*
The following command lists all the public workspaces:
pcli list /@/Public/*
When you are being prompted to enter a description by the AddFiles or Put command, you cannot use the EndOfFile (EOF) character of the operating system you are running on (UNIX: CTRL+D, Windows: CTRL+Z). When prompted, enter a single period (.) on a line by itself to end the description. Windows users can also press CTRL+D.
Note that this is different from the old-style command-line interface (CLI) that allows you to enter the EOF character to end the description.
On HP-UX systems only, in certain situations, running a complex PCLI script (or many java processes) may result in a message similar to: "You have encountered an out of memory error. Please restart Version Manager and try the operation again. If you continue to have problems, contact your Version Manager administrator for further assistance. java.lang.OutOfMemoryError: unable to create new native thread...". Additional Java errors may appear after this message.
HP has a tool called "HPjconfig" that may remedy this situation. It is designed to tune HP-UX to use Java applications. Go to http://www.hp.com and search for "HPjconfig". Note: Changes made by HPjconfig will require modifications to the kernel.
If you specify a revision number during check-in, you are prompted to confirm the action. Use the run -y put command in your scripts to automatically answer "Yes" to this prompt.
Running Deploy from the command line fails if the Version Manager username or password contains spaces. The problem does not occur when you perform the deploy operation directly from Mover.
The Version Manager Conversion Utility for SourceSafe can convert your existing SourceSafe databases into Version Manager project databases.
Please refer to the Serena PVCS Version Manager Administrator's Guide for information about how to use this utility.
Clicking around in the Search pane may result in Chrome distorting its contents. The distortion clears if you resize the browser window or the Search pane.
|
Part 2: Version Manager IDE Client |
If you install SourceBridge while TrackerLink is still set as the SCC provider, SourceBridge will try to use TrackerLink as the SCC provider. Source control will not work.
To correct this, set the SCC provider in the System Settings tab of the SourceBridge dialog box. For details, see the "About Setting Up SourceBridge" section of the Serena PVCS Version Manager Administrator's Guide.
If you close one project and open another without restarting ColdFusion, Pulse may display redundant source control activity information.
Pulse may display messages containing the text "pvcs.vm.param.LogInfo". Disregard these messages.
In some situations, javaw.exe, eclipse.exe, pclioutproc.exe processes may not end automatically when closing the application. This occurs when Power Builder or RAD is run using the Version Manager interface. You must manually stop the processes.
When you perform a get or when you undo checkout of a file or a unit, Rational Rose may display a Version Control Integration message, and the operation may fail. See the sections below for information on successfully performing a get or undoing checkout.
To ensure that you can successfully get a file or unit, do one of the following before getting:
You can now get the file.
If a Version Control Integration message appears during undo checkout, the following has occurred:
To complete undo checkout, you can get the latest revision of the file by write-protecting it and getting it as explained in the section above.
To avoid this error on future undo checkout operations, write-protect the model file or unit before attempting the operation.
In most SCC IDEs, you can submit issues and switch Tracker projects from the TrackerLink Admin dialog box. In most cases, this dialog box appears when you choose to run the external source control application.
Rational Rose, however, does not display the Tracker Admin dialog box. When you select Tools | Version Control | Start Version Control Explorer, the TrackerLink Settings dialog box appears instead.
Although there is currently no way to access the TrackerLink Admin dialog box from within Rational Rose, you can still submit issues and switch projects. See the next two sections for more information.
There are two ways to submit issues with Rational Rose:
Complete the procedure below if you are using TrackerLink with Rational Rose and wish to switch to a different Tracker project:
Select Tools | Version Control | Start Version Control Explorer. The Serena TrackerLink Settings dialog box appears.
Deselect the Auto-login to project check box. Once this option is deselected, you will be prompted to log in to a Tracker project every time you start Rational Rose.
Exit and restart Rational Rose. The Tracker login dialog box appears.
Complete the login process.
If you have not launched Visual Studio at least once before installing the Version Manager integration, you may see a package load failure the first time you open it. Do NOT tell Visual Studio to stop attempting to load the Version Manager package. Choosing incorrectly at this point will disable the integration and require an uninstall and reinstall to fix the integration. It will load properly the next time you open Visual Studio.
You can configure TrackerLink to "clean up" records from files that have been unlocked. Cleaning up removes the association with the file. If you are working with TrackerLink 6.5 and you unlock an unchanged file that you have associated with an issue, the file remains associated with the issue. This does not occur with TrackerLink 6.6 or later.
Visual Basic may prompt you to confirm the check-in location even though you are checking a file in from the same location to which you checked it out. This occurs when the case in the filename is changed during the check-in process. When prompted to check in anyway, select Yes. The file will be properly checked in to the correct location.
Some IDEs allow you to get an entire project from source control, which copies all files in the Version Manager project to the location of your choice. You can specify any workfile location except a root drive (such as C:\).
If you receive an error similar to "Ordinal 58 not found at ATL.DLL" when launching an Eclipse-based IDE, you may need to update your ATL.DLL file. Check the ATL.DLL file in the system32 directory of your Windows installation. The ATL.DLL file should be about 60 KB in size. If it is much smaller, the installation of another program has overwritten the file with an outdated version. Obtain the current version from Microsoft or from another computer that has the proper version installed.
For information on Microsoft DLLs, see support.microsoft.com.
On systems that are not set to the en_US locale, "Resource Key" errors occur in the serena_java.log file in your Serena installation directory. These errors do not mean that features are not working correctly; however, to ensure that the log remains readable, you can edit the log to remove these error messages.
In the compare dialog box, the Copy All Non-Conflicting Changes from Right to Left toolbar button does not work in Three-Way Compare mode.
Workaround: Toggle the Three-Way/Two-Way Compare toolbar button.
You should specify a larger heap size if you have extremely large projects. See KnowledgeBase article S105310 (http://knowledgebase.serena.com/InfoCenter/index?page=content&id=S105310) or the item in the Usage Cautions readme ("Out of Memory Error" or General Failure Operating on Large Projects).
You cannot import a source controlled Java project from Version Manager into Eclipse C++. Doing so will result in errors, such as: "Building workspace has encountered a problem."
When Visual Studio detects that a solution has been changed outside of your environment, it prompts you to reload the solution. If you reload the solution, Visual Studio will clear the Serena Output Window. To view any action that wrote to the output window, do so before reloading the solution.
When you save the results of a merge, the resulting file is saved in UTF-8 format. This does not pose a problem within Visual Studio 2005, but some older editors, such as Visual Studio 6, will be confused by the byte-order mark added to the front of the file.
To keep your files compatible with older editors, you can change the default to ASCII. To do so, select Options from the Tools menu in Visual Studio. Select Serena from the left pane of the resulting dialog box. Change the default to ASCII.
If you have not launched Visual Studio at least once before installing the Version Manager integration, you may see a package load failure the first time you open it. Do NOT tell Visual Studio to stop attempting to load the Version Manager package. Choosing incorrectly at this point will disable the integration and require an uninstall and reinstall to fix the integration. It will load properly the next time you open Visual Studio.
If you create a new project by selecting File | New | Project from Existing Code and then try to add the project to source control without saving it first in Visual Studio, Visual Studio will crash. To prevent this problem, save such projects before adding them to source control.
In some circumstances when attempting to get the latest revision, an error may appear which gives you the opportunity to send an error report to Microsoft. Clicking the Send button may crash Visual Studio.
An empty Visual Basic Web project cannot be added to source control. Place some content in the project before attempting to add it to source control.
The Compare Workspaces view can sometimes erroneously indicate that a restored folder is still deleted. This occurs if you:
Delete a folder from the Solution Explorer.
Compare workspaces.
Do a Force Update on the deleted folder:
Select Overwrite at the local workfile prompt.
Select Reload for the project prompt.
Select Overwrite for the solution prompt.
NOTE The folder is properly restored. It is only the display of its status in the Compare Workspaces view that is incorrect.
In order to use the integration on Windows, you must be an administrative user in Windows or you must invoke Visual Studio with the Run as administrator option enabled.
You can right-click on the Visual Studio shortcut and select Run as administrator from the resulting pop-up menu, or you can configure the shortcut to always run as administrator.
|
Part 3: Version Manager Web Client |
From an individual web client system, do not open more than one connection to a given Version Manager web server at a time. If you have multiple web servers, you can open a single connection to each server in its own browser tab or browser instance.
When viewing a file in the revision pane, you can refresh the contents of its parent project by pressing CTRL and clicking the project in the project pane. You can also click the Return to Contents of Project link in the revision pane.
When you click the browse button in the Add Workfiles dialog box, the resulting directory selection dialog box sometimes does not function properly on UNIX.
The workaround is to restart the browser.
One way in which the Web client will report communication difficulties with the Web server is by displaying IO error messages (such as "java.io.IOException" or "pvcs.io.CommException").
If an Access Control Database does not exist for a project database, you cannot change your Version Manager Web client password to log in to that project database. To fix this problem, create a new ACDB for the project database using the Version Manager desktop. Uncheck the "Enable access control database security" box. You can now change your password in the Version Manager Web client.
NOTE: Creating the new ACDB does not affect the users' existing permissions, since the ACDB is disabled.
The Licenses tab of the Version Manager Web Server Application Configuration utility displays multi-byte and high-ASCII characters as a string of numbers and letters. This behavior will be addressed in a future release.
This is a display issue only; the archive data is correct. If you perform a lock operation on the file and then refresh the display, the dates appear correctly.
This dialog can appear when invoking the Version Manager web client. At the bottom of the dialog the following text appears: "The digital signature was generated with a trusted certificate but has expired." This message appears when the certificate shipped with Version Manager has expired. All certificates have a fixed lifespan and eventually expire. You can do any of the following:
To avoid seeing this dialog each time you invoke the Version Manager web client, select the Always trust content from this publisher checkbox and click the Run button.
When you upgrade to Windows XP Service Pack 2, default security settings are changed. These changes can cause messages to appear that prompt you to explicitly allow the Help system to be viewed.
To allow the Help system to be viewed wihout seeing warnings, perform the following steps:
Open Internet Explorer.
Go to Tools | Internet Options.
Click the Advanced tab.
Scroll down to the Security section.
Select the Allow active content to run in files on My Computer check box.
Click OK.
If as a user without a password you access a project database that is configured for HOSTID, any licensing errors will result in a request for a password.
A message similar to the following may indicate that the locale setting of your system is not compatible with that of the server.
c:\work\pileon\pileon_rgering\chars\File€Euro.txt, You have encountered an internal processing error: 27749. Please restart Version Manager and try the operation again. If you continue to have problems, contact your Serena administrator for further assistance.
In the above case, a UNIX-based file server was running in the en_US locale, which does not include support for the Euro character.
To avoid this issue, ensure that the characters in your file names are compatible with the locale that the file server and/or Web server are running on.
The Restart Firefox option in the Add-ons dialog box might crash Firefox after installation of the PVCS Version Manager Web client on UNIX platforms.
Workaround: Close Firefox and then open a fresh Firefox session to connect to the PVCS Version Manager Web server after installing the PVCS Version Manager Web client on a UNIX platform.
Uninstalling the PVCS Version Manager Web client without closing Web client connections to the PVCS Version Manager Web server might crash Firefox on Unix platforms.
Workaround: Uninstall the PVCS Version Manager Web client from Firefox after closing all the PVCS Version Manager clients connected to the PVCS Version Manager Web server.
Validation of WS-Federation token failed with code 40:Token issuer not allowed. An error like this indicates that the SSO Trust Keys of the STS component on the SSO server do not match those of the client. See the Importing a Modified STS Trust Certificate from the SSO Server section of the Serena PVCS Version Manager Installation Guide.
|
Part 4: Version Manager WebDAV Server |
There is important information about using WebDAV in the Usage Cautions readme file.
It no longer exists as a seperate document. The server configuration information is in the Serena PVCS Version Manager Administrator's Guide. The client setup and use information is in the Serena PVCS Version Manager User's Guide.
Part 5: Copyright/Disclaimers/Support |
To contact Serena support, please log in at support.serena.com.
The following disclaimers are provided on behalf of third party components used by and distributed with the Version Manager Web server, Version Manager File Server, and WebDAV Server. Please see the Serena PVCS Version Manager documentation for acknowledgements, and individual LICENSE files for additional information, regarding any third party components.
THE JAVA RUNTIME ENGINE, TOMCAT AND XERCES JAVA PARSER (THIS SOFTWARE) IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SUN MICROSYSTEMS, OR THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
DocuComp® comparison technology licensed from ASI Software.
Portions of the software, DocuComp® comparison © 2004 ASI Software, Inc. All rights reserved.
This product includes software developed by
The Apache Software Foundation (http://www.apache.org/).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)
Portions © Copyright 2006 Microsoft Corporation. Al Rights Reserved.
Portions © Copyright 1996, 1999 International Business Machines Corporation and others. All Rights Reserved.
Portions © Copyright Intalio Inc. and others. All Rights Reserved.
Portions © Copyright eHelp Corporation. All Rights Reserved.
End Readme
Copyright © 2003–2013 Serena Software, Inc. All rights reserved.