Project transfer empty

[royvanmarrewijk]

Hi,

I use the Project Transfer function to create an export of the model once in a while and it usally it works fine. But for some reason it doesn't work anymore since the Project Transfer (DBMS -> EAP) is done within a second and the .EAP is empty.

Does anyone of you have an idea what this could be?

kind regards,
Roy

[qwerty]

What do you mean by "done within a second"?

q.

[Geert Bellekens]

No sorry Roy, never heard of a similar issue.

Geert

[Glassboy]

I've had that happen once, but after I restarted the client and recreated the target it all worked again.

[Robert Lelieveld]

Same issue here, when trying to transfer data from the DBMS to an .eap file the process completes immediately. Nothing was actually transferred.

Project Transfer
- DBMS to File

Source Project
- Microsoft OLE DB Provider for SQL Server, 'Test Connection' is OK
- security on the database: public, db_datareader, db_ddladmin

Target Project
- test.eap, just created, saved and closed

Contents of the log file:

Code: [Select]

+--------------------------------------------
| Data Transfer model log file
| Generated by Enterprise Architect
| Source DBMS: SQLSVR
| Target DBMS: JET
| Created On : Thursday, 11 August, 2016
+--------------------------------------------
2016-08-11 13:12:10  Removing data in: usystables

EA version 12.1.1224 is used.
Database Version: 7.0
SQL Server 11.0.5623 is used.

There are no issues with working with the DBMS version, via a server connection or via a cloud connection.
Restarting EA does not fix it.

What could be wrong?

[Robert Lelieveld]

In the options I found a flag saying to Use JET 4.0 - requires restart.
With or without the flag doesn't change the outcome of the data transfer action.

Who came across this same behavior and was able to solve it?

@Roy: were you able to solve it?


Thanks,
Robert

[voegelas]

Same problem here. It turned out that the table usystables, which lists all EA tables, was empty in the source project. After I populated this table with data from another EA project I could transfer the source project to a file.

[silvestri]

Same here while using  Postgres 9.6.1 and ODBC driver 9.05.03.00 and EA 13.

Any support and hint would be very appreciated.

[Robert Lelieveld]

Same problem here. It turned out that the table usystables, which lists all EA tables, was empty in the source project. After I populated this table with data from another EA project I could transfer the source project to a file.

Yes, this indeed fixed it!

After that, I had an issue with the t_taggedvalue table that apparently contained an orphaned value. You can recognize this because the ElementID is NULL.
Just remove it.

Then, the project transfer worked again without issues.

Looking at the various types in the project, it seems a lot more is missing somehow. I'm now analyzing the database against the base.sql file available in the download section to search for differences and applying them to the database.
No idea though, why many types etc are not in the database.

Kind regards,
Robert

[qwerty]

I guess a standard project integrity check would have cleaned those orphans. You should setup a rule to run this check at least once a week.

q.