Latest Contributions by WilliamCraft

Please go to the following directory on your ArcGIS for Server machine... ...\arcgisserver\config-store\security\ and provide the contents of the security-config.json and toke-config.json files.  I'm curious to see the security values that exist in those files at this point in time. Secondly, go to ...arcgisserver\config-store\web-adaptors\ and review your <servername>.json file in a text editor to see if the info inside it looks correct for your machine.  Third, I imagine that you have tried disabling any antivirus software on your machine already.  I know you said you turned off the firewall (I think this might be the Windows firewall), but just to cover your bases I would recommend making sure that any third-party anti-virus software is turned off in case it contains firewall components as well.  Lastly, it sounds like you have the permissions covered as far as the AGS config store and directories go.  But I think we discussed a domain account earlier in this thread; now I'm wondering, are you using that same domain account as the run-as account for the ArcGIS for Server Windows Service? ... View more

How are you enabling the database to become a geodatabase?  In other words, what is your workflow and which tool are you using to attempt this?  Here are the 10.1 instructions for enabling a geodatabase within SQL Server Express:  http://resources.arcgis.com/en/help/main/10.1/index.html#//018t0000000w000000 Since you are using SQL Server Express and since you indicated it is already installed, I believe the process is to create a Database Server connection via ArcCatalog (not the traditional 'Create Database Connection' option like you would for a SQL Server Std or Enterprise database). ... View more

There are a number of bugs that Esri reports which address similar behavior, but since you are at 10.2.1 I'm thinking this is a different issue entirely.  What does Fiddler show when you request that URL? ... View more

Try putting the ags domain account into the servers administrators group. ... View more

Does the script run without issue if launched as a stand-alone script rather than through a service? ... View more

When synchronizing the two replicas, are you reconciling in favor of geodatabase 1 or geodatabase 2? ... View more

Does the server have enough disk space for the specified export and/or import directory in order to accommodate the output? Is the directory of the file geodatabase specified as a network share or a mapped drive letter to a networked location?  In other words, from your local PC are you specifying a network share location or drive letter to a mapped network shared location which points to the server? ... View more

Do you have a 32-bit OS or a 64-bit OS?  I seem to recall a file size limit where corruption eventually occurs on a 32-bit system.  How large is the final output once the process completes? ... View more

I have to ask a very simple (and obvious) question: did you clear your browser cache in Chrome and then close/re-open your browser? ... View more

Can you try requesting the ArcGIS Server Manager URL from a different machine rather than from the server directly?  In other words, replace 'localhost' with your server name and then request it from your PC. ... View more

If all the databases exist within the same SQL Server instance, it is possible to execute cross-database queries if you fully qualify all of your tables within the SQL. ... View more

Two things I would do at this point in time to see if it resolves your issue: 1. Check the grid sizes on your spatial index of the feature class you are importing in SDE.  Are they all zeros or have they been automatically set by ArcSDE?  Try recalculating the spatial index via ArcCatalog, but you need to be connected as the data owner to do so.  The grid sizes may or may not change when you do this.  If they do change, try drawing the feature class again to validate performance.  If they do not change, manually change them to 1000,0,0 and re-check performance.  Another combination to try is 1000,3000,0 or 1000,3000,9000.  If none of these options work, reset the spatial index back to what it was or let ArcGIS calculate it again.  2.  Identify all of the attribute indexes for your base table (the polygon feature class table in SQL Server), the D table (deletes table), and the A table (adds table).  You can find out which A and D tables correspond to your base table by using a modified version of this query (written for oracle, but can be modified slightly for SQL Server): select substr(l.TABLE_NAME,1,30) table_name, substr('F'||layer_id,1,10) feature_table, substr('S'||layer_id,1,10) spatial_table, substr('A'||registration_id,1,10) adds_table, substr('D'||registration_id,1,10) deletes_table, substr(l.OWNER,1,12) owner from     sde.layers l, sde.table_registry r where    l.owner NOT IN ('SDE', 'SYS') and      l.table_name = r.table_name (+) and      l.owner      = r.owner (+) order by owner, table_name Once you identify the A and D tables, go into SQL Server Management Studio and manually rebuild the ATTRIBUTE indexes for the base, A, and D tables and then re-check performance. Lastly, the truncate operation error you are seeing about the data owner being required means that you need to connect to the geodatabase's Edit version as a data owner to perform the truncate.  You won't be able to do this on the Default version nor would you want to.  Have a look at this article to read more about the geodatabase owners: http://resources.arcgis.com/en/help/main/10.2/index.html#//002q00000004000000 ... View more

Hello:Also when setting up a connection file to use with Enable Enterprise Geodatabase tool is it best to use sa or sde for username? I can't answer your first question regarding the script, but the answer to your second question about the user account is to use the SDE user.  Do not use the 'sa' account for things like this; it's just bad practice since the account is too powerful.  The Create Enterprise Geodatabase tool will actually create the SDE user if you pick the SDE_SCHEMA (which you said you are doing), so use that same SDE user when running the Enable Enterprise Geodatabase tool. ... View more

Which version of ArcGIS Desktop and ArcSDE are you using?  Which version of SQL Server are you using?  Some quick online searching reveals that this error occurs when more than one record is returned from a query while only one is expected.  It is difficult to know which table is actually producing this behavior without tracing the queries at the RDBMS level or performing an SDEINTERCEPT and/or an SDETRACE depending on how you are connecting to your geodatabase.  It sounds to me like there could be an issue with your geodatabase's state lineage.  Have you performed a compress recently?  Have you tried running an SDEGDBREPAIR -o diagnose_metadata as well as an SDEGDBREPAIR -o diagnose_tables?  Replacing the word "diagnose" with "repair" (after referencing the SDEGDBREPAIR online help) will resolve the issues presented from the diagnosis.  This is just a possibility; I can't be sure about this as the cause for the error.  You may need to contact Esri Support for this one. ... View more

From your description, I'm not entirely clear if the performance issues you are experiencing are with the draw time of the feature class within ArcGIS or with the process of deleting and inserting of records.  Perhaps it is both workflows that are yielding slow behavior.  Two quick questions come to mind right away: Is the performance of your non-SDE source data the same, better, or worse than that of the SDE data you are describing?  In thinking about the complexity of your polygon features, do they have millions of vertices or only a few per polygon? You might see better performance with the following sequential steps: 1. TRUNCATE When connected to your Edit version (which is assumed to be a child version of Default), use the Truncate GP tool to wipe out the records from your polygon feature class.  It sounds like you need to clean it out entirely, but correct me if I'm wrong here.  Truncate works much more efficiently than a delete operation, but doing this will immediately commit your transaction in the RDBMS without the ability to roll back.  2. LOAD You can use the Simple Data Loader tool in ArcCatalog or the Load Objects tool in ArcMap to insert the records from your non-SDE source into your target geodatabase.  Make sure you're connected to your Edit version when doing this.  3. RECONCILE / POST Since you loaded data into the Edit version, those changes need to be "moved" into the Default version using the reconcile and post tools within ArcGIS Desktop.  4. COMPRESS You mentioned a compress earlier, and you are correct in that thought process.  After reconcile and post, compress your geodatabase as while connected to your Default version as the SDE user in order to move your adds and deletes to the base table.  5. RDBMS MAINTENANCE TASKS As you eluded to earlier, performing other RDBMS-related maintenance tasks can help to increase performance.  These include analyzing tables and indexes as well as rebuilding indexes.  There are many, many other types of database maintenance tasks that can help increase performance and are described online on a variety of sites.  On a related note, I personally do not recommend deleting a feature class and then importing data in order to create a new one... especially if the data you're working with is intended to be versioned.  If the data does not need to be versioned, then it is less of a challenge to do this.  (Permissions have been the main concern in that specific case, although this might be automatically handled in newer ArcGIS software if the data resides in a feature dataset.)  If the data needs to be versioned, then each time you delete the old feature class and add a new one via Import you will need to re-register it as versioned as you discussed already.  It is possible that your performance issues are related to other problems and have nothing to do with the methods you're using to delete and insert new data.  Therefore, if the above workflow doesn't help you I would recommend taking a look at your database server's memory, disk I/O stats, and CPU.  It could be data-related.  Otherwise, it could be network-related.  Performance issues are tough to troubleshoot, especially via a forum post.  It really could be just about anything that is causing the slow behavior. ... View more