Known Issue: Transfer File to DBMS
Error while transferring file from EA to DBMS
Description
The customer trying to load some data into their Database and They don’t know how to set up the server connection.
First they migrated the eapx file (from Sparx EA 15.2) to a qea file which worked well. Now they want to transfer it via SparxEA 16.1 into thier new empty database. But they get error while using file to DBMS option in project transfer
Possible Reasons
- Need to enter proper server name
- Need to fill the proper details in native connection area.
Need to enter proper details in native connection pop-up
First response – Troubleshooting Steps
(This is the initial Mail to the customer)
Thank you for contacting Prolaborate Support.
We understand that you are unable to configure the native connection for the file-to-DBMS transfer.
We have reviewed your screenshots and have noticed that the server name entered appears to be incorrect.
To assist you further, we recommend taking the correct server name for your MSQL using the following steps:
Step1 : Open MSSQl and you will see a login pop-up.
Step2 :In the login pop-up, you will be able to find the server name.
Please use the correct server name of your MSQL to configure the native connection for the file to DBMS transfer.
If you require any further assistance or have any questions, please do not hesitate to reach out to us.
Step 1: You Need to fill the details in Open server Connection dialog box.
Step 2: After that click the test if enter proper details we get connection successful message
Reference Documentation
Reference Tickets
Related Articles
Known Issue - Confluence
Q1. Failed connection in Confluence and Jira Integration Description Customer reported that they are unable to establish connection in both Confluence and Jira with Prolaborate. Customer shared the below screenshots of the configurations, Resolution ...
Known Issue - JIRA
Q1. "Not able to connect with Jira!" Error in Prolaborate Description Jira Items are not able to connect with Prolaborate elements and getting the below error. Possible Reason -1 The project may have been deleted on the Jira side after you configured ...
Known issue: Access denied error when clicking SSO in Prolaborate(Autoscaling environment)
"Access denied" error when clicking SSO in Prolaborate. Description: The customer reported being unable to access Prolaborate. When clicking the SSO, they encountered an "access denied" error in Prolaborate. Possible Reason: As confirmed by the Dev ...
Known Issue: Installation
Q1: HTTP error 401 and 401.2 - Unauthorized Access Description Customer reported that they installed Prolaborate 3.x freshly in their environment and they had encountered the following error. Remediation Enabling the options in IIS to resolve this ...
Know Issue - Connectivity Issues
Q1:Issue with Model cloud connection in EA. Description: The customer faced an error while connecting the model via connection. Model connection failure (Pro Cloud Server: The HTTP connection reported the following error: 12002) 1. The customer is ...