Author Topic: Major connection/SQL errors since moving to v16.1  (Read 9193 times)

ducatiross

  • EA User
  • **
  • Posts: 114
  • Karma: +1/-0
    • View Profile
Major connection/SQL errors since moving to v16.1
« on: March 01, 2023, 11:23:01 pm »
Hi everyone,

Recently I moved from version 15.2 to 16.1, and since then I (as well as a few colleagues also on v16) have been having frequent issues and errors such as :

Sparx Systems Database API [0x00001072] SQL API Open FAILED with error: 08S01 Connection failure
Context:
Select Style, ea_guid from t_object where  ea_guid IN ('{9EE7083B-6934-4c22-8958-52D2D715DFAC}','{A9343305-14ED-4c84-B6BF-ED3E6768F71D}','{0CE34EB3-33E9-4da2-90E1-1E41137834FD}','{28B3BAF8-BE89-410e-B374-D2AADA4A1BC8}','{25339896-DB43-47f6-AAC7-33FB9ED7065F}','{D28FB8AC-FE12-4a6d-907B-3882C95BCE0A}','{D440CF4F-A7DF-4f10-9361-B7948090F8F0}','{B468A837-1FF4-4cca-8040-932830740626}','{3BAEE52B-9E5E-403c-B1D0-3B4E233A3813}','{5621CF8A-BF01-4dd1-A6B7-A55ED432B95D}','{C8FFD492-1422-4503-9A63-1D5A2D806652}')

I feel like v16 is extremely sensitive to wifi/network connection fluctuations, whereas v15 was not.

Has anyone else had this and did you find a workaround ?

Sometimes it is so bad it makes EA unusable.

Closing EA and starting it again sometimes improves things, as does moving closer to the router or wifi booster box, but not always as other devices seem to have no problems with connecting to the internet.

Any advice would be gratefully received.

Matthew


ahavey

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Major connection/SQL errors since moving to v16.1
« Reply #1 on: March 09, 2023, 02:10:56 am »
We are experiencing the same. We recently upgraded from v15.1 to v16.1 and if the connection is lost a restart seems necessary. Whereas in 15.1 it recovered by itself.

I suspect the new data engine, but hopefully they can make the necessary changes to make it more robust!

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13240
  • Karma: +553/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Major connection/SQL errors since moving to v16.1
« Reply #2 on: March 09, 2023, 03:04:40 am »
Did you change the way you connected?

I heard the "native" connection is a lot less stable.

Geert

ducatiross

  • EA User
  • **
  • Posts: 114
  • Karma: +1/-0
    • View Profile
Re: Major connection/SQL errors since moving to v16.1
« Reply #3 on: March 09, 2023, 03:50:16 am »
Geert - no I don't think so. We are using a SQL Server database on an Azure platform to host the model DB, which is what we did for v15 - it's the same DB. I will check the connection method.

I tried to increase the timeout parameter in case that helped and it seemed to initially, but then it got worse again.

ahavey - at least it is not just me then !

ahavey

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Major connection/SQL errors since moving to v16.1
« Reply #4 on: March 10, 2023, 02:24:40 am »
No, not just you ducatiross.

So, what is the most stable way to connect to SQL Server?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13240
  • Karma: +553/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Major connection/SQL errors since moving to v16.1
« Reply #5 on: March 10, 2023, 03:48:22 am »
I think the classic OLEDB driver for SQL Server (as used by v15.2)

I did some testing with v16, but not in a production environment yet. (still waiting for some bug fixes)

Geert

BobM

  • EA User
  • **
  • Posts: 143
  • Karma: +9/-0
    • View Profile
Re: Major connection/SQL errors since moving to v16.1
« Reply #6 on: March 10, 2023, 06:49:30 pm »
Native connection in theory is containing both the SQL OLE DB provider and SQL ODBC driver to support native connectivity to SQL Server.

However I think I read (or saw in a webinar) somewhere that for SQL server the native connection uses just OLEDB so shouldn't give any performance advantages and the gain for the native connection support in EA is in the other database sources.

workingmatt

  • EA User
  • **
  • Posts: 22
  • Karma: +0/-0
    • View Profile
Re: Major connection/SQL errors since moving to v16.1
« Reply #7 on: July 17, 2024, 02:25:23 am »
I was seeing the 0x00001072 error with SQL API but only when I open the traceability window.

I'm using 64-bit v16.1.1627 connected to an Azure SQL database. I noticed there was a specific fix in build 1628 relevant to database connections and so far it seems to have worked. Have these database problems gone away for everyone with 1628? I was a little surprised there's not a v16.2 especially now that v17 beta is out - well done Sparx for improved quality.
« Last Edit: July 17, 2024, 02:37:16 am by workingmatt »

rnovicky

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Major connection/SQL errors since moving to v16.1
« Reply #8 on: September 24, 2024, 08:44:33 pm »
Unfortunately, I have the same issue using the build 1702.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Major connection/SQL errors since moving to v16.1
« Reply #9 on: September 24, 2024, 09:08:48 pm »
You did not state which DB you're using. Eventually you should contact Sparx support.

q.