PVCS Version Manager
8.6.3
Readme File: Known Issues

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

The Version Manager readme consists of the following files:

This readme file is organized into distinct parts. Please read the parts that correspond to the Version Manager components you are using.


Table of Contents

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

1.0 Known Windows and Linux/UNIX Issues

1.1 The 64-bit Release of Version Manager breaks when it is installed to "C:\Program Files" [DEF298504]

1.2 LDAP & SSL: "Failed to connect to LDAP server" [ENH09231; DEF113674]

1.3 As of Version Manager 6.8: Create Archive Privilege Name and Behavior Has Changed

1.4 As of Version Manager 6.8: Behavior of Command-Line Interface Output Messages Has Changed

1.5 As of Version Manager 6.8: Default Refresh Interval Has Changed

1.6 Extra Colon in Show History Report

1.7 Output of Vlog Command Has Changed

1.8 File Server Does Not Resolve Paths in Event Triggers or Custom Tool Definitions [SCR 14206]

1.9 CLI: Help (‑h) Output Incorrectly Displays All Options in Uppercase Letters [SCR14691; SCR14704]

1.10 Log Entries for File Server Authentication Are Confusing [SCR14692; SCR14703]

1.11 makedb: Confusing Error Message If File Server Utilities Are Disabled [SCR14693; SCR14702]

1.12 "Check Tip Against Version/Revision" Fails If Default Version Is Set [SCR 14749]

1.13 Using Multiple Clients via a Proxy Server Uses Multiple Licenses [DEF80597]

1.14 Lowest-Level Promotion Group Does Not Appear in the Checkout Dialog Box [DEF78383]

1.15 SSO/CAC Error : Invalid SSO token, validation result: 40

2.0 Known Windows Issues

2.1 File Server Expects a Configuration File to Have a ".cfg" Extension

2.2 Using Certain High ASCII Characters (č, ě, ř) in Version Labels [DEF81214]

2.3 Commands Display English Rather than Internationalized Strings [TSK15780]

2.4 Windows Systems using User Account Control (UAC): Run as administrator

3.0 Known UNIX Issues

3.1 Solaris Java Runtime Environment

3.2 VTRANSFER -r: Attempting to Change the Case of a File Name on a Case-Insensitive File Server Fails to Rename the Archive [DEF74812]

3.3 Full Path to Helper Applications Sometimes Required

3.4 Using Exceed 7.1 in Multiple Window Mode Causes Inconsistent Behavior in Version Manager

3.5 HP-UX: Exceed 7.1 Required

3.6 Disable Font Substitution in Exceed or other X Servers [DEF38783; TSK05722]

3.7 Linux: "Segmentation fault (core dump)" Error Occurs During Execution of Command-Line Commands

3.8 Linux: "Open Server Configuration File" Dialog Box Displays Empty Drop-Down List [SDF08089; DEF105837]

3.9 Web Client throws missing JRE error on Linux when using Java 7 Update 71 and newer or Java 8 Update 20 and newer

4.0 Known PCLI Issues

4.1 Spaces Not Supported in a Variable Index

4.2 Wildcard Characters Do Not Work at the Top Level of Workspace Paths

4.3 CTRL+D/CTRL+Z Cannot Be Used to End Descriptions

4.4 HP-UX: PCLI Out of Memory Messages Appear

5.0 Conversion Utility for SourceSafe

5.1 General

 

Part 2: Version Manager IDE Client

6.0 Known Issues in SCC IDEs

6.1 Source Bridge: "Failed to Initialize..." [DEF78056]

6.2 Pulse: Displays "pvcs.vm.param.LogInfo" Messages

6.3 RAD and Power Builder: javaw.exe, eclipse.exe, pclioutproc.exe Processes Do Not End After closing the Version Manager SCC Interface [TSK11696]

6.4 Visual Basic: Prompts for Confirmation of Check-In Location

6.5 Workfile Location Options Are Available for Getting Projects

7.0 Known Issues in Eclipse IDEs

7.1 Eclipse: Conflicts May Occur with the ATL.DLL File Placed by Another Application

8.0 Known Issues in Eclipse Rich Integrations

8.1 "Resource Key" Errors

8.2 Copy All Changes Toolbar Button Not Working [DEF77682]

8.3 "Out of Memory Error" or General Failure Operating on Large Projects [TSK04216]

8.4 Eclipse C++: Error on Import of Java Project [DEF222404]

9.0 Known Issues in Visual Studio Rich Integrations

9.1 Visual Studio 2015 Rich Integration does not support new project types 'Shared Project' and 'Light Switch'

9.2 Reloading a Solution Clears the Serena Output Window [DEF199774; TSK16023]

9.3 Windows Requires Administrative User Rights

 

Part 3: Version Manager Web Client

10.0 Known Issues

10.1 Do Not Simultaneously Access Multiple Projects / Project Databases on the Same Server [TSK15261; DEF184743; DEF144905]

10.2 Refreshing Content Pane after Viewing Revision

10.3 UNIX: Add Workfiles Directory Browsing Is Sometimes Disabled [DEF72497]

10.4 IO Error Messages Occur When the Version Manager Web Server Is Down [SCR 13848]

10.5 Unable to Change Password If No ACDB Exists

10.6 Licenses Tab of Version Manager Web Server Application Configuration Utility Displays Multi-Byte and High-ASCII Characters Incorrectly

10.7 Dates Sometimes Displayed Incorrectly in Web Client Project Pane [SCR 14213]

10.8 "Security Information: The application's digital signature has been verified. Do you want to run the application?"

10.9 Request for Password Displayed Rather Than Licensing Error [DEF91620]

10.10 You have encountered an internal processing error: 2xxxx [DEF100245; ENH07397]

10.11 UNIX: "Restart Firefox" Option Might Crash Firefox [DEF161647]

10.12 UNIX: Uninstalling Web Client Without Closing Connections Might Crash Firefox

10.13 ALF SSO Gatekeeper error has occurred: Error obtaining security token.

10.14 "Associate Issues" actions are performed incorrectly in Internet Explorer if the SBM URL was specified using an IPv6 address

 

Part 4: Version Manager WebDAV Server

11.0 Known Issues

11.1 See the Usage Cautions Readme File

11.2 Where is the WebDAV Server Implementation Guide?

 

Part 5: Copyright/Disclaimers/Support

12.0 Support

12.1 Support Information

13.0 Notice Regarding Third Party Software

 

To Top

Part 1: Version Manager CLI, Desktop Client, and PCLI

Return to Contents


1.0 Known Windows and Linux/UNIX Issues

1.1 The 64-bit Release of Version Manager breaks when it is installed to "C:\Program Files" [DEF298504]

The default installation directory for the 64-bit release of Version Manager is C:\Program Files (x86). Manually changing that path to C:\Program Files from the installer causes Version Manager to break, as some parts will be installed in C:\Program Files and others in C:\Program Files (x86).

You can install the 64-bit release of Version Manager to a different directory, just not C:\Program Files.

1.2 LDAP & SSL: "Failed to connect to LDAP server" [ENH09231; DEF113674]

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.

1.3 As of Version Manager 6.8: Create Archive Privilege Name and Behavior Has Changed

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.

1.4 As of Version Manager 6.8: Behavior of Command-Line Interface Output Messages Has 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.

1.5 As of Version Manager 6.8: Default Refresh Interval Has Changed

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.

1.6 Extra Colon in Show History Report

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.

1.7 Output of Vlog Command Has Changed

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.

1.8 File Server Does Not Resolve Paths in Event Triggers or Custom Tool Definitions [SCR 14206]

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.

1.9 CLI: Help (‑h) Output Incorrectly Displays All Options in Uppercase Letters [SCR14691; SCR14704]

The output from the -h option for CLI commands always shows options as all-uppercase; however, some options do not work if you use uppercase letters. To be safe, always use lowercase letters for CLI options.

1.10 Log Entries for File Server Authentication Are Confusing [SCR14692; SCR14703]

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.

1.11 makedb: Confusing Error Message If File Server Utilities Are Disabled [SCR14693; SCR14702]

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

1.12 "Check Tip Against Version/Revision" Fails If Default Version Is Set [SCR 14749]

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.

1.13 Using Multiple Clients via a Proxy Server Uses Multiple Licenses [DEF80597]

Simultaneous use of the desktop client (Version Manager) and a Web client (Version Manager or SBM) 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 licenses are consumed.

This problem also occurs if your DNS configuration does not return the same hostname for the IP address of end-user's PC as the name reported by that system.

1.14 Lowest-Level Promotion Group Does Not Appear in the Checkout Dialog Box [DEF78383]

Problem:

  1. Deploy a promotion model at the root level of a Project Database (PDB).

  2. Create a sub-project with a configuration file.

  3. In the sub-project's configuration file, declare an additional promotion group below the main promotion model's bottom level.

  4. Add a workfile to the sub-project.

  5. Place the desktop client in recursive mode (View | Filter | Recursive).

  6. Select the PDB level. The sub-project and versioned file appear in the right pane.

  7. Select the versioned file directly in the right pane.

  8. Right-click and select Check Out.

  9. Open the drop-down list.

    It shows the original bottom-level promotion group as defined by the top-level configuration.

Workaround:

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

  2. This time, select the sub-project.

  3. Select the versioned file in the right pane.

  4. Right-click and select Check Out.

  5. Open the drop-down list.

    This time, it displays the new bottom-level promotion group as defined by the sub-project configuration.

1.15 SSO/CAC Error : Invalid SSO token, validation result: 40

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 KB doc S138730 or the Importing a Modified STS Trust Certificate from the SSO Server section of the PVCS Version Manager Installation Guide.

Return to Contents


2.0 Known Windows Issues

2.1 File Server Expects a Configuration File to Have a ".cfg" Extension

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.

2.2 Using Certain High ASCII Characters (č, ě, ř) in Version Labels [DEF81214]

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

2.3 Commands Display English Rather than Internationalized Strings [TSK15780]

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:

  1. From the Windows Start menu, select Control Panel | System. The System Properties dialog box appears.

  2. Select the Advanced tab.

  3. Click the Environment Variables button. The Environment Variables dialog box appears.

  4. Click the New button. The New Variable dialog box appears.

  5. Enter NLSPATH in the Variable name field.

  6. Enter the location of the pvcsvm.cat file in the Variable value field.

  7. Click the OK button on each dialog box.

2.4 Windows Systems using User Account Control (UAC): Run as administrator

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.

Return to Contents


3.0 Known UNIX Issues

3.1 Solaris Java Runtime Environment

Version Manager on Solaris does not ship with a Java Runtime Engine (JRE). The installer prompts for the location of a JRE that is already installed. If the user running the installer cannot update certificate files in this JRE, the installer displays a certtool command that the user 'root' must run after completing the installation.

3.2 VTRANSFER -r: Attempting to Change the Case of a File Name on a Case-Insensitive File Server Fails to Rename the Archive [DEF74812]

Attempting to change the case of a file name on a case-insensitive File Server fails to rename the archive. To work around this issue, first run vtransfer -r to give the archive a different name, then run it again to rename that file to your desired name.

3.3 Full Path to Helper Applications Sometimes Required

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:

  1. The editor that Version Manager will use to display and edit your workfiles and to display reports

  2. Adobe Acrobat Reader, used for viewing online manuals

  3. An HTML browser, used for displaying reports and online help

3.4 Using Exceed 7.1 in Multiple Window Mode Causes Inconsistent Behavior in Version Manager

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.

3.5 HP-UX: Exceed 7.1 Required

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.

3.6 Disable Font Substitution in Exceed or other X Servers [DEF38783; TSK05722]

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:

  1. Launch Xconfig.

  2. Select Font Management.

  3. Select the Advanced Settings tab.

  4. Deselect the Automatic Font Substitution checkbox.

    NOTE The following two steps are optional, but recommended.

  5. Select the Local Fonts First checkbox.

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

3.7 Linux: "Segmentation fault (core dump)" Error Occurs During Execution of Command-Line Commands

See "Setting Up Your UNIX Environment for Version Manager" in Chapter 4 of the PVCS Version Manager Installation Guide.

3.8 Linux: "Open Server Configuration File" Dialog Box Displays Empty Drop-Down List [SDF08089; DEF105837]

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

3.9 Web Client throws missing JRE error on Linux when using Java 7 Update 71 and newer or Java 8 Update 20 and newer

Oracle JRE for Linux introduced a regression in releases 1.7.0_71 and 1.8.0_20 that prevents the Web Client from connecting to Java using a typical system configuration (see JDK-8064677.) As a result, users will see the error "This browser has no Java Runtime Environment (JRE)."

Workaround: This issue can be avoided by installing the packages gtk2-engines and gtk2-devel, which became an undeclared dependency for the Java browser Plug-in. Example:

yum install gtk2-engines gtk2-devel

If you use the i686 versions of the browser (e.g. firefox.i686) and the JRE on an x86_64 version of Linux, run the following command instead:

yum install gtk2-engines.i686 gtk2-devel.i686

Return to Contents


4.0 Known PCLI Issues

4.1 Spaces Not Supported in a Variable Index

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]

4.2 Wildcard Characters Do Not Work at the Top Level of Workspace Paths

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/*

4.3 CTRL+D/CTRL+Z Cannot Be Used to End Descriptions

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.

4.4 HP-UX: PCLI Out of Memory Messages Appear

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.

Return to Contents


5.0 Conversion Utility for SourceSafe

5.1 General

The Version Manager Conversion Utility for SourceSafe can convert your existing SourceSafe databases into Version Manager project databases.

Please refer to the PVCS Version Manager Administrator's Guide for information about how to use this utility.

Return to Contents

Part 2: Version Manager IDE Client

Return to Contents


6.0 Known Issues in SCC IDEs

6.1 Source Bridge: "Failed to Initialize..." [DEF78056]

If you install Source Bridge while TrackerLink is still set as the SCC provider, Source Bridge 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 Source Bridge dialog box. For details, see the "About Setting Up Source Bridge" section of the PVCS Version Manager Administrator's Guide.

6.2 Pulse: Displays "pvcs.vm.param.LogInfo" Messages

Pulse may display messages containing the text "pvcs.vm.param.LogInfo". Disregard these messages.

6.3 RAD and Power Builder: javaw.exe, eclipse.exe, pclioutproc.exe Processes Do Not End After closing the Version Manager SCC Interface [TSK11696]

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.

6.4 Visual Basic: Prompts for Confirmation of Check-In Location

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.

6.5 Workfile Location Options Are Available for Getting Projects

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

Return to Contents


7.0 Known Issues in Eclipse IDEs

7.1 Eclipse: Conflicts May Occur with the ATL.DLL File Placed by Another Application

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.

Return to Contents


8.0 Known Issues in Eclipse Rich Integrations

8.1 "Resource Key" Errors

On systems that are not set to the en_US locale, "Resource Key" errors occur in the serena_java.log file in your 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.

8.2 Copy All Changes Toolbar Button Not Working [DEF77682]

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.

8.3 "Out of Memory Error" or General Failure Operating on Large Projects [TSK04216]

You should specify a larger heap size if you have extremely large projects. See KnowledgeBase article S105310 or the item in the Usage Cautions readme ("Out of Memory Error" or General Failure Operating on Large Projects).

8.4 Eclipse C++: Error on Import of Java Project [DEF222404]

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

Return to Contents


9.0 Known Issues in Visual Studio Rich Integrations

9.1 Visual Studio 2015 Rich Integration does not support new project types 'Shared Project' and 'Light Switch'

Visual Studio 2015 introduced the new projects types 'Shared Project' and 'Light Switch'. At the moment these are not supported by Version Manager's RIDE integration as they require substantial changes to the RIDE code, exceeding the scope of this patch.

9.2 Reloading a Solution Clears the Serena Output Window [DEF199774; TSK16023]

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.

9.3 Windows Requires Administrative User Rights

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

Return to Contents


10.0 Known Issues

10.1 Do Not Simultaneously Access Multiple Projects / Project Databases on the Same Server [TSK15261; DEF184743; DEF144905]

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.

10.2 Refreshing Content Pane after Viewing Revision

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.

10.3 UNIX: Add Workfiles Directory Browsing Is Sometimes Disabled [DEF72497]

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.

10.4 IO Error Messages Occur When the Version Manager Web Server Is Down [SCR 13848]

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

10.5 Unable to Change Password If No ACDB Exists

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.

10.6 Licenses Tab of Version Manager Web Server Application Configuration Utility Displays Multi-Byte and High-ASCII Characters Incorrectly

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.

10.7 Dates Sometimes Displayed Incorrectly in Web Client Project Pane [SCR 14213]

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.

10.8 "Security Information: The application's digital signature has been verified. Do you want to run the application?"

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.

10.9 Request for Password Displayed Rather Than Licensing Error [DEF91620]

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.

10.10 You have encountered an internal processing error: 2xxxx [DEF100245; ENH07397]

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

10.11 UNIX: "Restart Firefox" Option Might Crash Firefox [DEF161647]

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.

10.12 UNIX: Uninstalling Web Client Without Closing Connections Might Crash Firefox

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.

10.13 ALF SSO Gatekeeper error has occurred: Error obtaining security token.

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 KB doc S138730 or the Importing a Modified STS Trust Certificate from the SSO Server section of the PVCS Version Manager Installation Guide.

10.14 "Associate Issues" actions are performed incorrectly in Internet Explorer if the SBM URL was specified using an IPv6 address

Workaround: Use a DNS host name in the SBM URL instead of an IPv6 address, or add the IPv6-like URL to IE's 'Trusted Sites' list.

Part 4: Version Manager WebDAV Server

Return to Contents


11.0 Known Issues

11.1 See the Usage Cautions Readme File

There is important information about using WebDAV in the Usage Cautions readme file.

11.2 Where is the WebDAV Server Implementation Guide?

It no longer exists as a separate document. The server configuration information is in the PVCS Version Manager Administrator's Guide. The client setup and use information is in the PVCS Version Manager User's Guide.

 

Part 5: Copyright/Disclaimers/Support

Return to Contents


12.0 Support

12.1 Support Information

To obtain product support, log into supportline.microfocus.com.

Return to Contents


13.0 Notice Regarding Third Party Software

The license information for Third Party components used by and distributed with PVCS Version Manager can be found in the PVCS installation directory.


End Readme
Copyright © 2003–2021 Micro Focus or one of its affiliates.