Some users crash ArcMap 10.4 selecting records from SQL Server

08-24-2016 03:57 PM
New Contributor III


We have been dealing with crashes for some users since we upgraded to 10.4 (and 10.4.1). After some research, a bug was submitted by Support Services that found that usernames over 22 characters crash ArcGIS Desktop 10.4.x when selecting over 100 records from a SQL Server 2014-based enterprise geodatabase configured with session-based log files.

Here is our setup:

DBMS: SQL Server 2014
Access Control: Windows Groups
Client: ArcGIS Desktop 10.4/10.4.1


There were some users that were crashing ArcMap 10.4.x while selecting records and other users who were not having any problems. We tried re-installing ArcGIS Desktop 10.4, provisioning brand-new Windows 7 & 10 desktops, and running ArcGIS Desktop 10.4.x on server operating systems. We also looked at SQL Server-based permissions, Active Directory user attributes, and ODBC vs. Native SQL Server clients. All pointed to something wrong with a user account and the only thing that was different was the length of the user name.  According to documentation here, a log table is created in TEMPDB when a client user selects more than 100 records using the default session-based log file configuration. Even when granted access via a Windows group, the logging operation uses the fully-qualified username.  Our Windows domain name alone is 13 characters. When paired with a username that exceeds 8 characters (DOMAIN[13] + "\"(1) + USERNAME[8]) ArcMap 10.4.x crashes when performing a selection of over 100 records. In testing, we created a long SQL Server login (non-Windows) username and got the same result.


- 10.3.1 desktop clients are unaffected; only 10.4.x.
- Users who are DBO in the database don't experience this problem.


- We did not test ArcGIS Pro.
- The web GIS seems OK but we haven't messed with it.
- We don't know if this affects SQL Server 2012 as we don't have any enterprise geodatabases running on it.


Until ESRI can address this issue, the workaround is to switch from session-based log files to either shared log files or log file pools.

We hope ESRI will fix this bug soon, but we wanted to post it here to see if anyone has experienced this super-frustrating issue.


Levin Conway

5 Replies
New Contributor III

Hi Levin,

We are having the same issue. We just upgraded to 10.4.1, from 10.2, and one of our ArcMap super users is unable to run a select-by-attribute query where more than a certain number of features are selected. I'm SO glad that you logged this issue! Because I was pulling my hair out trying to figure out why this one employee was having this issue where no one else was. He has a long last name.

As for the workaround, do you know if there is a way to just turn off the session logging for this one individual?

Thanks so much for documenting your case.

Mariette Shin

0 Kudos
New Contributor III


As far as I know the logging configuration applies to enterprise geodatabases, not individual users, and there doesn't appear to be a way to turn it off.  More information can be found in the documentation.


I'm just glad it wasn't just us experiencing this issue.  I'm hopeful that your response will help elevate the bug.




0 Kudos
New Contributor III

Same problem with 10.4.1 and SQL 2012.

0 Kudos
Esri Contributor

Hello All, 

This issue sounds like the following defect: BUG-000098582

If possible, please contact Esri Technical Support to have your organization attached to this defect. 



0 Kudos
Esri Contributor

The above defect has been addressed in the SQL Server Quality Improvement patch at ArcGIS 10.4.1.

 ArcGIS 10.4.1 for (Desktop, Engine, Server) SQL Server Quality Improvement Patch



  • BUG-000098582 - User names with more than 22 characters in SQL Server crashes ArcMap when selecting more than 100 features. 



0 Kudos