Author Topic: Full Structure for Duplication Issue  (Read 2787 times)

GeistBW

  • EA User
  • **
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Full Structure for Duplication Issue
« on: January 08, 2021, 05:12:45 am »
So I am used to using Copy to Clipboard -> Full Structure for Duplication . I used this a few days ago and it worked fine. I could even paste just fine. But now when I use this function, for a second it shows the progress bar like it is starting the copy, then this error comes up:
    Microsoft OLE DB Provider for ODBC Drivers [-2147217913]
    [Microsoft][ODBC SQL Server Driver][SQL Server] Conversion failed
    when converting the nvarchar value 'Approved' to data type int.

I haven't done anything with any "Approved" context.  I don't even know where "Approved" is used outside of the "Status" field in the Properties window.  Although everything I've done in Sparx, that field is left as the default value: Proposed.

Any idea on what happened?  Or how I can get back to how to make this copy function work again?

EA Sparx 15.0 and ProCloud Server 3
Thanx in advance.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13387
  • Karma: +566/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Full Structure for Duplication Issue
« Reply #1 on: January 08, 2021, 05:57:19 am »
Try Project Integrity check.

If that doesn't work, contact Sparx support.

Geert

GeistBW

  • EA User
  • **
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: Full Structure for Duplication Issue
« Reply #2 on: January 08, 2021, 06:16:23 am »
The Project Integrity check showed no problems.  If any other suggestions come to mind please let me know. I will also send email to Sparx Support.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8083
  • Karma: +118/-20
    • View Profile
Re: Full Structure for Duplication Issue
« Reply #3 on: January 11, 2021, 08:38:28 am »
First point, which may not help with this error.

Your error message indicates you're using 'ODBC SQL Server Driver'.

That driver is known to have problems and has never been a supported method for connecting to SQL server. You should get whoever is managing your PCS to update it.

See https://www.sparxsystems.com/enterprise_architect_user_guide/15.2/model_repository/connecttosqlserver.html

In particular:
Quote
Select 'Microsoft OLE DB Provider for SQL Server' or 'Microsoft OLE DB Driver for SQL Server' from the list.

Note:
  • 'Microsoft OLE DB Provider for SQL Server' is usually part of the Windows Operating System, otherwise it can be installed as part of MDAC 2.8
  • 'Microsoft OLE DB Driver for SQL Server' is a newly released driver that adds support for TLS v1.2 and other more recent features of Microsoft SQL Server (such as multi-subnet failover capabilities); this driver is available from the Microsoft website

What I also see in the error message is that some query in the XMI export is converting a text field to an integer value (likely a pdata field.) I would recommend trying a new version since my memory says that all of those were changed to work the other way around. Because I suspect that's not an answer that you will like, you may also be able to find the rogue value by checking the PDATA fields for both t_object and t_connector.