Serena PVCS Version Manager
Version 8.6.0
Readme File: Usage Cautions

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:

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, File Server, 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, File Server, and PCLI

1.0 Performance Considerations

1.1 Symbolic Linking to Version Manager Commands

1.2 Antivirus Software

1.3 Cleaning Up File Server Client Cache Files

2.0 Known Windows and UNIX Issues

2.1 Changes to Daylight Savings Time

2.2 Fixed Length Keyword Expansion Syntax Has Changed (as of 8.1.2)

2.3 Using Dashes (-) in Version Labels (Caution!)

2.4 Diff/Merge Tool: Scroll Bar Does Not Work on Large Files

2.5 Copy Project Database Fails with Privileges Error

2.6 Configuration Builder Cannot Access File Server Archives

2.7 Long User Names with Double-Byte Characters Interfere with Use of the Project Security Dialog Box

2.8 Users with No Assigned Privilege Set Receive the Unlimited Privilege Set

2.9 Issue Associations Fail on SSL-Enabled Servers

2.10 "Require Associations on Checkin" Requires SourceBridge Install to Client System [DEF172990]

2.11 LDAP Connection/Authentication Fails

2.12 Conflicting Path Maps

2.13 File Server Path Map Security Requires Access Control Database Security

2.14 Quotation Marks Required If the Path Used with INCLUDE Directive Contains Spaces

2.15 "Out of Memory Error" or General Failure Operating on Large Projects

2.16 DTK: PvcsSetProjectSemaphore() Is Not Supported by File Servers

2.17 Restart Version Manager After Using the Make Secure Dialog Box

3.0 Known Windows Issues

3.1 Administrative User Rights Required to Start the VM Application Server (except Windows 2000, 2003, & XP)

3.2 Administrative User Rights Required to Access vconfig and to modify vmwfvc.dll (except Windows 2000, 2003, & XP)

3.3 Conflicts with Third-Party DLL's - Error: "The ordinal <number> could not be located in the dynamic link library <Name>.dll"

4.0 Known UNIX/Linux Issues

4.1 "Error in getting local hostname"

4.2 Linux CAC: ActiveIdentity Client PIN Cache Settings

4.3 Solaris (United Kingdom and Ireland): Patch Required to Prevent Inconsistent Time-Stamping in Java Applications

4.4 PCLI: "Kill" Character Conflicts with PCLI Commands

4.5 Default File Descriptor Limit May Be Too Low on Some UNIX Systems

4.6 IPv6 is not supported on HP-UX and not fully supported on AIX.

5.0 Known PCLI Issues

5.1 Exporting and Then Importing a Project Database Works Only with the Same Platform

5.2 Slashes (/ \), Square Brackets ([ ]), and Colons (:) in Workspace and User Names May Cause Problems

 

Part 2: Version Manager IDE Client

6.0 Known Issues in SCC IDEs

6.1 PowerBuilder: Removing Locks on Unchanged Revisions Always Required

6.2 Requiring Issue Association: Set Your SCC Provider to Serena SourceBridge

7.0 Known Issues in Eclipse and Visual Studio Rich Integrations

7.1 Server-Side Processing Is Enabled By Default

7.2 Server-Side Processing Requires Definition of "localhost" on the File Server

7.3 Eclipse: You Must Exclude Certain Third-Party Folders e.g. ibmconfig

7.4 Eclipse RIDE on SuSE Linux: Sporadic Crashes

7.5 VS 2005: Files & Projects Disappear When Default Version (Label) Is Applied/Changed

7.6 VS 2005: Windows Requires Administrative User (except Windows 2000, 2003, & XP)

7.7 Application Server rejects pre-8.5.1 clients

 

Part 3: Version Manager Web Client

8.0 Performance Considerations

8.1 Antivirus Software

8.2 Cleaning Up File Server Client Cache Files

8.3 Purging Log Files and Temporary Files from the Server

9.0 Known Issues

9.1 Vista and Internet Explorer 7: Disable Protected Mode

9.2 Windows 2003 Server: Double-Byte File Names over 28 Characters Cause "HTTP 404 Page Not Found" Error

9.3 Naming Considerations

9.4 Using Event Triggers

9.5 Updating Keyword Values When You Add or Check In Workfiles

9.6 Error During Startup of Version Manager Web or WebDAV Server

9.7 Multi-Byte Characters Not Supported with iPlanet

9.8 Pop-Up Blocking Prevents Version Manager From Working Correctly

9.9 Windows: Application Server Freezes When Started and Stopped Without Accessing Any Archives

9.10 Issue Running Version Manager Web Server on Itanium

9.11 Ampersands or Upper-ASCII Characters in Servlet Definitions Cause Errors

9.12 Web Server Aplication Requires Definition of "localhost" on the File Server

 

Part 4: Version Manager WebDAV Server

10.0 Known Issues

10.1 Client Issues

10.2 Password Recommendation for WebDAV Clients

10.3 Troubleshooting Connection Problems

10.4 Only Default Versions Visible Through WebDAV Server

10.5 Specifying Privileges

10.6 Error During Startup of Version Manager Web or WebDAV Server

10.7 Using WebDAV with IIS and Microsoft FrontPage Server Extensions

10.8 Using the Euro Character on Solaris

 

Part 5: Copyright/Disclaimers/Support

11.0 Support

11.1 Support Information

12.0 Notice Regarding Third Party Software

12.1 Third Party Software Disclaimers

12.2 Third Party Software Rights

 

To Top

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

Return to Contents


1.0 Performance Considerations

1.1 Symbolic Linking to Version Manager Commands

If you use symbolic links to specify paths in Version Manager commands, the command will take longer to complete. To speed execution, specify full paths rather than symbolic links, or add the fully qualified paths of Version Manager commands to your environment.

1.2 Antivirus Software

If you use the Serena PVCS Version Manager File Server and you run real-time antivirus software on your clients, you may experience degraded performance. This is because the antivirus software scans the Version Manager file cache every time the cache is updated. To avoid this performance penalty, exclude the cache directory from real-time virus scans.

By default, the file cache is in a directory named pvcsfs under your system's temporary directory (as specified by the TMP or TEMP environment variable). You can set a different location for the cache by defining a path in either the FS_TMP or FS_TEMP environment variable.

For more information on antivirus-related performance improvements, see Serena KnowldegeBase article S123872 (http://knowledgebase.serena.com/InfoCenter/index?page=content&id=S123872). This article applies to both clients and file servers.

1.3 Cleaning Up File Server Client Cache Files

Version Manager 8.1.1 or later (and Version Manager 8.0.2.6) includes a feature that automatically cleans up old files in the File Server client cache directory 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.

Return to Contents


2.0 Known Windows and UNIX Issues

2.1 Changes to Daylight Savings Time

Most users should be unaffected by the new dates for Daylight Savings Time. However, if you have a Windows system that uses the TZ environment variable, then Version Manager will default to built-in, hard coded, USA-centric start and end dates for Daylight Savings Time.

To avoid this issue, you can use the PVCSTZ environment variable to override both the TZ variable and the time zone information that is provided by the operating system, should that be desired.

NOTE As of 8.1.4.0 (spring 2007), DST dates have been updated to reflect the current law. Also, an update with the new dates is available for Version Manager 8.1.3.2. It is attached to the KnowledgeBase article mentioned below.

See the Serena KnowledgeBase article, Is Version Manager affected by the changes to the U.S. Daylight Saving Time (DST) for 2007?, ID 5004791, for more information.

2.2 Fixed Length Keyword Expansion Syntax Has Changed (as of 8.1.2)

If the content of a keyword contains a "$" character, you must use the new syntax:

$Keyword::$123456::$

Where:

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$

2.3 Using Dashes (-) in Version Labels (Caution!)

From the command line, a dash (-) in a version label can be interpreted as a math operation upon the revision number. This can result in the incorrect revision being acted upon.

This can happen only in the circumstances described below:

The revision acted upon in that case will be based upon the revision number of the revision with the non-numerical, non-dash label (Beta, in the example above), minus the numerical portion of the requested, but nonexistent, label.

Here is a specific example:

Revision 1.6 has the Version Label: Beta

The nonexistent label used in the command is: Beta-4

The unintended revision math performed is: 1.6 - 4 = 1.2

The revision acted upon by the command is thus: 1.2

Recommendation: If you must use such a label numbering scheme, be sure never to specify a nonexistent label in a command. Better yet, avoid the possibility of encountering this behavior by ensuring that there is not a label like "Beta" that otherwise matches the sequence of labels.

NOTE By default, Version Manager checks for illegal characters (such as dash (-)) during label creation and rejects the label if it contains illegal characters. If you must create labels that include illegal characters, you can disable the filter that checks for illegal characters in labels. See the DisableBadLabelFilter directive in the Serena PVCS Version Manager Command-Line Guide.

2.4 Diff/Merge Tool: Scroll Bar Does Not Work on Large Files

If a file has over 32,000 lines, the scroll bar in the Diff/Merge tool will not work correctly. Use the Next, Previous, and Go to line features to navigate large files. Using the scroll bar alone, you may be unable to reach the desired location.

2.5 Copy Project Database Fails with Privileges Error

Under some circumstances, a copy project database operation may fail with a privileges error. This may occur when all of the following are true:

To work around this issue do one of the following:

2.6 Configuration Builder Cannot Access File Server Archives

Configuration Builder does not support the Version Manager File Server.

2.7 Long User Names with Double-Byte Characters Interfere with Use of the Project Security Dialog Box

User names that contain double-byte characters and are longer than 20 characters get truncated when you close the Project Security dialog box. In some cases, they also can prevent repeated use of the dialog box.

2.8 Users with No Assigned Privilege Set Receive the Unlimited Privilege Set

If you remove all privilege sets from a user (via Admin | Security in the Version Manager desktop client), the user actually receives the Unlimited privilege set.

If you do not want a user to have Unlimited privileges, make sure that the user has at least one privilege set.

2.9 Issue Associations Fail on SSL-Enabled Servers

If the Tracker, TeamTrack, or SBM web client is running on an SSL-enabled server, associations may fail. You can resolve this issue by adding an SSL certificate to the JRE keystore. See KnowledgeBase article: S134480 (http://knowledgebase.serena.com/InfoCenter/index?page=content&id=S134480)

See also
 
Using TrackerLink with Secure Sockets Layer (SSL)

2.10 "Require Associations on Checkin" Requires SourceBridge Install to Client System [DEF172990]

SourceBridge must be installed to the clients in order to enforce association on checkin; else the checkin will occur with no association and no prompt or warning that an association is required.

2.11 LDAP Connection/Authentication Fails

If your LDAP server is configured to use Secure Sockets Layer (SSL) but there is not a certificate database in the VM_Install_Dir/vm/common/bin/OS directory or the database is missing the required SSL certificates, you will receive errors, such as:

You can create a certificate database with the Mozilla Certutil utility. Certificate databases are platform independent and can be used across multiple operating systems.

To create and populate a certificate database using Mozilla Certutil:

Certutil is a command-line utility installed with Version Manager, so it should already be included in your system's path environment variable. (It is installed to this directory: VM_Install_Dir/vm/common/bin/OS.) For more information, see: http://www.mozilla.org/projects/security/pki/nss/tools/certutil.html.

  1. Create a folder for the certificate database. For example:

    C:\pvcs\ldap_cert

  2. Create a certificate database using the command:

    certutil -N -d "FolderPath"

    For example:

    certuil -N -d C:\pvcs\ldap_cert

  3. Do one of the following:

  4. For each LDAP server you have configured for use with Version Manager, use the Version Manager desktop client to specify the location of the appropriate certificate database. The relevant field is on the LDAP Server dialog off of the Configure Project/Project Database dialog.

    NOTE This location must be accessible by all clients, such as a mapped network drive or UNC path.

2.12 Conflicting Path Maps

By default, the Version Manager client will deny access to conflicting path maps and display a message. In the Open Project Database dialog, conflicting path maps will be shown in red. A path map conflict occurs when a user tries to access two, or more, path maps that fully or partially overlap but reside on different servers.

See the Serena PVCS Version Manager Administrator's Guide for information on resolving or working around such conflicts. If improperly handled, overlapping path maps can result in the wrong files being acted upon.

2.13 File Server Path Map Security Requires Access Control Database Security

You must enable Access control database security if security is enabled on a file server path map.

File server path map security is set up through the Version Manager File Server Administration utility. From the Path Map page, open the Add Path Map or Edit Path Map dialog box. If you enable either the Access control database field or the LDAP authentication checkbox, you must also enable the Access control database security checkbox (see below).

The Access control database security checkbox is on the General tab of the Configure Project Database dialog (from the desktop client: Admin | Configure Project). Select Security | Access Control Database from the Options tree.

2.14 Quotation Marks Required If the Path Used with INCLUDE Directive Contains Spaces

If you use the INCLUDE directive in a configuration file and there are blank spaces in the path of the configuration file being included, you must use quotation marks around the path. For example, if the sample project database is installed to the default location, define the INCLUDE directive to its configuration file as:

INCLUDE "c:\program files\serena\vm\common\sampledb\archives\basecfg.cfg"

2.15 "Out of Memory Error" or General Failure Operating on Large Projects

Large projects can exceed the memory allocated for Java in a variety of situations and with a variety of Version Manager interfaces. The following table describes some of the possible error scenarios.

ComponentSymptomSee
Application Server:
-File Server
-Web Client
-WebDAV Client
-RIDE IDE's (if using server-side processing)
Out of memory error (for example, during recursive view of a large project) Application Server
Desktop Client Out of memory error
Failure of Export/Import
Desktop Client and PCLI
IDEs Out of memory error IDEs
PCLI Out of memory error
Failure of Export/Import
Desktop Client and PCLI
NOTE: Export/Import Project May Fail with Large Projects
Version Manager may run out of memory when exporting or importing large projects. To avoid loss of data, retain the source project after exporting it. You can then return to it if the project is too large to import.
Desktop Client and PCLI

Java-based Version Manager clients use the following memory heap parameters:

The following sections describe how to set those values for the various clients.

2.15.1 Desktop Client and PCLI

To increase the amount of memory that the Desktop client and PCLI can allocate, define the environment variable PVCS_MX prior to launching the command or interface. The following examples show how to change the Java Heap Size used by Version Manager to 512MB (your needs may differ):

Environment Command
Windows set PVCS_MX=-Xmx512m
UNIX Bourne Shell PVCS_MX=-Xmx512m; export PVCS_MX
UNIX Korn Shell/Bash export PVCS_MX=-Xmx512m
UNIX C-Shell setenv PVCS_MX -Xmx512m

2.15.2 Application Server

The Version Manager Application Server hosts the following Version Manager features. Changes made here affect them all.

Do one of the following:

2.15.3 IDEs

See the section below specific to your IDE. The memory values shown below are examples; your needs may differ. The changes will take effect when you next launch the IDE.

SCC Clients

In the ISLV.ini file add a section and key value pair in the following format:

[CPCLI]
JAVAARGS=-Xms128m -Xmx512m

Visual Studio RIDE

In the ISLV.ini file add a section and key value pair in the following format:

[SVE]
sve.dotnet.jvmloader.jvm.initialHeapSize=128m
sve.dotnet.jvmloader.jvm.maxHeapSize=256m

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

2.16 DTK: PvcsSetProjectSemaphore() Is Not Supported by File Servers

The DTK call PvcsSetProjectSemaphore() is not supported by file servers. If you previously used this call to lock down the archives in preparation for builds or backups, you can achieve the same effect with archives on a file server by deselecting the Enable write access option in the Version Manager Administration Utility.

2.17 Restart Version Manager After Using the Make Secure Dialog Box

Restart the Version Manager Desktop Client after making changes to the Make Secure dialog box. If you reopen the dialog box during the same Version Manager session, it will not reflect the previous changes, and they could be lost when you close the dialog box.

Return to Contents


3.0 Known Windows Issues

3.1 Administrative User Rights Required to Start the VM Application Server (except Windows 2000, 2003, & XP)

To start the Version Manager Application Server, you must be an administrative user in Vista.

See the VS 2005: Windows Requires Administrative User topic for more information.

3.2 Administrative User Rights Required to Access vconfig and to modify vmwfvc.dll (except Windows 2000, 2003, & XP)

To access the vconfig.exe and to modify the vmwfvc.dll file, you must log into Windows as an administrative user or use the Run as administrator option in Vista.

See the VS 2005: Windows Requires Administrative User topic for more information.

3.3 Conflicts with Third-Party DLL's - Error: "The ordinal <number> could not be located in the dynamic link library <Name>.dll"

If you encounter a conflict with a 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:

Return to Contents


4.0 Known UNIX/Linux Issues

4.1 "Error in getting local hostname"

Version Manager cannot be licensed until the workstation is registered to the network. Register to the network before attempting to use Version Manager.

4.2 Linux CAC: ActiveIdentity Client PIN Cache Settings

Allowing PIN caching by ActiveIdentity Client on Linux systems can, in certain circumstances, result in access regardless of the PIN entered. To avoid this possibility, specify a short cache retention period or disable PIN caching in ActiveIdentity Client. For obvious reasons, we are not fully describing the very specific scenario which can bring about this undesired result.

4.3 Solaris (United Kingdom and Ireland): Patch Required to Prevent Inconsistent Time-Stamping in Java Applications

To prevent inconsistent time-stamping on Version Manager archives and workfiles, Solaris users in the United Kingdom and Ireland must download and install a patch from Sun Microsystems. The patch, 105210-10 or later, is available from the Sun Microsystems customer support web site, http://sunsolve.Sun.com.

4.4 PCLI: "Kill" Character Conflicts with PCLI Commands

The default kill character on HP-UX (Bourne and Korn shells) is @. This character conflicts with the PCLI listfile command (@listfile) and specifying a workspace at the command line. For example:

pcli listversionedfiles -prd:\productb -pp/newprj @listfile

—or—

pcli getworklocation -sp/@/mariec/myworkspace...

To avoid this conflict, set the kill character to a value other than @. For example:

stty kill ^U (sets the kill character to CTRL+U)

4.5 Default File Descriptor Limit May Be Too Low on Some UNIX Systems

Some PCLI operations, such as ListVersionedFiles, can open many files at a time. On some UNIX systems, the default open file descriptor limit may be set too low. We recommend that you set your file descriptor limit to 128 or higher. For very large databases, we recommend setting the limit as high as allowed by the operating system. For C shell users, use the "limit" command to set the limit. For Bourne and Korn shell users, use the "ulimit" command. The default file descriptor limit varies on each operating system and by system configuration. The default limit may or may not already be set higher than 128.

A lack of file descriptors can manifest itself in various ways. Typical problems include a failure to open or locate files in response to file-intensive commands such as AddFiles, ListVersionedFiles, and ImportArchives.

4.6 IPv6 is not supported on HP-UX and not fully supported on AIX.

In this release of Version Manager, use of IPv6 is not supported on HP-UX at all. On AIX, IPv6 cannot be used to reach the License Server (SLM).

Return to Contents


5.0 Known PCLI Issues

5.1 Exporting and Then Importing a Project Database Works Only with the Same Platform

When you export a project database on Windows, you can import it only on Windows; you cannot import it on UNIX without manually converting all the pathnames in the exported file and in the configuration file(s) it references. The same is true when you import a file on Windows that was exported on UNIX.

5.2 Slashes (/ \), Square Brackets ([ ]), and Colons (:) in Workspace and User Names May Cause Problems

Workspace or user names that contain slashes (/ \), square brackets ([ ]), or colons (:) can cause PCLI commands and the import/export of project databases to fail. Change any such preexisting names before importing/exporting or using other PCLI commands.

 

Part 2: Version Manager IDE Client

Return to Contents


6.0 Known Issues in SCC IDEs

6.1 PowerBuilder: Removing Locks on Unchanged Revisions Always Required

Version Manager allows you to configure a project database or project to always remove locks on unchanged files. If you are working with Version Manager projects within PowerBuilder, be sure to set this option. If you do not, objects in your PowerBuilder application may become out of sync with their associated versioned files when you undo a checkout or when you check in an unchanged revision. Objects may appear to be unlocked in PowerBuilder when in fact their associated Version Manager archives are still locked.

See the Serena PVCS Version Manager Administrator's Guide for more information.

6.2 Requiring Issue Association: Set Your SCC Provider to Serena SourceBridge

It is not enough to configure SourceBridge to require associations, you must also set the SCC provider to the issue management system you are using. Use the Version Manager SCC Admin to select the correct SCC provider from those installed to your client system. Depending on the version you have installed, you will see an SCC provider named for your issue management system. For example, Serena SourceBridge or Tracker TrackerLink.

Return to Contents


7.0 Known Issues in Eclipse and Visual Studio Rich Integrations

7.1 Server-Side Processing Is Enabled By Default

Server-side processing is enabled by default, so by default all event triggers will be executed on the server. If this is incompatible with your processes, you can revert to the previous behavior of client-side processing. See the Serena PVCS Version Manager IDE Client Implementation Guide for more information (the section on setting default options for your particular IDE).

7.2 Server-Side Processing Requires Definition of "localhost" on the File Server

If you are using the Server-Side Processing feature of the Rich IDEs, then all File Servers containing repositories used by these integrations must be defined on the server(s) through which the RIDE users connect--including the File Server itself (as "localhost" or using its server name). To do so, see the File Server chapter of the Serena PVCS Version Manager Administrator's Guide.

7.3 Eclipse: You Must Exclude Certain Third-Party Folders e.g. ibmconfig

Some third-party tools create folders that fail to function properly for the third-party tool if any outside content is added to them. Since the Serena RIDE integration adds a _serena folder when items are placed under source control, you must exclude sensitive third-party folders from source control. The ibmconfig folder is one folder known to have this issue. See the Serena PVCS IDE Implementation Guide for details on how to exclude files or folders from source control.

7.4 Eclipse RIDE on SuSE Linux: Sporadic Crashes

There is a dependency upon the library libexpat.0.so. Your SuSE installation probably has a newer version of this file, for example libexpat.1.so. Unfortunately there are several third-party libraries that depend upon the older version of the file. To avoid sporadic crashes, you must download and install a compact pack specific to your operating system in order to acquire the needed version of libexpat0. See http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/libexpat.so.0

7.5 VS 2005: Files & Projects Disappear When Default Version (Label) Is Applied/Changed

The rich integration uses the default version (label) to determine which files are visible in a given Version Manager workspace. To avoid confusion, it is important that you understand how this works.

If you use the desktop client to apply a default version or change the existing one for a project database or for a workspace, only files that have the version label will appear in Visual Studio. If the project and solution files do not have these labels, you will see no files.

To avoid the potential for confusion:

See the Serena Version Manager IDE Client Implementation Guide for more information.

7.6 VS 2005: Windows Requires Administrative User (except Windows 2000, 2003, & XP)

In order to use the integration on Windows (except Windows 2000, 2003, & XP), you must be an administrative user 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.

7.7 Application Server rejects pre-8.5.1 clients

To improve server stability using very large data sets, the Serena VM Web Application Server will reject pre-8.5.1 RIDE clients trying to use Server-side processing. Such clients will display a message similar to the following:

[INFO] Server-side processing can not be used with pre 8.4.1 server, switching to Client-side processing.
Please uncheck the 'Enable Server-side processing' feature available in Windows>Preference>Team>Serena>Client/Server to avoid this message.

These clients can still access the Project Database using the old-style Client-side processing, as indicated.
You can override this behavior and allow pre-8.5.1 clients access via Server-side processing by adding the following directive to server's ISLV.ini

   [APP_SERVER]
   pvcs.appserver.rejectClientsWithoutHugeSetsCapability=false

This should only be used if the RIDE projects are small in size and upgrading the clients to 8.5.1 or newer is not immediately possible.

 

Part 3: Version Manager Web Client

Return to Contents


8.0 Performance Considerations

8.1 Antivirus Software

If you use the Serena PVCS Version Manager File Server and you run real-time antivirus software on the system running the Version Manager web server, you may experience degraded performance. This is because the antivirus software scans the Version Manager file cache every time the cache is updated. To avoid this performance penalty, exclude the cache directory from real-time virus scans.

By default, the file cache is in a directory named pvcsfs under your system's temporary directory (as specified by the TMP or TEMP environment variable). You can set a different location for the cache by defining a path in either the FS_TMP or FS_TEMP environment variable.

For more information on antivirus-related performance improvements, see Serena KnowldegeBase article 70042.

8.2 Cleaning Up File Server Client Cache Files

Version Manager 8.1.1 or later (and Version Manager 8.0.2.6) includes a feature that automatically cleans up old files in the File Server client cache directory 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.

8.3 Purging Log Files and Temporary Files from the Server

The Version Manager web server generates log files and temporary files on the server machine. These files do not cause problems, but do use up hard drive space until deleted. We recommend that you purge these files periodically.

You can periodically delete the log files generated in the following directories:

Temporary files are generated on the server if the connection between the client and server is lost in the middle of a file transfer. Delete these files from the directory VM_Install_Dir\vm\inet\temp on Windows, and in the system temp directory on UNIX. Additionally, temporary files are generated from history and difference reports when users close the browser without logging out of the project. Delete these files from the VM_Install_Dir\vm\inet\temp\html directory.

Return to Contents


9.0 Known Issues

9.1 Vista and Internet Explorer 7: Disable Protected Mode

You must disable Protected Mode for the zone in which you will access the Version Manager web client. You can do this from the Internet Options dialog box in Internet Explorer (Tools | Internet Options | Security tab).

9.2 Windows 2003 Server: Double-Byte File Names over 28 Characters Cause "HTTP 404 Page Not Found" Error

This error occurs when you click on the link to see the revision information for a file with a file name that is over 28 double-byte characters in length.

Workaround: Create the following DWORD value under the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters

"UrlSegmentMaxLength"

Set the value to 500.

9.3 Naming Considerations

9.4 Using Event Triggers

The functionality of event triggers differs significantly in the Version Manager web client compared to the Version Manager desktop client. The difference is caused by how archives are modified. When you use the Version Manager web client to perform a task, the archives are modified by the Version Manager web server--not by the Version Manager web client. Therefore, the data and operations available to event triggers through the Version Manager web client differ from the data and operations available to event triggers through the Version Manager desktop client.

When working with event triggers, note the following:

9.5 Updating Keyword Values When You Add or Check In Workfiles

The Version Manager web client does not automatically update the expanded keyword values in your workfiles after you add them or check them in. To update the keyword values, get or check out the files to your workfile location.

9.6 Error During Startup of Version Manager Web or WebDAV Server

When attempting to start the Version Manager web server or WebDAV Server, you may get a Java exception error that includes the text JVM_Bind:8080 or JVM_Bind:8090. This may occur for one of the following reasons:

To change the port number, go to VM_Install_Dir/vm/common/tomcat/conf/server.xml, and change the value of Http10Connector port=.

You may also need to change the following ports if another application is using them:

If you change one or both of these entries to a different port number, make sure that the same ports are specified in the worker.apj12.port= and worker.apj13.port= statements of the VM_Install_Dir/vm/common/tomcat/conf/jk/workers.properties file.

NOTE: If you already have another Tomcat installation, you should change the shutdown port from 8005 to an unused value. Otherwise, both applications will stop when either application's shutdown routine is called.

9.7 Multi-Byte Characters Not Supported with iPlanet

At this time, the Version Manager Web Client does not support multi-byte characters when used with the iPlanet Web server. For multi-byte support, please use the Microsoft IIS Web server.

9.8 Pop-Up Blocking Prevents Version Manager From Working Correctly

If your browser is configured to prevent pop-up ads, the Version Manager web client may not work correctly. Either turn off the pop-up blocking feature, or add the Version Manager server to the list of sites that are allowed to display pop-up windows.

9.9 Windows: Application Server Freezes When Started and Stopped Without Accessing Any Archives

On Windows, if you start the Version Manager Application Server and then stop it before it has been used to access any archives, the daemons do not shut down cleanly. If this happens, close the Serena PVCS Version Manager Application Server console window, and remove the DaemonServer.exe process in the Windows Task Manager.

9.10 Issue Running Version Manager Web Server on Itanium

If you are using the Itanium processor, edit vm/common/bin/pvcsrunner.bat, replacing -server with -Xint. (This disables the HotSpot compiler.)

9.11 Ampersands or Upper-ASCII Characters in Servlet Definitions Cause Errors

Errors occur on the Version Manager Web Server if there is a literal ampersand or an upper-ASCII character in any field of a servlet definition.

If you need to use an ampersand character (&) in the servlet description, use the entity form (&amp;) rather than the literal form (&).

9.12 Web Server Aplication Requires Definition of "localhost" on the File Server

If one, or more, servlets are defined for the Version Manager Web Server Application (this provides access for the Version Manager Web Client), and the associated project databases are on a Version Manager File Server, then all File Servers containing repositories used by these components must be defined on the server(s) through which the Web Client users connect--including the File Server itself (as "localhost" or using its server name). To do so, see the File Server chapter of the Serena PVCS Version Manager Administrator's Guide.

 

Part 4: Version Manager WebDAV Server

Return to Contents


10.0 Known Issues

10.1 Client Issues

If you are able to connect to WebDAV Server but encounter problems working in a WebDAV client, the client may have WebDAV issues.

We recommend that you:

10.2 Password Recommendation for WebDAV Clients

Some WebDAV clients (e.g., Dreamweaver) may require you to enter a password for authentication. We recommend that you have a Version Manager password so that the WebDAV clients will work properly. If you do not have a Version Manager password, define one using the Version Manager desktop client.

10.3 Troubleshooting Connection Problems

To troubleshoot connection problems with WebDAV Server, first check the Tomcat server console for any errors or exceptions.

If you do not see any errors, do the following:

10.4 Only Default Versions Visible Through WebDAV Server

The workspace setting for default version (a label) determines which files are visible through WebDAV Server. Unlike the Version Manager desktop client, WebDAV Server only shows the files that match the default version setting. If a default version is not set, then the default is the tip revision of the trunk. In this case, only these tip revisions will be visible through WebDAV Server.

10.5 Specifying Privileges

After successfully connecting to WebDAV Server, most failures on common operations (e.g., check out or add workfiles) occur due to lack of privileges.

NOTE: To be able to create new archives through WebDAV, users must be assigned the Add Version Label privilege in addition to the Create Archive privilege.

Log in to Version Manager as that user to verify that you can perform the operations allowed with the specified privileges. If you can perform the correct operations in Version Manager, you should be able to perform them using WebDAV Server.

If you change a user's privileges, those changes are not visible to the user until you restart Tomcat or the user's current session times out.

10.6 Error During Startup of Version Manager Web or WebDAV Server

When attempting to start the Version Manager web server or WebDAV Server, you may get a Java exception error that includes the text JVM_Bind:8080 or JVM_Bind:8090. This may occur for one of the following reasons:

To change the port number, go to VM_Install_Dir/vm/common/tomcat/conf/server.xml, and change the value of Http10Connector port=.

You may also need to change the following ports if another application is using them:

If you change one or both of these entries to a different port number, make sure that the same ports are specified in the worker.apj12.port= and worker.apj13.port= statements of the VM_Install_Dir/vm/common/tomcat/conf/jk/workers.properties file.

NOTE: If you already have another Tomcat installation, you should change the shutdown port from 8005 to an unused value. Otherwise, both applications will stop when either application's shutdown routine is called.

10.7 Using WebDAV with IIS and Microsoft FrontPage Server Extensions

Microsoft Web Folders auto-detects if Microsoft FrontPage Server Extensions are running on an IIS web server. If detected, the Web Folders client does not use a WebDAV protocol and therefore does not interact with the WebDAV server. If you configure Serena PVCS Version Manager WebDAV Server redirected through an IIS webserver server with MS FrontPage Server Extensions, Web Folder clients will only interact with the FrontPage Server Extensions, and not the WebDAV server.

10.8 Using the Euro Character on Solaris

To ensure that the Euro character works properly on Solaris, do the following:

  1. Install the latest OS patches for Solaris.

  2. In the Solaris Login dialog box (console), click Options and then select Language | en_ISO8859-15.

  3. Log in; then start WebDAV Server by running ./pvcsstart.sh from VM_Install_Dir/vm/common/bin.

 

Part 5: Copyright/Disclaimers/Support

Return to Contents


11.0 Support

11.1 Support Information

To contact Serena support, please log in at support.serena.com.

Return to Contents


12.0 Notice Regarding Third Party Software

12.1 Third Party Software Disclaimers

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.

12.2 Third Party Software Rights

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. All 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–2017 Serena Software, Inc. All rights reserved.