| |
Results |
|
Known issues with split archives where the path and filename exceed 255 characters
|
Unable to access. The filename may be illegal , the filename may already exist as a directory, part of the directory path may already exist as a file, the TEMP directory may not exist, or there may be insufficient privileges. Create archive <ArchivePath>)
|
|
|
|
VM: Unable to add some workfiles unless name is changed. Error: "Invalid character in filename, or too many characters in path."
|
When trying to add a workfile with a name such as help, admin, classic, or hotspot an error occurs. Other names could also give a similar error even if they have no illegal characters in file name or long pathnames.
|
|
|
|
Script validation fails if some characters are used in a script name
|
-------- Illegal characters in path . Source:
|
|
|
|
DA: After startup Tomcat catalina log file contains errors like: Invalid URL found in class path
|
java.net.URISyntaxException: Illegal character in path at index 15: file:/D:/Vendor Programs/DA-Profile/conf/ Errors similar to the above may be repeated a few times with the path ending in either conf/ or conf/server/
|
|
|
|
DA: Get startup errors if DA Profile is installed in a pathname that contains a space
|
java.net.URISyntaxException: Illegal character in path at index 15: file:/D:/Vendor Programs/DA-Profile/conf/ Errors similar to the above may be repeated a few times with the path ending in either conf/ or conf/server/
|
|
|
Serena ChangeMan Version Manager Command-Line Reference Guide
|
For information about... See... Assigning privileges "Using Privileges" on page 181 Group privileges "AddGroup privilege" on page 187 "DeleteMessageFile directive" on page 137 "ModifyGroup privilege" on page 198 Illegal path separator character - ignored The configuration file contains a PathSeparator directive that uses an invalid character as the path component separator.
|
|
|
|
Serena PVCS Version Manager Command-Line Reference Guide
|
For information about... See... Assigning privileges "Using Privileges" on page 183 Group privileges "AddGroup privilege" on page 189 "DeleteMessageFile directive" on page 138 "ModifyGroup privilege" on page 200 Illegal path separator character - ignored The configuration file contains a PathSeparator directive that uses an invalid character as the path component separator.
|
|
|
|
Serena PVCS Version Manager Command-Line Reference Guide
|
For information about... See... Assigning privileges "Using Privileges" on page 185 Group privileges "AddGroup privilege" on page 191 "DeleteMessageFile directive" on page 138 "ModifyGroup privilege" on page 202 Illegal path separator character - ignored The configuration file contains a PathSeparator directive that uses an invalid character as the path component separator.
|
|
|
|
Problem: VMINET 6.1: Invalid characters in archives cause browser errors
|
One way to "fix" the problem is to modify, using "vcs -m" or "vcs -t" every change description and workfile description that contains invalid characters . ... The attached program, written by Paul Caruana of the PVCS Answerline can be run against archives, one at a time, to alter the characters to their new ISO standard values. ... - Version Manager executables in your PATH ... Keywords: Illegal character value not supported
|
|
|
|
Change Password fails if Project Database is accessed from a secured Path Map
|
... Server that has Path Map security enabled ... " is not authorized for path "AccessControlDatabasePath ... " is not authorized for path "AccessControlDatabasePath ... (Any non-alphanumerical characters in ProjectDatabaseName ... Disable Path Map Security on the File Server for this Path Map, by removing the path to the Access Control Database file from the Access control database
|
|
|
