Enable Network Topology
=====================
Parameters
Input Utility Network C:\Users\ycamacho\OneDrive - Geotecnologias S.A\Documentos\ArcGIS\Projects\Prueba\SQLServer-crgis36-pruebas_trelec(utility).sde\pruebas_trelec.UTILITY.Electric\pruebas_trelec.UTILITY.UtilityNetworkEPM
Maximum number of errors 10000
Only generate errors ENABLE_TOPO
Updated Utility Network C:\Users\ycamacho\OneDrive - Geotecnologias S.A\Documentos\ArcGIS\Projects\Prueba\SQLServer-crgis36-pruebas_trelec(utility).sde\pruebas_trelec.UTILITY.Electric\pruebas_trelec.UTILITY.UtilityNetworkEPM
=====================
Messages
Hi. Is there a standard solution for this error? I alredy install all the updates for Windows and restart the server
Start Time: jueves, 29 de agosto de 2024 08:35:25
ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds.
FDO error: -2147195905 [Error querying row from table pruebas_trelec.UTILITY.ElectricJunction]
Table schema changed after cursor declared [42000:[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Could not complete cursor operation because the table schema changed after the cursor was declared.] [pruebas_trelec.UTILITY.ElectricJunction][STATE_ID = 0]
Table schema changed after cursor declared [42000:[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Could not complete cursor operation because the table schema changed after the cursor was declared.] [pruebas_trelec.UTILITY.UN_6_DirtyAreas][STATE_ID = 0]
Can you post a snippet from the script you are running? Specifically, everything from where you define the cursor to where you are receiving this error.
When using a cursor you should just be creating it, iterating it, and closing it. If you are doing anything else between creating it and using it (like enabling the topology or running other gp tools) you run the risk of invalidating the cursor like this.
I am not running a script, just trying to enable topology. You think that is some kind of script or process running behind and is causing the error?
I misread your original post. If you get that error when enabling your network topology, you should log an issue with support. Are you using one of the standard utility network foundations? Have you made any alterations to the schema or attribute rules?
Is a personalized Asset Package for a client, it has alterations yeah
If you deploy it to a local geodatabase using the Asset Package to Geodatabase tool, do you receive a similar error?