Latest Contributions by TinaMorgan1

George,  I am so sorry I overlooked this post back in November! My understanding of the crash pop up is that it does go to an Esri development team for review, but unfortunately I do not have much more insight on it than that.  I will see what I can find out.   This article, though, is more specifically when the user who sees a crash wishes to contact Esri Support for investigation of those issues.  It is common that users ask us "Why all of the questions", so this was in hopes going to clarify why.   If you listened to Car Talk, it's the same scenario.  Someone calls in with a description of an issue.  Ray and (the late) Tom would then have to ask clarifying questions like "do you hear the rattle when the air conditioning is on?  Now is it a rattle or a screeching sound or both?  What year is your car?", because they understand the mechanics used to run an air conditioner.  Your answers help them give effective advice like "since this is an older car, and it only happens when the AC is on, and it is a rattle with a screeching sound I'd say check your Serpentine belt.".  As mentioned, a crash is a bug in our eyes.  We do not want that to happen.  I encourage you to call support to report the crash if it is still happening. ... View more

Hello, I see this is an older post, but just wanted to check if you were able to call Esri Support and find a resolution to this issue?    If you were able to get around the issue (either with or without support), do you have the details that helped you move forward? Sincerely, TM ... View more

I like my hash-browns warm and crispy!  I always say keep it simple.  If you don't need anything more than what a check out replica provides, then don't complicate it.  I like where you're going! Let us know if you have any specific questions or issues.   ... View more

so Check Out replicas are simple.  You create your check out replica to a file geodatabase, and then you can send that file geodatabase to remote locations, like a field worker's mobile device off the network.  Again you can use your favorite, supported method to get the file geodatabase into that environment (email, hard drive, ftp, etc).  Once the end user has the file geodatabase they will do their edits, then send it back to the parent server where it can be synchronized.  Check out replicas only persist for the one sync so there is no need to keep up maintenance on them like you would one and two way replicas.   ... View more

Being a little nitpicky here, a replica is a replica regardless of the connectivity between the parent and child.  The environment the replica is in can be 'connected' or 'disconnected', and that environment will then dictate the methods we can choose from to create and synchronize the replica.   To provide more info to your question, you have two options to create a replica where the parent and child geodatabases are in disconnected environments. 1.  You may use Create Replica command from the toolbar in ArcMap.  This method gives you the option to create an XML document local to the parent server.  You can then use your own methods to send that XML file to the child server (like email, ftp or hard drives).      The Create Replica wizard—ArcGIS Help | ArcGIS Desktop  2.  You may use the Create Replica from Server to replicate data from a remote geodatabase using a geodata service published on ArcGIS Server.     Create Replica From Server—Help | ArcGIS Desktop  ... View more

What is the underlying database, and what is the error? ... View more

Have you taken an Oracle level 12 trace?  This can help us see exactly what calls are being sent to and from the database when the failure occurs.   After you see the failure, do you see ANY data that was imported?   How many shapefiles are being imported?  If it is more than one, can you add a print statement in your code so you can monitor which files the code is able to parse through? Here is the python for Feature Class to Feature class (conversion tools) import arcpy arcpy.env.workspace = "C:/data/GreenvalleyDB.mdb/Public Buildings" arcpy.FeatureClassToFeatureClass_conversion("buildings_point", "C:/output/output.gdb", "buildings_point") Feature Class To Feature Class—Help | ArcGIS for Desktop  ... View more

Feature services published to ArcGIS Server require that all layers and stand-alone tables in the map reference a single enterprise geodatabase or enterprise database. WFS-T services require that all layers and stand-alone tables in the map reference a single enterprise geodatabase using the same database connection. The enterprise geodatabase or database must be registered with the ArcGIS server. Editable image services also require a registered enterprise geodatabase. 00134: Layer's data source is not supported—Documentation | ArcGIS Enterprise  ... View more

Hi Francis, First of all, what is the error you are getting when running this script? A troubleshooting tip would be to add a print statement after the MakeFeatureLayer line.  Seeing the print statement "MakeFeatureLayer complete" ensures us that the layer is successfully being created, and that the failure is definitely occurring during ChangeVersion statement. Just from reviewing the syntax provided: The ChangeVersion_Management syntax actually has 4 parameters.  Also, don't forget single quotes, and fully qualified names: ChangeVersion_management (in_features, version_type, {version_name}, {date}) arcpy.ChangeVersion_management('_mon_feature_layer','TRANSACTIONAL', '<schema>._ma_version_cible','') ... View more

Always take backups before using SQL in the repository.  We prefer this be done in test environments first, and always thoroughly test normal workflows after the SQL update. This workflow, however, is relatively straight forward, and I have not seen any cascading effects due to deleting replica sync versions that I have confirmed (doubly if necessary) are orphaned. If you have already unregistered the replica, then it is assumed you have already synchronized that replica, and done the appropriate maintenance to get your edits into the version you want them in (ultimately default then to base table with a compress).  If you still see your SYNC_SEND... versions in the sde_versions table after unregistering the replica, then those version could potentially block edits from being pushed through, will minimize how effective your compress will be, and over time will slow down your system.   ... View more

SQL Server:  Find orphaned sync send versions.  This will return any sync send versions that do not have a corresponding replica -  sync version # corresponds to GDB_ITEMS.ObjectID   select name from sde.sde_versions where name not in ( select v.name from sde.gdb_items g join sde.sde_versions v on g.objectid = Left(SubString(v.name, PatIndex('%[0-9.-]%', v.name), 10) , PatIndex('%[^0-9.-]%', SubString(v.name, PatIndex('%[0-9.-]%', v.name), 10) + 'X')-1) where g.type = '{4ED4A58E-621F-4043-95ED-850FBA45FCBC}') and name like 'SYNC%'; This will return all sde_version records that do not have an associated replica type in the gdb_items table.   ... View more

I like a challenge!  999999 basically says to me that a call was made to or from the client, but the client does not know how to handle this call.  If you are using an RDBMS as your database/geodatabase then 9 times out of 10 I find the answer in the RDBMS trace file.   999999: Error executing function.—Help | ArcGIS Desktop  Tips on taking a trace to troubleshoot client issues: 1.  Document EACH CLICK from opening the Arc product until the error.  Know what clicks are necessary and what clicks are not necessary.  For example, if part of the workflow is to add data to ArcMap, and if the symbols are not part of the issue, do not take the time to symbolize this data.   Write your clicks down! 2.  Close all Esri application on the desktop where you receive the error. 3.  Set up your trace to capture detailed info (choose proper events in SQL Server, use level 12 in Oracle, etc)...do not start the trace yet.  This may take coordination with a dba. 4.  Set up the sdeintercept on the desktop where you receive the error. 5.  Start your dbms trace (I like session based traces, or logon triggers in Oracle).  The intercept will trigger to be created as soon as you make a connection to your enterprise database from the Arc application. 6.  Follow your documented workflow exactly.  See the error.  Document the time down to the second.  Stop your trace and close all Arc applications.  Harvest your trace and intercept files. This gives us a database trace that tells us all the calls the database sends and receives, and a client intercept that tells us all the calls the client sends and receives.  With the timestamp and the clicks of the workflow we can seriously get some information here! ... View more

Please report crashes to Esri Support.  We treat those as bugs as we would like the software to tell you something meaningful when it encounters issues, rather than just shutting down because it doesn't know how to handle some call. We will want the following: 1.  Files:  crash error report, any applicable log files, RDBMS traces and sdeintercept if applicable. 2.  Exact workflow: start from "1.  Open ArcMap <version>, 2.  Add data from location <my complete location to the data>" 3.  Configuration information:  ArcDesktop version (including any patches and/or service packs),  operating system details. 4.  Data information:  Is there data in the map?  Where is it coming from?  5.  Patterns:  Does this happen for all users (run ArcMap as a different user to test)?, Does this happen for all desktop machines?  Does this happen for all data (create blank maps and add different datasets to test, use simple versus complex data if you think this could be part of the issue) WHY ALL THE QUESTIONS?   1 and 2 are pertinent to understand the issue and test in house.  Traces and logs can tell us exactly what is happening in the back end.   3 is the first layer of troubleshooting "does this crash occur in an Esri supported and certified environment?" 4, as a database person, this one helps me understand more about the structure of the data and how the client deals with it.   5 helps us understand if the crash is occurring due to some corruption to a user's profile, possible other software/hardware on a particular machine that the client takes issue with, or if specific data types may be causing the crash.  ... View more

You may need to take advantage of Asruji's suggestion and get the dba to create you a new view where they join the fields needed from the feature class to the database table.  You may then use that view alone in ArcMap. You have: 1.  A feature class (from the dba's perspective it is a table with a spatial column) 2.  An Oracle table not registered with the geodatabase (I understand you are accessing this table as a view already) What you need: Request from the dba to create a new view directly on the feature class and the database table.  We can do away with the view of that lone table.  This new view will look something like this... CREATE VIEW test_vw AS SELECT f.OBJECTID, t.TableColumn1,t.TableColumn2, f.SHAPE FROM MYFC f JOIN MYDBTABLE t ON f.OBJECTID = t.MYID; As asrujit_pb‌ said, if MyFC is registered as versioned your DBA will simply change the MyFC syntax to show the MyFC_evw (<-always double check that name in the feature class properties via ArcCatalog) This will give you a new view that already does the joining for you.  You only need to add this view as a query layer and can directly symbolize.  If you do not want to work with the query layer you can choose to register the view with the geodatabase (using your ArcDesktop 10.5.1) for a more seamless geodatabase experience with the view. ... View more

This all has just recently happened in the last few weeks.  In an effort to keep up with users who don't just use one technology anymore...it is the whole Enterprise now- enterprise geodatabase data/native database data published via ArcDesktop/ArcGIS Pro as services through ArcGIS Server consumed in Portal or AGOL.  We still have folks with deep specialties though  ... View more