https://community.esri.com/t5/arcgis-enterprise-ideas/enhanced-validation-for-high-availability-ha/idi-p/1662150 <P>The current Server Manager validation process provides limited utility when multiple machines are involved. I propose the following enhancements:</P><UL><LI><STRONG>Parallel and Incremental Validation:</STRONG><BR />The Validate All function should not wait for every validation task to complete before returning results.<BR />Instead, it should display results from completed validations immediately, while allowing ongoing tasks to continue in the background.</LI><LI><STRONG>Adaptive Timeout for Datastores:</STRONG><BR />Introduce shorter timeouts for datastores that take an extended period to respond.<BR />This prevents indefinite waiting periods without visibility into which datastores are responsive and which are still pending validation.</LI><LI><STRONG>Improved Datastore Management:</STRONG><BR />Datastores that have not been validated cannot currently be removed in Server Manager (only via the Admin directory). This should be fixed.</LI><LI><STRONG>Clearer Error Attribution:</STRONG><BR />In configurations with a Primary and Standby Relational Datastore, validation failures do not indicate which machine caused the issue.<BR />The Server Manager should list all individual datastores (Primary, Secondary, and Cluster) with their respective validation states.</LI><LI><STRONG>Enhanced Logging and Error Messaging:</STRONG><BR />Implement more descriptive error messages and logging. For instance, the error</LI></UL><P><EM>“ERROR: function sde.get_rowid(character varying, character varying, integer) does not exist </EM></P><P><EM>Hint: No function matches the given name and argument types. You might need to add explicit type casts. Position: 15<BR />appears in the Portal Map Viewer when editing feature services connected to an invalid or partially upgraded datastore.<BR />Such errors should explicitly indicate that a datastore issue may be the root cause.<BR /></EM>(Note: This issue also occurs for registered (e.g. Oracle) databases and should be investigated further.)</P><UL><LI><STRONG>Improved Datastore Validation Checks:</STRONG><BR />The describedatastore operation should verify datastore validity more thoroughly.<BR />Currently, both describedatastore and validate datastore in Server Manager may return positive results,<BR />even when the actual machine-level validation (as viewed under server/admin/data/datastoretype/.../machines) indicates problems.</LI></UL> Thu, 30 Oct 2025 12:15:09 GMT SimonSchütte_ct 2025-10-30T12:15:09Z https://community.esri.com/t5/arcgis-enterprise-ideas/enhanced-validation-for-high-availability-ha/idi-p/1662150 <P>The current Server Manager validation process provides limited utility when multiple machines are involved. I propose the following enhancements:</P><UL><LI><STRONG>Parallel and Incremental Validation:</STRONG><BR />The Validate All function should not wait for every validation task to complete before returning results.<BR />Instead, it should display results from completed validations immediately, while allowing ongoing tasks to continue in the background.</LI><LI><STRONG>Adaptive Timeout for Datastores:</STRONG><BR />Introduce shorter timeouts for datastores that take an extended period to respond.<BR />This prevents indefinite waiting periods without visibility into which datastores are responsive and which are still pending validation.</LI><LI><STRONG>Improved Datastore Management:</STRONG><BR />Datastores that have not been validated cannot currently be removed in Server Manager (only via the Admin directory). This should be fixed.</LI><LI><STRONG>Clearer Error Attribution:</STRONG><BR />In configurations with a Primary and Standby Relational Datastore, validation failures do not indicate which machine caused the issue.<BR />The Server Manager should list all individual datastores (Primary, Secondary, and Cluster) with their respective validation states.</LI><LI><STRONG>Enhanced Logging and Error Messaging:</STRONG><BR />Implement more descriptive error messages and logging. For instance, the error</LI></UL><P><EM>“ERROR: function sde.get_rowid(character varying, character varying, integer) does not exist </EM></P><P><EM>Hint: No function matches the given name and argument types. You might need to add explicit type casts. Position: 15<BR />appears in the Portal Map Viewer when editing feature services connected to an invalid or partially upgraded datastore.<BR />Such errors should explicitly indicate that a datastore issue may be the root cause.<BR /></EM>(Note: This issue also occurs for registered (e.g. Oracle) databases and should be investigated further.)</P><UL><LI><STRONG>Improved Datastore Validation Checks:</STRONG><BR />The describedatastore operation should verify datastore validity more thoroughly.<BR />Currently, both describedatastore and validate datastore in Server Manager may return positive results,<BR />even when the actual machine-level validation (as viewed under server/admin/data/datastoretype/.../machines) indicates problems.</LI></UL> Thu, 30 Oct 2025 12:15:09 GMT https://community.esri.com/t5/arcgis-enterprise-ideas/enhanced-validation-for-high-availability-ha/idi-p/1662150 SimonSchütte_ct 2025-10-30T12:15:09Z https://community.esri.com/t5/arcgis-enterprise-ideas/enhanced-validation-for-high-availability-ha/idc-p/1708922#M4648 <P>100% agree on all of these!</P> Thu, 18 Jun 2026 18:18:48 GMT https://community.esri.com/t5/arcgis-enterprise-ideas/enhanced-validation-for-high-availability-ha/idc-p/1708922#M4648 AH2 2026-06-18T18:18:48Z