Latest Contributions by RandallWilliams

I'm surprised by this response as well. I've heard of issues related to IPv6, but not subnets explicitly. I'd update the FlexLM_Timeout environment variable on the clients. Which version LM are you working with? If you haven't updated to the 10.4 version, I'd do so (for security reasons). The LM is backward compatible to previous versions of ArcGIS Desktop software. See also: Error connecting through VPN to Arcgis License Server - Community Contributions - Hermes ... View more

Is Google Earth maybe looking for a URL to the capabilities document? http://localhost:6080/arcgis/services/WIP78Mosaic/ImageServer/WMSServer?request=GetCapabilities&service=WMS ... View more

I'm pretty sure that this is an ArcGIS.com property. I don't have this one my servers, and the example you're pointing to is an ArcGIS.com tile server. ... View more

Hi Joanna, Can you step me through your workflow? ... View more

Are you registering a UNC path or a local path? EG: \\server\share or c:\path\to\data ? ... View more

@Rebecca the 10.2.2 patch is now live ArcGIS for Server Security 2016 Update 2 Patch ... View more

Hi @Karyn Tareen, The DOC team confirmed that there were issues migrating this document and are working on addressing this. Meanwhile, I've pulled the raw content from our KB management system and have posted the details below. Sorry for the inconvenience. Problem: After upgrading to ArcGIS 10.4 for Server, existing services that use data in geodatabases in SQL Server no longer work Description After upgrading ArcGIS for Server to version 10.4, services that consume data in geodatabases in SQL Server 2008 or 2008 R2 no longer function. ArcGIS Server logs show messages indicating "Connection was attempted with an older version of SQL Server client communications software that is not supported." Cause Beginning with ArcGIS 10.4, SQL Server 2008 and 2008 R2 are no longer supported. Solution Upgrade to SQL Server 2012 or SQL Server 2014, which are supported at ArcGIS 10.4 Customers who must continue to have access to their SQL Server 2008 or 2008 R2 geodatabases while planning their upgrade to SQL Server 2012 or SQL Server 2014, can upgrade the SQL Server client on the ArcGIS for Server machine to SQL Server 2012 Native Client or Microsoft ODBC Driver 11, and restart the ArcGIS Server Windows service. ** If a customer has moved to ArcGIS 10.4, but has connections to older geodatabases in SQL Server 2008 and 2008 R2, Esri Support will attempt to reproduce the issue with SQL Server 2012 or SQL Server 2014. If the issue cannot be reproduced on a supported version of SQL Server, the customer will be asked to update their version of SQL Server. Also, customers who move to ArcGIS 10.4 but are still using SQL Server 2008 or 2008 R2 will not be able to create a new geodatabase until they upgrade SQL Server to a supported release. Related Information: Microsoft SQL Server database requirements for ArcGIS 10.4 Connect to Microsoft SQL Server from ArcGIS   Manage connections in SQL Server ... View more

Yes, a lot of links were broken when the support site was recently updated. I'm working with the content team at Esri to find out where this doc went. I'll follow up... ... View more

Whelp, color me schooled! ... View more

Yup. The process of registering a Web Adaptor with a Portal will fail if another web adaptor has been previously registered. The registration screen will throw an error indicating the issue. The Server Web Adaptor must set at anonymous if federating through that web adaptor. ... View more

@Jacob Boyle above is correct. When you use IWA the assumption is that you're going to want Single Sign-On. SAML is the way to go in this case. ... View more

Hi Paul, Thanks for that excellent response. In terms of stand-alone portal, the same rule applies. That said, I haven't personally tested what happens after federation or what happens if data store is installed. Before I speak to these questions, I'm going to test this scenario in my sandbox and follow up. I strongly suspect that a name change is going to break a lot of these workflows from this standpoint. Thinking about this deeper and playing it out in my head, the data store component seems like it might be challenging to deal with. So does changing hostnames when the server is federated with a Portal. This is good conversation. I'll follow up. ... View more