Latest Contributions by deleted-user-zpcJw1u0IXiO

Thank you Curtis! With your help I did find what I was missing, and it was in %APPDATA%\Esri\Desktop10.3\ArcToolbox as you suggested, because 10.3 was my previous desktop version. So I copy/pasted the content from there into %APPDATA%\Esri\Desktop10.4\ArcToolbox, and then found My Toolboxes fully populated once again. Cheers, Justin ... View more

Thanks Dan. I believe My Toolboxes is pulled from Toolbox.tbx, am I right? And I believe it was stored in H:\My Documents\ArcGIS\, because that's where the empty Toolbox.tbx is now, and it's also the location of Default.gdb which contains feature classes that date from prior to the 10.4 update. So it's puzzling that that content was maintained, but not my tools. Yes I had searched on *.tbx on both C:\ and my My Documents location on H:\ and found only Toolbox.tbx in C:\Profile Backup\<my username>\Documents\ArcGIS, where it is a 4 KB file that is empty when I open it in ArcToolbox. On H:\ I found it only in a Pre-image info folder where it is last modified in 2013. I suppose that's better than nothing, but I do regret losing everything I've added to it in the years since. What shocks me is this has even happened, because during all previous ArcGIS Desktop updates, I have never lost the content of My Toolboxes. Has anyone else lost their tools on this upgrade? So what am I left with: trying a file recovery tool to restore what the Desktop installation deleted? Is there any other solution? ... View more

Thanks V Stuart Foote! By your suggestion I found the culprit was C:\Program Files (x86)\Intel\iCLS Client\msvcr90.dll in the system path. By editing the path to remove it, R6034 on ArcCatalog launch stopped coming up. I don't know if this path edit will negatively affect another application, but at least I know what to try putting back if so. Thanks again, Justin ... View more

Thanks Duncan, but no, I've no such 3rd party installed for ArcCatalog. ... View more

Hi Warren. I had posted another thread on this, and neglected to mention so on this one. My apologies for that. You can find the answered thread at ListFeatureClasses() or ListDatasets() fails since 10.2 upgrade‌, where you'll see it was an empty mosaic dataset that was found to be the troublemaker. ... View more

The ability to populate rasters in a database was great when it was introduced with ArcSDE 8.0, but that ship has sailed (and foundered on rocks and sank).  Disk-based imagery access is where you want to be now.  - V I know now what to do. Thank you very much, Vince. ... View more

Thanks for the reply, Vince. That's very helpful, but let me explain what I meant by "keeping the overview rasters out of ArcSDE." In my initial post I did not mention there is an existing reference mosaic dataset in the SDE gdb that I'm referring to in this thread. Last week I ran Export Raster Catalog Paths on it (because Export Mosaic Dataset Paths does not work for a referenced mosaic), and in the output found paths that do indeed point to TIF files on disk, as would be expected. I did also, however, find dozens of paths similar to the following two: \\winston\GISImagery\SWOOP2010\orthos\overviews\viewer1@bc@winston.sde\bc.GIS_ADMIN.AMD_SWOOP2010_OVR\\Ov_i05_L01_R00000972_C0000038C and C:\Users\kraemerj\AppData\Roaming\ESRI\Desktop10.1\ArcCatalog\sde@bc@winston.sde\bc.GIS_ADMIN.AMD_SWOOP2010_CAT\Raster.OBJECTID=18853 By the way, I don't know why the sde@bc@winston connection appears in some paths because I never create feature classes as the sde user. This mosaic had been loaded from a raster catalog, so perhaps it had something to do with no coffee the morning I created that catalog 😉 The overviews folder on disk (named in the first path above) contains nothing but two .sde connection files, so from these facts it appears the overviews are indeed stored in the SDE gdb. I've just checked the tool help for Build Overviews, and found: "The overviews generated for mosaic datasets on the SDE are stored within the geodatabase containing the mosaic dataset. These locations can be changed by first using the Define Overviews tool and specifying a location." So based on the fact I could use Define Overviews to specify the output location for overviews to produce them on disk, regardless of whether SDE or fgdb is host for the mosaic, and that mosaic performance hosted in SDE vs. fgdb will be just minimally different, my question becomes "is it better for image service performance to generate mosaic overviews on disk, or allow them to be created in SDE? ... View more

I input the code you supplied, but when I run the script, it doesn't even make it to that point, failing at the same point as before. The code never makes it all the way through the for dataset in arcpy.ListDatasets(): section. I even input some lines to skip the mosaic datasets, but it never reached them, i.e. for dataset in arcpy.ListDatasets():     print "Adding:", arcpy.ListFeatureClasses(feature_dataset=dataset)     if dataset == "u'bc.GIS_ADMIN.SWOOP2010'" or dataset == "u'bc.GIS_ADMIN.SWOOP2006'":         print "skipping SWOOP2010 and SWOOP2006"     else:         dataList += arcpy.ListFeatureClasses(feature_dataset=dataset) Reason I skipped those two is that SWOOP2006 remains empty, because I've not yet loaded anything into it, and it didn't help when I isolated only that one in the if statement above, hence SWOOP2010's presence there. I am curious if the empty mosaic dataset is a source of the problem, but have so far been unable to determine that. ... View more

PyScripter does not report the line where the error occurs. The script right now prints each feature class being added to dataList, and after printing the last few lines: Adding: [u'bc.GIS_ADMIN.traffic_lights', u'bc.GIS_ADMIN.valves', u'bc.GIS_ADMIN.StormStructures', u'bc.GIS_ADMIN.signs', u'bc.GIS_ADMIN.sidewalks', u'bc.GIS_ADMIN.manholes', u'bc.GIS_ADMIN.light_standard', u'bc.GIS_ADMIN.hydro_pole', u'bc.GIS_ADMIN.hydrants', u'bc.GIS_ADMIN.decorative_light_standard', u'bc.GIS_ADMIN.curb_gutter', u'bc.GIS_ADMIN.culverts', u'bc.GIS_ADMIN.bridge'] Adding: [] Adding: [] Adding: it then immediately reports the floating point error. I next ran the code in PyScripter Debug mode, and found it raised a more useful error message: 'ERROR 000622: Failed to execute (Reconcile Versions). Parameters are not valid. \nERROR 000800: The value is not a member of ABORT_CONFLICTS | NO_ABORT.\n' I don't know if this points to two separate problems, or if it's just indicating there's an invalid parameter and then explaining which one it is. It appears to correspond to the call to arcpy.ReconcileVersions_management(), specifically the line retval = convertArcObjectToPythonObject(gp.ReconcileVersions_management(*gp_fixargs((input_database, reconcile_mode, target_version, edit_versions, acquire_locks, abort_if_conflicts, conflict_definition, conflict_resolution, with_post, with_delete, out_log), True))) and the values for these parameter variables are: input_database: unicode u'Database Connections\\sde@bc@winston.sde' reconcile mode: str 'ALL_VERSIONS' target_version: str 'SDE.Default' edit_versions: list of 15, with item 0 being u'sde.DEFAULT' (item 11 has an ampersand in its version name, and was new when trouble started...) acquire_locks: str 'NO_LOCK_ACQUIRED' abort_if_conflicts: str 'NO_ABORT' conflict_definition: str 'BY_ATTRIBUTE' conflict_resolution: str 'FAVOR_TARGET_VERSION' with_post: str 'NO_POST' with_delete: str 'KEEP_VERSION' out_log: NoneType None All parameters appear to be valid, so might it be related to the item 11 version name "Peirson & Buckby rd extension"? Before I rename it to troubleshoot I'd like to know. If so, it seems weird the error would point to "The value is not a member of ABORT_CONFLICTS | NO_ABORT" when the variable's content clearly is one. ... View more

Uncomment the lines defining this variable and re-run the script and see if you receive a new error message. Doing so returns me to the floating point error I had reported originally (here with some more detail): Exception class: EInvalidOp Exception message: Invalid floating point operation. Exception address: 000007FED87FD6A3 ------------------------------------------------------------------------------ PyScripter version : 2.5.3.0 x64 Python DLL : python27.dll Python Engine : peInternal ------------------------------------------------------------------------------ I wonder if it might be a 64 bit or 10.2-related issue? Everything ran well before upgrading to 10.2. I do need to get this working again. ... View more