Add Database Connection Crash

DaveTenney · ‎10-10-2017

All

we have some users have recently had to install sql server(2014 and/or 2016) on their new machines as well as ArcGIS for Desktop. It appears that they have 2012 native client installed on their machine as well.

When they double click the "add database connection" within catalog, ArcMAP crashes.

any thoughts?

thanks

Dave

TracySchloss · ‎11-13-2017

We are having a similar problem with DB2. In our situation, as soon as the user clicks Add Database Connection, they are kicked out of ArcCatalog. At that point, the user hasn't even chosen a particular database type. The software would have no way of knowing what you were getting ready to connect to. However, there must be some level of awareness of what types of clients are available?! We did a test where we removed the DB2 client entirely, and Add Database Connection no longer crashed ArcCatalog. We don't know exactly what that means, but it seemed significant.

In your scenario, are you opening ArcCatalog in the ArcMap sidebar, or in it's own window?

DaveTenney · ‎11-13-2017

Tracy,

we were opening Catalog within ArcMAP.

the behavior was very sporadic between users and one action would fix one users problem and not others. we were using 10.3.1 and most of our users were using either sql14 or sql16. after talking with esri support and realizing version support we decided to push our timeframe of having all users upgrade to 10.5.1.

once we upgraded to 10.5.1 all of our issues were gone.

im not sure if that is a solution for you or not.

thanks

dave

TracySchloss · ‎11-13-2017

Our geodatabase is still at 10.0.2! Unfortunately. It's part of a large enterprise application, and it's about impossible to stay up on versions across all the clients and servers. We're in the process of upgrading to 10.3.1, because that's what's supported at the current version of DB2 we have. If we can get the geodatabase to 10.3.1, then I think we can use 10.5 clients, but not until then.

It was such a hard lift to migrate from those early 10.x releases, I expect it to be a more easier step to get to 10.5. I see 10.3.1 as a intermediate step we have to get through. At least then we'll be on a supported platform, for a while anyway.

It's nice to know your problems went away at version 10.5, though.

DaveTenney · ‎11-13-2017

We were lucky that we were at the point of considering the push to 10.5.1, we have been in your shoes many times where we weren't ready to make the jump to the latest and greatest.

good luck!

dave