Latest Contributions by LevinConway

Greetings, We have an internal ArcGIS Enterprise deployment which we have been using for several years with staff, utilizing VPN connections for remote devices. We now are looking at setting up a separate, external GIS server with public (unauthenticated) GIS services that could be consumed inside ArcGIS Online web maps. I am interested if and how portal federation could be achieved using the design pattern where both the Web Adaptor and ArcGIS Server Site are located in a DMZ (as detailed in this image). What would our options be? 1. Both the GIS Server site and the Portal instance would need to be located in the same DMZ. 2. The GIS Server site could be federated through the DMZ's internal firewall to our existing internal Portal located on the private network. 3. We would be better off with a "classic" implementation of ArcGIS Server, avoiding federation and possibly waiting for a future release that could federate our external server with ArcGIS Online. Thanks in advance for any insight! ... View more

Greetings, 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 Findings: 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. Exclusions: - 10.3.1 desktop clients are unaffected; only 10.4.x. - Users who are DBO in the database don't experience this problem. Unknowns: - 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. Workaround: 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. Thanks, Levin Conway ... View more

Greetings, I have just updated one of our development portals from 10.3.1 to 10.4.  The portal comes up OK, but when trying to switch between top menu items, the following error is thrown in Internet Explorer 11: A potentially dangerous Request.Path value was detected from the client (:). We are running our portal (and IIS-based web adaptor) on Windows Server 2012 R2.  Some research indicated that ESRI moved to .NET 4.x at this release, which has more secure request validation in ASP.NET. The good news is that this error only affects IE configurations that have Compatibility View enabled.  The bad news is that many organizations (including ours) have this turned on by default for intranet applications needing earlier versions of IE.  I have logged an ESRI case on this, but if anyone experiences this error, turning Compatibility View off is the workaround. ... View more

Greetings, At 10.2, ArcGIS Server authentication now supports multiple Windows AD domains.  However, we only have one domain and it is cumbersome for users to enter Domain\User each time they log into secured services or otherwise connecting to ArcGIS Server.  (Try finding the backslash on an iPhone)  For various reasons we cannot use integrated Windows authentication on the Web Tier. It would be great if administrators could configure an optional "default" Windows AD domain prefix that would be be "prepended" to the user name so users would not have to type the domain every time.  This would mimic the functionality of 10.1 without compromising the ability to use multiple domains.  Even adding the ability for the server to recognize user@domain would be an improvement.  (For example, Outlook Web Access accepts all three login "styles".) Thanks for your consideration, Levin Conway ... View more

Greetings, At 10.2, ArcGIS Server authentication now supports multiple Windows AD domains.  However, we only have one domain and it is cumbersome for users to enter Domain\User each time they log into secured services or otherwise connecting to ArcGIS Server.  (Try finding the backslash on an iPhone)  For various reasons we cannot use integrated Windows authentication on the Web Tier. It would be great if administrators could configure an optional "default" Windows AD domain prefix that would be be "prepended" to the user name so users would not have to type the domain every time.  This would mimic the functionality of 10.1 without compromising the ability to use multiple domains.  Even adding the ability for the server to recognize user@domain would be an improvement.  (For example, Outlook Web Access accepts all three login "styles".) Thanks for your consideration, Levin Conway ... View more

Greetings, Due to an odd combination of circumstances, we have 1 license for ArcGIS Server Enterprise Basic and 1 license for ArcGIS Server Workgroup Standard.  We have just started using multiuser editing and do so successfully on our Enterprise Basic server and it works fine for all of our desktop GIS users.  We would like to set up an additional server to publish web services internally (beyond the simple feature services available at Basic) and are wondering if we can use the Workgroup Standard license to do that by using one-way replication to replicate data from the Enterprise Basic SDE database to file geodatabases hosted on the Workgroup Standard Server.  The documentation clearly states the following: 1.   SDE Geodatabases created at the Workgroup level have a 10-user connection limit, but the connection limit doesn't apply for web service connections. We wouldn't be using any enterprise geodatabases either hosted or created on the Workgroup server, so would the connection limit not apply? 2.   File geodatabases containing simple feature geometry hosted on a single ArcGIS Server machine generally perform on par with enterprise SDE databases.  Using file geodatabases for publishing is a supported configuration, although we are aware that it does limit web-based editing workflows. We realize this is probably not a supported configuration, but is it possible?  If not we can upgrade our Workgroup Standard license to Enterprise Standard. Please advise. ... View more