Latest Contributions by WilliamCraft

You can remove specific connections by delete the corresponding .SDE files located at: C:\users\<your_user_name>\Documents\ArcGIS\Projects If the connection still remains after that, right click it from ArcGIS Pro and select "Remove".   ... View more

If I'm understanding your question correctly, you're interested in some examples of how Insights can be used to highlight trends/patterns that aren't otherwise obvious.  To me, you're asking about other datasets that would help justify the use case for Insights.  Maybe I'm misunderstanding you, though.  One idea that comes to mind is stock market data.  It's not an existing example or case study, so you'd have to create your own but it would help to illustrate the point of Insights I think.  You could take the daily closing prices from companies in a specific industry (for example, all oil and gas companies in the Houston area) and run those through Insights.  Technically these companies have a spatial location (i.e., their main HQ address) but you'd be mainly interested in what details emerge from Insights once the data is brought into the application... especially the temporal aspect.  Let me know if I'm way off base here.   ... View more

What is the version of the geodatabase to which you are trying to connect?  From within SQL Server, query the SDE.VERSION table and report back the release it is coming back with.  Also, please provide a screenshot of the error message.   ... View more

In the end, Josh Kalov's answer about copying the entire os.environ was what resolved my arcpy.mapping issues.  I wish I could give a correct answer to several people for their help along the way, especially to Joshua Bixby for hanging in there with me for so long, but I can only mark one answer as correct unfortunately.  Thank you to everyone for their help.   ... View more

Thanks for doing this.  It's amazing that it still yields the same error even with just this MXD in play.  I can open the MXD just fine by myself.  Something in my environment (on both computers) must be in play that I'm not realizing.  Thanks for your time in trying to help me.   ... View more

This may sound silly, but could you create a basic 10.6.1 or 10.7.1 MXD with just a basemap layer and post it here?  I'd like to download it and try that MXD with my script since none of the MXDs I create on my end seem to work.   ... View more

In the Python 2 script, I added an os.startfile(f) line of code to launch the 10.6 MXD interactively just to see what issues may arise.  The following errors are found when taking this approach: I have tried deleting my Normal.mxt but that only eliminates the first error shown above.  I can open this map document just fine by double clicking on it from Windows Explorer.   ... View more

I tried it with a newly-created, simple MXD containing a feature class from a FGDB and a basemap.  I also tried this on another computer, both having the same version of ArcGIS Pro 2.4; one computer had ArcGIS Desktop 10.6.1 and the other had 10.7.1.  Same result on both machines.  I'm so confused.   ... View more

Doing it the way you suggested still yields the same error for me: "RuntimeError: Object: CreateObject cannot open map document".  Looks like maybe our environments are different enough where it'll run for you but not me.  I am curious why my environment prevents the MXD object from being created.  Thanks for looking into this a bit more.  Much appreciated.   ... View more

I'm running it from ArcGIS Pro's catalog view via a custom toolbox/toolset.  There seems to be an issue with referencing the map document file when creating the MXD object.  Are you running the code within the Python window in ArcGIS Pro?   ... View more

I think I figured out how to get past this issue too, thanks to your comment, the information from Curtis and Joshua, and some online investigation into the error code from the screenshot above.  I added the following bold text to the environment parameter of my popen line: process = subprocess.Popen(result + "\\python.exe C:\\temp\\python\\ListMXDDataSources.py", stdout=subprocess.PIPE, stderr=subprocess.PIPE, creationflags = CREATE_NO_WINDOW, shell=True, env={'PATH': result, 'SYSTEMROOT': 'C:\windows'} Below is where things currently stand when I run my code as of now.  I think I'm getting much closer now.  Thank you to everyone.   ... View more

Thank you everyone for your help.  Curtis, the suggestion you made seemed to get me past the error I was experiencing.  I set the PATH, PYTHONHOME, and PYTHONPATH variables to only reference the Python 2.7 folder (C:\Python27\ArcGIS10.6).  However, I'm now getting a new error when the 2.7 code executes.  Note that that 'result' variable is equivalent to the value of "C:\Python27\ArcGIS10.6".   process = subprocess.Popen(result + "\\python.exe C:\\temp\\python\\ListMXDDataSources.py", stdout=subprocess.PIPE, stderr=subprocess.PIPE, creationflags = CREATE_NO_WINDOW, shell=True, env={'PATH': result, 'PYTHONHOME': result, 'PYTHONPATH': result}) ... View more

Thank you Stephanie Wendel for your help.   The failure seems to be associated with the site.py file of Python 3.  The Python 2 script works perfectly fine on its own.  Here is the underlying error after printing the stderr output from the subprocess.Popen line in the Python 3 code (line 45 above): ... View more

Thanks Joe.  The syntax highlighter isn't working properly for me so I was unable to do this myself.  Also FYI, I've just now made some revisions to my code as well.   ... View more