Latest Contributions by BillFox

Reference ESRI documentation v10.4: Upgrade an enterprise geodatabase in SQL Server Upgrade an enterprise geodatabase in SQL Server—Help | ArcGIS for Desktop  "Tip: If you are unsure of the database compatibility level of your SQL Server database, check the database properties from Microsoft SQL Server Management Studio. If your database compatibility level is 80, you must update your database compatibility level. See SQL Server documentation for instructions." But it does not indicate which level we must set it to for 10.4.1, 10.3.1. etc. Asrujit SenGupta‌ SButala-esristaff ... View more

Hi Paul, Did you receive any further information about ESRI/SQL Server compatibility levels? With 10.4.x not supporting SQL Server 2008 R2, has anyone seen ESRI documentation on SQL Server compatibility levels? 2016     130 2014     120 2012     110 2008 R2     105 2008     100 2005     90 2000     80 -Bill Asrujit SenGupta‌ Sanket‌ ... View more

Good idea, As of now I think you can do a hybrid with a public facing ArcGIS Server in the DMZ. secure the publishing folder with built-in user name/password share the secure service of your on premise enterprise geodatabase feature class to AGOL and use option to save user name/password with the service SAML AGOL to your AD add AD users to AGOL, groups, etc. but editor tracking from AGOL will probably post the built-in user instead of the SAML one on premise portal would post the correct AD user -Bill ... View more

Good idea, As of now I think you can do a hybrid with a public facing ArcGIS Server in the DMZ. secure the publishing folder with built-in user name/password share the secure service of your on premise enterprise geodatabase feature class to AGOL and use option to save user name/password with the service SAML AGOL to your AD add AD users to AGOL, groups, etc. but editor tracking from AGOL will probably post the built-in user instead of the SAML one on premise portal would post the correct AD user -Bill ... View more

Does anyone have a status update for this question? ... View more

Initial support cannot reproduce this error using Portal 10.4.1 Checking to see if it is a Portal 10.3.1 issue ... View more

Reference: Currently using Portal for ArcGIS v10.3.1 ... View more

nope, just noticed this same timeout error this morning with Portal for ArcGIS Web AppBuilder applications "out of the box" - Not using developer edition or any proxy adjustments. I'm running it by tech support. ... View more

Same error as you this morning, same v of chrome Works fine in Firefox 47.0.1 and ie 11 ... View more

This year's UC 2016 reply from Jack, Dear Bill, Thanks very much for your feedback on the UC Survey. You are absolutely right; we are pushing web GIS to be a complete GIS but it will take a while. Currently we are working on ArcGIS Pro COGO functionality going back to the old ArcInfo days. This functionality will be released this winter and given the fact that ArcGIS Pro can be commercialized into a cloud environment, it means that GIS professionals will be able to use browsers and carry out true curves and geometric network editing from nothing more than a browser environment. Best of luck to you, Bill, and I look forward to you having a great conference this year. Warm regards, Jack ... View more

Hi Alex, The native client item just references your windows desktop where ArcGIS Desktop is installed: Verify in your Control Panel > Programs > Programs and Features list which Microsoft SQL Server Native Client version you are using. Examples: Microsoft SQL Server 2008 R2 Native Client or Microsoft SQL Server 2012 Native Client As far as I can tell this SQL Server 2008/08 R2 issue requires at least SQL Server 2012 or 2014 as our database. And, requires the corresponding latest Microsoft SQL Server Native Client such as 2012 or 2014 depending on which SQL Server database version is in use. I think that latest native client gotcha applies to our desktops, ArcSDE/SQL Server site as well as our Portal for ArcGIS site. Some migration path examples/flow charts from ESRI support would be helpful with this issue but I know not everyone has the same setup. For example, a draft could look like this: Exhibit 'A' - So, you say you would like to migrate from ArcGIS 10.3.1-ish to 10.4.1 and you do not want to break anything. Review what you have: Your ArcGIS License Manager is 10.3.1 Your desktops are ArcGIS for Desktop 10.3.1 (and using Windows 7/8/10) Your ArcSDE (ArcGIS for Server) is 10.2.2 (and you have an ArcSDE Application service running for 3-tier connections) Your ArcGIS for Server site is 10.3.1 (and is federated with your Portal for ArcGIS) Your Portal for ArcGIS is 10.3.1 (and has a second SQL 2008 R2 geodatabase as its hosting container) Your Web Adaptor to ArcGIS for Server is 10.3.1 Your Web Adaptor to Portal for ArcGIS is 10.3.1 Your SQL Server is on the same server as your geodatabase and is 2008 R2 Your Windows Server Operating systems are at 2008 R2 Step 1 Install the latest SQL Server Native Client software on all user and server machines. Step 2 Get all your users & applications to stop using that ArcSDE Application Server and use only 2-tier direct connections to the geodatabase with that new native client software. Step 3 Stop that ArcSDE Application Server and remove it from the server and verify everything still works. Step 4 Update your ArcGIS License Manager from 10.3.1 to 10.4.1 (can probably be done even before step 1 since it runs on its own windows server) Step 5 Update your geodatabase from 10.2.2 to 10.3.1 Step 6 Update your SQL Server from 2008 R2 to 2014 (because 10.3.1 system requirements page does not list 2016 as supported and you would like to verify everything still works now that you have removed the ArcSDE Application Server and not introduced any 10.4.1 desktop or server items yet besides the license manager) Step 7 Update ArcGIS for Server site from 10.3.1 to 10.4.1 Step 8 Update Portal for ArcGIS from 10.3.1 to 10.4.1 Step 9 Remove the old 10.3.1 Web Adaptors and install new 10.4.1 Web Adaptors Step 10 Update the ArcGIS for Desktops from 10.3.1 to 10.4.1 (being sure that latest release SQL Server Native Client is already installed) Step 11 Update the geodatabase from 10.3.1 to 10.4.1 Step 12 Verify everything is still working Step 13 (Intentionally left empty due to hotels not having a thirteenth floor - same should apply to these procedures) Step 14 Update SQL Server from 2014 to 2016 Step 15 Verify everything is still working Any corrections/suggestions to the above would be greatly appreciated. -Bill Portal for ArcGIS​ ArcGIS for Server​ ... View more

did you upgrade the sql server client to sql server 2012 Native Client too? ... View more