Deployment Error Messages

Following are error messages that will display when the error is detected during deployment configuration validation.

Note: A separate message displays for each instance of an error, e.g. if two viewer names contain invalid characters, there will be two error messages reporting the condition, one for each instance of the error.

Error: Cannot complete validation.

Problem

This is a “catch all” error. If it appears, it means that the configuration file is corrupt.

Solution

The safest approach is to create a new configuration file, after making sure that the configuration specifications are available to re-enter.

Error: “Do not Sync these files” parameter in folder <name> contains one or more invalid characters: \/:"<>|.

Problem

Entries in the Do not sync these files field in the Deployment Configuration Editor right-pane should follow the Windows naming convention for file names.

Only * and ? are allowed wild card characters.

Solution

Check the Do not sync these files value in the Deployment Configuration Editor right-pane for the named folder to find and remove the invalid character.

Error: Folder <folder name> has no <parameter name> parameter.

Problem

This should never happen, unless the configuration file is corrupt. The list of parameters that displays for folders in the Deployment Configuration Editor right-pane is always the same. The values, of course, can change.

Solution

The safest approach is to create a new configuration file, after making sure that the configuration specifications are available to re-enter.

Error: <name> folder name contains one or more invalid characters: /*?"<>|.

Problem

The folder name, the path to the remote folder, should follow the Windows naming convention for file system object names.

Note: For folder names \ and : are allowed, because a folder name can be a path, not a single folder name.

Solution

Check the Local folder path value in the Deployment Configuration Editor right-pane for the named folder to remove the invalid character.

Error: Folder parameter “Local folder path” in <folder name>cannot be blank.

Problem

The Local folder path field in the Deployment Configuration Editor right-pane is not filled in for the named folder. It must have a value.

Solution

Enter the path where the named folder is located on its Viewer.

Error: Folder parameter ”Sync these files” in <folder name> cannot be blank.

Problem

The Sync these files field in the Deployment Configuration Editor right-pane is not filled in for the named folder. It must have a value.

Solution

Enter the files or file types that should be deployed when placed in the named folder.

Error: No folders are configured for viewer <name>.

Problem

Every viewer must have at least one watched folder.

Solution

Create a folder for the Viewer and enter values for its parameters.

Error: No viewers are configured.

Problem

This error can only apply for a Viewer-based configuration. The Server configuration includes a COMMON Viewer in the Deployment Configuration Editor left-pane that cannot be deleted.

The Viewer based configuration initially includes a My Computer Viewer in the left-pane. My Computer can be renamed or deleted. If it was deleted and no other Viewer was added the No viewers are configured error will display when the file is saved.

Solution

Add a Viewer to the configuration.

Error: “Sync these files” parameter in folder <name> contains one or more invalid characters: \/:"<>|.

Problem

Entries in the Sync these files field in the Deployment Configuration Editor right-pane should follow the Windows naming convention for file names.

Only * and ? are allowed wild card characters.

Solution

Check the Sync these files value in the Deployment Configuration Editor right-pane for the named folder to find and remove the invalid character.

Error: <name> viewer name contains one or more invalid characters: \/:*?"<>|.

Problem

The viewer name, which is the same as computer network ID, should follow the Windows naming convention for file system object names.

Solution

Check the named Viewer in the Deployment Configuration left pane and remove any invalid characters.

Example

  1. view1 is listed in the Deployment Configuration Editor left pane with two back slashes.

\\view1

  1. An error message displays in the lower right pane as follows.

Error: "\\view1" Viewer name contains one or more invalid characters: \/:*?"<>|

  1. \\view1 is renamed and is correctly listed as view1.

Error: Viewer <viewer name> has no <parameter name> parameter.

Problem

This should never happen, unless the configuration file is corrupt. The list of parameters that displays for viewers in the Deployment Configuration Editor right-pane is always the same. The values, of course, can change.

Solution

The safest approach is to create a new configuration file, after making sure that the configuration specifications are available to re-enter.

Warning: Folder <name> is not found.

Problem

A folder has been added to a Viewer; however the shared folder is not found in that location.

Solution

Do one of the following.

Verify that the folder UNC path to the deployment server is correct.

Make sure the deployment server is online when deployment is implemented.

Make sure the local viewer is online when it should be included in deployment.

Warning: Local folder path <path> is not found.

Problem

The target path for the deployed files on the Viewer is not found.

Solution

Make sure the path exists on the Viewer when a copy of the configuration file is placed in its Data directory.

Warning: Master configuration path is unreachable.

Problem

The editor checks the access to the master configuration UNC path when saving the configuration file.

The warning means that the network path could not be accessed at the time. This might be because the server or the local machine is off-line, or the path is indeed invalid.

Solution

Make sure the path is valid and, when ready for deployment, that the folder can access the listed Viewers.

More information

Deployment configuration error reporting.

About Server to Viewer file deployment.