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. |
Pro Cloud Server Troubleshooting Connecting Enterprise Architect to a Cloud Model |
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" |
Configure WebEA models - via Text Editor |
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:
|
|
Connection refused |
There was no response from the server, check that Pro Cloud Server is running! Possible reasons:
|
|
OSLC not supported |
The server port is not configured to support OSLC. Possible reasons:
Using the Pro Cloud Server 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:
|
|
Incorrect login details |
The specified login details were not valid for the current model! Possible reasons:
|
User Security |
Connection timed out |
Request Error: Connection timed out after 5001 milliseconds. Possible reasons:
|
|
Failed to Connect |
Request Error: Failed to connect to xxx.xxx.xxx.xxx port yy: Connection refused Possible reasons:
Note that, if the Pro Cloud Server is being re-directed via IIS, you must ensure this matches the IIS port used for the Pro Cloud Server. |
|
The configured database is not defined |
The configured database is not defined in the Pro Cloud Server. Possible reasons:
|
Add Database Manager |
Secure connection is required |
A secure connection is required for the selected model. This message indicates that the "Require a secure and authenticated connection" option is enabled for this Model Connection/Database Manager. To access this model via WebEA you must use the HTTPS protocol. You must also use a Port which has "Require SSL" enabled, and has the "Authentication" option set to either Model or Global. |
Configure Database Manager Port Configuration |
Problem reading the model root |
Problem reading the model root. Possible reasons:
|
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:
|
|
An unexpected response was received |
An unexpected response was received, check the Pro Cloud Cerver 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 Pro Cloud Server does not return the expected XML message. Check that the defined Sparx Systems Pro Cloud Server details, like server name and port are correct 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:
Using the Sparx Systems Pro Cloud Server 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:
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:
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:
|
|
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:
|
|
No credentials provided |
400 - User Security is enabled, however no credentials were provided. Possible Reasons:
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>" |
|
Incorrect Access Code |
The entered access code is incorrect! Possible reasons:
Check the webea_config.ini file for the correct access code / "auth_code". |
How to configure WebEA models |
Model is Shutdown |
The selected model is shutdown. Possible reasons:
Using the Pro Cloud Server Configuration Client, check that the Database Manager is set to "Enabled". |
Pro Cloud Server Configuration Client - Application |
Version Mismatch |
Warning - WebEA / OSLC Version mismatch Each release of the Pro Cloud Server 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:
When updating the Pro Cloud Server 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 Pro Cloud Server installation to the relevant location on your web server. |
Pro 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:
|
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:
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:
|
|
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:
|
Learn more
- Cloud Server Troubleshooting