Q1: Will the Admin Account and Support Account Consume a License?
Answer
The admin@prolaborate.com account is an inbuilt user automatically included during Prolaborate installation.Regarding the support@prolaborate.com account, please note that the Prolaborate Support ID is reserved for internal maintenance purposes and does not count towards the license allocation.
Tags: Admin account, Support Account consume License
Q2: Is it Possible to Delete the Admin Account (admin@Prolaborate.com)?
Answer
The super admin account (admin@prolaborate.com) is an inbuilt user automatically included during Prolaborate installation. As a result, it is not possible to delete the super admin account from within the application. However, it is feasible to customize the email associated with this account (e.g., change admin@prolaborate.com to @ot.govt.org). While modification is possible for customization or compliance with specific requirements, the deletion of this account is not supported.
Tags: Delete Admin Account, Delete Support account, admin@prolaborate.com
Answer
Prolaborate has nothing to do with XAMPP. So, any changes are unrelated to the Prolaborate application and will not impact it.
Reference Ticket
Ticket ID: #8098
Subject: Preparation for production build on windows 2019
Department: Prolaborate Support
Q4: Getting HTTP Error when opening a diagram via Prolaborate's EA Diagram Editor.
Answer
The HTTP Error occurs due to an incorrect connection string present in the Prolaborate Repository Setting. This error might occur if the connection string in the repository settings is misconfigured, pointing to an HTTP address that leads to connectivity issues.

To resolve this issue, ensure that the connection string in the Prolaborate Repository Setting accurately reflects the necessary parameters, including the correct protocol (such as HTTPS), address, and port for accessing Enterprise Architect. Confirming the correct configuration of the connection string typically resolves this HTTP Error.
Reference Ticket
Ticket ID: #9002
Subject: Issue with Diagram Editor in PCS Environment
Department: Sparx Platform Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000033607103
Q5: Is it possible to use the same DNS and port combination for mapping different applications like Pro Cloud Server and Prolaborate?
Answer
Yes, it is possible to use the same DNS and port combination for different applications like Pro Cloud Server and Prolaborate. However, it is important to ensure that each application is mapped to a unique URL or subdomain to avoid conflicts and ensure proper routing of requests. This can be achieved by configuring the applications with different virtual directories or subdomains.
If you are using an AWS EC2 instance, please make sure the application gateway is configured accordingly to handle the requests for different applications.
Q6: What DNS naming convention is recommended for Pro Cloud Server and Prolaborate services?
Answer
For optimal clarity and consistency, we recommend adopting a clear and descriptive naming convention. As an example, the suggested convention is as follows:*
- ProCloud Server:
- DNS Name: `procloud.ea-organizationname.com`
- Prolaborate:
- DNS Name: `prolab-app.organization-name.com`
For on-premise installations, it is advisable to tailor the DNS names according to the organization's name. For instance, if the organization's name is ABC Corporation, the DNS name for ProCloud Server could be "procloud.abc-corp.com", and for Prolaborate, it could be "prolab-app.abc-corp.com". This approach ensures that the naming convention aligns with the specific requirements of each on-premise customer, providing a personalized and easily identifiable solution within their infrastructure.
Ref Ticket
Q7: Why does Prolaborate show a license missing after migrating to another server?
Answer
When migrating to a new server, the machine ID associated with Prolaborate's license changes. As a result, the existing license becomes invalid. To resolve this issue, obtain a new license that corresponds to the machine ID of the new server. Once the new license is obtained, update the Prolaborate configuration with the new license details to activate the software on the migrated server.
Ticket ID: #8666
Subject: RE: Entergy Prolaborate Installation
Department: Prolaborate Support
Q8: Is an SMTP server available with Prolaborate offering, and can you provide configuration details?
Answer
If you have an existing SMTP server, we can help you configure it within your Prolaborate environment. However, if you don't have an SMTP server and need us to set up a new one, please note that this service is available at an additional cost.
Reference
Q9: What if I have Prolaborate installed on a drive other than the default (C:)? Will the Data Migrator still work?
Answer
Yes, absolutely! The enhanced Data Migrator is designed to seamlessly function regardless of whether Prolaborate is installed on the C: or D: drive, or any other drive for that matter. You won't need to manually update any configuration files anymore. The Data Migrator will automatically detect and incorporate the correct path for Prolaborate, ensuring smooth and hassle-free migration.
Reference:
Ticket ID: #9039
Subject: Prolaborate V5.2 introduction
Department: Prolaborate Support
Q10: Can Prolaborate and Pro Cloud Server be installed on the same server?
Answer
Yes, it is possible to install both Prolaborate and Pro Cloud Server on the same server. However, they may need to operate on different ports to avoid conflicts.
Q11: Is it possible to run both Prolaborate and Pro Cloud on the same port ?
Answer
Yes, if you wish to run both Prolaborate and Pro Cloud Server with the same port, you can set up an External Load Balancer to handle this scenario. Both applications need to operate on the same port while using different domain names.
Q12: Users are unable to log in to Prolaborate using their Active Directory (AD) credentials due to smart card authentication. What can be done?
Answer
As of now, Prolaborate doesn't support smart card authentication. Users must use passwords to log in. If users are unable to access their passwords due to smart card authentication, they should contact the AD administrator or IT support team for the password.
Reference
Ticket ID: #8558
Subject: FW: [Extern] RE: [Extern] RE: Sparx Systems Prolaborate - Tullverket
Department: Prolaborate Support
Q13: The Prolaborate login through authentication failed error when the server machine and local machine have different time zones. What can be done?
Answer
The error occured due to the application generates a token with an expiration time. Upon expiration, a new token is created. However, in your case, there is a discrepancy in the time settings. The time is set one hour ahead, which results in a mismatch between the time given to the token and the actual time.
This mismatch between the token's time and the actual time is what's causing the authentication issue you're experiencing.
To resolve this, we recommend enabling the "Set time automatically" option in your device's date and time settings. By enabling this setting, your device will synchronize its time with the correct time provided by an external time server. Once the time settings are accurately synchronized, the authentication process should function as expected.
ad user unable to login with password,
consume license,
migrat,
delete admin,
smtp,
pfx,
license missin,
ssl renewa,
pkccs7 to,
http error,
mdg based re,port toggle,
smart card authentication,
delete,
prolaborate and pcs on same serve,
support account,
same port,
custom query,
data migrator,
admin account,
other drive,
smtp available,
file path,
enable sorting,
ea diagram editor.