Prev Next

Troubleshooting WebEA

If WebEA users experience a problem, an error message will be displayed on the screen. This topic provides a list of common WebEA error messages that could occur. Each entry describes the situation that has occurred and provides guidance on how to correct the error.

WebEA Configuration Test

On initial set up, these steps can be performed to help identify configuration issues:

Step

Action

See also

1

On the Web Server machine, open a web browser and test access to the WebEA login page.

E.g. http://localhost/webea/login.php

Failing this, check that the Web Server has been set up as described in the WebEA Installation and Configuration topic.

WebEA Installation and Configuration

2

On a client machine test access to the WebEA login page.

E.g. http://<server name>/webea/login.php

Failing this suggests there is a network/communication issue between the client and the web server.

3

Before attempting to access a model via WebEA, confirm you can successfully open the model using Enterprise Architect's 'Connect to Cloud' option.

Failing this, refer to the Cloud Server Troubleshooting Help topic.

Cloud Server Troubleshooting Connecting Enterprise Architect to a Cloud Service

4

In the webea_config.ini file, add a model connection with the minimum required options, as outlined here. Ensure these match the settings used when connecting via Enterprise Architect. Note, the 'sscs_db_alias' should match the value entered in the 'Model Name' field.

sscs_protocol = "<Protocol>"

sscs_server = "<Server Name or IP address>"

sscs_port = "<Port>"

sscs_db_alias = "<Model Name>"

auth_code = "" ;leave this empty

If the Project has Enterprise Architect User Security enabled then also include:

login_prompt = "true"

If the Protocol being used is HTTPS then also include:

sscs_use_ssl = "true"

If you are using HTTPS with a Self-signed certificate then also include:

sscs_enforce_certs = "false"

How to configure WebEA models

5

Try accessing the model in WebEA. Failing this, the error returned by the WebEA login screen might help identify the cause of the issue.

WebEA Error Messages

Issue

Comments

See also

Server could not be found

Server could not be found on the network!

This error usually occurs when WebEA does not receive any kind of response from the specified server name (or IP number).

Possible reasons:

  • The server is turned off
  • The server is behind a firewall and WebEA is unable to make a connection to it

Connection refused

There was no response from the server, check that Pro Cloud Service is running!

Possible reasons:

  • Pro Cloud Service is not installed
  • Pro Cloud Service is not running
  • Pro Cloud Service is not listening on the expected port

OSLC not supported

Your server is not configured to support OSLC.

Possible reasons:

  • WebEA communicates with Sparx Systems Cloud Service via OSLC, but the defined Sparx Systems Cloud Service has been configured to not allow OSLC requests for this Port.

Using the Cloud Configuration Client, check the configuration for the Port which you are using to access this model. Ensure the "OSLC Supported" option is enabled.

Port Configuration

Protocol Mismatch

Protocol and Port mismatch. Check that the correct protocol and port have been configured.

Possible reasons:

  • There is a mismatch between the connection settings; for example, 'sscs_use_ssl' has been set to true but a protocol of HTTP was specified

Incorrect login details

The specified login details were not valid for the current model!

Possible reasons:

  • The supplied user ID and password combination did not match any user credentials defined in the model
User Security

Connection timed out

Request Error: Connection timed out after 5001 milliseconds.

Possible reasons:

  • Invalid Cloud Server settings (sscs_*), WebEA cannot connect to the defined server/port
  • Apache/PHP web server requires a proxy server to reach the Cloud Service machine and the proxy settings defined in the .config file are incorrect or invalid

Failed to Connect

Request Error: Failed to connect to xxx.xxx.xxx.xxx port yy: Connection refused

Possible reasons:

  • The 'sscs_port' option in the webea_config.ini file does not match the port setting in your Pro Cloud Service configuration file (SSCloudServices.config); make them the same

Note that, if the Cloud Service is being re-directed via IIS, you must ensure this matches the IIS port used for the Pro Cloud Service.

The configured database is not defined

The configured database is not defined in the Cloud Service.

Possible reasons:

  • The 'sscs_db_alias' option in the webea_config.ini file does not correspond to the 'Database Alias' defined in Add Database Manager; correct the values so that they do correspond
Add Database Manager

Problem reading the model root

Problem reading the model root.

Possible reasons:

  • The WebEA options for the current model do not match a Pro Cloud Server configuration
  • You are attempting to access a DBMS repository which has not had a Project transferred into it. See Step 4 on the Server Based Repositories help page.
Server Based Repositories

No response when selecting an Object

After WebEA loads the initial page (the model root or default diagram), there is no response to selecting objects.

Possible reasons:

  • Your browser does not have javascript enabled; re-enable it
  • The cURL PHP module/extension is not installed and enabled on the server; install/enable cURL on your web server
  • The PHP version is wrong; it must be greater than PHP 5.0 with all extensions supported

An unexpected response was received

An unexpected response was received, check the cloud service configuration!

This error normally occurs while attempting to login or connect to a model from the initial page. The error message will display whenever the response from the configured Cloud Service does not return the expected XML message.

Check that the defined Sparx Systems Cloud Service server name and port are the details of an actual Cloud Service and not those of a web server.

The selected database does not have Pro Features enabled

The selected database does not have Pro Features enabled.

This error normally occurs if the selected model does not have 'Pro Features' enabled.

Possible reasons:

  • In the Cloud Service Configuration Client, the Database Manager for this model does not have the 'Enable Pro Features (OSLC, WebEA and Integration)' option enabled
  • The Pro Cloud Server's license has expired and the server is now operating as the free, core edition of the Cloud Service
  • The License key entered is invalid and the Pro Cloud Server is operating as the core edition

Using the Cloud Service Configuration Client, check the Database Manager configuration. Ensure that the 'Enable Pro Features (OSLC, WebEA and Integration)' option is enabled.

Configure Database Manager

Diagram image not found

Diagram image not found.

This error indicates that the diagram exists in the model, but the image of the diagram has not been generated.

Possible reasons:

  • The model does not have the 'Auto create Diagram Image and Image Map' option enabled in model-specific options
  • The diagram was created in Enterprise Architect, but has not yet been saved
  • Or, the user is on an old version (prior to build 1350) of Enterprise Architect and the Worker application is not running for this model (it has not been configured, it is not currently running, or has not run since the diagram was saved)

Open the model in  Enterprise Architect (build 1350 or later), enabled the 'Data Cache' options, and click on the 'Create' button as described in the 'Model Configuration' section of the 'WebEA Installation and Configuration' topic.

Alternatively, ensure that the Worker application is running for this model. See the 'How to configure automatic viewable components' topic for details.

How to configure automatic viewable components WebEA Installation and Configuration

Resource not found

404 - Resource with identifier '{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}' could not be found

The item (element, Package or diagram) with this GUID could not be found in the current model.

Possible Reasons:

  • The item has been deleted from the model.

To confirm that the item has been deleted, check the parent Package (or parent element) in WebEA.

If the error occurred when selecting an item on a diagram, the diagram image might have to be regenerated.

SSL Error

Error: SSL certificate problem: unable to get local issuer certificate

This error suggests you are attempting an HTTPS connection without having SSL enabled.

Possible Reasons:

  • The webea_config.ini file does not include sscs_use_ssl = "true" for this Model. Try adding this, then attempt to access the Model again.

Self signed certificate error

Request Error: SSL certificate problem: self signed certificate

This error suggests you are attempting an HTTPS connection with SSL using a self-signed certificate, however WebEA has not been configured to allow self-signed certificates.

Possible Reasons:

  • The webea_config.ini file does not include sscs_enforce_certs = "false" for this Model. Try adding this, then attempt to access the Model again.

No credentials provided

400 - User Security is enabled, however no credentials were provided.

Possible Reasons:

  • The Project has Enterprise Architect user security enabled; however, WebEA is not configured to either show a login prompt or automatically login with specific credentials

Check that the webea_config.ini contains:

     login_prompt = "true"

Or, all of these:

     login_prompt = "false"

     sscs_model_user = "<user id>"

     sscs_model_pwd = "<password>"

Version Mismatch

Warning - WebEA / OSLC Version mismatch

Each release of the Pro Cloud Service includes an OSLC component and the WebEA component (php files). If you are using the OSLC component from one release and the WebEA component from another, then WebEA might not function as intended.

Possible Reasons:

  • A new version of the Pro Cloud Service was installed, however the new version of WebEA was not copied to the Web Server

When updating the Pro Cloud Service to a newer version, ensure that WebEA is also updated. That is, after performing the installation of the Pro Cloud Server, copy the new WebEA files from the Cloud Server installation to the relevant location on your web server.

Cloud Server Installation

Basic login fields not shown

The basic login fields will not be visible when attempting to log in to a model under these circumstances:

  • The webea_config.ini has sscs_model_user defined
  • The model has the user option 'Restrict access to Windows & OpenID users only' enabled
Single Sign-On (SSO) Options

Problems loading pages

Issue

Comments

See also

No response when clicking on diagram elements

When clicking on an element on a diagram nothing happens.

Possible reason:

  • The element properties are being loaded in the Properties View, however the Properties View is automatically hidden due to a narrow screen/browser width (less than 800px).

From the hamburger menu at the top right of WebEA, select 'Properties' to turn off the Properties View.

Pages don't load correctly

After the server has been updated to a new version of WebEA, clients experience problems with pages loading incorrectly.

Possible reason:

  • The user's browser is using a cached version of WebEA's client side files, which is causing unpredictable results
    The solution is to clear the browser cache, to force the browser to download the latest version of the application files from the server; the process for clearing the cache is different for each browser/device - consult the user manual for your browser

Login page in Internet Explorer

The 'Login' page is not drawn correctly and appears different to other browsers; that is, the selection boxes next to each model name are not square.

All login attempts to models with authentication fail saying 'No model selected!'

Possible reasons:

  • IE is running in 'Compatibility View' mode, which does not support HTML5 and CSS3; turn off 'Compatibility View' at least for the server hosting WebEA

Learn more

  • Cloud Server Troubleshooting