Prev Next

Troubleshooting

Integration Server messages

There are certain error messages that could display during the definition of the Integration Server settings; most are self explanatory. This table describes the most common error messages.

Error Message

Description

See also

Please enter a value for [field_names]. The Integration Server can only be saved (while enabled) when all mandantory fields have a value

Reason:  When the 'Enabled' flag is checked, all remaining Integration Server fields are mandatory.  This message occurs when one or more Integration Server fields are empty and the 'Enabled' flag has been checked.  [field_names] represents a placeholder for a comma separated list of field names that are empty.

The executable name of SBPI.EXE was expected

Reason:  The 'Executable Path' field has a value but it does not include the filename "...\SBPI.exe", which is the only valid filename that can be used.

The specified Integration Server path of [full_path] does not exist or is invalid

Reason:  The 'Executable Path' field has a value but the path portion of the specified value is not valid or does not exist on the Pro Cloud Server machine.

Install and Configure

The specified Port is a duplicate of [duplicate_plugin_name]

Reason:  The 'Port' field has been assigned a Port number, but it is the same as a Port being used by another Integration Data Provider identified by the name [duplicate_plugin_name].

The System Output Window

Integration Data Provider messages

There are certain error messages that could display during the definition of an Integration Data Provider; most are self explanatory. This table describes the most common error messages.

Error Message

Description

See also

Please enter a value for [field_names]. An Integration Provider cannot be saved without all mandatory fields being assigned a value.

Reason:  To minimize the chance of defining an invalid Data Provider, the application ensures that all mandatory fields are given a value.  [field_names] represents a placeholder for a comma separated list of field names that are empty.

Ports need to be unique across all Providers, the port value of [new_port] has already been used by [other_provider]

Reason:  A Port number has been defined for the current Data Provider, however the value is a duplicate of another provider's Port.

The System Output Window

The specified execution path for the provider does not exist or is invalid, [full_path]

Reason: The 'Execution Path' for the data provider has been assigned a value, but either the path or filename, or both, cannot be found on the local machine.

Install and Configure

The specified Port is a duplicate of the Integration Server

Reason:   A Port number has been defined for the current Data Provider, but the value is a duplicate of the Port used by the Integration Server.

Failed to rename config file [old_filename] to [new_filename]

Reason:  When the user changes the config filename of an existing Data Provider, the Cloud Server must rename the old filename to the new one. This message will be shown if the rename task is not successful, (which can occur if the file is in use by another process) and in this case manual intervention is the only way to resolve this issue.

Prefixes need to be unique across all Providers, the prefix value of [new_prefix] has already been used by [other_provider]

Reason:   A Prefix has been defined for the current Data Provider, but the value is a duplicate of the prefix used by another provider.

Config filenames need to be unique across all Providers, the config filename of [new_filename] has already been used by [other_provider]

Reason:   A Config filename has been defined for the current Data Provider, but the value is a duplicate of the config filename used by another provider.

General Troubleshooting

This table provides general advice to help identify and resolve common issues with the Integration component of the Pro Cloud Server.

Problem Description

Problem:  After making changes to the Integration definitions of the Server or Data Providers, the Enterprise Architect users do not notice any differences.

Solution:  After changing the Integration configuration, was the Pro Cloud Server restarted?  If not, restart the Pro Cloud Server.

Problem:  A newly configured Integration Data Provider is not listed in the navigation breadcrumb of Enterprise Architect (after the Pro Cloud Server has been restarted).

Solution: Confirm that the currently open model has a Binding entry for the Data Provider. For details, see the 'Bindings' field in the Data Providers table of the Integration Plug-ins Help topic.

Problem:  Selecting items within the Integration navigation breadcrumb of Enterprise Architect seem to have no effect.

Solution:  It is possible that errors (or warnings) are occurring that are logged to the System Output window, therefore make sure the System Output window is displayed while using the Integration window.

Problem: General errors seem to be occurring, however no useful information is shown in the System Output Window.

Solution:  Each Integration Data Provider has the capability to write detailed entries to a log file; to ensure that the most detailed information is written, change the log level for the Data Provider to SYSTEM (restart the Pro Cloud Server) and then retry the same action in Enterprise Architect. Then review the Data Provider's log file; that is, in C:\Program Files (x86)\Sparx Systems\Pro Cloud Server\SBPI\Logs, on the Pro Cloud Server.