Highlighted
Commander
Commander
10102 views

Error with new restricted folders in the PVCS web client.


When I create a restricted folder and then try to access it, it works fine in the local client. But in the web client, when I click on the new restricted folder, it immediately displays a red X on the folder and it can't be accessed at all. No error pop-ups occur, just the red X on the folder.
0 Likes
7 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert


Hello Greg,
Can you please clarify what you mean by "it works fine in the local client"? Do you get access as the same user (kindly compare the username values as shown at the bottom on the screen), or do you get prompted for a (different) user ID and/or (different) password, and you get access once you enter those?
Also, can you please indicate both the exact VM release that the I-Net server is running as well as the login source that is being used in the project database?
Thanks in advance,
- Richard.
0 Likes
Highlighted
Commander
Commander


By the 'local' client, I mean the application thats installed on my machine. The 'web' client is the one most of our users use from the PVCS webserver. I'm the PVCS admin, so I'm allowed access to all the PVCS user apps. The I-Net server is running version 8.1.4.x, and users login to IE 8 browser by going through the login URL (http://pvcs01.dearborn.ford.com/ADAM?... as an example). You get access as the same user.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert


Hello Greg,
Can you please indicate the login source that is used on the project database, and whether or not that login source is modified in the restricted project? Please show the entire contents of the project's CFG file with your reply, as well as the LOGIN section of the CFG file that was used by the PDB root.
Also, can you please confirm that Version Manager shows the same user ID at the bottom of the screen at all levels in the desktop client GUI (PDB root level and project level), and that the I-Net web client shows the same ID at the PDB root level as the desktop client GUI shows at the same level?
Thanks in advance,
- Richard.
P.S. I should point out that use of IE 8 is not supported with VM 8.1.x. It may work to some extent, but please use a supported browser when investigating anomalies. The supported IE releases for VM 8.1.4.x would be IE 6, IE 7. Use of IE 8 is supported as of VM 8.2.1.
0 Likes
Highlighted
Commander
Commander


Let me see if this makes any more sense to you. We have a Raslab server where we can install PVCS for testing purposes. I presently have PVCS installed on it to test one of your hotfixes for another issue. Out of curiosity, I opened one of the PVCS projects giving me the restricted folder problem, clicked on the restricted folder and did get a popup error here. The error is: 'ChangeMan Version Manager could not read the configuration file "I:\PROJ\Test.db\configs\knowax.cfg". Please contact your Serena administrator for further assistance.' It looks like there is a problem with the PVCS server app accessing the configuration file. If I remove the config file on the restricted folder, the folder becomes accessable again.

Version Manager does show the same user ID at the bottom of the screen at all levels in the desktop client as well as the I-Net web client.

The login source is modified in a restricted folder. Here is a sample of a restricted folder's config file:

# VERSION Merant VM_8.0.0.0

# $Revision: 1.21 $

ACCESSDB = "\\pvcsna1\proj\escape.db\configs\WAS6_Prod.db"

The original config file used to build this one has all the rest of the lines removed from it to build this one. Here is the original config file for this project:

# VERSION Merant VM_8.0.0.0

# $Revision: 1.21 $

#####################

# Branching & Locking

#####################

BaseVersion =

BranchVersion =

DefaultVersion =

BranchWarn

MultiLock User

MULTILOCK REVISION

ForceUnlock

%if "$(PVCSVer)" >= "v8.1.4"

PESSIMISTICLOCKING

%endif

#########################

# Access Control Database

#########################

%if "$(PVCSVer)" >= "v6.5.00"

AccessControl

%endif

##############

# Journal File

##############

JOURNAL = "\\pvcsna1\proj\escape.db\journal\escape.jnl"

###############

# Login Sources

###############

%if "$(PVCSVer)" >= "v6.5.00"

LOGIN = LDAP,HOST,VLOGIN

#LOGIN = LDAP,VLOGIN,HOST

%else

LogIn Host

%endif

NoCase = VCSId

#####################

# Workfile Attributes

#####################

NoDeleteWork

###################

# Keyword Expansion

###################

PathSeparator = /

ExpandKeywords NoTouch

#####################

# Reference Directory

#####################

ReferenceDir =

#############################

# Command-line interface only

#############################

VCSDIR = ;"\\pvcsna1\arch\escape.db/*"

NoIgnorePath

SignOn

Verbose

# Diagnostic = 0

VCSEdit =

DateFormat = mm/dd/yyyy hh:mm:ss

MonthNames = January February March April May June July August September October November December AM PM

MessageSuffix = +-msg

NoDeleteMessageFile

############

# Semaphores

############

SemSuffix = +-sem

Semaphore Network = File

Semaphore Local = File

SemaphoreRetry = 6

SemaphoreDelay = 30

################

# Event Triggers

################

EventTrigger AllEvents

EventTrigger PrePut

EventTrigger PostPut

EventTrigger PreGet

EventTrigger PostGet

EventTrigger PostJournal

EventTrigger PrePromote

EventTrigger PreVersionLabel

EventTrigger UnconditionalPrePut

EventTrigger PostPromote

EventTrigger PostVersionLabel

EventTrigger PreLock

EventTrigger PostLock

EventTrigger PreUnLock

EventTrigger PostUnLock

EventTrigger PreCreateArchive

EventTrigger PostCreateArchive

###############

# Archive Files

###############

ArchiveSuffix +-arc

ArchiveSuffix . +.-arc

AutoCreate

NoCtrlZ

############################################################################

# Default Archive Attributes - The following values are used to determine an

# archive's attributes when the archive is created and are not used at any

# other time.

############################################################################

NoExclusiveLock

CheckLock

Owner=

AccessList=

WriteProtect

NoCompressDelta

NoCompressWorkImage

NoCompress

NoGenerateDelta

NoTranslate

NoExpandKeywords

###############################################################################

# Suffix settings for text files. We assume that a file with an unknown suffix

# is a binary file and the above default values are safe for binary files.

###############################################################################

NewLine=\r\n

CommentPrefix=

RecordLength=

######################

# Source Code Suffixes

######################

# C, C++

GenerateDelta .c .cc .cpp .cxx .h .hh .hpp

Translate .c .cc .cpp .cxx .h .hh .hpp

ExpandKeywords .c .cc .cpp .cxx .h .hh .hpp

CommentPrefix .c .cc .cpp .cxx .h .hh .hpp = " * "

# Objective C

GenerateDelta .m

Translate .m

ExpandKeywords .m

CommentPrefix .m = " * "

# Lex

GenerateDelta .l

Translate .l

ExpandKeywords .l

CommentPrefix .l = " * "

# YACC

GenerateDelta .y

Translate .y

ExpandKeywords .y

CommentPrefix .y = " * "

# Java

GenerateDelta .jav .java

Translate .jav .java

ExpandKeywords .jav .java

CommentPrefix .jav .java = " * "

# Fortran

GenerateDelta .f .for .f77 .f90

Translate .f .for .f77 .f90

ExpandKeywords .f .for .f77 .f90

CommentPrefix .f .for .f77 .f90 = "C "

# Pascal

GenerateDelta .pas

Translate .pas

ExpandKeywords .pas

CommentPrefix .pas = " * "

# BASIC

GenerateDelta .bas .frm .vbp .pag .dsr

Translate .bas .frm .vbp .pag .dsr

ExpandKeywords .bas .frm .vbp .pag .dsr

CommentPrefix .bas .frm .pag .dsr = "rem "

CommentPrefix .vbp = "; "

# Visual Studio

GenerateDelta .rc

Translate .rc

ExpandKeywords .rc

CommentPrefix .rc = "// "

# Assembly

GenerateDelta .asm .s

Translate .asm .s

ExpandKeywords .asm .s

CommentPrefix .asm .s = "; "

# Scheme

GenerateDelta .scm

Translate .scm

ExpandKeywords .scm

CommentPrefix .scm = "; "

# Lisp

GenerateDelta .lisp

Translate .lisp

ExpandKeywords .lisp

CommentPrefix .lisp = ";;; "

# COBOL

GenerateDelta .cbl .cob .cpb .cpf .cpy .cpv .eco .pco .sas

Translate .cbl .cob .cpb .cpf .cpy .cpv .eco .pco .sas

ExpandKeywords .cbl .cob .cpb .cpf .cpy .cpv .eco .pco .sas

CommentPrefix .cbl .cob .cpb .cpf .cpy .cpv .eco .pco .sas = " *"

ColumnMask .cbl .cob .cpb .cpf .cpy .cpv .eco .pco COBOL

Renumber .cbl .cob .cpb .cpf .cpy .cpv .eco .pco 1-6 from 10 by 10

###################

# Makefile Suffixes

###################

# Configuration Builder

GenerateDelta .bld

Translate .bld

ExpandKeywords .bld

CommentPrefix .bld = "# "

# Make

GenerateDelta .mk .mak

Translate .mk .mak

ExpandKeywords .mk .mak

CommentPrefix .mk .mak = "# "

#########

# Scripts

#########

# DOS batch

GenerateDelta .bat

Translate .bat

ExpandKeywords .bat

CommentPrefix .bat = "rem "

# Shell

GenerateDelta .sh .csh

Translate .sh .csh

ExpandKeywords .sh .csh

CommentPrefix .sh .csh = "# "

# REXX and NT

GenerateDelta .cmd

Translate .cmd

ExpandKeywords .cmd

# TCL

GenerateDelta .tcl

Translate .tcl

ExpandKeywords .tcl

CommentPrefix .tcl = "# "

#Perl

GenerateDelta .pl

Translate .pl

ExpandKeywords .pl

CommentPrefix .pl = "# "

# AWK

GenerateDelta .awk

Translate .awk

ExpandKeywords .awk

CommentPrefix .awk = "# "

# SED

GenerateDelta .sed

Translate .sed

ExpandKeywords .sed

CommentPrefix .sed = "# "

###################

# Development Tools

###################

# FoxPro

GenerateDelta .prg

Translate .prg

ExpandKeywords .prg

CommentPrefix .prg = "* "

################

# Internet Files

################

# JavaScript

GenerateDelta .js

Translate .js

ExpandKeywords .js

COMMENTPREFIX .js = "//"

# CGI

GenerateDelta .cgi

Translate .cgi

ExpandKeywords .cgi

# HTML

GenerateDelta .htm .html .shtml .asp

Translate .htm .html .shtml .asp

ExpandKeywords .htm .html .shtml .asp

COMMENTPREFIX .html = ""

# Virtual Reality Model

GenerateDelta .wrl

Translate .wrl

ExpandKeywords .wrl

CommentPrefix .wrl = "# "

# DTD

NEWLINE .dtd = \r\n

COMMENTPREFIX .dtd = "<!--"

GENERATEDELTA .dtd

EXPANDKEYWORDS .dtd

# CSS

NEWLINE .css = \r\n

GENERATEDELTA .css

EXPANDKEYWORDS .css

COMMENTPREFIX .css = "/*"

# XML

NEWLINE .xml = \r\n

GENERATEDELTA .xml

EXPANDKEYWORDS .xml

COMMENTPREFIX .xml = "<!--"

# JSP

NEWLINE .jsp = \r\n

EXPANDKEYWORDS .jsp

COMMENTPREFIX .jsp = "//"

GENERATEDELTA .jsp

###########

# Documents

###########

# Text

GenerateDelta .txt .text .etext

Translate .txt .text .etext

ExpandKeywords .txt .text .etext

# PostScript

GenerateDelta .ps .eps .ai

Translate .ps .eps .ai

# Rich Text Format

GenerateDelta .rtf

Translate .rtf

# Troff

GenerateDelta .t .tr .roff .troff .roff .man .me .ms

Translate .t .tr .roff .troff .man .me .ms

# TeX

GenerateDelta .tex

Translate .tex

# LaTeX

GenerateDelta .latex

Translate .latex

# Texinfo

GenerateDelta .txi .texi .texinfo

Translate .txi .texi .texinfo

######

# Data

######

# UU-Encoded

Translate .uu .uue

# Shell Archive

Translate .sha .shar

# Windows INI

GenerateDelta .ini

Translate .ini

# Windows INF

GenerateDelta .inf

Translate .inf

# Tab Separated Values

Translate .tsv

# Comma Separated Values

Translate .csv

# Comma-Delimited

Translate .cas

ACCESSDB = "\\pvcsna1\proj\escape.db\configs\escape.db"

PROMOTE LOCAL DEV

PROMOTE DEV QA

PROMOTE QA PROD

NOEXPANDKEYWORDS .sas

%if "$(System)" == "Windows NT/80x86"

LDAPINFOFILE = "//pvcsna1/proj/pvcsldap_fds.ini"

%else

LDAPINFOFILE = "//pvcsna1/proj/pvcsldap_unix.ini"

%endif
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert


Hello Greg,
The error would seem to indicate that the path "I:\PROJ\Test.db\configs\knowax.cfg" is not accessible from all clients. While you can store any path to a CFG file in Version Manager, care must be taken to ensure the given path is valid for all clients.
Given the paths shown in the CFG file all refer to "\\pvcsna1\pro", you would likely want to use a similar path to access the project CFG file .You could even compare it to the path that is used to access the root-level CFG file (perform a right-click -> Properties on the PDB icon from the desktop client to see that path). The path that is used to access the CFG file becomes extra important if you are using VM File Servers, since those require that the path starts with the Client name of one of the Path Maps that are defined on the File Server(s).
If you change the path to one that can be used by all clients, the problem you are seeing should go away.
One thing in closing: I noticed the project-level CFG file looks like a PDB root-level CFG file, which is generally something you want to avoid. For example, the PROMOTE directives can cause serious problems if the root-level CFG file also defines any of DEV, QA, PROD or LOCAL. If there effectively is no root-level CFG file (meaning it only defines VERY few global directives) then this setup can be OK, but in general you want project-level CFG files to only contain modifications from the root-level CFG file, and not redefine anything that is already defined at the root.
With kind regards,
- Richard.
0 Likes
Highlighted
Commander
Commander


When you use the button on the right to select a configuration file, it populates with the drive letter (K:\) instead of the server name (pvcsna1). This fixed the problem - I'll just have to not be as click happy when populating this box for now on, and pay more due deligence to what I'm doing : )
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert


Hello Greg,
Glad that you were able to get the PDB to work. It is still worth investigating why the default path show up with a K: drive if that is not what should be show there, as that is a source of potential other problems going forward.
If you click the project configuration file button, Version Manager generates a path based on that project's default archive location. If that ends up using a K: drive, then the path listed under "New Archive Location" on the project's Properties screen likely shows the same K: drive reference, and that will drive the archive paths that get stored in the PDB once you start adding files.

    If K: is not valid then that should get resolved to use a valid path instead. Start looking at the highest level archive path in the PDB (root-level), because archive paths use inheritance from the top down.

    If the K: drive is a valid File Server Path Map Client name then using it is OK, and the CFG files should probably not be using the UNC location and switch to the virtual K: drive instead.

Basically you want to have a single path to access files in a repository, even if there are multiple ways to get to that file. Ideally that path is File Server Path Map based, as this avoids having to deal with file-level permissions and/or having the right drive mapped.
If you have any remaining questions, please let me know. If not, then I'm glad all is working now.
Kind regards,
- Richard.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.