Deployer Messages

1232	Repository-based deployment does not support deployment of {0} assets when part of a project that also contains either MWS, Optimize, or Business Rules assets.
Explanation	Deployer does not support deployment of Universal Messaging assets when part of a project that also contains MWS, Optimize, or Business Rules assets.
Action	Remove the the Universal Messaging assets from the deployment set and update the deployment map accordingly. To deploy Universal Messaging assets, you must create a separate project that contains the Universal Messaging assets.

1234	Deployer issued the following exception while attempting to compile the package: "{0}"
Explanation	Deployer invoked the wm.server.packages:compilePackage service, and the compilePackage service returned an error.
Action	Verify the network connectivity between the Deployer server and each target Integration Server. Also, verify that the target Integration Servers are up and running. For more information about the error that the compilePackage service returned, see the deploy or simulation report.

1240	Error occurred while attempting to compile the package {0}. Error details : {1}
Explanation	This error message is shown in case of compilation errors while compiling java sources present in Integration Server package.
Action	Fix the compilation issue.

185	Successfully stored the password entry.
Class	I

186	Successfully retrieved the password.
Class	I

187	Successfully deleted the password entry.
Class	I

188	Successfully retrieved the list of password handles.
Class	I

189	Successfully updated the password entry.
Class	I

190	Existing password does not match the specified old password.
Class	E
Explanation	The specified old password does not match the password handle.
Action	Supply the correct existing password.

191	Password handle {0} does not exist.
Class	E
Explanation	An error occurred while retrieving the password entry for the password handle.
Action	Supply a valid password handle.

192	An error occurred while listing password handles.
Class	E
Explanation	An error occurred while getting the list of available password handles from the password store.
Action	Check the Integration Server logs for more details.

193	An error occurred while storing the password entry for handle {0}.
Class	E
Explanation	An error occurred while storing the entry for the specified handle and pasword values.
Action	Check the Integration Server logs for more details.

194	An error occurred while deleting the password entry for handle {0}.
Explanation	An error occurred while deleting the password entry for the supplied password handle.
Action	Check the Integration Server logs for more details.

195	The current user is not authorized to access password store operations.
Class	E
Explanation	Only an authorized user can perform create/delete/update/fetch operations on password stores.
Action	Obtain the proper authorization.

1205	Repository-based deployment does not support the simulate operation for the mapped target servers.
Class	E
Explanation	Repository-based projects do not support simulate operations for the mapped target servers.
Action	Perform Deploy operation.

2	Deployer could not connect to server aliases {0}. Make sure the server alias information is correct and the server is running.
Class	E
Explanation	Deployer could not connect to the specified server when executing the CreateBuild command-line script.
Action	Make sure the connection information specified to the script is correct and that the server is running.

3	You are not authorized to extract the {0} project. Ask an administrator or user that has build authorization for the project to perform this task, or ask an administrator to update the authorization for the specified project to give you build authorization.
Class	E
Explanation	You do not have build authority for the specified project.
Action	Ask an administrator or user that has build authorization for the project to perform this task or ask an administrator to update the authorization for the specified project to give you build authorization.

5	Error checking authorization: {0}. Make sure the service exists and the permissions for the service are adequate to allow execution of the service.
Class	E
Explanation	An error occurred while invoking the wm.deployer.authorization:isAuthorized service on the Integration Server that is running Deployer.
Action	Make sure the service exists and the permissions for the service are adequate to allow execution of the service.

6	Error writing project file into build file {0}. Make sure there is sufficient disk space, memory, and operating system privileges.
Class	E
Explanation	An error occurred while trying to write the project file in the build archive file.
Action	Make sure there is sufficient disk space, memory, and that you have the proper operating system privileges.

7	Error writing properties file into build file {0}. Ensure that the project name was correctly specified and that there is sufficient disk space, memory, and operating system privileges.
Class	E
Explanation	An error occurred while attempting to write the build properties file in the build archive file.
Action	Ensure there is sufficient disk space, memory, and operating system privileges.

8	Error closing build file {0}. Make sure there is sufficient disk space, memory, and operating system privileges to close the build file.
Class	E
Explanation	An error occurred while attempting to close the build file.
Action	Make sure there is sufficient disk space, memory, and operating system privileges to close the build file.

9	Error creating build report {0}. Make sure there is sufficient disk space, memory, and operating system privileges to create a build report.
Class	E
Explanation	An error occurred when attempting to create a build report.
Action	Make sure there is sufficient disk space, memory, and operating system privileges to create a build report.

10	Error during extraction: {0}
Class	E
Explanation	An error occurred while attempting to create a build for a project. The extraction error can be any error that occurred when attempting to create a build. This error can be caused by an object that is listed in the project, but does not exist on the source system.
Action	Ensure that all objects listed in the project exist on the source system.

11	Error extracting IS package {0}: {1}. Make sure the service exists and that the permissions are adequate to allow execution of the service.
Class	E
Explanation	An error occurred while invoking the wm.deployer.resource.extractor.is:extractPackage service.
Action	Make sure the service exists and that the permissions are adequate to allow execution of the service.

12	Error extracting IS ACL(s) on source system {0}: {1}. Make sure the service exists and the permissions are adequate to allow execution of the service.
Class	E
Explanation	An error occurred while invoking the wm.deployer.resource.extractor.is:extractAcls service on the specified source system.
Action	Make sure the service exists and that the permissions are adequate to allow execution of the service.

13	Integration Server ACL {0} does not exist on the source system.
Class	E
Explanation	The identified asset does not exist on the source system.
Action	Either remove the asset from the project or add it to the source system.

14	Deployer encountered the following error while extracting Integration Server users from source system {0}: {1}
Class	E
Explanation	An error occurred while invoking the wm.deployer.resource.extractor.is:extractUsers service on the specified source system.
Action	Make sure the service exists and that you have the proper permissions to execute the service.

15	The Integration Server user account {0} does not exist on the source system. Either remove the user account from the project or create it on the source system.
Class	E
Explanation	The identified IS user account does not exist on the source system.
Action	Either remove the user account from the project or create it on the source system.

16	Deployer encountered the following error while extracting Integration Server groups from source system {0}: {1}
Class	E
Explanation	An error occurred while invoking the wm.deployer.resource.extractor.is:extractGroups service on the specified source system.
Action	Make sure the service exists and that the permissions are adequate to allow execution of the service.

17	The Integration Server group {0} does not exist on the source system. Either remove the group from the project or create the group on the source system.
Class	E
Explanation	The identified Integration Server group does not exist on the source system.
Action	Either remove the group from the project or create the group on the source system.

18	Deployer encountered the following error while extracting Integration Server ports from source system {0}: {1}
Class	E
Explanation	An error occurred while invoking the wm.deployer.resource.extractor.is:extractPorts service on the specified source system.
Action	Make sure the service exists and the permissions are adequate to allow execution of the service.

20	Deployer encountered the following error while extracting Integration Server scheduled service {0} ({1}) from source system {2}: {3}
Class	E
Explanation	An error occurred while invoking the pub.scheduler:getTaskInfo service on the specified source system.
Action	Make sure the service exists and the permissions are adequate to allow execution of the service. If the error message indicates that the scheduled service is not on the source system, either remove the scheduled service from the project or add it to the source system.

21	Deployer encountered the following error while extracting assets from Trading Networks from source system {0}: {1}
Class	E
Explanation	An error occurred while invoking the wm.tn.admin:exportData service on the specified source Trading Networks system.
Action	Make sure the source Trading Networks system is running, the service exists, and the permissions are adequate to allow execution of the service.

35	Error invoking service "{0}".
Class	E
Explanation	An error occurred invoking a service on the Integration Server that is running Deployer.
Action	Verify that the service exists and that the permissions are adequate to execute the service. For more information, see the Integration Server error message in the Integration Server error log.

36	An error occurred while invoking service "{0}" on system "{1}".
Class	E
Explanation	An error occurred while invoking a service on a remote system.
Action	Verify that the service exists and that the permissions are adequate to execute the service. For more information, see the Integration Server error message in the Integration Server error log.

38	Project {0} is empty; it does not contain any assets to extract. Use the Deployer user interface to add assets to the project.
Class	E
Explanation	The specified project does not contain any assets to extract.
Action	Use the Deployer user interface to add assets to the project.

39	The following source servers are currently unavailable: {0}. Check your network connection and make sure the source servers are running.
Class	E
Explanation	The source servers are not responding to a ping. To ping a server, Deployer executes services as follows: - For an Integration Server system, Deployer uses the wm.server:ping service. - For a Trading Networks system, Deployer uses the wm.tn:ping service. - For any other system, Deployer uses the ping plug-in Web service.
Action	Check the network connection and make sure the source servers are running.

41	Deployment set {0} has unresolved dependencies and could result in an incomplete deployment. Use the Deployer user interface to resolve the dependencies
Class	E
Explanation	The deployment set has unresolved dependencies and could result in an incomplete deployment.
Action	Use the Deployer user interface to resolve the dependencies.

42	Integration Server package files {0} do not exist. Use the Deployer user interface to verify and edit the list of files for the package.
Class	E
Explanation	The list of files specified for the package do not exist.
Action	Use the Deployer user interface to verify and edit the list of files for the package.

43	Integration Server package {0} does not exist on the source system. Either remove the package from the project or add it to the source system.
Class	E
Explanation	The identified Integration Server package does not exist on the source system.
Action	Either remove the package from the project or add it to the source system.

44	Deployer encountered the following error while extracting assets from {0} on source system {1}: {2}
Class	E
Explanation	An error occurred while invoking the Deployer plug-in web service getObjects on the specified source system.
Action	Make sure the source system is running, the service exists, and the permissions are adequate to execute the service.

45	Build file {0} does not contain a properties file. Build cannot load because the file is incomplete. Make sure the build file is not corrupted and has not been manually updated.
Class	E
Explanation	Build cannot load because the file is incomplete.
Action	Make sure the build file is not corrupted and has not been manually updated.

53	Integration Server port {0} does not exist on the source system and was not extracted into the build. Make sure the port exists in the source system.
Class	E
Explanation	The Integration Server port was not extracted into the build.
Action	Make sure the port exists in the source system.

54	The Integration Server scheduled service does not exist on source system {0}: {1}
Class	E
Explanation	The scheduled service does not exist on the source server.
Action	Either remove the scheduled service from the project or add it to the source system.

68	Deployer encountered the following error while extracting Integration Server package {0} node ACLs: {1}
Class	E
Explanation	Error when executing the wm.deployer.resource.gui.IS:getTypedPackageContents service.
Action	Make sure the service exists on the Integration Server and the user has the necessary privileges to execute the service.

69	Error writing to the build file {0}. Make sure the build file exists, that it has read/write permission, and that the file system has adequate space.
Class	E
Explanation	An error occurred while trying to write to the build file.
Action	Read the error message to determine the possible causes. Make sure the build file exists, that it has read/write permission, and there is adequate space for it on the file system.

70	Trading Networks field group {0} does not exist on the specified source Trading Networks system. Either remove the profile field group from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks profile field group does not exist on the specified source Trading Networks system.
Action	Either remove the profile field group from the project or add it to the source Trading Networks system.

71	Trading Networks field definition {0} does not exist on the source Trading Networks system. Either remove the profile field definition from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks profile field definition does not exist on the source Trading Networks system.
Action	Either remove the profile field definition from the project or add it to the source Trading Networks system.

72	Trading Networks Profile {0} does not exist on the source Trading Networks system. Either remove the profile from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks profile does not exist on the source Trading Networks system.
Action	Either remove the profile from the project or add it to the source Trading Networks system.

73	Trading Networks TPA {0} does not exist on the source Trading Networks system. Either remove the TPA from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks trading partner agreement (TPA) does not exist on the source Trading Networks system.
Action	Either remove the TPA from the project or add it to the source Trading Networks system.

74	Trading Networks document attribute {0} does not exist on the source Trading Networks system. Either remove the document attribute from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks document attribute does not exist on the source Trading Networks system.
Action	Either remove the document attribute from the project or add it to the source Trading Networks system.

75	Trading Networks document type {0} does not exist on the source Trading Networks system. Either remove the Trading Networks document type from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks document type does not exist on the source Trading Networks system.
Action	Either remove the Trading Networks document type from the project or add it to the source Trading Networks system.

76	Trading Networks processing rule {0} does not exist on the Trading Networks source system. Either remove the processing rule from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks processing rule does not exist on the Trading Networks source system.
Action	Either remove the processing rule from the project or add it to the source Trading Networks system.

77	Trading Networks external ID type {0} does not exist on the source Trading Networks system. Either remove the external ID type from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks external ID type does not exist on the source Trading Networks system.
Action	Either remove the external ID type from the project or add it to the source Trading Networks system.

78	Trading Network contact type {0} does not exist on the source Trading Networks system. Either remove the contact type from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks contact type does not exist on the source Trading Networks system.
Action	Either remove the contact type from the project or add it to the source Trading Networks system.

79	Trading Networks binary type {0} does not exist on the source Trading Networks system. Either remove the binary type from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks binary type does not exist on the source Trading Networks system.
Action	Either remove the binary type from the project or add it to the source Trading Networks system.

80	Trading Networks profile group {0} does not exist on the source Trading Networks system. Either remove the profile group from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks profile group does not exist on the source Trading Networks system.
Action	Either remove the profile group from the project or add it to the source Trading Networks system.

81	Trading Networks extended field {0} for profile {1} does not exist on the source Trading Networks system for the specified profile. Either remove the extended field from the project or add it to the appropriate profile in the source Trading Networks system.
Class	E
Explanation	The identified Trading Networks extended field does not exist on the source Trading Networks system for the specified profile.
Action	Either remove the extended field from the project or add it to the appropriate profile in the source Trading Networks system.

82	Trading Networks security data item {0} does not exist on the source Trading Networks system. Either remove the security data item from the project or add it to the source Trading Networks system.
Class	E
Explanation	The identifed Trading Networks security data item does not exist on the source Trading Networks system.
Action	Either remove the security data item from the project or add it to the source Trading Networks system.

85	Warning creating build {0}. See build report for details.
Class	W
Explanation	Deployer issued a warning while creating the build.
Action	Check the build report for details.

87	Deployer encountered the following error while extracting Integration Server extended settings from source system {0}: {1}
Class	E
Explanation	An error occurred while invoking the wm.deployer.resource.extractor.is:extractExtendedSettings service on the specified source system.
Action	Make sure the service exists and that the permissions are adequate to allow execution of the service.

93	Trading Networks queue {0} does not exist on the source system. Either remove the asset from the project or add it to the source system.
Class
Explanation	The identified asset does not exist on the source system.
Action	Either remove the asset from the project or add it to the source system.

94	Integration Server extended setting {0} does not exist on the source server.
Class	E
Explanation	The indicated extended setting does not exist on the source server.
Action	Either remove the extended setting from the project or add the extended setting to the source server.

109	TN processing rule {0} does not exist on the source system. Either remove the asset from the project or add it to the source system.
Class
Explanation	The identified asset does not exist on the source system.
Action	Either remove the asset from the project or add it to the source system.

114	TN extended field {0} for profile {1} does not exist on the source system. Either remove the asset from the project or add it to the source system.
Class
Explanation	The identified asset does not exist on the source system.
Action	Either remove the asset from the project or add it to the source system.

117	Cannot write to build directory: {0}. The Integration Server user does not have privileges to create or write to a file. Make sure the user has the correct privileges.
Class
Explanation	The Integration Server user does not have privileges to create or write to a file.
Action	Make sure the user has the correct privileges.

118	Error writing checkpoint report: {0}. An error occurred while attempting to close the build file. Make sure there is sufficient disk space, memory, and operating system privileges.
Class
Explanation	An error occurred while attempting to close the build file.
Action	Make sure there is sufficient disk space, memory, and operating system privileges.

119	IS scheduled service {0} ({1}) does not exist on the source server. Either remove the scheduled service from the project or add it to the source system.
Class
Explanation	The identified asset was not found on the source system.
Action	Either remove the asset from the project or add it to the source system.

122	TN Dls {0} does not exist on the source server. Either remove the asset from the project or add it to the source system.
Class
Explanation	The identified asset does not exist on the source system.
Action	Either remove the asset from the project or add it to the source system.

125	TN Fp {0} does not exist on the source system.
Class
Explanation	The identified asset does not exist on the source system.
Action	Either remove the asset from the project or add it to the source system.

128	TN Archival Service {0} does not exist on the source system.
Class
Explanation	The identified asset does not exist on the source system.
Action	Either remove the asset from the project or add it to the source system.

130	The Target Server/Group {0} is not currently available; skipping that Target Server/Group. Check your network connection, and verify that the Target Server/Group is running.
Class
Explanation	Deployer cannot ping a target server or some servers in a target group. This might occur because the servers in question are not running or because of network latency.
Action	Make sure that the servers in question are running.

131	{0} {1} {2} does not exist on the source system.
Class
Explanation	The identified objects do not exist on the source system.
Action	Either remove the identified objects from the project or add them to the source system.

133	Could not rebuild project {0} because the specific build in the project could not be rebuilt. See the Integration Server logs for more information.
Class
Explanation	Deployer could not migrate the project because the specific build in the project could not be rebuilt.
Action	See the Integration Server logs for more information.

135	Deployer could not migrate project {0}. Make sure all source servers specified in project {0} are running. See the Integration Server logs for more information.
Class
Explanation	Deployer could not migrate the project.
Action	See the Integration Server logs for more information.

136	Could not migrate projects data. See the Integration Server logs for more information.
Class
Explanation	Deployer was unable to migrate the project data.
Action	See the Integration Server logs for more information.

139	Some of the projects could not be migrated. See the Integration Server logs for more information.
Class
Explanation	Deployer could not migrate all projects.
Action	See the Integration Server logs for more information.

144	The source servers hosting the deployment sets are from different releases. Make sure all source servers are from the same release.
Class	E
Explanation	Deployer issues this message and ends the build process when you modify the version of the source server alias for existing projects.
Action	Make sure all source servers are from the same release.

145	Deployer did not migrate the following target groups because the alias servers were not migrated to the correct version. Change the version of the server alias or target group so that the two match.
Class	E
Explanation	You migrated a target group to a different version than that of its server alias.
Action	Change the version of the server alias or target group so that the two match.

153	Marked {0} {1} for deletion. The indicated server, or the network connection to that server, is not available. Alternatively, the command-line values for user and password might not be valid on the indicated server. Confirm that the server is running and reachable, and that the user/password values are valid.
Class	W
Explanation	The indicated server, or the network connection to that server, is not available. Alternatively, the command-line values for user and password might not be valid on the indicated server.
Action	Confirm that the server is running and reachable, and that the user/password values are valid.

154	Streamed file {0} for file {1} in deployment set {3} not found. The Integration Server, or the network connection to that server, might be shut down. Confirm that the server is running and that the network connection is up.
Class	W
Explanation	The Integration Server, or the network connection to that server, might be shut down.
Action	Confirm that the server is running and that the network connection is up.

155	Error while reading streamed file {0} for file {1} in deployment set {3}. See the Integration Server logs for more information.
Class
Explanation	An error occured while reading the streamed file.
Action	See the Integration Server logs for more information.

156	Deployer could not connect to the source server aliases specified in the project. Deployer could not rebuild and upgrade the project {0}. Make sure the server alias information is correct and the servers are running.
Class
Explanation	Deployer could not migrate the project because the specific build in the project could not be rebuilt.
Action	Make sure the source servers for the deployment set in the build are running.

158	Build name {0} contains one or more of the following invalid characters: # & @ ^ ! & * : $ / ` ' ; , ~ + = > < " Remove the invalid characters from the build name.
Class	E
Explanation	The build name contains one or more of the following invalid characters: # & @ ^ ! % * : $ /\ \` ' ; , ~ + = > < \ "
Action	Remove the invalid characters from the build name.

159	Deployer could not migrate the Deployer settings. See the Integration Server logs for more information.
Class	E
Explanation	Deployer encountered an error while migrating the Deployer settings.
Action	Check the Integration Server logs for more information.

161	Deployer could not migrate settings.
Class	E
Explanation	Deployer did not receive the settings during migration.
Action	Reload the Deployer package.

4	Project {0} does not contain a deployment set named {1}.
Class	E
Explanation	The Deployer user interface referenced a deployment set name that is not recognized by the Deployer. Another Deployer session might have deleted this deployment set, or the project might be corrupted on the file system.
Action	Refresh the page and try again. If the same error occurs, this project might be corrupted on the file system and you might have to discard it.

6	Deployer did not find a dependency on component {0} was found.
Class	E
Explanation	The Deployer user interface attempted to delete a dependency that is not recognized by Deployer. Another Deployer session might have deleted the dependency, or the project might be corrupted on the file system.
Action	Refresh the page and try again. If the same error occurs, this project might be corrupted on the file system and you might have to discard it.

7	Deployer cannot access server alias {0} in deployment set {1}.
Class	E
Explanation	The Deployer user interface referenced a source server name that is not recognized by Deployer. Another Deployer session might have deleted the source server from the project, or the project might be corrupted on the file system.
Action	Refresh the page and try again. If the same error occurs, this project might be corrupted on the file system and you might have to discard it.

8	Package {0} from server alias {1} does not exist in deployment set {2}.
Class	E
Explanation	The Deployer user interface referenced a package or server name that is not recognized by Deployer. Another Deployer session might have deleted the package or server name from the project, or the project might be corrupted on the file system.
Action	Refresh the page and try again. If the same error occurs, this project might be corrupted on the file system and you might have to discard it.

9	Server {0} already exists in deployment set {1} as a non-Integration Server server. You cannot add Integration Server objects to it.
Class	E
Explanation	You passed an incorrect value for the parameter.
Action	Avoid executing the service outside of the Deployer user interface.

10	Package {0} already exists in deployment set {1} as a complete package. Cannot add package components or files to it.
Class	E
Explanation	You attempted to add package components to a deployment set that already exists on the deployment set.
Action	If you want to include the entire package in a deployment set, no action is necessary because it is already included. If you want the deployment set to contain only a partial package, first remove the entire package from the deployment set before trying to add specific package components.

11	Project {0} already contains a deployment set named {1}. Use a different name for the new deployment set.
Class	E
Explanation	You attempted to add a deployment set to the specified project, but the project already has a deployment set that uses the same name that you specified.
Action	Use a different name for the new deployment set.

12	Project name {0} contains illegal characters.
Class	E
Explanation	The project name contains spaces or one or more of the following invalid characters: # & @ ^ ! % * : $ /\ \` ' ; , ~ + = > < \ "
Action	Specify another name for the project that does not include the illegal characters.

13	Could not complete project copy due to file system error. Check your Integration Server's disk space. If you believe there is sufficient space, try the copy again. As a final option, manually recreate the project.
Class	E
Explanation	Deployer encountered an error writing the project to disk.
Action	Check your Integration Server's disk space. If you believe there is sufficient space, try the copy again. As a final option, manually recreate the project.

14	Project {0} already exists. Use a different, unique name for the new project.
Class	E
Explanation	A project with the name you specified already exists.
Action	Use a different, unique name for the new project.

15	Deployer was unable to invoke service {0}.
Class	E
Explanation	Deployer was unable to find the specified Integration Server service.
Action	Determine whether a required Integration Server package is disabled, missing, or whether parts are missing. Check for the following packages: WmDeployer, WmAdmin, WmRoot, WmDeployerResource, and WmModeler.

16	Unable to delete build {0}. The build file is probably in use. This file exists in the <serverDirectory>/packages/WmDeployer/persist/projects/<YourProjectName>/builds directory. Locate the process that is accessing this file and stop it. Then try to delete the build again.
Class	E
Explanation	Deployer was unable to delete the specified build file.
Action	The build file is probably in use. This file exists in the <serverDirectory>/packages/WmDeployer/persist/projects/<YourProjectName>/builds directory. Locate the process that is accessing this file and stop it. Then try to delete the build again.

17	Project {0} does not contain a build named {1}.
Class	E
Explanation	The Deployer user interface referenced a build name that is not recognized by Deployer. Another Deployer session might have deleted this build, or the project might be corrupted on the file system.
Action	Refresh the page and try again. If the same error occurs, this project might be corrupted on the file system and you might have to discard it.

18	Deployer could not load build {0}.
Class	E
Explanation	The build file is corrupted.
Action	Use Windows Explorer to locate the <serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\builds directory and manually remove the corrupted build file. Then use Deployer to rebuild.

19	Deployment map {0} already exists in project {1}.
Class	E
Explanation	You attempted to create a deployment map with the same name as an existing deployment map.
Action	Use a different name for the new deployment map.

20	Deployment map {0} does not exist in project {1}.
Class	E
Explanation	The Deployer user interface referenced a deployment map name that is not recognized by the Deployer. Another Deployer session might have deleted this deployment map, or the project on the file system might be corrupted.
Action	Refresh the page and try again. If the same error occurs, this project might be corrupted on the file system and you might have to discard it.

21	Deployer could not load deployment map {0} from project {1}.
Class	E
Explanation	The deployment map file is corrupted.
Action	Use Windows Explorer to locate the <serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\targets directory and manually remove your deployment candidate file. Then use Deployer to recreate it.

26	Deployer could not save deployment map {0}.
Class	E
Explanation	Deployer encountered an error writing to disk.
Action	Check your Integration Server's disk space. If you believe there should be sufficient space, try to save again. If this is not successful, try one or both of the following: Restart the server. Recreate the deployment map.

28	Deployment set {0} is not mapped to target {1}.
Class	E
Explanation	The Deployer user interface referenced a deployment set name that is not recognized by the Deployer. Another Deployer session might have deleted this deployment set, or the project might be corrupted on the file system.
Action	Refresh the page and try again. If the same error occurs, this project might be corrupted on the file system and you might have to discard it.

31	Could not invoke service {0} remotely.
Class
Explanation	An integration service invocation failed.
Action	Ensure that the Integration Server is running and that the service exists on that Integration Server. Also ensure that you have the proper previleges to execute the service.

32	Server Alias cannot be blank.
Class	E
Explanation	You left the required Server Alias field blank.
Action	Specify a value for the Server Alias field and try again.

54	The value specified for the task parameter is not valid.
Class	E
Explanation	You passed an incorrect value for the task parameter. The task must be either DEFINE, MAP, EXTRACT, DEPLOY, or VIEW.
Action	Avoid executing the service outside of the Deployer user interface.

58	Deployer cannot perform export operation because the file {0} already exists under WmDeployer/outbound
Class	E
Explanation	You attempted to export a build with the same name as an existing build.
Action	Use a different name when you export the build.

59	The Deployer import map file {0} is not accessible or does not exist.
Class	E
Explanation	You attempted to import a build that does not exist.
Action	Refresh the Import Build page and try again.

60	User is not authorized to export builds from project {0}.
Class	E
Explanation	You are not authorized to export builds for the specified project. You must have build authorization for the project.
Action	Ask an administrator or user that has build authorization for the project to perform this task or have an administrator assign you build authorization.

61	User is not authorized to import builds to project {0}.
Class	E
Explanation	You are not authorized to import builds for the specified project. You must have build authorization for the project.
Action	Ask an administrator or user that has build authorization for the project to perform this task or have an administrator assign you build authorization.

64	Deployment set {0} already exists in project {1}.
Class	E
Explanation	You attempted to create a deployment set in a project that already contains a deployment set of the same name.
Action	Use a different name for the new deployment set.

65	Deployer encountered an error and did not save deployment {0}.
Class	E
Explanation	Deployer encountered an error while writing to disk.
Action	Check your Integration Server's disk space. If you believe there should be sufficient space, try to save again. If Deployer still cannot save the deployment, restart the server or recreate the deployment candidate.

67	Deployment candidate {0} does not exist in project {1}.
Class	E
Explanation	The Deployer user interface referenced a deployment candidate that is not recognized by Deployer. Another Deployer session might have deleted the deployment candidate, or the project might be corrupted on the file system.
Action	Refresh the page and try again. If the same error occurs, this project might be corrupted on the file system and you might have to discard it.

68	Unable to delete deployment map {0}.
Class	E
Explanation	Deployer was unable to delete the specified deployment map file.
Action	The deployment map file is probably in use. This file exists in the <serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\targets directory. Locate the process that is accessing this file and stop it. Then try to delete the deployment candidate again.

69	Unable to delete deployment candidate {0}.
Class	E
Explanation	Deployer was unable to delete the deployment candidate file.
Action	The deployment candidate file is probably in use. This file exists in the <serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\deployments directory. Locate the process that is accessing this file and stop it. Then try to delete the deployment candidate again.

72	Deployer could not load deployment {0} from project {1}.
Class	E
Explanation	The deployment candidate file is corrupted.
Action	Use Windows Explorer to locate to the <serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\deployments directory and manually remove the deployment candidate file. Then use Deployer to recreate it.

73	Deployer could not add component {0} of type {1}.
Class	E
Explanation	Deployer does not recognize the specified Integration Server component.
Action	Rather than attempting to add the component to the project, add the files that comprise the component (example, "ns" directory). You can also try adding the entire package rather than individual components of the package.

75	When you specify "deploymentName", you cannot specify additional arguments .
Class	E
Explanation	You specified incorrect arguments when running the deploy.bat or deploy.sh script.
Action	The deploy script can either reference an existing deployment candidate or create a new deployment candidate. When you specify the "deploymentName" argument to reference an existing deployment candidate do not supply other arguments.

76	When you specify "newDeploymentName", "buildName" and "deploymentMapName" are required.
Class	E
Explanation	You specified incorrect arguments for the deploy.bat or deploy.sh script.
Action	You can specify the deploy script to either reference an existing deployment candidate or to create a new deployment candidate. If you use the "newDeploymentName" argument to create a new deployment candidate, you must also specify the "buildName" and "deploymentMapName" arguments.

77	You are not authorized to modify the project definition.
Class	E
Explanation	You are not authorized to define a project.
Action	Ask an administrator or user that has define authorization to perform the action for you or have an administrator assign you define authorization.

78	You are not authorized to modify the project target mapping.
Class	E
Explanation	You are not authorized to map a project.
Action	Ask an administrator or user that has map authorization to perform the action for you or have an administrator assign you map authorization.

79	You are not authorized to modify project deployments.
Class	E
Explanation	You are not authorized to deploy a project.
Action	Ask an administrator or user that has deploy authorization to perform the action for you or have an administrator assign you deploy authorization.

80	You are not authorized to remove project builds.
Class	E
Explanation	You are not authorized to build a project.
Action	Ask an administrator or user that has build authorization to perform the action for you or have an administrator assign you build authorization.

81	Deployer cannot delete build {0} because it is being used by deployment candidate {1}.
Class	E
Explanation	You attempted to delete a build that is referenced by a deployment candidate.
Action	Delete or modify the deployment candidate that references the build or do not delete this build.

82	Deployer cannot delete deployment map {0} because it is being used by deployment candidate {1}.
Class	E
Explanation	You attempted to delete a deployment map that is referenced by another deployment candidate.
Action	Delete or modify the deployment candidate that references the deployment map.

83	Deployer encountered the following exception while parsing project {0}: {1}
Class	E
Explanation	An exception occurred while trying to load the project. The exception be due to an input/output error.
Action	Review the exception message to determine the cause of the error.

85	Deployer could not add package {0} to the deployment set.
Class	E
Explanation	Deployer was unable to determine which components in the package were available for variable substitution. The problem might be that the source Integration Server was temporarily unavailable.
Action	Check the Integration Server Error log to determine the reason that Deployer was unable to access information about the package components.

86	Deployment map {0} in project {1} is corrupted and must be removed. It references deployment set {2} which does not exist.
Class	E
Explanation	The deployment map file is corrupted.
Action	Use Windows Explorer to locate the <serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\targets directory and manually remove the deployment map file. Then use Deployer to recreate it.

87	Deployer cannot remove deployment set {0}. It is referenced by deployment map {1}.
Class	E
Explanation	You attempted to delete a deployment set that is being referenced by a deployment map.
Action	Perform one of the following: - Delete or modify the deployment map that references the deployment set. - Do not delete the deployment set.

89	Deployer could not save adapter connection metadata for project {0}
Class	E
Explanation	The project is corrupted.
Action	Retry the last action taken on the deployment project. If the action is unsuccessful, create a new project.

92	Deployer cannot update package {0} version in the deployment set.
Class	E
Explanation	Deployer was unable to access the specified package on the server.
Action	Retry the action. If the action is unsuccessful, investigate why Deployer is unable to locate the specified package on the remote server. If the package appears to be available on the remote server, shut down the Deployer window (as well as the window that launched Deployer) and restart the browser.

93	Both the {0} and the {1} Deployer plug-ins contain the Deployer plug-in type {2}.
Class	E
Explanation	More than one plug-in for the same type of deployment asset has been detected. This indicates a problem with the configuration of the Deployer.
Action	Update the configuration of the Deployer to remove extraneous plug-ins for the same type of deployment asset. Alternatively, you can uninstall, then reinstall Deployer.

96	Deployer is currently unable to access Trading Networks system: {0}.
Class	E
Explanation	No data was returned from the specified Trading Networks server. This indicates that the Trading Networks server is not accessible.
Action	Ensure that the Trading Networks server is accessible over the network and that you have correctly configured the server alias.

97	Deployer is currently unable to access target system: {0}.
Class	E
Explanation	The target Trading Networks Server is not available. The server did not respond to a server ping.
Action	Ensure that the Trading Networks Server is accessible over the network and that you have correctly configured the server alias for the Trading Networks server.

98	Deployer cannot check target cluster configuration. The target is missing the Deployer resource package. This can be installed from the Servers > IS & TN screen.
Class	E
Explanation	An error occurred while Deployer attempted to access a service on the target WmDeployerResource package.
Action	Install the current version of WmDeployerResource package on the target server.

99	Cluster node details not available.
Class	E
Explanation	An error occurred when the Deployer attempted to access a service on the target WmDeployerResource package.
Action	Install the current version of the WmDeployerResource package on the target server. Also, ensure that the target server is running and that Deployer can access it over the network.

101	The source servers hosting the deployment sets are different versions.
Class	E
Explanation	The source servers hosting the deployment sets are different versions.
Action	Modify the source servers to use the same versions.

102	The target server or target group is a different version than the project source. Select servers that use the same version.
Class	E
Explanation	Deployer issues this error message when you add a target server or target group to a deployment map and the version of the target server or group is different than that of the project source server.
Action	Use a target server or target group that is the same version as the project source server.

106	Dependencies may not contain the $ character.
Class	E
Explanation	You added a manual dependency that contains the $ character.
Action	Remove the $ character.

109	Failed to install resource package on Integration Server {0}: {1}
Class	E
Explanation	Deployer is trying to install the WmDeployerResource package on the IntegrationServer indicated by <serverName>, but the attempt failed. The <exceptionMessage> provides more information.
Action	Make sure the server is running and connected to the network, and that the system has sufficient disk space, memory, and necessary operating system privileges.

110	Deployer could not locate resource package {0}. Make sure the WmDeployerResource package has been installed on the Integration Server that hosts Deployer and that the system has sufficient disk space, memory, and the necessary operating system privileges.
Class	E
Explanation	An error occurred when the Deployer tried to locate the WmDeployerResource package. The <exceptionMessage> provides information about why that attempt failed. The resource package might not exist on your Integration Server or might require more memory.
Action	Make sure the WmDeployerResource package has been installed on the Integration Server that hosts Deployer and that the system has sufficient disk space, memory, and the necessary operating system privileges.

112	Unable to import the XML document {0} nl{1}. The XML file you passed in either the import map or the import varsub flow is invalid. Correct the XML file as necessary.
Class
Explanation	The XML file you passed in either the import map or the import varsub flow is invalid.
Action	Correct the XML file as necessary.

114	Input XML varsub information is not valid. It might contain an asset type for which varsub is not supported. Validate the XML file against the wm.deployer.flows:DeploymentMap_Definition or wm.deployer.flows:Varsub_Definition XSD.
Class
Explanation	The varsub XML file is not valid. It might contain an asset type for which varsub is not supported. The assets for which varsub is supported are AdapterConnection, ScheduledService, ExtendedSettings, Port, AdapterNotification, AdapterListener, eform, and webServiceDescriptor.
Action	Validate the XML file against the wm.deployer.flows:DeploymentMap_Definition or wm.deployer.flows:Varsub_Definition XSD.

116	Exporting of map {0} failed; the exported map file already exists in the WmDeployer/replicate/inbound folder. Make a backup of the map file in another location, delete the map file from the inbound folder, and then export the map file again.
Class
Explanation	The exported map file already exists in the WmDeployer/replicate/inbound folder.
Action	Make a backup of the map file in another location, delete the map file from the inbound folder, and then export the map file again.

118	Importing of map {0} failed. Make sure the wm.deployer.gui.UITarget:addMapSetToProject service exists and that the user has the necessary previleges for executing the service, and then try again.
Class
Explanation	This error might occur for no specific reason.
Action	Make sure the wm.deployer.gui.UITarget:addMapSetToProject service exists and that the user has the necessary privileges for executing the service, and then try again.

119	Deployment map {0} already exists in project {1} and cannot be overwritten.
Class
Explanation	You attempted to import a map file for a map that already exists.
Action	Delete the existing map and then import the map. If you need a backup of the existing map export the map and store it in a different location.

120	Unable to list remote server aliases.
Class
Explanation	This error might occur for no specific reason.
Action	Make sure the wm.deployer.Util:listAliases service exists and the user has the necessary privileges for executing the service. then try again.

121	Unable to list target group aliases.
Class
Explanation	This error might occur for no specific reason.
Action	Make sure the wm.deployer.gui.UITargetGroup:listTargetGroups service exists and the user has the necessary privileges for executing the service. Then try again.

124	Deployment set {0} is not valid for project {1}.
Class
Explanation	One or more deployment sets defined in the map file you are importing are not included in the project definition.
Action	Make sure the map file you are trying to import is consistent with the define step of the project.

125	The target server {0} is not valid for plugin type {1}. Either define the target server alias on the Deployer where you are trying to import the map file or remove the target server alias from the exported map file.
Class
Explanation	This error is shown when you attempt to import a map file that contains a target server alias that is not defined on that Deployer.
Action	Either define the target server alias on the Deployer where you are trying to import the map file or remove the target server alias from the exported map file.

126	The target group {0} is not valid for plugin type {1}. Define the target group on the Deployer where you are trying to import the map file or else remove the target group from the exported map file.
Class
Explanation	This error is shown when you try to import a map file that contains a target group not defined on that Deployer.
Action	Define the target group on the Deployer where you are trying to import the map file or else remove the target group from the exported map file.

129	Either the number passed is not a number or is negative. Enter an integer value for the flag -id for the command --showReport.
Class
Explanation	This error is thrown by the Deployer comand line interface for the --showReport command. The --showReport command requires an integer value for the flag -id. If an integer is not entered for this flag then the above error is thrown.
Action	Enter an integer value for the flag -id for the command --showReport.

133	Error exporting properties for the project {0}.
Class
Explanation	This error might occur for no specific reason.
Action	Make sure the wm.deployer.gui.UIProject:getFormattedProjectInfo service exists and the user has the necessary privileges for executing the service.

135	Error retrieving properties for the project {0}.
Class
Explanation	This error might occur for no specific reason.
Action	Make sure the wm.deployer.gui.UIProject:getFormattedProjectInfo service exists and the user has the necessary privileges for executing the service.

136	Unable to import zip file; zip file might be corrupt. Copy the build file from the source Deployer again. If this does not fix the problem, rebuild the original project and export the build again.
Class
Explanation	The build file placed in the WmDeployer/replicate/inbound is corrupted. This can occur because of error while copying the build file.
Action	Copy the build file from the source Deployer again. If this does not fix the problem, rebuild the original project and export the build again.

137	Install of WmDeployerResource package cannot proceed. All the nodes in this cluster are not online. The following nodes are offline: {0}. Installing the package on the local node only.
Class
Explanation	This error occurs when you try to install the WmDeployerResource package on a cluster node and some of the nodes of the cluster are offline.
Action	Make sure all the nodes in the cluster are online.

138	You tried to add a target server or a target group of the same name as one that already exists in the deployment map.
Class	E
Explanation	You tried to add a target server or a target group of the same name as one that already exists in the deployment map.
Action	Rename the target server or target group alias and add it to the map.

139	Cannot import the deployment map. Make sure the field names, values and the structure of the XML file are valid.
Class
Explanation	The exported map does not have the expected structure.
Action	If you modified the XML, validate the exported XML with the service wm.deployer.flows:validateXMLWithXSD. If you are exporting a map, pass the schema file as wm.deployer.flows:DeploymentMap_Definition. If you are exporting a varsub, pass the schema file as wm.deployer.flows:Varsub_Definition.

140	Cannot import variable substitution values. Make sure the field names and values and the structure of the XML file are valid.
Class
Explanation	This error occurs when the exported map does not have the expected structure.
Action	If you have modified the XML, validate the exported xml with the service wm.deployer.flows:validateXMLWithXSD. If you are exporting a map then pass the schema file as wm.deployer.flows:DeploymentMap_Definition. If you are exporting a varsub then pass the schema file as wm.deployer.flows:Varsub_Definition.

142	Project {0} already contains a deletion set named {1}. Rename the deployment or deletion set you are trying to create or delete the existing deployment or deletion set from the project. Then retry your action.
Class
Explanation	You tried to add a deployment or deletion set of the same name as one of the deployment or deletion sets already in the project.
Action	Rename the deployment or deletion set you are trying to create or delete the existing deployment or deletion set from the project. Then retry your action.

143	A project can have only one deletion set for each server type. Deletion set {0} already exists for {1}. You can add assets to existing deleting sets, or delete the existing deletion set before trying to create another deletion set.
Class
Explanation	You attempted to create a deletion set on a project that already contains one. Only one deletion set can be created for a project.
Action	You can add assets to existing deleting sets, or delete the existing deletion set before trying to create another deletion set.

144	Deployer encountered an error while trying to get dependent assets for deletion set {0}. See the Integration Server logs.
Class	E
Explanation	This error might occur for no specific reason.
Action	Ensure the wm.deployer.gui.UITarget:checkTargetDependencies service exists and the user has the necessary privileges for executing the service.

146	Deletion sets definition file {0} already exists for this project. Make a back up of the existing file in another location and then delete the file. Then export the deletion set again.
Class
Explanation	The exported file already exists and another export for the same deletion set would cause this error.
Action	Make a back up of the existing file in another location and then delete the file. Then export the deletion set again.

147	Rollback on deployment candidate {0} failed. Check the rollback report for more information.
Class
Explanation	This error might occur for no specific reason.
Action	Check the rollback report for further information.

148	No such deployment candidate {0} found in project {1}. Delete and recreate the deployment candidate.
Class
Explanation	This error might occur for no specific reason.
Action	Delete and recreate the deployment candidate.

149	Deployment candidate {0} in project {1} is not checkpointed. Use the Deployer command-line interface to create a checkpoint for the deployment candiate. If you want to deploy without creating a checkpoint, use the -force flag.
Class
Explanation	This error is shown when you attempt to deploy without creating a checkpoint from the Deployer command-line interface.
Action	Use the Deployer command-line interface to create a checkpoint for the deployment candiate. If you want to deploy without creating a checkpoint, use the -force flag.

150	The WmDeployerResource package is not installed on the target Integration Server. Install the WmDeployerResource package on the target Integration Server from the Deployer user interface on the Integration Server alias page.
Class
Explanation	The WmDeployerResource package is not installed on the target Integration Server.
Action	Install the WmDeployerResource package on the target Integration Server from the Deployer user interface on the Integration Server alias page.

158	Deployer did not save the versions for the aliases {0} because the aliases do not exist. Make sure the alias for which you specified the version is valid.
Class	E
Explanation	The alias for which you tried to update the version does not exist.
Action	Make sure the alias for which you specified the version is valid.

159	The deployment set contains source servers of different versions. Source servers in a deployment set must be the same version. Remove the source servers with the wrong version from the deployment set or change the versions to match.
Class	E
Explanation	The source servers in the deployment set are different versions.
Action	Remove the source servers with the wrong version from the deployment set or change the versions to match.

160	The deployment maps contain target servers of different versions. Target servers in deployment maps must be the same version. Remove the target servers with the wrong version from the deployment maps or change the versions to match.
Class	E
Explanation	The target servers in the deployment maps are different versions.
Action	Remove the target servers with the wrong version from the deployment maps or change the versions to match.

162	Repository name {0} contains illegal characters.
Class	E
Explanation	The repository name contains one or more spaces or the following invalid characters: # & @ ^ ! % * : $ /\ \` ' ; , ~ + = > < \ "
Action	Remove the invalid characters from the repository alias name.

163	Deployment set name {0} contains illegal characters.
Class	E
Explanation	The deployment set name contains one or more spaces or the following invalid characters: # & @ ^ ! % * : $ /\ \` ' ; , ~ + = > < \ "
Action	Remove the invalid characters from the deployment set name.

164	Deployment map name {0} contains illegal characters.
Class	E
Explanation	The deployment map name contains one or more spaces or the following invalid characters: # & @ ^ ! % * : $ /\ \` ' ; , ~ + = > < \ "
Action	Remove the invalid characters from the deployment map name.

165	Deployment candidate name {0} contains illegal characters.
Class	E
Explanation	The deployment candidate name contains one or more spaces or the following invalid characters: # & @ ^ ! % * : $ /\ \` ' ; , ~ + = > < \ "
Action	Remove the invalid characters from the deployment candidate name.

166	Component {0} not found in composite {1} from repository source {2}.
Class	E
Explanation	The contents of the repository have been modified.
Action	Run the build script again or recreate the repository.

167	There is an error in deployment candidates(s) {0} from project {1}. See the Integration Server logs for more information.
Class	E
Explanation	Deployer displays this error for various reasons.
Action	See the Integration Server logs for an explanation of the exception.

168	Cannot save variable substitutions. There are no servers selected.
Class	E
Explanation	Deployer requires that you select at least one server for variable substitutions.
Action	Select at least one server from the list of selected servers.

172	When adding a new target server to the map, Deployer will remove any checkpoints created for the associated deployment candidates. You must recreate any checkpoints you want to use. Do you want to continue?
Class	W
Explanation	Adding new target servers to the map will cause Deployer to remove any checkpoints previously created for the deployment candidates associated with this map.
Action	If you continue with the change, you must recreate any checkpoints you want to use for the associated deployment candidates.

173	When modifying the deployment set, Deployer will remove any checkpoints created for the associated deployment candidates. You must recreate any checkpoints you want to use. Do you want to continue?
Class	W
Explanation	Modifying the deployment set will cause Deployer to remove any checkpoints previously created for the deployment candidates associated with this project.
Action	If you continue with the change, you must recreate any checkpoints you want to use for the project.

180	Repository {0} is not connected. The specified flat file directory does not exist.
Class	E
Explanation	The specified repository does not exist.
Action	Ensure that the repository exists in the specified location.

183	When modifying the deletion set, Deployer will remove any checkpoints created for the associated deployment candidates. You must recreate any checkpoints you want to use. Do you want to continue?
Class	W
Explanation	If you modify the deletion set, Deployer will remove any checkpoints previously created for the deployment candidates associated with this project.
Action	If you continue with the change, you must recreate any checkpoints you want to use for the project.

201	Checkpoint for Deployment Candidate {0} failed. For more information, see the checkpoint report.
Class	E
Explanation	Possible causes for this error: 1) The project file could not be found in, or loaded from, the build. 2) The target file or deployment candidate could not be loaded from disk. 3) The user is not authorized to create a checkpoint. 4) Another reason shown in the checkpoint report.
Action	Verify that the build is available and correct and that there is sufficient disk space and memory. Also review the checkpoint report and verify that the necessary operating system privileges are set and that the user has authorization to create a checkpoint.

202	Checkpoint for deployment candidate {0} completed with warnings. For more information, see the checkpoint report.
Class	W
Explanation	Deployer encountered a warning while extracting objects from source system.
Action	Review the checkpoint report to determine any further action to take. Most warnings require no action by the user.

206	Checkpoint for deployment candidate {0} failed: {1}
Class	E
Explanation	Deployer encountered an exception while extracting objects from the source system. The following are possible causes for the exception: 1) Deployer could not find project file in, or load it from, the build. 2) Deployer could not load the target file or deployment candidate from disk. 3) The user is not authorized to create a checkpoint. 4) Other reasons as shown in the checkpoint report.
Action	Verify that the build is available and correct, and that there is sufficient disk space and memory. Also review the checkpoint report to verify that the necessary operating system privileges are set and that the user has authorization to create a checkpoint.

300	User is not authorized to create variable substitution file for project {0}.
Class	E
Explanation	You are not authorized to perform the action of variable substitution for the specified project. You must have map authorization for the project.
Action	Ask an administrator or user that has map authorization for the project to perform this task or have an administrator assign you map authorization.

301	Could not save variable substitution file {0}.
Class	E
Explanation	Deployer encountered an error writing to disk.
Action	Check your Integration Server's disk space. If you believe there should be sufficient space, try to save again. If saving again is not successful, perform one or both of the following and retry the action: Restart the server. Recreate the variable substitution information.

302	Variable substitution object type {0} is invalid.
Class	E
Explanation	Deployer attempted to create a variable substitution item that is not valid. This might occur if the service that is attempting to create the variable substitution item is invoked by something other than the Deployer user interface.
Action	Contact Software AG Global Support to report this issue and request a fix.

306	Deployer cannot import the substitute configuration values into the deployment map. The .vs file does not exist.
Class	E
Explanation	There are no .vs files in the WmDeployer/replicate/inbound folder.
Action	Copy the variable substitution file to the WmDeployer/replicate/inbound folder and then import it into the deployment map.

309	Unable to export variable substitution information.
Class	E
Explanation	This error occurs when the exported map already exists in the WmDeployer/replicate/inbound folder.
Action	Backup the file to a different location and delete the original. Then export the map again.

311	The Deployer {0} file is not accessible or does not exist.
Class	E
Explanation	The XML file name you passed for importing the varsub is not present in the WmDeployer/replicate/inbound folder.
Action	Check and correct the file name you passed in the command-line.

1	Version Mismatch Error: The server alias is a different version number than the other source/target servers. Source and target servers must use the same version as the server alias.
Class	E
Explanation	The versions of the source or target servers are different than the version selected for the alias version.
Action	Remove the aliases with the wrong version from the deployment set or change the verison to match the source servers.

2	The target Integration Server is part of a cluster, but is not properly configured to support clustered deployment. See the product documentation for instructions on proper cluster configuration.
Class	W
Explanation	One of the target Integration Servers is not properly configured for clustering.
Action	See the webMethods Integration Server documentation for a description of the proper configuration settings for clustering.

105	No publishable document types needed to be synchronized in the following package(s): "{0}"
Class	I
Explanation	The packages with document types are deployed. However, there are no unsynchronized document types.
Action	Make sure that no unsynchronized document types are used for process development.

111	The source user has no username. Deployer cannot deploy an undefined user.
Class	E
Explanation	This error occurs when Deployer cannot deploy or roll back a target server due to an undefined user.
Action	Verify that the user exists on the source server and that configuration details are correct.

113	The source user "{0}" has a non-ASCII password. Deployer cannot deploy assets to an undefined user.
Class	E
Explanation	Deployer is attempting to deploy an invalid user.
Action	Verify that the selected user is valid.

115	An error occurred while attempting to deploy user "{0}" with the following error message follows: <p>"{1}"</p>
Class	E
Explanation	An error occurred while attempting to deploy a user.
Action	Check the Integration Server logs and error messages in the output report for more information.

118	Deployer encountered the following exception while attempting to put package "{0}" into the inbound directory: "{1}"
Class	E
Explanation	There might be network connectivity problems between Deployer and each target Integration Server. Alternatively, the target Integration Servers might not be currently running.
Action	Verify network connectivity between the Deployer server and each target server. Also, verify that the target Integration Servers are running.

131	Deployment completed with errors. Following is a path to the output report, followed by an error message: "{0}" <p>Error message: "{1}"</p>
Class	E
Explanation	Deployment completed with errors.
Action	Check the Integration Server logs, as well as error messages in the output report.

134	Deployer encountered an error while synchronizing documents in the following packages: "{0}"
Class	E
Explanation	This error occurs when a Broker or UM mapped with an Integration Server is unavailable.
Action	Ensure that the mapped JMS Broker or UM is available.

156	Deployer encountered an error during deployment. Deployer did not find package "{0}" in the build zip file "{1}".
Class	E
Explanation	Deployer invoked the wm.server.util:putPackageFile service and the service returned an error.
Action	See the deployment or simulation report to determine which error putPackageField service returned.

157	Deployer encountered an error during deployment. "{0}" package was not found in the build zip file: "{1}".
Class	E
Explanation	The specified package was not found in the build. Typically, this indicates that the deployment set is not current with the build.
Action	Re-create your deployment set and build files.

160	While attempting to install package "{0}" an exception with the following error message occurred: <p>"{1}"</p>
Class	E
Explanation	Deployer invoked the pub.packages:installPackage service, and the service returned an error.
Action	Verify network connectivity between the Deployer server and each target server. Verify that the target Integration Servers are running. For more information about the error returned by the installPackage service, see the deployment or simulation report. For more information about the installPackage service, see Integration Server Built-In Services Reference.

161	The number of bytes read from package "{0}" was not correct.
Class	E
Explanation	An I/O exception occurred while reading the specified package. As a result, all data from the package could not be read. This exception can occur for the following reasons: - The I/O operation failed or was interrupted while accessing the build file. - A security violation has occurred, which typically means that the user running Deployer does not have correct privileges to access the files.
Action	Verify that the file system and the build file that contains the source package are not corrupt. Verify that the user attempting this action has the proper authority to read files on the file system. You might need to re-create the build.

164	The scheduled service type "{0}" for service name "{1}" is unknown and could not be processed.
Class	E
Explanation	Your version of Deployer is out of date.
Action	Ensure that you have the latest version of the WmDeployer package.

170	Deployer encountered the following error while retrieving the scheduled service with service name "{0}" from target "{1}": "{2}".
Class	E
Explanation	This error occurs when Deployer fails to get details for a scheduled service for the variable substitution.
Action	Verify that the scheduled service exists under the specified name on the target server.

187	Deployer encountered the following exception while performing a remote invoke of the service "{0}": "{1}"
Class	E
Explanation	This error occurs when Deployer cannot invoke a service on a remote server, which indicates that the remote server might be offline.
Action	Verify that the remote server is running and available.

190	Deployer encountered the following error while attempting to deploy Group: "{0}": "{1}"
Class	E
Explanation	An error occurred while attempting to deploy the group.
Action	Recreate the build and deploy the group again.

193	Deployer encountered the following error while attempting to deploy ACL "{0}": "{1}"
Class	E
Explanation	An error occurred while attempting to deploy an ACL.
Action	Check Integration Server logs and error messages in the Deployment report.

197	Deployer encountered the following error while attempting to deploy Port "{0}" associated with package "{1}": "{2}".
Class	E
Explanation	An error occurred while attempting to deploy a port associated with a package.
Action	Check for error messages in the output report and Integration Server logs. Verify that the specificied port is available on the target server. Recreate the build if problems persist.

199	Deployment failed.
Class	E
Explanation	The deployment failed.
Action	Review the deployment report and Integration Server logs to determine the cause of the failure, and take the appropriate action.

204	Deployer encountered the following Trading Networks error while attempting to import "{0}" with name "{1}": "{2}", message: "{3}"
Class	E
Explanation	An error occurred attempting to import one of the following Trading Network object types: Document Attributes, Document Types, Field Groups, ID Types, Contact Types, Binary Types, or Profile Groups. Possible causes include: - A network connection error occurred between the Deployer server and the target Integration Server. - The target Integration Server is not running. - The target WmTN package on the target Integration Server is not loaded or enabled. - There could be problems with the Trading Networks object type being imported to the target.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Networks object type is allowed. See the webMethods Trading Networks documentation for details about permissible Trading Networks object types.

231	There are no required patches specified for the target Integration Server.
Class
Explanation	This message occurs when a user deploys unrequired patches into a target.
Action	See the patch details for more information.

234	Deployer encountered the following error while pausing the listener "{0}" associated with package "{1}": "{2}"
Class	E
Explanation	Could not pause the listener associated with the package.
Action	Check the Integration Server logs and error messages in the output report for more information.

235	Deployer encountered an error while disabling of port "{0}" associated with package "{1}".
Class	E
Explanation	An exception occurred while disabling the port associated with the package.
Action	Check the Integration Server logs and error messages in the output report for more information.

236	Deployer encountered an error while enabling the listener "{0}" associated with package "{1}": "{2}"
Class	E
Explanation	Deployer could not enable the specified listener.
Action	See the webMethods Integration Server documentation for specific instructions on how to enable a listener.

240	Deployer encountered the following error while suspending the triggers: "{0}"
Class	E
Explanation	Deployer could not suspend the triggers on the target Integration Server. Deployer attempts to suspend all triggers by setting the maximum percentage of document retrieval threads and the maximum percentage of trigger execution threads to zero.
Action	Verify network connectivity between Deployer and each target Integration Server. Also, verify that the target Integration Servers are running. For more information about the configuration settings for document retrieval threads and trigger execution threads, see information about configuring the server in the webMethods Integration Server documentation.

242	Could not resume the Integration Server triggers. Error message follows: "{0}"
Class	E
Explanation	Deployer could not resume the triggers on the target Integration Server. Deployer attempts to resume all triggers by resetting the maximum percentage of document retrieval threads and the maximum percentage of trigger execution threads to the values they had before Deployer suspended the triggers.
Action	Verify network connectivity between the Deployer server and each target Integration Server. Verify that the target Integration Servers are running. For more information about configuration settings for document retrieval threads and trigger execution threads, see information about configuring the server in the webMethods Integration Server documentation.

243	Deployer did not deploy deployment set "{0}" because it contains the following unsatisfied dependencies: "{1}"
Class	E
Explanation	The dependencies required by the specified deployment set are missing on the target system.
Action	Either install the necessary components on the target system, or change the Deployer project so that it no longer requires the missing dependencies.

244	Deployer encountered the following exception while checking dependencies on target "{0}" for deployment set "{1}": "{2}"
Class	E
Explanation	An exception occurred while checking dependencies for the deployment set at the target.
Action	Check Integration Server logs and error messages in the output report for exception details.

250	Simulation failed.
Class	E
Explanation	The deployment simulation failed.
Action	Refer to the simulation report and Integration Server logs to determine the cause of the failure and take the appropriate action.

256	There are no targets mapped for the current deployment set.
Class	E
Explanation	There are no valid target servers mapped for the deployment set.
Action	Verify that the specified target servers are mapped appropriately for the current deployment set.

257	Deployer cannot deploy the deployment set because there are no source servers specified.
Class	E
Explanation	There are no source servers mapped for the deployment set to define assets for deployment.
Action	Verify that source servers are defined appropriately for assets to be deployed.

263	The following Trading Networks error occurred while attempting to import processing rules: class: "{0}", message: "{1}"
Class	E
Explanation	An error occurred when attempting to import processing rules into Trading Networks. Possible causes include: - A network connection error between the Deployer server and the target Integration Server running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Networks object type is allowed. See the webMethods Trading Networks documentation for details about permissible processing rules.

265	Deployer encountered the following Trading Networks error while attempting to import "{0}" with a group code "{1}" and name "{2}": class: "{3}", message: "{4}"
Class	E
Explanation	An error occurred when attempting to import field groups into Trading Networks. Possible causes include: - An error in the network connection between the Deployer server and the target Integration Server running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Networks object type is allowed. See the webMethods Trading Networks documentation for details about permissible field groups.

266	Deployer encountered the following Trading Networks error while attempting to import field definitions: class: "{0}", message: "{1}"
Class	E
Explanation	An error occurred when attempting to import field definitions into Trading Networks. Possible causes include: - An error in the network connection between the Deployer server and the target Integration Server running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Networks object type is allowed. See the webMethods Trading Networks documentation for details about permissible field definitions.

270	Deployer encountered the following Trading Networks error while attempting to import partner profiles: class: "{0}", message: "{1}"
Class	E
Explanation	An error occurred when attempting to import partner profiles into Trading Networks. Possible causes include: - A network connection error between the Deployer server and the target Integration Server running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Netwoks object type is allowed. See the webMethods Trading Networks documentation for details about permissible partner profiles.

274	Deployer encountered the following Trading Networks error while attempting to import trading partner agreements: class: "{0}", message: "{1}"
Class	E
Explanation	An error occurred when attempting to import trading partner agreements (TPAs) into Trading Networks. Possible causes include: - A network connection error between the Deployer server and the target Integration Server running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded and/or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The TN object type is allowed. See the webMethods Trading Networks documentation for details about permissible trading partner agreements (TPAs).

277	Deployer encountered an error while attempting to import "{0}" with a type code "{1}" and a name "{2}". The following is the error information from Trading Networks: class: "{3}", message: "{4}"
Class	E
Explanation	An error occurred when attempting to import external ID types, contact types, or binary types into Trading Networks. Possible causes include: - A network connection error between the Deployer server and the target Integration Server running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Networks object type is allowed. See the webMethods Trading Networks documentation for details about permissible external ID types, contact types, and binary types.

280	Triggers were not suspended prior to package deployment. Failure to suspend a trigger during deployment could cause problems on the target server.
Class	E
Explanation	Triggers were not suspended prior to package deployment.
Action	Not suspending a trigger during deployment can cause problems on the target. Check the Integration Server logs for more information.

282	Scheduled services were not suspended prior to deployment. Failure to suspend scheduled services during deployment could cause problems on the target server.
Class	E
Explanation	Scheduled services were not suspended prior to deployment. Failure to suspend scheduled services during deployment can cause problems at the target.
Action	Check the Integration Server logs and error messages in the output report for more information.

284	Scheduled services were not started after deployment.
Class	E
Explanation	Scheduled services were not started after deployment. There might be an issue with a target server.
Action	For more information, check the Integration Server logs and error messages in the output report.

286	Listeners were not suspended prior to deployment. Failure to suspend listeners during deployment could cause problems on the target server.
Class	E
Explanation	Listeners were not suspended prior to deployment. Failure to suspend listeners during deployment could cause problems on the target server.
Action	Check the Integration Server logs for errors in suspending the listeners.

288	Listeners were not started after deployment.
Class	E
Explanation	Listeners were not started after deployment. It happens when the ports are disabled or if they will be used for the first time.
Action	Check the Integration Server logs and error messages in the output report.

296	Deployer did not deploy the {0}, which is required for source package "{1}" and it does not already exist at the target. Although the source package would be deployed to the target, some services in that package will not run correctly until that ACL is created at the target.
Class	E
Explanation	The Read, Write, List, or Execute ACLs required for the deployed package to run correctly are not being deployed to the target Integration Server, and that ACL does not already exist on the target Integration Server. Typically, this indicates that the ACLs associated with the package were not extracted.
Action	Repeat the extraction step using Deployer to ensure that all ACLs are included.

297	Deployer did not deploy the {0}, which is required for source package "{1}" and it does not already exist on the target. Some services in that source package will not run correctly until that ACL is created at the target.
Class	E
Explanation	The Read, Write, List, or Execute ACLs that are necessary for the deployed package to run correctly are not being deployed to the target Integration Server, and the specified ACL does not already exist on the target Integration Server. Typically, this problem indicates that the ACLs associated with the package were not extracted.
Action	Perform the extraction step again using Deployer to ensure that all ACLs are included.

298	Deployer encountered the following exception while invoking of the service "{0}": "{1}"
Class	E
Explanation	This exception occurs when Deployer invokes a service on a remote server.
Action	Verify that the source or target server is available.

302	Deployer encountered the following exception while creating the directory "{0}": "{1}".
Class	E
Explanation	An exception occurred while attempting to create a directory.
Action	Ensure that the appropriate write permissions exist to allow for the creation of the new directory and that adequate free space is available.

303	Deployer encountered an exception while creating one of the temporary jar files in "{0}": "{1}"
Class	E
Explanation	An exception occurred while attempting to create one of the temporary jar files.
Action	Ensure that the appropriate write permissions exist for the new file location and that adequate free space is available.

304	Target Server {0} is unavailable.
Class	E
Explanation	Deployer could not connect to the specified target server.
Action	Verify the following: - Network connectivity between Deployer and each target Integration Server. - The target Integration Servers are running. - The target Integration Server alias is defined on the Deployer host server.

305	An exception occurred while getting a Trading Networks docType object. This is most likely caused by a user-defined extension to the Trading Networks type BizDocType. Copy the jar files containing the extensions from the webM_install_dir/IntegrationServer/packages/WmTN/code/jars directory into the WmDeployer/code/jars directory.
Class	E
Explanation	There is a user-defined extension to a Trading Networks document type and Deployer does not have access to the associated jar files.
Action	To ensure Deployer has access to the associated jar files, copy the jar files containing the extensions from the webM_install_dir/IntegrationServer/packages/WmTN/code/jars directory into the WmDeployer/code/jars directory.

306	An error occurred while attempting to import extended field definitions; error information from Trading Networks: class: "{0}", message: "{1}"
Class	E
Explanation	An error occurred when attempting to import extended field definitions into Trading Networks. Possible causes include: - An error in the network connection between the Deployer server and the target Integration Server that is running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded and/or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Networks object type is allowed. See the webMethods Trading Networks documentation for details about permissible extended field definitions.

307	Deployer encountered the following Trading Networks error while attempting to import security data for profile: "{0}": class: "{1}", message: "{2}"
Class	E
Explanation	Deployer encountered an error occurred while attempting to import the security data for the specified profile into Trading Networks. Possible causes include: - A network connection error between the Deployer server and the target Integration Server running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Networks object type is allowed. See the webMethods Trading Networks documentation for details about permissible Trading Networks Security Data.

308	An error occurred while attempting to import queues: class: "{0}", message: "{1}"
Class	E
Explanation	An error occurred when attempting to import the public queues into Trading Networks. Possible causes include: - A network connection error between the Deployer server and the target Integration Server running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded and/or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Networks object type is allowed. See the webMethods Trading Networks documentation for details about permissible public queues.

309	An error occurred while attempting to import profile group "{0}" with value "{1}". class: "{2}", message: "{3}"
Class	E
Explanation	An error occurred when attempting to import the profile groups into Trading Networks. Possible causes include: - A network connection error between the Deployer server and the target Integration Server running Trading Networks. - The target Integration Server is not running. - The WmTN package is not loaded and/or enabled on the target Integration Server. - The Trading Networks object type being imported to the target might be in error.
Action	Verify the following: - There are no network connectivity errors between the Deployer server and each target Integration Server. - All target Integration Servers are running. - The WmTN package on each target Integration Server is loaded and enabled. - The Trading Networks object type is allowed. See the webMethods Trading Networks documentation for details about permissible profile groups.

326	An error occurred while deploying package "{0}". Item "{1}" could not be loaded because of reason "{2}". The package may have partially loaded; please check your target server.
Class	E
Explanation	The specified package did not load due to the reason returned from the target Integration Server.
Action	See the webMethods Integration Server documentation for the specific requirements for loading a package.

328	The JVM "{0}" on the target server is older than the "{1}" JVM recommended on the source for package "{2}".
Class	E
Explanation	The JVM version running on the target is older than the minimum JVM version property specified by the source.
Action	Change the minimum JVM property for the package being deployed and redeploy the package.

329	The "{0}" target JVM is older than the JVM recommended "{1}" on the source for package "{2}".
Class	E
Explanation	The JVM version running on the target is older that the minimum JVM version property required by the source.
Action	Change the minimum JVM property for the package being deployed, and then deploy again.

330	The target package version is null.
Class	E
Explanation	For partial deployment, Deployer requires that the package is present on the target server and that version of the package is not null and matches that of the source server.
Action	Verify that the package version defined on the target server is appropriate for partial package deployment.

334	Source package is of type Patch and package does not exist on target. The package: "{0}" will not be deployed. Re-define package to Full to deploy the package on target
Class	E
Explanation	This message indicates that the target partial mode package is undefined.
Action	Verify that the specified package exists on the target server and that it is valid for partial package deployment.

337	An error occurred while deploying package: "{0}"
Class	E
Explanation	Deployer invoked the pub.packages:installPackage service and the installPackage service returned an error.
Action	For more information about the error that the installPackage service returned, see the deployment or simulation report. For more information about the installPackage service and the requirements for installing packages, see the Integration Server Built-In Services Reference.

338	Deployer issued the following exception while attempting to activate the package: "{0}"
Class	E
Explanation	Deployer invoked the pub.packages:activatePackage service, and the activatePackage service returned an error.
Action	Verify the network connectivity between the Deployer server and each target Integration Server. Also, verify that the target Integration Servers are up and running. For more information about the error that the activatePackage service returned, see the deploy or simulation report. For more information about the activatePackage service, see the documentation for webMethods Integration Server documentation.

352	The package name "{0}" contains the invalid "{1}" character. For more information about illegal characters, see the webMethods Integration Server documentation.
Class	E
Explanation	The package name contains illegal characters.
Action	See the webMethods Integration Server documentation for information about how to name a package.

353	"{0}" is an invalid value for the Cleanup File Age parameter. Valid values are 1-9999.
Class	E
Explanation	The value specified for the Cleanup File Age parameter is invalid.
Action	Specify a valid value between 1 and 9999 for the Cleanup File Age parameter.

354	Invalid File Age parameter "{0}". Valid values are 0-9999.
Class	E
Explanation	The value specified for the File Age parameter is invalid.
Action	Specify a value between 0 and 9999 for the File Age parameter.

355	The Allow Recursive Polling parameter "{0}" is invalid. Valid values are "yes" and "no".
Class	E
Explanation	The specified Allow Recursive Polling parameter is neither "yes" nor "no".
Action	Specify either "yes" or "no" for the Allow Recursive Polling parameter.

356	The Run As User value "{0}" contains invalid character "{1}". For more information about illegal characters, see the webMethods Integration Server documentation.
Class	E
Explanation	The Run As User value contains illegal characters.
Action	For more information about illegal characters, see the webMethods Integration Server documentation.

357	No value was provided for the required Run services as user parameter.
Class	E
Explanation	The Run services as user parameter value is not specified.
Action	Specify a value for the Run services as user parameter. For more information, see the webMethods Integration Server documentation.

358	"{0}" is an invalid value for the File Polling Interval parameter. Valid values are 1-9999.
Class	E
Explanation	The value specified for the File Polling Interval parameter is invalid.
Action	Specify a valid value between 1 and 9999 for the File Polling Interval parameter.

359	No value is specified for the File Polling Interval parameter. Valid values are 1-9999.
Class	E
Explanation	No value is specified for the File Polling Interval parameter.
Action	Specify a value between 1 through 9999 for the File Polling Interval parameter.

360	"{0}" is an invalid value for the Cleanup Interval parameter. Valid values are 1-9999.
Class	E
Explanation	The value specified for the Cleanup Interval parameter is invalid.
Action	Specify a value between 1 and 9999 for the Cleanup Interval parameter.

361	"{0}" is an invalid value for the Maximum Number of Invocation Threads parameter. Valid values are 1-10.
Class	E
Explanation	The value specified for the Maximum Number of Invocation Threads parameter is invalid.
Action	Specify a value between 1 and 10 for the Maximum Number of Invocation Threads parameter.

362	No value provided for the required Maximum Number of Invocation Threads parameter.
Class	E
Explanation	No value was specified for the Maximum Number of Invocation Threads parameter.
Action	Specify a value between 1 and 10 for the Maximum Number of Invocation Threads parameter.

363	"{0}" is an invalid value for the Port parameter. The Port parameter requires an integer value.
Class	E
Explanation	The value specified for the Port parameter is not an integer.
Action	Specify a valid value for the Port parameter.

364	"{0}" is an invalid value for the Port parameter. The value for the Port parameter must be greater than -1.
Class	E
Explanation	The value for the Port parameter is not valid.
Action	Specify a valid value for the Port parameter.

365	No value was specified for the required Port parameter. Specify a value for the Port parameter.
Class	E
Explanation	No value was specified for the Port parameter.
Action	Specify a valid integer type value that is greater than -1 for the Port parameter.

366	The Client Authentication value: "{0}" is invalid. Valid values are 'true' and 'false'.
Class	E
Explanation	The specified Client Authentication value is neither "true" nor "false".
Action	Specify either "true" or "false" for the Client Authentication value.

367	The Host parameter requires a value.
Class	E
Explanation	The value for the Host parameter was not specified.
Action	Specify a value for the Host parameter.

368	"{0}" is an invalid value for the Type parameter. Valid values are "pop3" and "imap".
Class	E
Explanation	The value specified for the Type parameter is invalid.
Action	Specify either "pop3" or "imap" for the Type parameter.

369	Specify a value for the Type parameter. Valid values are "pop3" and "imap".
Class	E
Explanation	No value is specified for the required Port parameter.
Action	Specify either "pop3" or "imap" for the Port parameter.

370	The user name value: "{0}" contains an invalid character: "{1}". Refer to the Administering Integration Server guide for listed illegal characters.
Class	E
Explanation	The user name value contains illegal characters.
Action	For information about legal characters for user accounts, see the Administering Integration Server guide.

371	No value provided for user name. This field is mandatory.
Class	E
Explanation	No value is provided for user name.
Action	Specify a value for the user name. For information about the legal characters for user accounts, see the Administering Integration Server guide.

372	Invalid value provided for the "Log out after each mail check" parameter: "{0}". Valid values are "yes" and "no".
Class	E
Explanation	The specified value for the "Log out after each mail check" parameter is neither "yes" nor "no".
Action	Specify a valid value for the "Log out after each mail check" parameter. Valid values are "yes" and "no".

373	The Authorize value "{0}" is invalid. Valid values are Yes and No.
Class	E
Explanation	The specified Authorize value is neither Yes and No.
Action	Specify either Yes or No for the Authorize value.

374	"{0}" is an invalid value for the Time Interval parameter. Valid values are 1-9999.
Class	E
Explanation	The value specified for the Time Interval parameter is invalid.
Action	Specify a valid value between 1 and 9999 for the Time Interval parameter.

375	Specify a value for the required Time Interval parameter. Valid values are 1-9999.
Class	E
Explanation	The required Time Interval parameter has not been specified.
Action	Specify a value from 1 through 9999 for the Time Interval parameter.

376	The Reply value: "{0}" is invalid. Valid values are "yes" and "no".
Class	E
Explanation	The specified Reply value is neither "yes" nor "no".
Action	Specify either "yes" or "no" for the Reply value.

377	The Send reply e-mail on error value "{0}" is invalid. Valid values are Yes and No.
Class	E
Explanation	The Send reply e-mail on error value is set to a value other than Yes or No.
Action	Specify either Yes or No for the Send reply e-mail on error value.

378	The Remove value: "{0}" is invalid. Valid values are "yes" and "no".
Class	E
Explanation	The specified Remove value is neither "yes" nor "no".
Action	Specify either "yes" or "no" for the Remove value.

379	"{0}" is an invalid value for the Delete invalid messages parameter. Valid values are Yes and No.
Class	E
Explanation	The value specified for the Delete invalid messages parameter is invalid.
Action	Specify a valid value of Yes or No for the Delete invalid messages parameter.

380	The Multithread processing value "{0}" is invalid. Valid values are Yes and No.
Class	E
Explanation	The Multithread processing is set to a value other than Yes or No.
Action	Specify either Yes or No for the Multithread processing value.

381	"{0}" is an invalid value for the Number of threads if multithreading is turned on parameter. Valid values are 1-99.
Class	E
Explanation	The value specified for the Number of threads if multithreading is turned on field is invalid.
Action	Specify a value between 1 and 99 for the Number of threads if multithreading is turned on field.

382	Enter a value for the Number of threads if multithreading is turned on parameter. Valid values are 1-99.
Class	E
Explanation	There is no value set for the Number of threads if multithreading is turned on parameter.
Action	Specify a value between 1 and 99 for the Number of threads if multithreading is turned on parameter.

383	The Break Mmsg value: "{0}" is invalid. Valid values are "yes" and "no".
Class	E
Explanation	The specified Break Mmsg value is neither "yes" nor "no".
Action	Specify either "yes" or "no" for the Break Mmsg value.

384	The Include Headers value: "{0}" is invalid. Valid values are "yes" and "no".
Class	E
Explanation	The specified Include Headers value is neither "yes" nor "no".
Action	Specify either "yes" or "no" for the Include Headers value.

421	Unknown system type: "{0}".
Class	E
Explanation	The source system type is unknown, which indicates that your version of Deployer is out of date.
Action	Ensure that you have the latest version of the WmDeployer package.

422	Unable to invoke "{1}" because the connection object is of an unknown type. Its value is: "{0}".
Class	E
Explanation	The system type object is set to a value that is not recognized. This issue might occur if the user manually edits the project XML file.
Action	Rebuild the project file and map the steps again. Do not manually edit the project file.

423	Deployer encountered an exception while writing the bytes for package "{0}" to the output stream in preparation for deployment to the target "{1}".
Class	E
Explanation	An exception occurred when Deployer tried to write the package data to disk. That exception can occur for the following reasons: - The I/O operation failed or was interrupted while accessing the build file. - A security violation occurred, which typically means that the user running Deployer lacks the correct privileges to access the files.
Action	Verify that the file system is not corrupt and that adequate disk space is available for writing new files. Also verify that the user has appropriate privileges to write files on the file system.

430	There is no logical server defined for the specified Server ID.
Class
Explanation	Either no logical server is defined in the WmDesigner service on the target Integration Server server, or the server is not up and running and available for process model deployment.
Action	Verify that the logical server is defined in the WmDesigner service on the target Integration Server server and that the server is available.

431	The most-likely fix for that is to use webMethods Administrator on your target server to define a logical server with the name: "{0}".
Class
Explanation	This problem occurs when the logical server is not defined in the WmDesigner service on the target Integration Server server for process model deployment.
Action	Verify that the logical server is defined in the WmDesigner service on the target Integration Server server.

433	Cannot associate {0} ACL "{1}", with "{2}" because user "{3}" is not in the Write ACL: "{4}" .
Class	E
Explanation	Cannot associate the ACL because the user is not a member of the Write ACL.
Action	Add the user to the Write ACL.

435	Deployer cannot suspend selected triggers. You can suspend selected triggers only with Integration Server 6.0.1 Fix 144, Integration Server 6.1 Fix 22, or Integration Server 6.5 and later. Alternatively, you can suspend all triggers in the project properties.
Class	E
Explanation	Selected trigger suspension is supported only in the following releases: - Integration Server 6.0.1 Fix 144 - Integration Server 6.1 Fix 22. - Integration Server 6.5 and later
Action	You can suspend all triggers in the project properties.

447	The "{0}" file was deployed.
Class	I
Explanation	This message occurs when a user deploys files.
Action	Check whether the files are deployed or not.

449	Deployer could not suspend the adapter notifications. Adapter suspension is supported only with Integration Server 6.5 and later.
Class	E
Explanation	Adapter notifications could not be suspended because this functionality is only supported for Integration Server 6.5 and later.
Action	None.

457	Suspend adapter notifications prior to deploying packages. Failure to suspend adapter notifications during deployment can cause problems on the target.
Class	E
Explanation	Adapter notifications were not suspended prior to package deployment.
Action	Check the Integration Server logs and error messages in the output report for more information.

458	Deployer suspended adapter notification "{0}" but could not verify status.
Class	E
Explanation	Deployer suspended the adapter notification but was unable to verify its status after the suspension.
Action	For more information, check the Integration Server logs and error messages in the output report.

459	Deployer resumed adapter notification "{0}" but could not verify status.
Class	E
Explanation	Deployer resumed adapter notification but could not verify the status.
Action	Check the Integration Server logs and error messages in the output report for more information.

460	Suspend trigger "{0}" failed: {1}
Class	E
Explanation	Deployer could not suspend the trigger.
Action	Check the Integration Server logs and error messages in the output report for more information.

461	Suspend adapter notification "{0}" failed: {1}
Class	E
Explanation	Suspension of adapter notification failed.
Action	Recreate the build and deploy again. If the problem persists, check the target server adapter settings.

477	The source group has no name. Deployer cannot deploy an undefined group.
Class	E
Explanation	This message occurs when Deployer attempts to roll back an undefined group.
Action	Verify that the specified group is defined on the source server.

482	The source ACL has no name. Deployer cannot deploy an undefined ACL.
Class	E
Explanation	Deployer attempted to roll back an undefined ACL.
Action	Verify that the specified ACL exists on the source server.

492	The Extended Setting in the source has no name. Deployer cannot deploy an undefined Extended Setting.
Class
Explanation	This message occurs when Deployer attempts to roll back of an undefined Extended Setting.
Action	Verify that the specified Extended Setting exists on the target server.

496	The Trading Networks instance is not currently available on the target server "{0}". Please check your network connection and verify that the Trading Networks instance is installed, configured, and running.
Class	E
Explanation	The target Trading Networks server is not accessible due to a network connection problem.
Action	Check your network connection. Verify that the Trading Networks instance is installed, configured, and running.

501	Deployer issued the following exception after it failed to load the variable substitution object {0}.
Class	E
Explanation	The map file: <serverDirectory>\packages\WmDeployer\persist\projects\<projectName>\targets\<mapName>\<deploymentSetName>_<targetServerName>.xml is either corrupt or not present.
Action	Verify that the map file exists. If it does, you might need to use Deployer to recreate your map and variable substitution actions.

505	ERROR: Failed to generate IData for Port. The following exception was thrown: {0}
Class	E
Explanation	The port type is unknown. This indicates that your version of Deployer is out of date.
Action	See the error log of the Deployer server.

506	Variable {2}, in {0} "{1}" will be changed from "{3}" to "{4}" on the target system.
Class
Explanation	This message is displayed in the deployment report when the variable is substituted during deployment.
Action	Verify that the displayed variables are substituted.

600	The target server is Integration Server {0}, which does not support this feature. Deployer cannot update the following adapter connections with the variable substitution values: {1}
Class	E
Explanation	The version of the target Integration Server is a version prior to version 6.1. Versions of the Integration Server prior to 6.1 do not support the APIs that are required to update the adapter connections.
Action	Either upgrade the target Integration Server to version 6.1 or later, or manually update the Adapter connections on the target system.

615	Deployer encountered an error while retrieving current values for adapter connection "{0}".
Class	E
Explanation	Deployer invoked the wm.art.admin.connection:getResourceConfiguration service but was unable to get current values for the adapter connection in the varsub page.
Action	The wm.art.admin.connection:getResourceConfiguration service might not be operational or the WmART package is not installed on the target machine. Verify that both the service and the package are installed and operational.

706	Rollback failed. For more information, see the rollback report and the Integration Server log.
Class
Explanation	This message occurs when a rollback operation fails.
Action	Review the rollback report and take appropriate action.

850	Deployer issued the following error while rolling back the contact type: "{0}"
Class	E
Explanation	Deployer issued an exception while rolling back the contact type.
Action	Contact the Trading Networks target administrator.

851	Deployer issued the following exception while deleting the document type during rollback: "{0}"
Class	E
Explanation	An exception occurred while deleting the document type.
Action	Contact the administrator of the target Trading Networks system for assistance.

852	Deployer issued the following exception while deleting the field group during rollback: "{0}"
Class	E
Explanation	An exception occurred while deleting the field group.
Action	Contact the administrator of the target server for assistance.

854	Deployer issued the following exception while deleting the external ID type during rollback: "{0}".
Class	E
Explanation	An exception occurred while deleting the external ID type during rollback.
Action	Verify that target server is running, then try the deleting the external ID type again.

856	Deployer issued the following exception while deleting the processing rule during rollback: "{0}"
Class	E
Explanation	An exception occurred while deleting the processing rule.
Action	Contact the administrator of the target server for assistance.

858	Deployer issued the following exception while deleting the profile during rollback: "{0}"
Class	E
Explanation	An exception occurred while deleting the profile.
Action	Verify that the target server is running. Then try the deletion again.

859	Deployer could not suspend the "{0}" scheduled service type with service name "{1}" because it was deployed to a clustered Integration Server.
Class	E
Explanation	The service was deployed to a clustered Integration Server and could not be suspended.
Action	Suspend the service manually at each target.

860	Deployer could not resume the scheduled service type "{0}" with service name "{1}". The service was deployed to a clustered Integration Server and could not be resumed. You must resume the service manually at each target.
Class	E
Explanation	The service was deployed to a clustered Integration Server and could not be resumed.
Action	Resume the service manually at each target.

861	Scheduled services are being deployed to a clustered Integration Server and cannot be started after deployment.
Class	E
Explanation	Scheduled services cannot be started on the clustered target.
Action	Start the services manually on each clustered target.

862	Scheduled services have been deployed to a clustered Integration Server and were not suspended after deployment. If suspension is required, then do so manually at each target.
Class	E
Explanation	Scheduled services could not be suspended at the clustered target after deployment
Action	Suspend the services manually at each target.

864	Deployer requires that scheduled services be updated at a clustered Integration Server, but this is not supported with this release. You can update the scheduled services by deploying them to each of the individual Integration Servers in the cluster.
Class	E
Explanation	This deployment candidate requires that scheduled services be updated at a clustered Integration Server, which is not supported with this release.
Action	Update the services by deploying to each of the individual Integration Servers in the cluster.

869	The deployment failed and Deployer is performing an automatic rollback. Please see the separate rollback report for more information about the failed deployment.
Class	E
Explanation	This message occurs when a deployment fails and an automatic rollback occurs.
Action	Please see the Rollback report and take appropriate action.

1003	An IO exception occurred while attempting to access: "{0}". Exception details follow: "{1}".
Class	E
Explanation	An exception occurred when Deployer tried to create, write data to, or save a file. This exception can occur for the following reasons: - The I/O operation failed or was interrupted while accessing the build file. - A security violation has occurred, which typically means that the user running Deployer lacks appropriate privileges to access the files.
Action	Verify that the file system is not corrupt and that adequate disk space is available for creating, writing, and/or saving new files. Also verify that the user has proper privileges to create, write, and save files on the file system.

1004	An exception occurred while attempting to access "{0}". Exception details follow: "{1}".
Class	E
Explanation	An exception occurred when Deployer tried to access (that is, create, save, read, or load) the indicated <object>, where <object> is one of thte following: checkpoint, deployment, build, deployReport, targetFileName, or targetServer. Possible causes of the exception include the following: - The deployment, reportFiles, or targetFile Object could not be loaded from the file system. - An I/O operation failed or was interrupted while accessing the build or checkpoint file. - A security violation has occurred, which typically means that the user running Deployer does not have privileges to access files necessary to perform the deploy operation. - A target Integration Server Adapter and/or Trigger could not be suspended/resumed. - A variable substitution failed. - Deployer could not obtain a connection to a target server.
Action	Verify the following: - The file system is not corrupt. - Adequate disk space is available for creating and/or saving new files. - The user attempting this action has the proper authority to create and save files on the file system. - The target server is running, and is reachable on the network.

1005	You are not authorized to deploy the "{0}" project.
Class	E
Explanation	The user does not have the authorization to deploy the specified project.
Action	Ask an administrator or user that has deploy authorization to perform the action for you. Alternatively, have an administrator update your authorization to assign you deploy authorization for the project.

1006	You are not authorized to deploy the "{0}" project for the following reason: "{1}".
Class	E
Explanation	An error occurred when invoking the service on the host Integration Server. Integration Server cannot determine whether the user is authorized to deploy the specified project.
Action	Verify that the host Integration Server is still running. If you are running Deployer from a remote location, verify the network connectivity between the Deployer user interface and the server.

1007	The following exception occurred while attempting to process "{0}": "{1}"
Class	E
Explanation	In the message, <subMessage> is one of the following sub-messages that Deployer displays to provide additional information about the exception: -<targetFileName> - An exception occurred while performing a [remote] invoke of the service: <ISServiceName>. Exception details follow: <exceptionInfo> - An exception occurred while attempting to XMLDecode the file: <buildFileName>. Exception details follow: <exceptionInfo>. - <errorMessageReturnedFromIS> - An exception occurred getting a Trading Networks, TN, docType object. That is most likely caused by a user-defined extension to the TN type BizDocType. Copy the jar files, which should be found in the <webM install dir>\\IntegrationServer\\packages\\WmTN\\code\\jars directory, containing those extensions into the WmDeployer/code/jars directory. - Source package is of type upgrade and required target package version is null. - Error: no Logical Server for Server ID" The most-likely fix for that is to use webMethods Administrator on your target server to define a logical server with the name: <sourceSystemName>. - An Exception occurred while attempting to IDataBinCoder the file: '<buildFileName>'. Exception details follow: <exceptionInfo> - Overwrite 'everything else' field is set to <overwriteEverythingElseString>, which is invalid. - The Port: <sourcePortName>, associated with Package: <packageName> - Disabling of the Port: <sourcePortName>, associated with Package: <packageName> - Enabling of the Port: <sourcePortName>, associated with Package: <packageName> - Resuming the scheduled-service: " + scheduledServiceName - Suspending the scheduled-service: " + scheduledServiceName - <serviceName> - A SOAP fault occurred while performing a remote invoke of the service: <ISServiceName>.The SOAP Fault string follows: <faultString> - Getting information about the Port: <sourcePortName>, associated with Package: <packageName> The reason for the exception can be one of the following: - There is a problem with connectivity to the target Integration Server. - The target Integration Server is not running. - The target Integration Server requires a Broker Server, but no Broker Server is connected to it. - There is a user-defined extension to a Trading Networks document type, and Deployer does not have access to the associated jar files. - You specified a partial package for deployment; however, the package does not exist on the target. - You specified a logical server that is not defined on the target. - The overwrite flag is invalid, which can only occur if the build file was manually edited.
Action	Based on the reason for the exception, perform one of the following: - Verify the network connectivity between the Deployer server and each target server. - Verify that each target server is running. - If the target Integration Server requires that a Broker be connected to it, ensure that a Broker is connected. - If a user-defined Trading Networks document type is in use, ensure Deployer has access to the associated jar files. To do so copy the jar files located in the <serverDirectory>\packages\WmTN\code\jars directory (which contain the Trading Networks document type extensions) to the <serverDirectory>\packages\WmDeployer\code\jars directory. - If you specified a partial package and the package does not exist on the target, either remove the package from the deployment or specify a full package for deployment. - If the definition of a logical server is missing, use webMethods Administrator on your target server to define a logical server with the name indicated in the error message. - If the overwrite flag is invalid, ensure that your build file has not been manually edited.

1008	The deploy report: "{0}" already exists. Please move it to a different directory.
Class	E
Explanation	The deploy report already exists.
Action	Move the existing deploy report file to a different directory.

1010	An error occurred interacting with server: "{0}". Exception details follow: "{1}"
Class
Explanation	This error occurs if the servers in a cluster are not up and running or if the cluster is invalid for some reason.
Action	Verify that the cluster is configured correctly and that all servers are up and running.

1011	Error invoking service wm.deployer.UIAuthorization. Contact Software AG support.
Class	E
Explanation	Error invoking service wm.deployer.UIAuthorization.
Action	Contact Software AG support.

1014	An exception occurred while attempting to close the file "{0}". This will not affect deployment, but will keep a lock on the file. Exception details follow: "{1}"
Class	E
Explanation	The build file could not be closed because an I/O exception occurred. The exception can occur for the following reasons: - The I/O operation failed or was interrupted while accessing the build file. - A security violation has occurred, which typically means that the user running Deployer does not have correct privileges to access the files.
Action	Verify that the file system is not corrupt and that adequate disk space is available for saving new files. Also verify that the user attempting this action has proper privileges to save files on the file system.

1015	The Overwrite Existing field is set to {0}, which is invalid.
Class	E
Explanation	The overwrite flag was set to a value that the code did not recognize. This occurs when a user has manually edited the XML in the target file.
Action	Repeat the build and map steps. Do not manually edit the target file.

1018	A null aliasValues IData was returned from the invocation of wm.server.remote:getAliasValue against remote host: {0} Cannot continue with deployment of Trading Networks. Make sure the WmTN package and the Trading Networks JDBC pool on the target server are enabled.
Class	E
Explanation	Deployer invoked the wm.server.remote:getAliasValue service while deploying Trading Networks assets, and a null value was returned.
Action	Make sure the WmTN package and the Trading Networks JDBC pool on the target server are enabled.

1024	The target cluster {0} is not currently available. Deployer is skipping that cluster. Check your network connection and make sure all target servers ({1}) are running within the cluster.
Class	E
Explanation	Deployer cannot connect to the target cluster servers due to network connection problems.
Action	Check your network connection. You should be able to access the target server machines.

1025	webMethods Deployer does not support deployment of certificates. Certificates for profile "{0}" will not be deployed.
Class	W
Explanation	Deployer does not support the deployment of certificates.
Action	Deployer does not support deployment of certificates. Certificates for profile "{0}" will not be deployed.

1026	Deployer cannot enable adapter connection {0} on target {1}. Make sure the pub.art.connection:enableConnection service is operational and the WmART package is installed on the target server.
Class	E
Explanation	Deployer invoked the pub.art.connection:enableConnection service but could not enable adapter notification on the target server after deployment.
Action	Make sure the pub.art.connection:enableConnection service is operational and the WmART package is installed on the target server.

1027	Adapter connection {0} on target {1} is not enabled. Make sure the pub.art.connection:queryConnectionState service is operational and the WmART package is installed on the target server.
Class	E
Explanation	Deployer invoked the pub.art.connection:queryConnectionState service but could not enable adapter connections on the target server after deployment.
Action	Make sure the pub.art.connection:queryConnectionState service is operational and the WmART package is installed on the target server.

1028	Deployer cannot update adapter connection "{0}" on target "{1}".
Class	E
Explanation	Deployer invoked the wm.art.dev.connection:updateConnectionNode service but could not update adapter connections on the target server after deployment.
Action	Make sure the wm.art.dev.connection:updateConnectionNode service is operational and the WmART package is installed on the target server.

1029	Unable to disable adapter connection {0} on target {1}. Check the Integration Server logs and error messages in the output report for more information.
Class	E
Explanation	Unable to disable adapter connection on target.
Action	Check the Integration Server logs and error messages in the output report for more information.

1030	Deployer encountered an error retrieving current values for adapter connection {0} on target {1}. Make sure the wm.art.admin.connection:getResourceConfiguration service is operational and the WmART package is installed on the target server.
Class	E
Explanation	Deployer invoked the wm.art.admin.connection:getResourceConfiguration service but could not get current values for the adapter connection in the varsub page.
Action	Make sure the wm.art.admin.connection:getResourceConfiguration service is operational and the WmART package is installed on the target server.

1031	Deployer cannot set the adapter notification for {0} on target {1}. The selected adapter notification might be active on the target server. Review the project settings.
Class	E
Explanation	Deployer could not set variable substitution values for adapter notification.
Action	The selected adapter notification might be active on the target server. Review project settings to make sure they are appropriate.

1032	The adapter notification for {0} on target {1} is not enabled.
Class	E
Explanation	Deployer invoked the pub.art.notification:queryPollingNotificationState service but could not enable adapter notification on the target server after deployment.
Action	Make sure the pub.art.notification:queryPollingNotificationState service is operational and the WmART package is installed on the target server.

1033	Deployer cannot enable adapter notification for {0} on target {1}.
Class	E
Explanation	Deployer invoked the pub.art.notification:enablePollingNotification service, but could not enable adapter notification on the target server after deployment.
Action	Make sure the pub.art.notification:enablePollingNotification service is operational and the WmART package is installed on the target server.

1034	Deployer cannot disable the adapter notification for {0} on target {1}. Check the Integration Server logs for more information. Re-create the build and redeploy if necessary.
Class	E
Explanation	Deployer cannot disable adapter notification.
Action	Check the Integration Server logs for more information. Re-create the build and deploy again if necessary.

1039	Deployer cannot fine the deployment reports for deployment candidate {0}.
Class	E
Explanation	There are no reports for the deployment candidate.
Action	Try to view the reports using a simulate or deploy operation.

1040	Invalid ID for deployment report. Please use the list command to verify your inputs.
Class	E
Explanation	This message occurs when a Deployer user attempts to view the deployment report through command line interface and the report ID does not exist.
Action	Perform simulate and deploy operations and refer to the report ID shown.

1041	Deployer cannot read report {0}.
Class	E
Explanation	This message occurs when Deployer is unable to display reports in a browser.
Action	Ensure that the report HTML or XML files are valid and not corrupted.

1045	An error occurred while attempting to import functional permissions: class: "{0}", message: "{1}"
Class	E
Explanation	This error occurs when Deployer is unable to deploy Trading Netowrk functional permissions, and it indicates that there might be a problem with the build.
Action	Verify that the selected functional permissions are valid on the source server, and rebuild if necessary.

1049	An exception occurred while deleting DLS "{0}"
Class	E
Explanation	An exception occurred while deleting DLS.
Action	Contact the administrator of the target Trading Networks system for assistance.

1050	An exception occurred while deleting the "{0}" functional permission.
Class	E
Explanation	An exception occurred while deleting the functional permission.
Action	Verify that the target server is running and try the deletion again.

1055	An error occurred while attempting to import DLSs. The following is the error information from Trading Networks: class: "{0}", message: "{1}"
Class	E
Explanation	Deployer displays this error when it cannot deploy Trading Netowrk DLSs. It indicates that there might be a problem with the build.
Action	Verify that the selected DLSs are valid on the source server and rebuild if necessary.

1057	Invalid ID for build report. Use the list command to verify your inputs.
Class	E
Explanation	Deployer displays this message when a Deployer user attempts to view the build report through the command line interface and the specified report ID does not exist.
Action	Perform a build operation on the deployment sets and refer to the build report ID shown.

1058	Unable to read JMS trigger {0}.
Class	E
Explanation	Deployer is unable to read the JMS trigger files from the source server.
Action	Ensure that the JMS trigger was created properly on the source server.

1059	Unable to read build zip file.
Class	E
Explanation	Deployer is unable to read the build zip file while deploying.
Action	Verify that the project build file is correct, and ensure that it has not been corrupted.

1060	Error deploying to cluster. One or more of the nodes in the cluster are not running. Check the cluster configuration and the extended settings for further information.
Class	E
Explanation	Not all of the nodes in the cluster are running.
Action	Check the cluster configuration and the extended settings.

1063	Action failed: The target server is unavailable. See the Integration Server logs for more information.
Class
Explanation	The target server is not available.
Action	Check the Integration Server logs for any relevant errors or messages.

1067	An error occurred while attempting to import archival services. The following is the error information from Trading Networks:<p>class: "{0}", message: "{1}"</p>
Class	E
Explanation	This error occurs when Deployer is unable to deploy the Trading Networks archival services and indicates that there might be a problem with the build.
Action	Verify that the selected archival services are valid on the source server and rebuild if necessary.

1068	Automatic rollback in logical cluster group {0} failed because the connection to target server {1} was refused.
Class	E
Explanation	Deployer displays this message when an automatic rollback fails.
Action	Ensure that the specified server is online and that the network connection works. For more information, see the rollback report and take appropriate action.

1069	Deployment in logical cluster group {0} failed. Connection to target server {1} was refused. Deployer will perform rollback on logical group {2}.
Class	E
Explanation	This error occurs when Deployer is unable to deploy assets to a logical cluster group of target servers.
Action	Verify that the servers in the logical cluster group are online and available.

1074	Deployer cannot import Trading Networks partner profiles without a My Enterprise profile.
Class	E
Explanation	Deployer was unable to deploy the Trading Networks partner profile.
Action	Verify that a My Enterprise profile exists on the target server. If not, you must deploy the My Enterprise profile first.

1076	Deployer encountered an exception while trying to delete {0}. Exception details follow: "{1}"
Class	E
Explanation	An exception occurred while trying to delete the node.
Action	Refresh the node list and try deleting again.

1125	Assets in deletion set {0} have unresolved dependencies. Either add the dependent assets or remove the existing assets from the deletion set.
Class	E
Explanation	Assets in the deletion set have unresolved dependencies.
Action	Add the dependent assets, or remove the existing assets from the deletion set.

1126	Deployment to a logical cluster failed and Deployer performed a rollback. Refer to the deployment and rollback reports for more details.
Class	E
Explanation	Deployment to a logical cluster failed and rollback has occurred.
Action	See the deployment and rollback reports for more details.

1129	Error occured when deploying file to a Target. Please check the target Integration Server logs for details. {0}
Class	E
Explanation	This error occurs when deploying large files. It indicates that the target server WmDeployerResource package is not operational.
Action	Verify that the WmDeployerResource package is installed on the target server. If it is already installed, try re-installing.

1130	An error occured while creating or reading the streaming file {0} corresponding to {1} in the build. Check the target Integration Server logs for details.
Class	E
Explanation	This error occurs when extracting large files from a source server. It indicates that the WmDeployerResource package is not operational.
Action	Verify that the WmDeployerResource package is installed on the target server. If it is already installed, try re-installing.

1135	The deployment or deletion set "{0}" contains unresolved dependencies or references. Please resolve the unresolved dependencies to continue with deployment.
Class	E
Explanation	The deployment or deletion set contains unresolved dependencies or references.
Action	Resolve the unresolved dependencies or references for the deployment or deletion sets in your project.

1152	The delivery of artifacts to the {0} target server failed. For details, check the logs of the target server.
Class	E
Explanation	The delivery of artifacts to the target server failed.
Action	For more information, check the deployment report and the Integration Server log.

1153	The activation of artifacts on the {0} target server failed. For details, check the logs of the target server.
Class	E
Explanation	The activation of artifacts on the target server failed.
Action	For details, check the deployment report and the Integration Server log.

1161	Deployer could not deliver artifacts to {0} because the server is unavailable.
Class	E
Explanation	The target server is unavailable.
Action	Ensure the target server is running.

1167	Unable to delete artifacts previously delivered to {0} because the server is unavailable.
Class	E
Explanation	The target server is unavailable.
Action	Make sure the target server is running.

1173	Skipping the activation of deployment on {0} because the target server is unavailable.
Class	E
Explanation	Target server is unavailable.
Action	Ensure target server is running.

1183	A simulation initiated by user {0} for deployment candidate {1} of project {2} is in progress. Wait until the simulation in progress is complete.
Class	E
Explanation	Another user is running an operation for this project.
Action	Wait until the other operation finishes.

1184	A deployment initiated by the user {0} for deployment candidate {1} of project {2} is in progress. Wait until the deployment in progress is complete.
Class	E
Explanation	Another user is running an operation for this project.
Action	Wait until the other operation finishes.

1185	A rollback initiated by user {0} for deployment candidate {1} of project {2} is in progress. Wait until the rollback in progress is complete.
Class	E
Explanation	Another user is running an operation for this project.
Action	Wait until the other operation finishes.

1186	A checkpoint initiated by user {0} for deployment candidate {1} of project {2} is in progress. Wait until the checkpoint in progress is complete.
Class	E
Explanation	Another user is running an operation for this project.
Action	Wait until the other operation finishes.

1187	You cannot deploy the {0} project because it is not locked.
Class	E
Explanation	The project was not locked before deployment.
Action	Lock the project.

1188	You cannot deploy the {0} project because it is locked by another user.
Class	E
Explanation	Another user has locked the project.
Action	Wait until the project is unlocked by the other user.

1189	You cannot simulate the deployment for the {0} project because it is not locked.
Class	E
Explanation	The project was not locked before simulation.
Action	Lock the project.

1190	You cannot simulate the deployment for the {0} project because it is locked by another user.
Class	E
Explanation	Another user has locked the project.
Action	Wait until the project is unlocked by the other user.

1191	You cannot rollback the deployment for the {0} project because it is not locked.
Class	E
Explanation	The project was not locked before you attempted to roll back the deployment.
Action	Lock the project.

1192	You cannot rollback the deployment for the {0} project because it is locked by another user.
Class	E
Explanation	Another user has locked the project.
Action	Wait until the project is unlocked by the other user.

1193	You are not authorized to generate a checkpoint for the {0} project because it is not locked.
Class	E
Explanation	The project was not locked before you attempted to generate a checkpoint.
Action	Lock the project.

1194	You are not authorized to generate a checkpoint for the {0} project because it is locked by a different user.
Class	E
Explanation	Another user has locked the project.
Action	Wait until the project is unlocked by the other user.

1195	The deletion of delivered to the {0} target server artifacts failed. For details, check the logs of the target server.
Class	E
Explanation	The deletion of delivered to the target server artifacts failed.
Action	Check the deployment report for details. There might be additional information in the log of Integration Server.

1201	Repository-based deployment does not support the rollback operation for the mapped target servers.
Class	E
Explanation	Repository-based projects do not support rollback operations for the mapped target servers.
Action	Only Deploy operation is supported.

1203	There are no target servers or target groups mapped for deployment candidate {0}.
Class	E
Explanation	There are no target servers or target groups mapped to the deployment set in the map step.
Action	Map at least one deployment set to a target server or a target group in the map step.

1204	The success flag does not match any messages returned by the target server {0}.
Class	E
Explanation	Either the target server returned the success flag of true and the messages from the target server contains error messages, or the target returned a success flag of false and the message from the target server does not contain an error message.
Action	Check the target server logs or contact Software AG Global Support.

1206	An error ocurred while saving deployment candidate {0}.
Class	E
Explanation	An error encountered while saving the deployment candidate.
Action	Contact Software AG Global Support.

1210	Deployer did not delete the assets from {0} because the server is unavailable.
Class	E
Explanation	The target server is unavailable.
Action	Ensure target server is running.

1212	Deployer failed to delete the assets on the target server {0}. For more information, see the target server's logs.
Class	E
Explanation	The deletion of assets on the target server failed.
Action	Check the deployment report and the Integration Server log for details.

1215	Deployer failed to delete the assets on the target server {0}. For more information, see the target server's logs.
Class	E
Explanation	The deletion of assets on the target server failed.
Action	Check the deployment report for details. There might be additional information in the Integration Server log.

1216	Target server {0} did not return any messages.
Class	E
Explanation	Deployer did not receive any messages from target server {0}.
Action	Check the target server log for details.

1217	Deletion set {0} contains unresolved dependencies. Please resolve the dependencies to proceed with deployment.
Class	E
Explanation	The deletion set contains unresolved dependencies.
Action	Resolve the unresolved dependencies for the deletion set.

1218	Repository-based deployment does not support the rollback operation for target servers of types {0}.
Class	E
Explanation	Repository-based deployment does not support rollback operation for target servers of the given type.
Action	Remove the assets of the unsupported runtimes from the deployment and deletion sets and update the deployment map accordingly.

1219	Repository-based deployment does not support the simulate operation for target servers of types {0}.
Class	E
Explanation	Repository-based deployment does not support simulate operation for target servers of the given type.
Action	Remove the assets of the unsupported runtimes from the deployment and deletion sets and update the deployment map accordingly.

1220	Repository-based deployment does not support deletion sets for target servers of types {0}.
Class	E
Explanation	Repository-based deployment does not support deletion sets for target servers of the given type.
Action	Remove the assets of the unsupported runtimes from the deletion set and update the deployment map accordingly.

1221	Repository-based deployment does not support deletion sets for the selected target servers.
Class	E
Explanation	Repository-based deployment does not support deletion sets for the selected target servers.
Action	Remove the deletion set from the project.

1222	The repository is corrupted. The binary file for composite {0} of type {1} is missing from repsoitory {2}.
Class	E
Explanation	The binary file is missing from the repository.
Action	Rebuild the repository using Asset Build Environment.

1227	Deployer issued the following exception while deleting the field definition during rollback: "{0}"
Class	E
Explanation	An exception occurred while deleting the field definition.
Action	Contact the administrator of the target server for assistance.

1230	No value was specified for the required package parameter. Specify a value for the package parameter.
Class
Explanation	No value was specified for the package parameter.
Action	Specify a valid package value for the package parameter.

11	Plugin {0} does not exist.
Class	E
Explanation	The specified plug-in is not correctly configured in the Deployer plugin configuration file. This indicates an incomplete or damaged installation, or possibly a modification to the plugin configuration file located in <serverDirectory>\packages\WmDeployer\config\plugin folder.
Action	Make sure a file named <pluginName>.cnf exists in the <serverDirectory>\packages\WmDeployer\config\plugin directory.

25	The versions for the aliases {0} were not persisted successfully. Verify that the specified version is valid.
Class	E
Explanation	The specified versions are not valid.
Action	Ensure that the specified versions are valid.

26	The version {0} reported by the {1} plugin for the server alias {2} does not match the version {3} set by the user.
Class	E
Explanation	The version reported by the plugin is different from the version set for the server alias.
Action	Set the correct version for the server alias.

28	Plugin server name {0} contains illegal characters.
Class	E
Explanation	The plugin server name contains one or more spaces or the following invalid characters: # & @ ^ ! % * : $ /\ \` ' ; , ~ + = > < \ "
Action	Remove the invalid characters from the plugin server name.

30	Plugin server {0} of type {1} does not exist for the specified runtime type. Create a new plugin server or remove it from the project map.
Class	E
Explanation	The plugin server does not exist for the specified runtime type.
Action	Create a new plugin server or remove it from the project map.

1	A target group with the name {0} already exists.
Class	E
Explanation	You specified a name for a target group that already exists. Deployer requires that target groups be uniquely named.
Action	Specify a unique name for the target group.

2	Target group {0} does not exist.
Class	E
Explanation	The specified target group does not exist
Action	Verify that the target group exists in the Deployer server target groups.

5	Error invoking service {0}. This usually indicates a problem with the Integration Server installation. On the local Deployer server, determine whether the following Integration Server packages are disabled, missing, or missing parts:<p>WmDeployer</p><p>WmAdmin</p><p>WmRoot</p><p>WmDeployerResource</p><p>WmModeler</p>
Class	E
Explanation	Deployer was unable to invoke a required Integration Server service. This usually indicates a problem with the Integration Server installation.
Action	On the local Deployer server, determine whether the following Integration Server packages are disabled, missing, or missing parts: WmDeployer WmAdmin WmRoot WmDeployerResource WmModeler

6	Deployer encountered the following error while invoking getConnectionInfo for system {0}: {1}
Class	E
Explanation	Deployer could not retrieve the logical server connection information from the source server. The source server might not be running or the logon credentials might be incorrect.
Action	Make sure the specified source server is running and that the logon credentials in the plug-in server configuration, including the Port value, are correct.

7	The call to getConnectionInfo for system {0} returned the following exception for host name {1}: {2}
Class	E
Explanation	Deployer was unable to retrieve the logical server connection information from the source server. The source server might not be running or the logon credentials might be incorrect.
Action	Make sure the specified source server is running and that the logon credentials in the plug-in server configuration, including the Port value, are correct.

8	The call to getConnectionInfo for system {0} returned the following missing data: {1} Make sure the specified source server is running and that the logon credentials in the plug-in server configuration, including the Port value, are correct.
Class	E
Explanation	Deployer was unable to retrieve the logical server connection information from the source server. The source server might not be running or the logon credentials might be incorrect.
Action	Make sure the specified source server is running and that the logon credentials in the plug-in server configuration, including the Port value, are correct.

9	Deployer encountered the following error while connecting to Integration Server {0}: {1}
Class	E
Explanation	Deployer was unable to connect to the specified remote Integration Server. The Integration Server might not be running, or the logon credentials might be incorrect.
Action	Make sure the Integration Server is running and that the logon credentials in the remote server configuration, including the Port value, are correct.

10	Deployer encountered the following error while invoking the required Integration Server service {0} on system {1}: {2} This usually indicates an incomplete or error with the installation of a plug-in on the remote server. On the specified remote server, determine whether the following required Integration Server packages are disabled, missing, or incomplete:</p><p>- WmDeployer</p><p>- WmAdmin</p><p> - WmRoot</p><p>- WmDeployerResource</p><p>- WmModeler</p>
Class	E
Explanation	Deployer was unable to invoke a required Integration Server service. This usually indicates an incomplete or error with the installation of a plug-in on the remote server.
Action	On the specified remote server, determine whether the following required Integration Server packages are disabled, missing, or incomplete: - WmDeployer - WmAdmin - WmRoot - WmDeployerResource - WmModeler

11	A Target Server with name {0} already exists. Rename the target server alias or use a different name for the Target Group.
Class
Explanation	Target servers and target groups cannot have the same names.
Action	Rename the target server alias or use a different name for the Target Group.

12	Failed to load the plug-in server configuration file {0}. This indicates that the configuration file has been modified and Deployer can no longer parse the configuration file. Try to delete and then re-add the plug-in server. This should correctly recreate the configuration file. If this fails, send the contents of the server configuration file, located in "<serverDirectory>/packages/WmDeployer/config/pluginServer/<pluginName>" to Software AG Global Support.
Class	E
Explanation	When Deployer started, it could not successfully load the plug-in server configuration file. This indicates the configuration file has been modified and Deployer can no longer parse the configuration file.
Action	Try to delete and then re-add the plug-in server. This should correctly recreate the configuration file. If this fails, send the contents of the server configuration file, located in "<serverDirectory>/packages/WmDeployer/config/pluginServer/<pluginName>" to Software AG Global Support.

13	Failed to save plugin server config file {0}. The plug-in configuration file provided by Software AG does not contain the entry identifying the class necessary to remotely install the communication component. The configuration file may have been altered incorrectly. Reinstall Deployer. Your project data will remain unchanged.
Class	E
Explanation	The plug-in configuration file provided by Software AG does not contain the entry identifying the class necessary to remotely install the communication component. The configuration file might have been altered incorrectly.
Action	Reinstall Deployer. Your project data will remain unchanged.

14	{0} target group {1} dependencies have been resolved. See the Integration Server error log for details. Contact webMethods Global Support if the problem cannot be resolved locally.
Class	E
Explanation	The invocation of the Communication Component Installation class has failed.
Action	See the Integration Server error log for details. Contact Software AG Global Support if the problem cannot be resolved locally.

15	{0} Target Group {1} validation failed. Unable to resolve some servers within the group. Your installation could be damaged or corrupt. Reinstall Deployer. Your project data will remain unchanged.
Class	E
Explanation	The remote installation of the communication component was unable to locate the component file on the file system. Your installation could be damaged or corrupt.
Action	Reinstall Deployer. Your project data will remain unchanged.

18	Deployer encountered the following error while pinging plug-in server {0}: {1} Deployer cannot contact the remote server hosting the identified plug-in. The host could be down or the host name could be incorrect. Verify the host name (or IP address) and ensure that the system is available.
Class	E
Explanation	Deployer cannot contact the remote server hosting the identified plug-in. The host could be down or the host name could be incorrect.
Action	Verify the host name (or IP address) and ensure that the system is available.

19	Plug-in {0} on target group {1} does not contain any servers.
Class	E
Explanation	You have attempted to add a target group with no servers.
Action	Add target servers in that target group.

29	Cannot create a Target Group with same name as that of a Target Server. Either rename the target group or delete the existing target group or target server with the same name.
Class
Explanation	You cannot create a target group with same name as one used by a target server.
Action	Either rename the target group or delete the existing target group or target server with the same name.

30	{0} Target Group {1} validation failed. Unable to resolve some servers within the cluster {2} in the group {3}. Make sure all nodes in the cluster are running and the WmDeployerResource package is installed on all of these nodes. If the WmDeployerResource package is not installed, install it using the Deployer user interface.
Class
Explanation	Deployer cannot ping some of the cluster servers.
Action	Make sure all nodes in the cluster are running and the WmDeployerResource package is installed on all of these nodes. If the WmDeployerResource package is not installed, install it using the Deployer user interface.

31	Validation of plug-in {0} on target group {1} failed. Deployer cannot resolve server {2} which is a part of the cluster {3}. Remove this server manually from target group.
Class	E
Explanation	A server in the cluster could not be resolved.
Action	Manually remove the server from the tagret group.

32	Invalid version specified for the target group {0} of type {1}. The valid versions can be {2}.
Class	E
Explanation	The version specified for the target group is not valid.
Action	Specify the correct version.

33	The server aliases {0} version do not match the target group {1} version. Server aliases and target groups must be of the same version. Modify either the definition of the targets within the target group or modify the version of the target group.
Class	E
Explanation	The version of the targets in the target group do not match the version of the parent target group.
Action	Modify either the definition of the targets within the target group or modify the version of the target group.

34	Target group name {0} contains illegal characters.
Class	E
Explanation	The target group name contains one or more spaces or the following invalid characters: # & @ ^ ! % * : $ /\ \` ' ; , ~ + = > < \ "
Action	Remove the invalid characters from the target group name.

35	Target group {0} does not exist.
Class
Explanation	A target group was mapped for deployement but is either not defined or was deleted.
Action	Define the target group.

1	You are not authorized to checkpoint the {0} project. Use the Deployer user interface to grant the user the right to deploy the project.
Class	E
Explanation	The user is not authorized to generate a checkpoint for the project.
Action	Use the Deployer user interface to grant the user the right to deploy the project.

3	Error invoking service "{0}".
Class	E
Explanation	An exception occurred while invoking the wm.deployer.UIAuthorization:isAuthorized service. This could mean that Integration Server is either not running or that it cannot be reached on the network.
Action	Verify that the Integration Server is running and available on the network.

4	Error cloning source system "{0}": {1}
Class	E
Explanation	The project contains a source system of an unknown type.
Action	Rebuild the project.

6	Checkpoint summary file "{0}" does not exist.
Class	E
Explanation	The checkpoint file does not exist on the disk.
Action	Use Deployer to create a checkpoint.

7	Cannot write to checkpoint directory "{0}".
Class	E
Explanation	You cannot create or write to the specified directory.
Action	Ensure that you have the correct privileges to create and write to the directory and that the file system has enough space for the creation of a new directory.

9	Error creating checkpoint "{0}": {1}
Class	E
Explanation	An exception occurred while creating the checkpoint report.
Action	Ensure that you have the correct privileges to create and write to files and that the file system has enough space for the new file.

10	Error saving checkpoint project {0}: {1}. Make sure you have the correct privileges to create and write to files and that the file system has enough space for the new file
Class	E
Explanation	The specified file could not be saved to disk.
Action	Make sure you have the correct privileges to create and write to files and that the file system has enough space for the new file.

13	Deployer cannot generate a checkpoint at {0} because the target server is unavailable
Class	E
Explanation	The target server is unavailable.
Action	Ensure that the target server is running.

15	Checkpoint on the target server {0} failed. Please check the target server's logs for details.
Class	E
Explanation	The checkpoint operation failed due to the reason specified in the checkpoint report.
Action	Check the checkpoint report for details. There might also be additional information in the Integration Server log.

18	Skipping the delete checkpoint for {0} because the server is unavailable.
Class	E
Explanation	The target server is unavailable.
Action	Ensure that the target server is running.

22	Failed to delete checkpoint for target server {0}.
Class	E
Explanation	Deletion of checkpoint failed.
Action	Check Deployer and Integration Server logs.

23	Repository-based deployment does not support the checkpoint operation for the mapped target servers.
Class	E
Explanation	Repository-based projects do not support checkpoint operations for the mapped target servers
Action	Perform Deploy operation.

24	Deployer does not allow you to create checkpoints for transactional deployment.
Class	I
Explanation	You cannot create a checkpoint for projects that use transactional deployment. Deployer creates checkpoints automatically for transactional deployment.
Action	See the webMethods Deployer documentation for more information.

25	Repository-based deployment does not support checkpoint operation for target servers of type {0}.
Class	E
Explanation	Repository-based deployment does not support checkpoint operation for target servers of the given type.
Action	Remove the assets of the unsupported runtimes from the deployment and deletion sets and update the deployment map accordingly.

3.42	The simulate, checkpoint, deploy, or rollback operation encountered an error while generating the report. Contact Software AG Global Support.
Class	E
Explanation	The simulate, checkpoint, deploy, or rollback operation encountered an error while generating the report.
Action	Contact Software AG Support.

5.37	Deployer cannot retrieve the project specified on the command. Make sure the user is authorized to view this information.
Class
Explanation	Deployer cannot retrieve the project specified on the command.
Action	Make sure the user is authorized to view this information.

5.38	Deployer cannot retrieve the build information specified on the command. Make sure the user is authorized to view this information.
Class
Explanation	Deployer cannot retrieve the build information specified on the command.
Action	Make sure the user is authorized to view this build information.

5.39	Deployer cannot retrieve the map specified on the command. Make sure the user is authorized to view this information.
Class
Explanation	Deployer cannot retrieve the map the user specified on the command.
Action	Make sure the user is authorized to view this information.

5.40	Deployer cannot retrieve the deployment candidates specified on the command. Make sure the user is authorized to view this information.
Class
Explanation	Deployer cannot retrieve the deployment candidates specified on the command.
Action	Make sure the user is authorized to view this information.

5.41	Deployer cannot retrieve the map for the user and project specified on the command. Make sure the user is authorized to view this information.
Class
Explanation	Deployer cannot retrieve the map for the user and project specified on the command.
Action	Make sure the user is authorized to view this information.

5.42	Deployer cannot retrieve the build information specified on the command. Make sure the user is authorized to view this information
Class
Explanation	Deployer cannot retrieve the build information specified on the command.
Action	Make sure the user is authorized to view this information.

5.43	There are no .map files in the IntegrationServer/packages/WmDeployer/replicate/inbound folder. Make sure the file you want to import exists in the specified folder.
Class
Explanation	There are no .map files in the IntegrationServer/packages/WmDeployer/replicate/inbound folder.
Action	Make sure the file you want to import exists in the specified folder.

5.63	The Integration Server to which you are trying to connect is configured to accept only secure connections on the UNIX platform. Use the correct digital certificates to establish the connection.
Class
Explanation	The Integration Server to which you are trying to connect is configured to accept only secure connections on the UNIX platform.
Action	Use the correct digital certificates to establish the connection.

5.64	Deployer encountered an error while invoking the service. Make sure the Integration Server to which you are trying to connect is up and running and you have properly installed all required components.
Class	E
Explanation	This error is encountered when trying to invoke the service from CLI.
Action	Make sure the Integration Server to which you are trying to connect is up and running and you have properly installed all required components.

1	Parameter {0} cannot be null or empty
Class	E
Explanation	The specified parameter is either null or empty.
Action	Provide a valid value for the parameter.

2	Parameter {0} cannot be null.
Class	E
Explanation	The specified parameter is null.
Action	Provide a valid value for the parameter.

3	Parameter {0} cannot be a negative integer
Class	E
Explanation	The specified value is a negative integer.
Action	Provide a positive integer value for the parameter.

4	File {0} does not exist.
Class	E
Explanation	The specified file does not exist in the specified location.
Action	Provide a valid file.

5	SSL-enabled connections require that either the TrustClientCertificatesByDefault parameter be set to true or that both TrustStoreFileName and TrustStorePassword are specified.
Class	E
Explanation	Either the TrustClientCertificatesByDefault parameter is set to false or either the TrustStoreFileName, TrustStorePassword, or both are not specified.
Action	Set the TrustClientCertificatesByDefault parameter to true or provide valid values for both the TrustStoreFileName and TrustStorePassword parameters.

2	Failed to ping the target {0} of type {1} with following exception : {2}. Either the target is unavailable or the credentials provided are invalid.
Class	E
Explanation	Either the target is unavailable or the credentials provided are invalid.
Action	Verify that the server is up and running, and that the specified parameters are valid.

3	An unexpected error occurred while pinging the target {0}. Error details : {1}
Class	E
Explanation	An unexpected error occurred while pinging the target.
Action	Check the server logs for more details.

11	Deliver operation on the target server {0} of type {1} failed with following exception : {2}. Please check the target server's logs for details.
Class	E
Explanation	The Deliver operation failed due to the reason specified in the Deliver report.
Action	Check the Deliver report for details. There might also be additional information in the Integration Server log.

12	An unexpected error occurred while performing variable substitutions for the asset with ACDL file name {0}. Error details : {1}
Class	E
Explanation	An unexpected error occured while substituting values.
Action	Check server logs for more details.

21	An unexpected error occurred while deleting the delivered assets for the deployment with ID {0} from target {1}. Error details : {2}
Class	E
Explanation	An unexpected error occurred while deleting the delivered assets.
Action	Check the server logs for more details.

30	An unexpected error occurred while activating the deployment with ID {0} for target {1}. Error details : {2}
Class	E
Explanation	An unexpected error occurred while activating the delivered assets.
Action	Check the server logs for more details.

50	Runtime type of the artifact {0} is different from the target runtime type {1}
Class	E
Explanation	The runtime type of the specified artifact is different than the target runtime type.
Action	Ensure that the runtime type of the asset to be deployed is same as the target server type.

1233	The Package: "{0}" will not be activated. The dependent package "{1}" version "{2}" does not match the package version "{3}" present on the target server.
Class
Explanation	The dependent package version does not match the package version present on the target server.
Action	Ensure that the target server package version is the same as the dependent package version on the source server.