I have a SQL Server geodatabase on our network, which I believe is SQL Server 2012. I don't have access to the database itself, but I need to connect to it to extract several feature classes. I have an FME job that extracts everything and writes it to a file geodatabase. A little while ago, I started getting connection errors in FME stating that it could not connect to the gdb and to check the database connection parameters. We use db authentication, so I had my password reset, but it still wouldn't connect. I realized that I started getting the errors right after I had upgraded to Pro 2.1 (and now 2.1.2). I can connect to the gdb in Desktop 10.5, and I can connect to a different database with the SQL instance using a non-spatial reader in FME, but I can't access the geodatabase either in Pro or in FME (I was using FME 2017.1, and now upgraded to 2018, and it still isn't working).
My coworker had Pro 2.0 and could connect to the gdb in Pro and in FME 2017, and he upgraded to Pro 2.1 today and is now getting the same error I am (see below).
It seems like there's an issue when connecting with a 64-bit application as opposed to a 32-bit one, but we could both connect using Pro 2.0, so I don't understand what would have changed. I checked the SQL database requirements for Pro 2.1 (Microsoft SQL Server database requirements for ArcGIS Pro 2.1—Help | ArcGIS Desktop ) but SQL Server 2012 SP3 is listed, so it seems like it's still compatible. Does anyone know what might have changed from Pro 2.0 to 2.1 that would be causing this error?