More

Problem accessing 10.0 File Geodatabase from ArcGIS Desktop 10.1


I'm on 10.0 SP4 (build 4000) and two co-workers are on 10.1 original release (build 3035 I believe). The DB was provided by a client and saved on a network drive. Since I have no issue accessing the data I assumed it was created in 10.0 or earlier. One of the co-workers is trying to access the data remotely, the other from within the office network. They both got the same "Failed to connect to database" error message. A third co-worker on 10.0 gave it a try in the office and it worked for him.

This looks to me a typical backward compatibility scenario, plus there are other DBs created in 10.0 and they had no issue accessing from 10.1. I'm puzzled why this is happening? Shapefiles were created so everyone can reference the data, but I'm really curious in finding out what could be the cause of the issue.


ArcGIS for (Desktop, Engine, Server) WMTS Tiles Misalignment Patch

This multiple version patch addresses an issue where tiles served from an ArcGIS for Server WMTS service do not align correctly with other layers in the map and WMTS services consumed in ArcGIS for Desktop or ArcGIS Engine causes a shift in display.

  • Introduction
  • Issues Addressed with this patch
  • Installing this patch on Windows
  • Installing this patch on Linux
  • Patch Updates
  • How to identify which ArcGIS products are installed
  • Getting Help

Introduction

Esri® announces the ArcGIS for (Desktop, Engine, Server) WMTS Tiles Misalignment Patch. This patch addresses an issue where tiles served from an ArcGIS for Server WMTS service do not align correctly with other layers in the map and WMTS services consumed in ArcGIS for Desktop or ArcGIS Engine causes a shift in display. It is recommended to install the ArcGIS for Desktop and ArcGIS Engine patches to avoid any misalignment issues when consuming WMTS services from ArcGIS for Server. A patched ArcGIS for Desktop or ArcGIS Engine correctly aligns a WMTS layer served from either a patched or unpatched ArcGIS for Server. A WMTS service served from a patched ArcGIS for Server will allow the layer to align correctly in non-Esri client applications. This patch deals specifically with the issue listed below under Issues Addressed with this patch.

Issues Addressed with this patch

  • BUG-000088847 - Tiles from WMTS Services for some coordinate systems (or CRS) do not align in ArcGIS Desktop and when served from ArcGIS Server.
  • BUG-000088454 - If a folder path contains letter 'u' after '' ArcGIS for Server search service fails to register the folder with an error For Input String: "sage".
  • BUG-000082640 - When choosing a different location for installation of ArcGIS for Server 10.3 other than the default for the arcgisserver folder, the installation still creates the folder under c:arcgisserver folder and a new location specified. Also, when the arcgisserver that was initially created is removed, the system automatically creates a new arcgisserver folder with a directories subfolder that is empty.
  • BUG-000084674- Incorrect related rows are returned when the related data has edits, is archived, is non-versioned and keysets are used.
  • BUG-000084197 - A blank page returned when trying to access secured services on ArcGIS for Server (AGS) 10.3 REST page if the AGS is federated to portal and if the browser language is set to non-English language.
  • BUG-000082467 - ArcGIS for Server opens too many files and does not release the file handles when serving cached services.
  • BUG-000088244 - Optimize the deletion of objects from the geodatabases internal metadata.
  • BUG-000087118 - REST cache regenerates for each request when more than 100 services are accessed.
  • BUG-000086943 - The Verify, Repair and Rebuild Connectivity Tools need to identify and fix the max EID corruption problems.
  • BUG-000086566 - Recreating cache tiles for a cached service with preexisting cache fails randomly, at times leaving temporary files such as ".freelist, tmp.bundle, tmp.bundlx, tmp.freelist, compress.bundle, *.lock".
  • BUG-000086461 - Mosaic dataset not seen in full extent due to less number of overview levels.
  • BUG-000086412 - Queries against feature services layers that contain a many columns takes longer than queries against the same layers map service endpoint.
  • BUG-000086192 - Loading data into a Geometric network Feature Class using arcpy.Append_management in Python can result in corrupted network features.
  • BUG-000083258 - Add support for CORS in Map/Image Services Tile Handler.
  • BUG-000082869 - An incorrect KML network link is created when ArcGIS for Server machine name has 'services' in it.
  • BUG-000082777 - Data specific: When re-caching data using a certain area of interest the Status.gdb shows negative tile count.
  • BUG-000082665 - Disable SSLv3 on the internal tomcat to prevent "POODLE" vulnerability.
  • BUG-000082467 - ArcGIS for Server opens too many files and does not release the file handles when serving cached services.
  • BUG-000082423 - Under consistent load, the javaw.exe process at ArcGIS 10.2.2 for Server consumes 25% of the server's RAM, and any further request forces the process to use 100% of the machine's CPU.
  • BUG-000081679 - When publishing to a federated GIS Server that has a config store on a DFS share, item information does not get copied to the portal item.
  • BUG-000081401 - Multiple cross-site scripting (XSS) vulnerabilities in ArcGIS for Server.
  • BUG-000081239 - ArcGIS Server has an open redirect vulnerability.
  • BUG-000080898 - Reflected cross-site scripting security (XSS) vulnerability.
  • NIM103623 - After publishing services to a federated GIS Server, item information is sometimes missing from the Portal item that is created.
  • NIM103555 - Printing a map service with more layers including legends result in performance issues with ArcGIS for Server 10.2.2 print service.
  • NIM103130 - Some of the tiles fail to generate on demand when the requests are sent through REST connection in ArcGIS for Server 10.2.2.
  • NIM102939 - Multiple stored cross-site scripting (XSS) found in ArcGIS for Server. This occurs in ArcGIS for Server 10.1, 10.1 SP1, 10.2, 10.2.1, and 10.2.2.
  • NIM102197 - Unauthorized users can access tiles from a secured map service immediately after any authorized user accesses the service.
  • NIM099582 - ArcGIS Server performance drops when switching the identity store configuration from Active Directory to Active Directory with nested group support.
  • NIM098130 - ExportTiles fails for Japanese iOS client due to mangled Japanese characters in JSON responses.
  • NIM097651 - Public map services become private and require authentication after a brief disconnect of the config-store when the server is under load.
  • NIM087627 - Creation of Tile Package fails with an error "Invalid function arguments", when Server Tiling scheme is based on a custom projection.
  • BUG-000083610 - Printing an external secure service with limit usage referrers fails in an ArcGIS Online web application.
  • BUG-000082665 - Disable SSLv3 on the internal tomcat to prevent "POODLE" vulnerability.
  • BUG-000081401 - Multiple cross-site scripting (XSS) vulnerabilities in ArcGIS for Server.
  • BUG-000081239 - ArcGIS Server has an open redirect vulnerability.
  • BUG-000080898 - Reflected cross-site scripting security (XSS) vulnerability.
  • NIM100965 - Starting a service with 0 minimum instances causes the service locks not to release if service is consumed while it is starting.
  • NIM102939 - Multiple stored cross-site scripting (XSS) vulnerabilities found.
  • NIM102197 - Unauthorized users can access tiles from a secured map service immediately after any authorized user accesses the service.
  • NIM100306 - In ArcGIS for Server 10.2.1, when a service with the 'Minimum Instances' parameter set to zero gets published with errors on a non-default cluster.
  • NIM097651 - Public map services become private and require authentication after a brief disconnect of the config-store when the server is under load.
  • BUG-000082506 - 400 Bad Request errors occur when a user's role list exceeds 4KB.
  • NIM102939 - Multiple stored cross-site scripting (XSS) found.
  • NIM102197 - Unauthorized users can access tiles from a secured map service immediately after any authorized user accesses the service.
  • NIM098557 - Folder Navigation in REST is slowed by the amount of services located in the folder.
  • NIM097880 - In a distributed environment with two clusters a Load Balancer, a stopped machine causes a significantly increase in the access time for the REST and Manager endpoints.
  • NIM097651 - Public map services become private and require authentication after a brief disconnect of the config-store when the server is under load.
  • NIM092249 - With very large bundles REST tile handler is not responding with a valid tile, whereas the SOAP request returns with success.
  • NIM091406 - If there are two layers in the map pointing to the same dataset, one with a definition query and the other with a relate, querying related records returns no results for the second layer - works fine for the first layer.
  • NIM098133 - The layer without relate should not display relationship information when another layer off the same FeatureClass has an in-memory relationship.

Installing this patch on Windows

Installation Steps:

    Download the appropriate file to a location other than your ArcGIS installation location.

ArcGIS 10.3.1 Checksum (Md5)
ArcGIS Desktop
Background Geoprocessing (64-bit)
ArcGIS-1031-BGDT-WTM-Patch.msp 2FC8E4F8790B97C20A17DAC546F950B2
ArcGIS Engine
Background Geoprocessing (64-bit)
ArcGIS-1031-BGE-WTM-Patch.msp 941ACE03E80532D34B853BC3C76E08DA
ArcGIS for Desktop ArcGIS-1031-DT-WTM-Patch.msp 4965A062630D1A97B16282F2355F7A6C
ArcGIS Engine ArcGIS-1031-E-WTM-Patch.msp C58D06922294CAED3C5830CDB31E48B2
ArcGIS for Server ArcGIS-1031-S-WTM-Patch.msp F39EB7BC0C524EFCB1E5E0115A7DC09B
ArcGIS 10.3 Checksum (Md5)
ArcGIS Desktop
Background Geoprocessing (64-bit)
ArcGIS-103-BGDT-WTM-Patch.msp A250C5A58341F3BF47D7B290BB715B63
ArcGIS Engine
Background Geoprocessing (64-bit)
ArcGIS-103-BGE-WTM-Patch.msp 961E1EC46C29D15ACD1364217F2DC07A
ArcGIS for Desktop ArcGIS-103-DT-WTM-Patch.msp E2F2FDCBA04DB8396B1DF205574BF448
ArcGIS Engine ArcGIS-103-E-WTM-Patch.msp 3DA7DDE48CB038352BFEA2AF6CE4DF13
ArcGIS for Server ArcGIS-103-S-WTM-Patch.msp C6C18864431E699D2BE80ABA1009076B
ArcGIS 10.2.2 Checksum (Md5)
ArcGIS Desktop
Background Geoprocessing (64-bit)
ArcGIS-1022-BGDT-WTM-Patch.msp 4E8627159B364B71356BC7476A02E0B9
ArcGIS Engine
Background Geoprocessing (64-bit)
ArcGIS-1022-BGE-WTM-Patch.msp B5A6AC83E5197A4D1A58DCD025C4C502
ArcGIS for Desktop ArcGIS-1022-DT-WTM-Patch.msp 5811EB71DD28A158E283227F28B75522
ArcGIS Engine ArcGIS-1022-E-WTM-Patch.msp F8D08873A7A9E001B5D62F58DC9119E7
ArcGIS for Server ArcGIS-1022-S-WTM-Patch.msp F7D8814629DD8591E8BA8135AEA4F93E
ArcGIS 10.2.1 Checksum (Md5)
ArcGIS Desktop
Background Geoprocessing (64-bit)
ArcGIS-1021-BGDT-WTM-Patch.msp BA93B38E6B6CC4ED3D57A6D2844F723B
ArcGIS Engine
Background Geoprocessing (64-bit)
ArcGIS-1021-BGE-WTM-Patch.msp F07854EAE6AB649A335B0CDAA0D629DA
ArcGIS for Desktop ArcGIS-1021-DT-WTM-Patch.msp D96078CFE70A435C0E3E68A125F8AAA0
ArcGIS Engine ArcGIS-1021-E-WTM-Patch.msp 4AB1621E057408786A12BDEC50AA4613
ArcGIS for Server ArcGIS-1021-S-WTM-Patch.msp 94745506448C2C37E3D402C5A7DBD73B
ArcGIS 10.2 Checksum (Md5)
ArcGIS 10.2 for Server Security Patch (September 2013) is required to be installed prior to installing the ArcGIS 10.2 for Server version of this patch.
ArcGIS Desktop
Background Geoprocessing (64-bit)
ArcGIS-102-BGDT-WTM-Patch.msp 559442A20AF4CE3BA2807B404EA385F6
ArcGIS Engine
Background Geoprocessing (64-bit)
ArcGIS-102-BGE-WTM-Patch.msp D0A96F45ACED67A418FBA0F23C63DBDA
ArcGIS for Desktop ArcGIS-102-DT-WTM-Patch.msp 0F26ECFD0B833D5AE25A6BC2455CE2D8
ArcGIS Engine ArcGIS-102-E-WTM-Patch.msp CAEBA6BBD97E94562A6C4978926B952A
ArcGIS for Server ArcGIS-102-S-WTM-Patch.msp 6011261E1EB4B60EE3A045CC006C3453
ArcGIS 10.1 SP1 QIP Checksum (Md5)
ArcGIS Desktop
Background Geoprocessing (64-bit)
ArcGIS-101SP1QIP-BGDT-WTM-Patch.msp 881E2F62F0A72978CF31A20ECFA30B31
ArcGIS Engine
Background Geoprocessing (64-bit)
ArcGIS-101SP1QIP-BGE-WTM-Patch.msp FFBD2B1D56FC6FEA494F49B211CAE157
ArcGIS for Desktop ArcGIS-101SP1QIP-DT-WTM-Patch.msp AEA4A249421B454733B3A2E60569A3A8
ArcGIS Engine ArcGIS-101SP1QIP-E-WTM-Patch.msp BC970655D25EB7A063F4268C8F4EDFC6
ArcGIS for Server ArcGIS-101SP1QIP-S-WTM-Patch.msp 935BCB81D30EA903563EA139B3F38079

NOTE: If double clicking on the MSP file does not start the setup installation, you can start the setup installation manually by using the following command:

Installing this patch on Linux

Installation Steps:

Complete the following install steps as the ArcGIS Install owner. The Install owner is the owner of the arcgis folder.

ArcGIS 10.3.1, 10.3, 10.2.2, 10.2.1, 10.2, or 10.1 SP1 QIP for Engine or Server must be installed before installing this patch.

    Download the appropriate file to a location other than your ArcGIS installation location.

Patch Updates

Check the Patches and Service Packs page periodically for the availability of additional patches. New information about this patch will be posted here.

  • ArcGIS Engine 10.3.1
  • ArcGIS 10.1 SP1 QIP for Desktop, Background Geoprocessing 64-bit for Desktop, Engine, Background Geoprocessing 64-bit for Engine, ArcGIS for Server.
  • ArcGIS Engine 10.2 (Linux)
  • ArcGIS for Server 10.2 (Windows)
  • ArcGIS engine 10.3 (Linx)

How to identify which ArcGIS products are installed

To determine which ArcGIS products are installed, choose the appropriate version of the PatchFinder utility for your environment and run it from your local machine. PatchFinder will list all products, hot fixes, and patches installed on your local machine.

Getting Help

Domestic sites, please contact Esri Technical Support at 1-888-377-4575, if you have any difficulty installing this patch. International sites, please contact your local Esri software distributor.


ArcGIS 10.2.1 for (Desktop, Engine, Server) Utilities and Telecom Update 3 Patch

This patch is the third in a series of updates targeting utility and telecom workflows, though it can be beneficial to all users of ArcGIS 10.2.1. The patch targets a number of issues addressing problems with the geometric network, versioning and also corrects issues with the st_geometry storage type.

  • Introduction
  • Issues Addressed with this patch
  • Installing this patch on Windows
  • Installing this patch on Linux
  • Upgrade a geodatabase
  • Patch Updates
  • How to identify which ArcGIS products are installed
  • Getting Help

Introduction

Esri® announces the ArcGIS 10.2.1 for (Desktop, Engine, Server) Utilities and Telecom Update 3 Patch. This patch is the third in a series of updates targeting utility and telecom workflows, though it can be beneficial to all users of ArcGIS 10.2.1. The patch targets a number of issues addressing problems with the geometric network, versioning and also corrects issues with the st_geometry storage type. This patch deals specifically with the issues listed below under Issues Addressed with this Patch.

Issues Addressed with this patch

  • BUG-000086943 - The Verify, Repair and Rebuild Connectivity Tools need to identify and fix the max EID corruption problems.
  • BUG-000086941 - Support read only geodatabases in Oracle.
  • BUG-000086192 - Loading data into a Geometric network Feature Class using arcpy.Append_management in Python can result in corrupted network features.
  • BUG-000086160 - Requests made in parallel to add or delete feature classes are causing deadlocks to the gdb_tables_last_modified table.
  • BUG-000085669 - When creating a new version during an edit session, stopping the edit session in the base version without saving the edits may corrupt the geometric network in the newly created version.
  • BUG-000085184 - Splitting a complex edge causes related objects to be unrelated.
  • BUG-000085006 - ArcCatalog 10.3 crashes when compressing with a specific ArcSDE geodatabase.
  • BUG-000084498 - ArcGIS Desktop crashes when posting versioned edits to default with the features registered as versioned with options to move edits to base.
  • BUG-000083139 - Change version dialog is extremely slow to open.
  • BUG-000082420 - Calling ISimpleJunction.EdgeFeatureCount within a loop against data in sde yields a "Out of Server Memory" error.
  • NIM104524 - Performance degradation is observed with the 'Select by Location' tool when using ArcGIS 10.0 SP5 and above against enterprise geodatabases.
  • NIM102561 - The IFeatureEdit2.SplitWithUpdate method does not call IFeatureClassEdit.CustomSplitPolicy on a complex edge feature class extension.
  • NIM101805 - Do not allow the registering of views with the geodatabase.
  • NIM101236 - When viewing a non-versioned, archived SQL Server feature class with more than 123 columns, the following error message is received: "Error opening feature class. Out of server memory."
  • NIM100811 - Slow performance using the Feature Class to Feature Class geoprocessing tool to load data into a SQL Server geodatabase.
  • NIM099678 - The Identify tool fails to identify SDEBINARY features when a join exists from a feature class to a table using the same connection.
  • NIM096843 - Redundant execution of queries - per execution of spatial query on ST_GEOMETRY FC.
  • NIM096793 - Records can be left in the Geometry CAD side table when compressing updated features to the base table.
  • NIM094902 - The ST_Intersection fails with the error "ORA-28579" when dealing with certain multipart line features.
  • NIM094237 - Records can be left in the Geometry CAD side table when updating features and saving edits to base.
  • NIM088143 - Joining a versioned feature class to a table not registered with the geodatabase causes ArcMap to crash.
  • NIM085757 - The trace weight field is not preserved on new feature classes added to an existing Geometric Network.
  • BUG-000081231 - After disconnecting and connecting linear source features from a geometric network and updating the associated schematic diagram, a new schematic ID is generated for that feature and the vertices are removed.
  • BUG-000082028 - Standard editing workflows consume increasing amounts of memory and do not release it after editing has stopped.
  • BUG-000082630 - Versioned Difference Cursor single branch edits invert the "type" of change reported (e.g., Deletes become Inserts, Inserts become Deletes).
  • NIM088321 - User defined spatial index grids are not honored by ArcGIS when using the Add Spatial Index tool, even though the tool runs successfully.
  • NIM096460 - After dropping and rebuilding the geometric network and updating a schematic diagram containing schematic rules, network junction locations are not preserved.
  • NIM097184 - Creating a checkout in a 9.3.1 geodatabase fails with 10.2.1 Desktop.
  • NIM097983 - Optimize the opening of map documents by augmenting the geodatabase schema cache to include properties of the sde metadata.
  • NIM098475 - Spatial indexes are not created when creating a feature class on an ArcSDE 10 database from an ArcGIS Desktop 10.2 client.
  • NIM098196 - Exporting SDE schema using Oracle expdp generates ora-39127, ora-20098 and ora-06512 error about the spatial index created on GDB_items table having the st_grids parameter as commas when Oracle 11gR2 is used.
  • NIM098665 - Making a connection to a non-spatial Oracle database using either a Spatial Database Connection or an OLE Database Connection takes a significantly long time when there is a large amount of objects in the database.
  • NIM099484 - Provide a mechanism to enable instrumentation of memory usage when creating a feature cache in desktop.
  • NIM096111 - Rotating a point after a specific selection workflow on a geometric network rotates and shifts the entire geometric network.
  • NIM100182 - Bad SCHEMATICTID when diagrams get exported. Schematic features associated with GIS features which are not part of the geometric network are exported with "-2" at the end of their SCHEMATICTID.
  • NIM100823 - Rebuild the spatial index on a versioned feature class fails with an SRID mismatch error.
  • NIM100941 - Improve the Performance and Scalability of Creating and Syncing replicas by more efficiently caching database information.
  • NIM101461 - When feature classes with different SRIDs are used in an ST_intersection query, it fails with 'ORA-06530: Reference to uninitialized composite'.
  • NIM101468 - Unable to hide standalone tables using the IWorkspaceExtension.DataDictionaryTableNames method in ArcGIS 10.1 and above.
  • NIM101270 - Recalculating the feature extent on specific datasets returns the following error: "Failed to recalculate extent. The specified coordinate exceeds the valid coordinate range."
  • NIM101376 - ArcGIS for Desktop fails to save the connectivity rules for a specific geometric network.
  • NIM101746 - The Alter Field online help documentation page indicates that the Alter Field tool is available at all license levels however, the tool is unavailable at lower license levels.
  • NIM102077 - ArcGIS reports that an Oracle SDELOB or WKB feature class created in a pre-10.1 geodatabase does not have a spatial index when it does exist.
  • NIM102230 - Do not return the Documentation field on joined queries for Geodatabase internal metadata.
  • NIM102846 - When exporting diagrams into another schematic dataset using the Export Schematic Dataset process configured with GUIDs reattachment, the process expects GUIDs for each feature they contain. This is blocking when GUIDs are only missing for a feature class, in particular when this is missing for _Junctions.
  • NIM102848 - Creating a spatial index will pass values gathered from existing enterprise feature classes that may be invalid instead of passing correct values.
  • NIM102883 - When using a newer client (10.1+) against an older SQL server geodatabase (pre-10.1) through an application server connection, creation of a spatial index will fail on GEOMETRY or GEOGRAPHY feature classes with 'This SDE server does not support this client or operation'.
  • NIM102895 - Data exported via a XML workspace does not retain any 4-byte (or greater) characters in the data's attribute table.
  • NIM102996 - After dropping a spatial index on a binary feature class through an application server connection to a pre-10.1 geodatabase in SQL Server, ArcGIS is unable to determine the index is gone.
  • NIM103593 - File Geodatabase lock files should be opened as Read, rather than as Read/Write. This improves feature class/table creation performance.
  • NIM103683 - When script/query/constant attributes are configured on a schematic feature class for which the schematic features are not initialized, the attributes are not updated.
  • NIM103708 - Filter the AUDSYS, OJVMSYS, GSMADMIN_INTERNAL, DVSYS Oracle objects from connection in ArcGIS.
  • NIM103781 - The network index DESC query must only fetch the necessary attributes and not SELECT * when obtaining the USERID or ELEMENT mappings.
  • NIM104247 - Implement two new API functions for se_enable_schema_chache and se_disable_schema_cache.
  • NIM104317 - When fetching a network dataset index page, only fetch the pageblob.
  • NIM104321 - MDXT_xxx$% tables show up in ArcCatalog, connected to a 11.2.0.4 or 12.1.0.1 instance, and some are not deleted even when the feature class is deleted.

  • NIM086295- On Oracle ST_OrderingEquals is always returning the same value as ST_Equals.
  • NIM088921 - Importing an SDE schema dump fails with ORA-39083 and ORA-02309 on SDE.st_type_export.validate_spref using datapump impdp.
  • NIM089510 - Inconsistent results with st_astext_f query on polygons with more than 292 vertices.
  • NIM090071 - Labeling features based on join table's field throws 'ArcMap drawing errors' when the table and feature class are stored in different DBMS.
  • NIM094291 - The extent of data created in MicroStation DGN files is not correctly calculated in ArcMap 10.2 which causes the data to be displayed in the wrong location.
  • NIM094556 - Results from the Trace Geometric Network geoprocessing tool to trace connected are not consistent with the trace results from the Find Connected tool in the Utility Network Analyst toolbar.
  • NIM095455 - In an edit session, snapping stops working on a layer if a join exists on that layer.
  • NIM096135 - Provide option to create user schema geodatabases by a user other than SYS.
  • NIM096817 - Loading a large amount of coordinates via ST_Geometry function results in ORA-20004 and ORA-20000 errors.
  • NIM097346 - Extproc not initialized when a ST_Intersects query involving a versioned view and a base table is the first query run in the session.
  • NIM099098 - ST_ASTEXT Function is failing when the result set contains more than one record, and when the NUMPOINTS is

Installing this patch on Windows

Installation Notes:

System Administrators: A technical paper is available that discusses the enterprise deployment of ArcGIS 10.2.1 setups using Microsoft Systems Management Server (SMS), System Center Configuration Manager (SCCM), and Group Policy, including additional system requirements, suggestions, known issues, and Microsoft Software Installation (MSI) command line parameters. Deployment in a lockdown environment is also covered. ArcGIS 10.2.1 Enterprise Deployment.

Installation Steps:

ArcGIS 10.2.1 for Desktop, Engine, or Server must be installed before installing this patch.

    Download the appropriate file to a location other than your ArcGIS installation location.

NOTE: If double clicking on the MSP file does not start the setup installation, you can start the setup installation manually by using the following command:

Installing this patch on Linux

Installation Steps:

Complete the following install steps as the ArcGIS Install owner. The Install owner is the owner of the arcgis folder.

ArcGIS 10.2.1 for Engine or Server must be installed before installing this patch.

    Download the appropriate file to a location other than your ArcGIS installation location.

Checksum (Md5)
ArcGIS Engine ArcGIS-1021-E-UTU3-Patch-lx.tar 21E7110C913C615832CDC750A09FD458
ArcGIS for Server ArcGIS-1021-S-UTU3-Patch-lx.tar FF5B27D6E3061595368E0A53A6F710F2

Upgrade a geodatabase

A geodatabase upgrade is required after applying this patch. To upgrade the geodatabase, follow the instructions in the help section specific to your database management system:

Patch Updates

Check the Patches and Service Packs page periodically for the availability of additional patches. New information about this patch will be posted here.

How to identify which ArcGIS products are installed

To determine which ArcGIS products are installed, choose the appropriate version of the PatchFinder utility for your environment and run it from your local machine. PatchFinder will list all products, hot fixes, and patches installed on your local machine.

Getting Help

Domestic sites, please contact Esri Technical Support at 1-888-377-4575, if you have any difficulty installing this patch. International sites, please contact your local Esri software distributor.


Large ArcGIS Server 'Site': stability issues

We have an existing ArcGIS Server (AGS) 10.0 solution that is hosting close to 1,000 mapping services. We have been working on an upgrade to this environment to 10.2.1 for a few months now and we are having a hard time getting a stable environment. These services have light use, and our program requirements are to have an environment that can handle large amounts of services with little use. In the AGS 10.0 space we would set all services to 'low' isolation with 8 threads/instance. We also had 90% of our services set to 0 min instances/node to save on memory. Below is a summary of our approaches and where we are today. I'm posting this to the community for information, and I am really interested in some feedback and or recommendations to make this move forward for our organization.

  • Targeted ArcGIS Server 10.2.1
  • Config-store/directories are hosted on a clustered file server (active/passive) and presented as a share: servernameshare
  • Web-tier authentication
    • 1 web-adaptor with anonymous access
    • 1 web-adaptor with authenticated access (Integrated Windows Authentication with Kerberos and/or NTLM providers)
    • 1 web-adaptor 'internally' with authenticated access and administrative access enabled (use this for publishing)

    We have a few arcgis server deployments that look just like this and are all running fairly stable and with decent performance.

    Approach 1: Try to mirror (as close as possible) our 10.0 deployment methodology 1:1

    • Build 4 AGS 10.2.1 nodes (virtual machines).
    • Build 4 individual clusters & add 1 machine to each cluster
    • Deploy 25% of the services to each cluster. The AGS Nodes were initially spec'd with 4 CPU cores and 16GB of RAM.
      • Each ArcSOC.exe seems to consume anywhere from 100-125MB of RAM (sometimes up to 150 or as low as 70).
      • Publishing 10% of the services with 1 min instance (and the other 90 to 0 min instances) would leaving around 25 ArcSOC.exe on each server when idle.
      • The 16GB of RAM could host a total of 100-125 total instances leaving some room for services to startup instances when needed and scale slightly when in use.

      our first problem we ran into was publishing services with 0 instances/node. Esri confirmed 2 'bugs':

      #NIM100965 GLOCK files in arcgisserverconfig-storelock folder become frozen when stop/start a service from admin with 0 minimum instances and refreshing the wsdl site

      #NIM100306 : In ArcGIS Server 10.2.1, service with 'Minimum Instances' parameter set to 0 gets published with errors on a non-Default cluster

      So. that required us to publish all of our services with at least 1 min instance per node. At 1,000 services that means we needed 100-125GB of ram for all the ArcSOC.exe processes running without any future room for growth.

      Approach 2: Double the RAM on the AGS Nodes

      • We added an additional 16GB of RAM to each AGS node (they now have 32GB of RAM) which should host 200-250 arcsoc.exe (which is tight to host all 1,000 services).
      • We published about half of the services (around 500) and started seeing some major stability issues.
        • During our publishing workflow. the clustered file server would crash.
          • This file server hosts the config-store/directories for about 4 different *PRODUCTION* arcgis server sites.
          • It also hosts our citrix users work spaces and about 13TB of raster data.
          • During a crash, it would fail-over to the passive file server and after about 5 minutes the secondary file server would crash.
          • This is considered a major outage!

          The file-server crash was clearly caused by publishing a large amounts of services to this new arcgis server environment. We caused our clustered file servers to crash 3 separate times all during this publishing workflow. We had no choice but to isolate this config-store/directories to an alternate location. We moved it to a small web-server to see if we could simulate the crashes there and continue moving forward. So far it has not crashed that server since.

          During bootups, with the AGS node hosting all the services, the service startup time was consistently between 20 and 25 minutes. We were able to find a start-up timeout setting at each service that was set to 300 seconds (5 minutes) by default. we set that to 1800 seconds (30 minutes) to try and get these machines to start-up properly. What was happening is that all the arcsoc.exe processes would build and build until some point they would all start disappearing.

          In the meantime, we also reviewed the ArcGIS 10.2.2 Issues Addressed List which indicated:

          NIM099289 Performance degradation in ArcGIS Server when the location of the configuration store is set to a network shared location (UNC).

          We asked our Esri contacts for more information regarding this bug fix and basically got this:

          1. 1. The Services Directory
          2. 2. Server Manger
          3. 3. Publishing/restarting services
          4. 4. Desktop
          5. 5. Diagnostics

          Approach 3: Upgrade to 10.2.2 and add 3 more servers

          • We added 3 more servers to the 'site' (all 4CPU, 32GB RAM) and upgraded all to 10.2.2. We actually re-built all the machines from scratch again
          • We threw away our existing 'config-store' and directories since we knew at least 1 file was corrupt. We essentially started from square 1 again.
          • All AGS nodes were installed with a fresh install of 10.2.2 (confirmed that refreshing folders from REST page were much faster).
          • Config-store still hosted on web-server
          • We mapped our config-store to a DFS location so that we could move it around later
          • Published all 1,000 ish services successfully with across 7 separate 'clusters'
          • Changed all isolation back to 'high' for the time being.

          This is the closest we have gotten. At least all services are published. Unfortunately it is not very stable. We continually receive a lot of errors, here is a brief summary:

          Level Message Source Code Process Thread
          SEVERE Instance of the service '<FOLDER>/<SERVICE>.MapServer' crashed. Please see if an error report was generated in 'C:arcgisserverlogsSERVERNAME.DOMAINNAMEerrorreports'. To send an error report to Esri, compose an e-mail to [email protected] and attach the error report file. Server 8252 440 1
          SEVERE The primary site administrator '<PSA NAME>' exceeded the maximum number of failed login attempts allowed by ArcGIS Server and has been locked out of the system. Admin 7123 3720 1
          SEVERE ServiceCatalog failed to process request. AutomationException: 0xc00cee3a - Server 8259 3136 3373
          SEVERE Error while processing catalog request. AutomationException: null Server 7802 3568 17
          SEVERE Failed to return security configuration. Another administrative operation is currently accessing the store. Please try again later. Admin 6618 3812 56
          SEVERE Failed to compute the privilege for the user 'f7h/12VDDd0QS2ZGGBFLFmTCK1pvuUP1ezvgfUMOPgY='. Another administrative operation is currently accessing the store. Please try again later. Admin 6617 3248 1
          SEVERE Unable to instantiate class for xml schema type: CIMDEGeographicFeatureLayer <FOLDER>/<SERVICE>.MapServer 50000 49344 29764
          SEVERE Invalid xml registry file: c:program filesarcgisserverinXmlSupport.dat <FOLDER>/<SERVICE>.MapServer 50001 49344 29764
          SEVERE Unable to instantiate class for xml schema type: CIMGISProject <FOLDER>/<SERVICE>.MapServer 50000 49344 29764
          SEVERE Invalid xml registry file: c:program filesarcgisserverinXmlSupport.dat <FOLDER>/<SERVICE>.MapServer 50001 49344 29764
          SEVERE Unable to instantiate class for xml schema type: CIMDocumentInfo <FOLDER>/<SERVICE>.MapServer 50000 49344 29764
          SEVERE Invalid xml registry file: c:program filesarcgisserverinXmlSupport.dat <FOLDER>/<SERVICE>.MapServer 50001 49344 29764
          SEVERE Failed to initialize server object '<FOLDER>/<SERVICE>': 0x80043007: Server 8003 30832 17
          • Each AGS node makes 1 connection (session) to the file-server containing the config-store/directories
          • During idle times, only 35-55 files are actually open from that session.
          • During bootups (and bulk administrative operations), the file's open jump consistently between 1,000 and 2,000 open files per session
          • The 'system' process on the file server spikes especially during bulk administrative processes.
          • The AGS nodes are consistently in communication with the file server (even when the site is idle). CPU/Memory and Network monitor on that looks like this:

          • AGS nodes look similar. It seems there is a lot of 'chatter' when sitting idle.
          • Requests to a service succeed 90% of the time but 10% of the time we receive HTTP 500 errors:

          Error: Error exporting map

          Code: 500

          We have an existing site with the ArcGIS SOM instance name of 'arcgis'. These 1,000 services are running in that 10.0 site for the past few years. Users have interacted with this using a URL like: http://www.example.com/arcgis/rest/services/ <FOLDER>/<MapService>/MapServer

          We are trying to host all these same services so that users accessing this URL will be un-impacted. If we cannot, we will switch to 1 server in 1 cluster in 1 site (and instead have 7 sites). We will then be re-publishing all our content to individual sites but will have different URL's:

          We would have extensive amount of work to either (or both) communicate all the new URL's to our end users (and update all metadata, products, documentation, and content management systems to point to the new URL's) and/or build URL Re-direct (or URL Re-write) rules for all the legacy services. Neither of two options are ideal, but right now we seem to have exhausted all other options.

          Hopefully this will help other users while they troubleshoot thier arcserver deployment. Any ideas are greatly appreciated with our strategy to make this better. Thanks!


          Custom projection in 10.1

          How to add a custom projection (local coordinate system) to the ArcGIS Server 10.1?

          Used a variant described in the article User Defined Objects . In version 10.0 it worked - GeometryService return the correct result. But now (in version 10.1) the GeometryService returns an error '400': the input data are not geographic coordinate system or a projected coordinate system

          by nicogis

          Problem solved. Tried the proposed version, but the server did not work with the suggested folders. Began to look for an option to specify how these additional folders in the server configuration files, and came across a topic The PEOBJEDITHOME variable does not work on localized versions of ArcGIS 10.1 . Now it works.

          by nicogis

          Great article and gets me really close to being able to define a custom coordinate system for ArcGIS for Server.

          Is there any information as to what needs to be placed in the PEOBJEDITHOME folder? Do i just put in there my custom .prj files?

          In the catalog PEOBJEDITHOME placed files that define parameters of coordinate system, projection or transformation. File name is determined by the parameters that it describes. For example, to describe the projections in this folder place a file PROJCS with rows as follows:

          Each row contains the projection parameters. To determine the geographic coordinate system created file GEOGCS etc.
          Detail described in the article: User defined Objects


          Traditional Geodatabase replication use-cases

          ArcSDE manages the versioning schema of the geodatabase and supports client application access to the appropriate views of the geodatabase. ArcSDE also supports export and import of data from and to the appropriate database tables and maintains the geodatabase scheme defining relationships and dependencies between the various tables.

          ArcSDE provides a variety of data replication options associated with a traditional versioned geodatabase as shown in Figure 5.8.

          • Check-out and synchronization with mobile laptop clients
          • Provisioning and synchronization with ArcGIS Windows Mobile clients
          • Incremental updates to an Enterprise geodatabase publishing database
          • Incremental updates to a file geodatabase publishing environment
          • Corporate production Enterprise geodatabase synchronized with multiple remote office production Enterprise geodatabases
          • Centralized scalable ArcSDE distributed geodatabase architecture sharing a common storage area network
          • Local production geodatabase sharing versions of their data for regional and national operations
          • Global remote operations exchanging versions of their data with regional and corporate management operations

          Mobile operations

          Mobile field operations are a big part of GIS workflows within most organizations.

          • Many mobile operators do not have direct input to the computerized business workflow processes.
          • Often information collected in the field must be entered into the system once the users return to the office.
          • In many cases, there is a staff of editors who enter material from marked-up hardcopy provided by the field operators.

          ArcSDE geodatabase replication support for disconnected editing operations.

          Figure 5.9 shows ArcSDE geodatabase replication support for disconnected desktop SDE geodatabase client editing operations.

          Check-out operations were initially supported with the ArcGIS 8.3 release.

          • ArcGIS editor opens edit session with production geodatabase (creates edit version).
          • Check-out of work area operational layers to desktop SDE geodatabase (e.g., SQL Express).
          • Check-out reference layers to mobile file geodatabase.
          • Complete disconnected field edit operations.
          • Check-in field edits to version on central production geodatabase on return.

          ArcSDE geodatabase replication support for disconnected Workgroup SDE geodatabase editing operations.

          Figure 5.10 shows ArcSDE geodatabase replication support for disconnected Workgroup SDE geodatabase server editing operations.

          Check-out operations were initially supported with the ArcGIS 8.3 release.

          • ArcGIS Editor opens an edit session with the production geodatabase (creates edit version).
          • Check-out of work area operational layers to workgroup SDE geodatabase (e.g., SQL Express).
          • Check-out reference layers to mobile file geodatabase.
          • Deploy for disconnected field edit operations.
          • Multiple editors can check out from workgroup SDE geodatabase for mobile field operations.
          • Reconcile and post field edits in mobile workgroup SDE geodatabase.
          • Check-in field edits to version on central production geodatabase on return.

          Distributed Geodatabase Operations can be used to support disconnected SDE geodatabase clients with incremental synchronization capabilities.

          Production/publication operations

          A versioned production geodatabase performs many functions related to the editing workflows that place processing demands on the server.

          • Default version queries
          • Multiple edit version sessions
          • Reconcile and post operations
          • Data schema table dependencies and relationships to maintain data consistency
          • Geodatabase history archiving
          • General maintenance operations

          For many GIS operations, hundreds of users throughout the organization require access to the production data source, most requiring access to the published DEFAULT version.

          Several reasons an organization may want to use a separate publication geodatabase:

          • More scalable server architecture (distributed database loads).
          • More secure production environment (viewer access limited to a publication data source).
          • Expand data center capacity (publication database can be hosted by cloud vendor).
          • Limit public access to DMZ (publication database can be located in the DMZ).

          Figure 5.11 shows how ArcSDE replication is used to share a version of the Enterprise geodatabase on a separate publication geodatabase.

          • Feature-level check-out to production SDE geodatabase was supported with the ArcGIS 8.3 release.
          • One-way incremental multi-generation checkout to SDE geodatabase was supported with the ArcGIS 9.2 release.
          • One-way incremental multi-generation checkout to file geodatabase was supported with the ArcGIS 9.3 release.

          There are several advantages to using a separate publication geodatabase instance for sharing data to GIS viewers.

          Organizations use one-way geodatabase replication for the following reasons:

          • Improved performance and system scalability.
            • Replicating to a simple feature (DEFAULT) read-only publication database can improve query performance and increase platform capacity.
            • Replicating to a file geodatabase can reduce DBMS processing loads and improve display performance.

            Separating the publication database from the maintenance database improves data security.

            • Limits direct user access to the production geodatabase.
            • Provides web access to a separate copy of the published dataset.
            • Filtered versions of the production geodatabase can be distributed to separate publication instances, based on enhanced security requirements.

            Extract/transform/load operations

            Figure 5.12 shows how ArcSDE geodatabase replication can be used to move data to a different geodatabase schema. Geodatabase transformation is a term used to represent replication to a geodatabase with a different schema.

            The ArcGIS for Desktop Data Interoperability extension is used to create a script to transform data between the two schema.

            Distributed geodatabase operations

            Figure 5.13 shows a distributed geodatabase configuration. ArcGIS Geodata services can be used to establish distributed geodatabase operations for scale-out database architectures.

            Distributed regional office support:

            • Centralized corporate geodatabase represents the parent production database.
            • Versioned replica is provided to establish each regional production database.
            • Regional editors work from their individual production geodatabases.
            • Regional sites reconcile and post their edits before synchronizing with corporate.
            • Regional updates are synchronized with the central parent corporate geodatabase.
            • Corporate reconcile and post corporate and regional updates.
            • Corporate updates are synchronized back to the regional geodatabases.

            Distributed remote ArcGIS editor (disconnected geodatabase editing operations):

            • Version replica provided to ArcGIS editor desktop geodatabase (SQL Express).
            • Reference data layers are replicated to local file geodatabase (one-way geodatabase replication).
            • ArcGIS editor can work in a disconnected mode when mobile.
            • ArcGIS editor synchronizes changes with corporate when connected.

            Geodatabase replication can be used to build and support central data center high-capacity scale-out geodatabase operations:

            • Parent production geodatabase established for regional production data integration.
            • Versioned replica is provided to establish each regional production database.
            • Regional editors' ArcGIS Desktop applications are deployed on centralized remote desktop host.
            • Regional editors work from their individual production geodatabases in the central data center.
            • Regional child production databases reconcile and post their edits before synchronizing with parent geodatabase.
            • Regional updates are synchronized with the parent geodatabase.
            • Corporate editors reconcile and post regional version updates.
            • Corporate updates are synchronized back with regional geodatabases.

            Distributed geodatabase architecture provides a highly scalable computing infrastructure without placing high demands on any single database or server component.

            Enterprise architecture deployment strategies

            Distributed geodatabase replication technology integrates a variety of desktop, mobile, and server solutions into an adaptive geospatial communications environment connecting operations across the enterprise and throughout the community.

            Enterprise GIS operations often include a variety of geodatabase replication functions as shown in Figure 5.14.

            • Local desktop clients with direct access to central maintenance geodatabase and network services.
            • Mobile GIS viewers sometimes connected to central maintenance geodatabase.
            • Remote Citrix clients accessing central Citrix servers for ArcGIS Desktop access to central maintenance data source.
            • One-way incremental replication updates between maintenance and publishing database.
            • ArcGIS Server web applications and services published to GIS viewers.
            • Remote ArcGIS Desktop clients accessing a local data source replicated from a central maintenance geodatabase
            • Local updates are incrementally replicated to central maintenance database
            • Incremental replicated updates from a central maintenance database
            • Highly scalable published web services to a variety of GIS viewers

            ArcGIS Server mapping services can be deployed directly from the data center, or geodatabase replication services can be used to provide incremental updates to ArcGIS Server web services maintained within a private or public cloud hosting infrastructure. The Cloud computing infrastructure provides a new adaptive platform environment for managing high capacity map publishing services.

            Federated architecture deployment strategies

            Database and Web technology standards provide opportunities to better manage and support user access to a rapidly growing volume of geospatial data resources. Federated architectures identified in Figure 5.15 provide better data management, integrating community and national GIS operations. Geodatabase replication services and managed extract, transform, and load (ETL) processes support loosely coupled distributed geodatabase environments.

            Multi-layered data architecture patterns are becoming more common. Solutions include the standard desktop, server, and mobile patterns for each implementation level.

            • Some local municipalities share regional data centers for maintenance and publishing operations.
            • Local municipalities publish maintenance database layers to a distribution database of record for regional sharing.
            • Regional databases are integrated at the national level maintenance geodatabase.
            • National data is replicated to a publishing geodatabase for public web services.
            • Cloud platform can be used for publishing national web services.

            Community deployment strategies

            The ArcGIS Platform is building community relationships that change the way people work. ArcGIS provides a platform for collaboration, sharing, and community analysis that helps us better define and understand the world.

            Technology is changing the way GIS is serving our communities:

            • Online GIS platforms deployed in the cloud enable real-time location analytics and spatial visualization for everyone.
            • Direct spatial query of big data repositories and on-the-fly location analysis are showing relevant, real-time activity visualized on a spatial map display on multiple desktop and mobile devices.
            • Configurable applications deliver a solution framework that is easy to build and maintain for integration, collaboration, and efficient information exchange.
            • Social media streaming and satellite imagery delivered real-time on filtered map displays is changing the way people understand the world.

            GIS imagery data architecture

            Figure 5.17 shows the data source architecture patterns available to manage imagery data. Imagery data sources include aerial photography, elevation data, and satellite imagery.

            Imagery is becoming the most valuable real-time business intelligence. Aerial photographs and satellite images can be collected in real time during a regional emergency and used to evaluate and respond to national disasters in a timely way. The volume of imagery is growing exponentially as technology for data collection and storage is rapidly evolving to leverage these digital information products.

            Imagery can provide valuable information when information products are examined over time. Views of the global ice caps and effects on ground cover can show information for managing climate change. Community development and agriculture changes can benefit from national imagery datasets showing changes in communities and farm products on a global scale.

            An imagery file share is used to store the raw imagery files.

            • Imagery can be stored and delivered when needed, maintaining optimum source quality.
            • Single preprocessed images can be distributed using the ArcGIS for Server image service (without the Image extension).
            • Multiple raw imagery files can be distributed using a mosaic dataset with the ArcGIS for Server Image extension.

            Imagery is a primary resource for visualizing live global assets.

            • The mosaic dataset provides the core functionality to organize and manage your imagery data resources.
            • ArcGIS for Server provides Web client access to imagery data sources through a standard REST API.
            • The mosaic dataset with the Imagery Extension enables on-the-fly processing, including multi-image mosaicking as it is compiled through the ArcGIS for Server image service.
            • An imagery service cache is a collection of preprocessed tiled map images stored at multiple scales for rapid dissemination.
            • Imagery historical archiving provides online access to imagery resources showing change over time. Hardware vendor content-addressable storage (CAS) solutions provide protected long term storage for imagery file repositories.

            What is a mosaic dataset?

            Figure 5.18 shows a mosaic dataset. The mosaic dataset was developed to manage and deploy imagery information products in a time-sensitive workflow environment.

            • A catalog that provides the source of the pixels and footprints of the rasters.
            • A feature class that defines the boundary.
            • A set of mosaicking rules that are used to dynamically mosaic the rasters.
            • A set of properties used to control the mosaicking and any image extraction.
            • A table for logging during data loading and other operations.
            • Optionally, a seam line feature class for seam line mosaicking.
            • Optionally, a color correction table that defines the color mapping for each raster in the raster catalog.

            ArcGIS image access patterns

            Figure 5.19 shows a variety of available ArcGIS imagery deployment patterns. Imagery deployment patterns include ArcGIS for Desktop direct access to imagery, ArcGIS for Server image service access to single preprocessed imagery raster datasets, ArcGIS for Server with Image Extension license access to multiple imagery files with on-the-fly processing, and direct access to preprocessed imagery cache tiles.

            ArcGIS for Desktop direct access to imagery

            ArcGIS for Desktop provides direct access to imagery resources. ArcGIS for Desktop is used to create a mosaic dataset and perform imagery analysis. Mosaic dataset can be used as a common search engine for organizing and accessing local imagery resources. Creating, editing, or working with imagery is a core ArcGIS for Desktop capability and does not require an ArcGIS Image extension.

            ArcGIS for Server image service access to imagery

            ArcGIS for Server capabilities include Image Service access to pre-processed imagery. Imagery must be preprocessed and mosaicked as a raster dataset for direct access by ArcGIS for Server Image Service (without the Image Extension). An imagery raster dataset (providing single image access) can be stored in a file system or loaded into a geodatabase.

            ArcGIS for Server Image Extension access to imagery

            The ArcGIS for Server Image Extension enables Image Service access to multiple imagery files. The ArcGIS Image Extension is a license added to ArcGIS for Server, which extends the capability of serving raster data. Specifically, it allows you to use the mosaic dataset and on-the-fly imagery processing through the ArcGIS for Server Image service.

            The ArcGIS for Server Image Extension gives you the ability to:

            • Put your valuable imagery to use quickly.
            • Serve collections of imagery or lidar data as image services.
            • Dynamically create and serve mosaics from the original imagery, without the need to pre-compute the mosaics.
            • Serve multiple views using the original imagery.
            • Access the catalogs of imagery that make up the mosaic dataset.
            • Exploit overlapping imagery, perform on-the-fly image processing, and explore temporal changes, using the advanced image-serving capabilities of this extension.

            ArcGIS Imagery cache tiles

            ArcGIS for Server provides direct access to preprocessed imagery cache. The image service cache is a preprocessed pyramid of imagery tiles configured at a range of scales. [Image service caching] improves the performance of image services in client applications. When accessing cached imagery using the enable cache view mode, the preprocessed cached tiles are sent to the client without future processing.

            When you add an imagery cache with an image service, you end up with a dual-purpose image service that is accessed depending on its purpose. One purpose is to provide the fastest access to the image as a tiled service. The other purpose is to provide access through the mosaic dataset to the imagery repository, for queries, downloading, access to individual items, and to use in processing and analysis. Both options are available through a single image service starting with the ArcGIS 10.1 release.

            Specific benefits of a cached image service include:

            • Improved performance for basemap images.
            • Skips overview generation.
            • Improved performance for slow formats.

            Imagery deployment workflow

            Figure 5.20 shows the optimum imagery service configuration for optimum web delivery.

            Recommended image caching workflow:

            • Create mosaic dataset.
            • Serve image services to key users (dynamic).
            • Create map cache for larger web community.
            • Maintain mosaic dataset.
            • Update cache.
            • Provides static background image.
            • Delivered as tiles for web caching.
            • Most scalable web delivery.
            • Created and served using mosaic dataset with ArcGIS for Server.
            • Preprocessing and on-demand caching options.

            CPT Platform Capacity Calculator custom imagery services

            The CPT Platform Capacity Calculator can be used to demonstrate variation in Image service performance due to the selected data source format.

            CPT Platform Capacity Calculator can be configured to show performance of the seven (7) available Imagery data source formats.


            Article ID:41119
            Bug Id:NIM090672
            Software: ArcGIS - ArcEditor 9.3.1, 10 ArcGIS - ArcInfo 9.3.1, 10 ArcGIS - ArcView 9.3.1, 10 ArcGIS for Desktop Advanced10.1 ArcGIS for Desktop Standard 10.1 ArcGIS for Desktop Basic 10.1
            Platforms: Windows Windows 7, Server 2008 R2

            Description

            A recent Microsoft update (deployed as KB 2732673, KB 2775511, or KB 2824408) may result in data corruption when using ArcGIS on a Windows 7 system and writing data to remote data storage on a Windows Vista, Windows 7, or a Windows Server 2008/2008 R2 or 2012 system. This data corruption appears as truncation of a write request and has shown up in file geodatabases and shapefiles.

            Additional Information

            An error message referencing the ItemType appears when creating new datasets or items (tables, feature classes, feature datasets, raster datasets, and so forth) in a 10.x file geodatabase created on a network share.

            For example, the following message is displayed when creating a new feature class:

            "Failed to create feature class.
            The item was not found. [ItemType:
            <70737809-852C-4A03-9E22-2CECEA5B9BFA>]"

            File geodatabases created with ArcGIS 9.3.1 return the following error when creating new datasets or items, renaming the file geodatabase, or accessing the geodatabase properties.

            "Failed to connect to database.
            This release of the Geodatabase is either invalid or out of data. [Invalid Geodatabase release]"

            Cause

            Microsoft has acknowledged the problem, identified the affected component as RDBSS.sys, and provided further details in this Windows SDK Support Team Blog.

            Esri and Microsoft are working closely to understand what has changed in the RDBSS.sys component and how to resolve the problem.

            How Microsoft made these updates available

            KB 2732673 and KB 2824408 are hotfixes to address specific issues. The KB 2775511 update is a cumulative update that is available exclusively through the Windows Update Catalog.

            Because this update is available only through the Windows Update Catalog, the KB 2775511 update is not considered a security update by Microsoft and is not being deployed broadly.

            Workaround

            • If the patches listed above have not yet been installed, do not install them, per Microsoft's recommendation.
            • If the patches listed above have been installed, Microsoft recommends uninstalling them until a solution is found.
            • Create the file geodatabase or shapefile locally before copying it to the network share. Feature classes can then be created in the file geodatabase on the network share. Note that this is not applicable for raster datasets, attempting to create a raster dataset in the file geodatabase fails on the network share.
            • Create and work with file geodatabases locally.


            Common software upgrade questions

            This section addresses common questions about the upgrade behavior of ArcGIS Server 10.9 . Before upgrading, carefully review the following information:

            Can I upgrade directly to ArcGIS Server 10.9 ?

            Yes however, the minimum version requirement to do so is 10.3 and later. For example, if you have version 10.5.1 installed, running the 10.9 setup will automatically upgrade it to 10.9 . There is no need to obtain and install each released version to upgrade to 10.9 .

            Do I need to reauthorize when upgrading to 10.9 ?

            If you are upgrading to 10.9 , you need to reauthorize your software with a new authorization file for 10.9 . You can access your new authorization files in My Esri .

            Do I need to uninstall an earlier version of ArcGIS Server before installing ArcGIS Server 10.9 ?

            No. If you have an earlier version of ArcGIS Server installed (10.3 or later), the setup will automatically upgrade it to ArcGIS Server 10.9 without additional configuration. Additionally, you can install ArcGIS Server 10.9 on its own without having an earlier version of the software installed on your machine.

            Do the ArcGIS Web Adaptor and ArcGIS Server product versions need to be in sync?

            Yes. You cannot configure an earlier version of ArcGIS Web Adaptor to work with an ArcGIS Server 10.9 site. The Web Adaptor version must always match the version of the ArcGIS Server site. You'll need to install ArcGIS 10.9 Web Adaptor at the same time you upgrade your ArcGIS Server machines.

            What is the order for upgrading my ArcGIS Enterprise deployment to 10.9 ?

            1. Portal for ArcGIS
            2. ArcGIS Web Adaptor (for Portal for ArcGIS )
            3. ArcGIS Server
            4. ArcGIS Web Adaptor (for ArcGIS Server )
            5. ArcGIS Data Store (If you have configured one or more highly available data stores, upgrade the primary machines first, followed by any stand-by machines.)

            Do I need to back up anything before installing ArcGIS Server 10.9 ?

            All of your services, site information, and security settings are preserved when upgrading to ArcGIS Server . However, it's recommended that you back up your data before installing the software.

            If the server you're upgrading is connected to an Active Directory deployment that includes multiple domain controllers, but not all domain controllers are configured as global catalog servers, you'll need to manually specify the domain controller used by ArcGIS Server after performing the installation. For full instructions, see Configure the domain controller used by ArcGIS Server .

            If I've federated my server with a portal, do I need to upgrade Portal for ArcGIS when I upgrade the server?

            For your portal deployment to function correctly, your hosting server and Portal for ArcGIS versions need to be the same. However, as of 10.5.1 , you can federate a server from an earlier version with a portal of a later version as long as it is not set as a hosting server, a GeoAnalytics Server, a raster analysis server, or an image hosting server. If the ArcGIS Server site you've federated with Portal for ArcGIS includes multiple machines, upgrade your ArcGIS Server machines sequentially. If you have ArcGIS Web Adaptor (single or multiple) configured with your ArcGIS Server site, you also need to update the web adaptors to the same version as ArcGIS Server .

            If I've federated my server with a portal, should I unfederate before upgrading?

            No. It's recommended that you do not unfederate when you upgrade your portal deployment. Doing so will adversely impact your portal deployment. For example, when you unfederate, all hosted service items remain in the portal, but they are disconnected from their services in ArcGIS Server . This means that members will not be able to access, share, or use these services in the portal. Additionally, any existing ArcGIS Server services that were imported during the federation process are removed from the portal and are no longer available.

            Do I need to stop my GIS services and ArcGIS Server before installing ArcGIS Server 10.9 ?

            If you have not already stopped ArcGIS Server , the setup will do it for you at the appropriate point in the installation.

            In a multiple-machine site, can some of my ArcGIS Server machines run 10.9 and others run an earlier version?

            No. For your site to function correctly, all ArcGIS Server machines must be at the same update version. You can upgrade your ArcGIS Server machines at the same time or sequentially. If you have ArcGIS Web Adaptor configured with your ArcGIS Server site, you also need to update the web adaptor to the same update version.

            When upgrading, what password do I designate for the ArcGIS Server account?

            When you begin the 10.9 set up, a panel appears requesting the user name and password of the ArcGIS Server account. This is the account you defined when installing the software. If the account has changed since you installed the earlier version, for example, by using the configure ArcGIS Server account utility, you'll need to enter the user name and password you designated when modifying the account.

            I can't log in to Server Manager after installing ArcGIS Server 10.9 . What do I do?

            If you are experiencing issues logging in to Server Manager after installing the latest software update, you may need to clear your browser's cache to log in. This is typically due to residual information from the previous version of Server Manager being cached in the browser. Before clearing your browser's cache, make sure you are attempting to log in with an account that has administrative privileges to your site.

            I don't see new features in Server Manager after upgrading to ArcGIS Server 10.9 . What's going on?

            If you notice that new features in Server Manager are not displaying in your browser after upgrading to 10.9 , clear your browser's cache. Once you clear the cache, you'll see new features in Server Manager .

            What else do I need to consider before upgrading ArcGIS Server ?

            • Before you upgrade your ArcGIS Server site, ensure that any databases you use are supported at the upgraded ArcGIS Server release. See the following relevant relational database management systems requirements for details:

            If you configured an enterprise geodatabase as the managed database for your hosting server and you are upgrading to 10.9 , you need to conduct a few additional steps. Once you've upgraded ArcGIS Server , register the enterprise geodatabase as a database (as opposed to a managed database). Next, install ArcGIS Data Store and configure a relational data store for the hosting server.


            Working with feature data

            Summary This section in the ArcObjects .NET software development kit (SDK) Help system contains topics about working with feature- and row-based datasets such as, feature classes and tables, as well as general geodatabase functionality.

            A geodatabase is a repository of geographic data built on industry standard relational database management systems (RDBMS). Geodatabases work across a range of database management system (DBMS) architectures, and file systems come in many sizes and have varying numbers of users. They can scale from small single-user databases built on files up to larger workgroups, departments, and enterprise geodatabases accessed by many users.

            The geodatabase library provides the application programming interface (API) for the geodatabase. The objects in the library provide a unified programming model for all supported data sources in ArcGIS, including remote geodatabases, local geodatabases, and file-based data sources. This library defines many of the classes and interfaces used higher in the architecture.

            Some topics focus on data sources other than the geodatabase, for example, computer-aided design (CAD) datasets and shapefiles. Although there are important differences to be aware of when developing against these data sources, there are many similarities and common workflows between these and the geodatabase.

            This topic highlights on the core elements of the geodatabase that an application developer should understand to effectively utilize the geodatabase API. It also contains brief overviews of programming with complex datasets and geodatabase customization. Because this is an overview topic, linked references to more detailed ArcGIS Desktop Help topics, step-by-step programming topics, and complete code examples can be found under each section in this topic.


            Watch the video: Convert shapefile to Geodatabase in ArcGis (October 2021).