catastrophic failure

[majikman]

I'm attempting to connect to my MySQL database but I keep getting the message

Provider[-2147418113]
Catastrophic Failure


Does anyone know how to get around this?
Or, could you provide me with details to how you were able to connect to your MySQL DB?

Additionally, just to clarify the situation, I did test the conection when I setup the ODBC driver and it worked fine. In fact, it can actually pull the database names from the DB server but I just can't get EA to connect to it. I'm running MySQL 5.0.18 installed on a Slackware 11.0 system with a Linux kernel version 2.6.18.2. If there is any other information I can provide, please let me know. I'd really hate for this thing to be the reason I don't decide to go with Enterprise Architect as my solution since I really like its other features. Thanks!

[majikman]

more info... i checked the boxes "Don't Optimize Column Width" and "Return Matching Rows" on the mysql connector/odbc stuff.

although i have no idea what all this means, I saw this on the mysql page so maybe someone can figure this out. this is the trace from an attempt to connect with the catastrophic failure message:


EA              944-9ccENTER SQLAllocConnect
HENV                027C1830
HDBC *              0225E47C

EA              944-9ccEXIT  SQLAllocConnect  with return code 0 (SQL_SUCCESS)
HENV                027C1830
HDBC *              0x0225E47C ( 0x027c1e50)

EA              944-9ccENTER SQLSetConnectAttrW
SQLHDBC             027C1E50
SQLINTEGER                 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER          0x0000000F
SQLINTEGER                  -6

EA              944-9ccEXIT  SQLSetConnectAttrW  with return code 0 (SQL_SUCCESS)
SQLHDBC             027C1E50
SQLINTEGER                 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER          0x0000000F (BADMEM)
SQLINTEGER                  -6

EA              944-9ccENTER SQLSetConnectAttrW
SQLHDBC             027C1E50
SQLINTEGER                 109 <SQL_ATTR_CURRENT_CATALOG>
SQLPOINTER          0x000EEA64 (NYI)
SQLINTEGER                  12

EA              944-9ccEXIT  SQLSetConnectAttrW  with return code 0 (SQL_SUCCESS)
SQLHDBC             027C1E50
SQLINTEGER                 109 <SQL_ATTR_CURRENT_CATALOG>
SQLPOINTER          0x000EEA64 (NYI)
SQLINTEGER                  12

EA              944-9ccENTER SQLDriverConnectW
HDBC                027C1E50
HWND                00000000
WCHAR *             0x74329A38 [      -3] "******\ 0"
SWORD                       -3
WCHAR *             0x74329A38
SWORD                        2
SWORD *             0x00000000
UWORD                        0 <SQL_DRIVER_NOPROMPT>


additionally, i tried connecting without selecting a database but Enterprise Architect closes with the error message that there was a network problem. however, by looking at the trace, the problme seems to be that it attempts to run "select count(*) from usys_system" without actually selecting a database. this error message should be fixed so that it reports something more descriptive. the network error message is misleading and is flat out wrong.

[thomaskilian]

sometimes it's a simple thing missing. can this thread help you: http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=general;action=display;num=1174423345;start=0#0

[chrisHauert]

Hi
I'm trying to connect to a mysql db (Server version 5.0.37, Client 5.1.11). The odbc-connection test runs without problems (myodbc version 3.51.15). Even from ms access I can connect to the ea-db I created with the script.
But when trying to connect to the db from ea corp. edition version 6.5.806 I get the same error message Provider [-2147418113]. The same error happens when trying to transfer an *.eap content to the same database (followed by the message "could not open the database").
So I guess the answer isn't that simple

[chrisHauert]

Hi, meanwhile I succeeded to connect to an EA-DB in a mySQL Server 5.0 with Version EA 7.0.81x.

Apparently I had to use a system-dsn in the ODCB connection, not a user-dsn. I also entered directly userid and password in the odcb-connection definition.

Having reconnected today I get some ugly messages when creating a new mindmapping topic ":Microsoft Cursor Engine [-2147217864] ..."

beside that, it works -> hope that might help you too

[«Midnight»]

Hi Chris,

At least you've got a connection, so that's progress.

Meanwhile, I don't like the failure with mind mapping. Please try this again with build 816 - just to make sure Sparx has not already addressed the issue.

If it still does not work, please submit a bug report directly to Sparx. Search my recent posts for a way to do this while keeping the rest of us in the loop.

Thanks much,
David

[bmioch]

Make sure you check these two options in your ODBC connection. It may clear up the problem you are talking about.

"Don't Optimize Column Width" and "Return Matching Rows"

[chrisHauert]

thanks nice MG and bmioch

with build 816 and the options set it now works correctly, great!

hope these kind of details will enter in the EA documentation as well

[bmioch]

Step 7 - http://www.sparxsystems.com.au/EAUserGuide/index.html?setupmysqlodbcdriver.htm (Thanks Roy)

[RoyC]

Actually, to avoid confusion, that's step 7 in:

http://www.sparxsystems.com.au/EAUserGuide/index.html?setupmysqlodbcdriver.htm

The point about the two checkboxes is quite important, so we flagged it in the topic Bill linked to, and then provided the explicit instruction in the above topic. Also, in the help installed with the product build (as distinct from the Help on the website) we show the checkboxes as selected to further highlight the point. The website Help hasn't been refreshed for a couple of builds, it seems.

I think Bill got caught by Windows Explorer's little foible of keeping the original topic HTTP address after you follow links to other topics.

Regards

Roy

[Martin Terreni]

I don't have the "don't optimize..." option  
I'm using MySQL ODBC 3.51.20

[Martin Terreni]

solved it. just keep the "initial catalog" blank.

[jmandala]

This worked for me as well.