Latest Contributions by RichardDaniels

Any insight on how ArcGIS Pro 2.6+ is behaving with Microsoft Office 365 for Enterprise? To me it appears that ArcGIS Pro does not recognized that version of Office. When Office 365 is used Pro acts like NO office components are available.   ... View more

This is still an ongoing issue. Of note for ArcGIS Pro 2.4.x and earlier,  ESRI recommended 32 bit drivers. With Pro 2.6 and above the driver has to match the bitness of Microsoft Office that  you have installed. That being stated, our organization has moved to Office 365 (64 bit) and ArcGIS Pro and ArcMap does not recognized that 'any' version of Office is installed.    newest Microsoft Access Engine 2016 components are available at: Download Microsoft Access Database Engine 2016 Redistributable from Official Microsoft Download Center Any ideas on enabling Excel files with ArcGIS Pro 2.6+ with Office 365 would be welcome.   ... View more

Note - Microsoft Access Database Engine 2016 is now the preferred option to address this issue. The bitness you install should match the version of Office you have loaded (i.e., if you have 32 bit Microsoft Office use 32 bit engine; if you have 64 bit Office, use 64 bit engine).  ... View more

Agree - Microsoft Access Database Engine 2016 now the preferred option to address this issue. The bitness you install should match the version of Office you have loaded (i.e., if you have 32 bit Microsoft Office use 32 bit engine; if you have 64 bit Office, use 64 bit engine).  ... View more

State Plane Coordinate System of 2022 is approaching. What is ESRI's plan to upgrade the Map Projection engines to handle them? ... View more

This fix should be posted as a new thread so those with ArcGIS Pro 2.5 can find it 🙂 "delete C:/users/<your user id>/AppData/Roaming/Esri/AcrGISPro folder and let Pro create a new one." arcgispro 2.5‌ ... View more

I had the this same error, in my case I fixed the issue by making my method public. public static async void LoadNewProject(CreateProjectSettings ps2) { //load the newly defined project; must be public to avoid threading errors! try { Project thePrj = await Project.CreateAsync(ps2); await Project.OpenAsync(thePrj.URI.ToString()); } catch (Exception eX) { //do something TrackErrorLibrary.reportError("SystemError", Project.Current.Name.ToString() + ". " + eX.Message + ". "); } } ... View more

The key is that when you create your code is that many of your commands are asyn. This means they need to be in a async method and the method has to be public to avoid CalledOnWrongThreadException. For example, you could have a call in your 'regular' synchronous code to LoadTemplateProject, that then calls your async method. public static void LoadTemplateProject(string myTemplatePath) //Load the requested map template var projectFolder = System.Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments).ToString() + @"\ArcGIS\Projects"; CreateProjectSettings ps = new CreateProjectSettings() { CreateNewProjectFolder = true, LocationPath = projectFolder, TemplatePath = myTemplatePath, TemplateType = TemplateType.LocalScene }; LoadNewProject(ps); } public static async void LoadNewProject(CreateProjectSettings ps2) { //load the newly defined project; must be public to avoid threading errors! try    {    Project thePrj = await Project.CreateAsync(ps2);    await Project.OpenAsync(thePrj.URI.ToString());    } catch (Exception eX)    {    MessageBox.Show(eX.Message);    } } ... View more

How can this be marked as the correct answer when it does not answer the question? none of the Pro Snippiest show create a new map definition, add it to the current project, and make it the active map. ... View more

You need the Microsoft Access Database Engine components 2010, version 14.0. The 2007 version work as well but that version has conflicts with versions of Office > 2016 (i.e., if you open Access it will upgrade any installed 2007 engine components to the 2016+ version -rebreaking the fix). See: Download Microsoft Access Database Engine 2010 Redistributable from Official Microsoft Download Center  ... View more

We installed this patch and it did not break anything as currently configured. That being stated, it is hard to test the fix since the work around was to combine all licenses for a particular feature into a single EFL code. To test you would have to re-divide your entitlements and see if this breaks the license manager again. Rich ... View more