Please enable JS

Frequently Asked Questions

During the upgrade, the latest database schema wouldn’t have got executed. Visit this link and choose the appropriate version to download the latest database schemas.

There would have been some discrepancy with the upgrade. Please share the logs with Prolaborate team.

Open Prolaborate app server and start or restart the services.

Select the latest version in this page to download the database schemas.

This error shows up when the required Windows features are not properly installed. Please reinstall the features as per this link and the issue should get resolved.

This error shows up when the required Windows features are not installed. Please install the features as per this link and the issue should get resolved.

The following could the reasons:

  1. Prolaborate app server is not reachable
  2. IIS is not running in the app server
  3. Prolaborate site is stopped in IIS
  4. Prolaborate site is blocked by your security policies
  5. Domain configuration of your Prolaborate site is not done properly

Please check the following:

  1. The following settings are done in IIS Manager:
    1. Click on the Prolaborate Application pool. Under Actions on the right-hand side panel, click on Advanced settings.
      • Under General, check whether Enable 32-Bit Applications is set as True.
      • Under Process Model, check whether Identity is set as ApplicationPoolIdentity
    2. Click on the Prolaborate site. Under Actions on the right-hand side panel, click on Basic settings and check the Physical path. It should be the path of WebApplication folder. For example, C:\Program Files (x86)\Prolaborate\WebApplication
  2. All permissions are set for IUSR and IIS_IUSRS users for Prolaborate folder (typically located at C:\Program Files (x86)).
  3. All the tables are created in Prolaborate database.

Please follow the below steps and fix the BaseURL:

  1. Open the server where Prolaborate is installed.
  2. Go to C:\Program Files (x86)\Prolaborate\ProlaborateServiceManagement.
  3. Open Prolaborate Service Management.exe
  4. Click on Manage Configuration.
  5. Update BaseURL. It should be the URL you use to visit Prolaborate.
  6. Click on Save.

Check if “ProlaborateConfigFilePath” and “ProlaborateLicenseFilePath” are set correctly in web.config file typically located at C:\Program Files (x86)\Prolaborate\WebApplication\.

  1. Check if ASP .NET 4.5 or above version is installed and registered on IIS
  2. Check if required user permissions are available on Prolaborate installation folder. Users (IUSR, IIS_IUSRS) should be granted full access for that folder
  3. Check if the database schema is up to date

The error will show up when

  1. Authentication is not enabled in Prolaborate for an Enterprise Architect model which has Security enabled in it
  2. The Authentication details are incorrect.

If you are getting this error even when Security is not enabled for this model, Security might be enabled at the Active Directory level. You need to create a user from Enterprise Architect and use those credentials for Authentication in Prolaborate.

If you are getting this error even after giving the right credentials, check if you are able to login to the model using Enterprise Architect.

If no, the credentials are invalid.

If yes, you must be using the default credentials when you enabled Security in EA, which is admin and password. You need to use the Change Password option once to resolve the issue.

Change the password in EA and use the same in Prolaborate. You can even change the password to password.

Once you go back to Prolaborate and refresh the Repositories page, the status will change to Active.

This error appears when Prolaborate is not able to connect to its database. The reason could be any one of

  1. Database password has expired. It is recommended to change it again with the same password; else you need to update the same in Prolaborate configuration.
  2. Some issue with connectivity or database server. Try connecting to the Database manually and see if it is possible. If this is possible, the issue should be temporary and Prolaborate will work fine
  3. Database details are not valid

Open Prolaborate Service Management.exe typically located at C:\Program Files (x86)\Prolaborate\ProlaborateServiceManagement

Click on Manage Configuration. Please check the database details in the Database tab

This error is to do with 'client impersonation'.

To fix it, start IIS Manager. Select the server in the left pane and double click 'Authentication' under the 'IIS' group in the central pane. Select 'ASP.NET Impersonation' and select 'Disable' at the top of the right pane.

This status shows up when Prolaborate could not establish a connection with the configured Enterprise Architect (EA) Model.

It could be because of the following reasons:

  1. Either database configuration in Pro Cloud Server (PCS) is incorrect or the details of EA database entered in Prolaborate are incorrect. Check whether you are able to connect to the EA model using Cloud Connection of EA with the same details entered in Prolaborate
  2. The port used by PCS (For example, 804) is not open. From a browser in a local machine, enter the server name or DNS or IP address of the server where PCS is installed appended by the port number (For example, SSN007:804) and check whether you are getting a Congratulatory message.
  3. PCS Pro Features are not enabled
  4. PCS OSLC Support is not enabled. Open PCS configuration file (Sample path: C:\Program Files (x86)\Sparx Systems\Cloud Services\Service\SSProCloud.config) and check if OSLC_Support is set to 1. If not, change the value to 1.
  5. To ensure OSLC support is working fine, check whether the following calls are working from the server where Pro Cloud Server is installed:
    1. localhost:[PCS port]/[PCS Database Manager alias]/oslc/am/pbstructure/
    2. localhost:[PCS port]/[PCS Database Manager alias]/oslc/am/sp/

    PCS port is 804 by default. The alias can be found in the PCS console.