|
POST
|
other users have the same issue with the affected MXD's. MXD Doctor does not fix anything when run.
... View more
10-11-2016
02:20 PM
|
0
|
1
|
3307
|
|
POST
|
During computer life cycles most users go from Office 2010, to 2012, etc. as an upgrade. When done in this fashion the compatibility pieces from previous versions of Office remain. I believe we did not notice the Office 2007 dependency in the past because of this. With the Windows 10 upgrade and simultaneous upgrade to Office 2016 we, in effect, cleared this history and removed all the old compatibility components (i.e., dll registration). In answer to your question regarding Desktop 10.4, if the Excel XLSX files are working with ArcGIS Desktop 10.3.1 they should continue to work with Desktop 10.4. The issue appears to be an undocumented dependency on Microsoft Office
... View more
09-15-2016
01:49 PM
|
2
|
0
|
7834
|
|
POST
|
We are seeing an issue that is occurring after an employee’s Operating System is upgraded to Windows 10. PROBLEM: After a computer is upgraded to Windows 10 and Office 2016 users are unable to use EXCEL .xlsx files in ArcGIS Desktop 10.3.1. Attempting to use an Excel file .xlsx file can cause ArcMap to crash. REASON: During the upgrade Office 2016 is installed and all previous versions of Office removed. This removes the Office 2007 connectors that allowed 32 bit applications (like ArcGIS Desktop) to read.xlsx files. These are required if you have an .xlsx file you want to use in ArcGIS but do not have Excel 2007 installed. The 2007 Office System Driver can be downloaded from the Microsoft Download Center. If you have Microsoft Excel 2010 and higher or no version of Microsoft Excel installed, you STILL must install the 2007 driver before you can use .xls AND .xlsx files. FIX: Install the Office 2007 data connectivity components from https://www.microsoft.com/en-us/download/details.aspx?id=23734. Hope this helps someone! Rich Daniels
... View more
09-15-2016
11:38 AM
|
4
|
12
|
22112
|
|
POST
|
crashes double clicking or when attempting to open the MXD with File | Open. Rich
... View more
09-15-2016
11:32 AM
|
0
|
0
|
3392
|
|
POST
|
ArcMap works fine and you can create and save new MXDs. Old MXD's created before the Windows 10 upgrade continue to crash. MXD Doctor says they are fine and the MXD can be opened without issue on other machines. This effects all uses on the machine so it is not a user profile issue. I think the GAC and Registry is not properly migrated during the OS in place upgrade. Repair of the installation does not fix the issue. We have had to uninstall all ArcGIS Desktop and then resinstall from scratch. Rich
... View more
09-15-2016
11:31 AM
|
1
|
2
|
3307
|
|
POST
|
Even if that is the case, it appears one of your machines could use the SQL 2008 R2 data and one could not. You should load Microsoft SQL Server 2012 Native Client on the machine with the problem and see if that helps. Rich
... View more
08-24-2016
04:29 PM
|
0
|
0
|
3340
|
|
POST
|
One thing that works was uninstalling all ArcGIS Desktop 10.3.1 software, then deleting any remaining files at C:\Program Files (x86)\ArcGIS\Desktop10.3 and reinstalling. Of course this is painful for a large organization. This indicates that 'some' dll's' were corrupted by the Windows 10 upgrade... As a side note we did repair SQL Native Client 2012 (64 bit) after the upgrade but this did not resolve the problem (many of the data sources in the MXD were on SQL 2008 R2 servers and need Native Client to connect). Rich
... View more
08-18-2016
01:38 PM
|
1
|
0
|
3392
|
|
POST
|
We had ArcGIS Desktop 10.3.1 installed on Windows 7 machines. The machines were upgraded to Windows 10 (64 bit). Now many of the old MXD's created prior to the upgrade will not open and crashes ArcMap. User is starting on the MXD by double clicking. The same MXD can be opened on machines that have Windows 10,.but had ArcGIS Desktop 10.3.1 installed 'after' the upgrade. Ideas are welcome. Rich
... View more
08-17-2016
05:23 PM
|
0
|
18
|
8815
|
|
POST
|
We are having a similar issue, in our case we have ArcGIS Desktop 10.3.1 on Windows 7 then we upgraded the Operating System to Windows 10. After that, many MXD's would not open and when double clicked ArcMap would crash on startup. Perhaps the Windows 10 upgrade hosed the SQL Native Client? Has repairing the SQL Native Client fixed this for anyone?
... View more
08-16-2016
02:30 PM
|
0
|
1
|
2083
|
|
POST
|
If your IPv4 (preferred) over IPv6 settings are correct -and you can ping the server from the client (and client from the server) and Ping is returning an IPv4 address then I would fall back to checking your PORT settings. At Windows 7 and higher the Microsoft Firewall blocks the LM ports and you need top configure them manually. See: http://desktop.arcgis.com/en/arcmap/10.3/get-started/license-manager-guide/configure-the-arcgis-license-manager-to-work-through-a-firewall.htm There is also an environment variable you can set on the Client that increases the time-out setting used for license checkout/check-in calls. This setting is often needed in VPN or Citrix scenarios. Rich
... View more
08-12-2016
09:08 AM
|
0
|
1
|
5036
|
|
POST
|
I still have this problem with 10.3.1. C:\Users\<user id here>\AppData\Local\ESRI\Desktop10.3\AssemblyCache is updated with the new version of the the add-in from the well-known location but the old version is not removed from the cache, this results in two versions of the Add-in being displayed in ArcGIS Desktop. Supposedly if you including the .esriAddIn at your well known file location (along with the .config and .dll file we created) force ArcMap to updated/refersh the Add-in if the information in the esriAddIn file indicts that it is newer that what is cached in the AccemblyCache? When Add-in's were first released I thought that was the intent. To solve your problem delete all files from C:\Users\<user id here>\AppData\Local\ESRI\Desktop10.3\AssemblyCache, also in your new Add-In ensure you update the build date and version number. Rich D.
... View more
08-01-2016
10:05 AM
|
1
|
0
|
887
|
|
POST
|
Using Visual Studio 2013 with C# to build and update the StreetView & Birds Eye View add-in. Issue is that starting last week the Web Browser Control, used on a form, starts displaying the following message. Further research determined that the WebControl used in Visual Studio defaults to IE7 compatibility. To prevent the above warning you need to "set" your preferred compatibility PRIOR to loading the form in HK_CU registry. More information on this problem can be found at: http://stackoverflow.com/questions/1786905/web-browser-component-is-ie7-not-ie8-how-to-change-this. Key items for those building Add-ins is that the "exe" name you add to the registry is ArcMap.exe -not the name of your add-in. In your button (that is clicked to open the form) you need to call a method to set the browser type THEN create the form instance. For example: protected override void OnActivate() { /* This activates the Windows Form after the user clicked on the button*/ setBrowserType(); CreateForm(); } private void CreateForm(); { if (this.frm==null || this.frm.IsDisposed) { this.frm = new FrmStreetView(); this.frm.Hide(); this.windowWrapper = new WindowWrapper(ArcMap.Application.hWnd)l } } public static void setBrowserType(); { /* move to registry setting and create new DWord value if it does not exist */ RegistryKey key = Microsoft.Win32.Registry.CurrentUser.OpenSubKey(@"SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION", TRUE); if (key.GetValue("ArcMap.exe")==null) { /* set to IE 10 compatibility */ key.SetValue("ArcMap.exe, 10001, RegistryValueKind.DWord); key.flush(); } key.Close(); } Hope this helps someone! Rich
... View more
07-28-2016
10:20 AM
|
1
|
0
|
1462
|
|
POST
|
Just found the 3400 download site, no mention there that the Data Access expansion pack functionality has been rolled into the core product (per this blog).. I don't think that is fully the case because the nmf we use for our agency works fine in version 2505 but in the new version it will not open all the layers in our basemap (i.e., default ESRI imagery in particular). Note - the depreciation planhas this version being RETIRED on October 1, 2017. Should we invest any additional resources into this software or abandon it and move on to another solution (i.e., was this the last release)?
... View more
07-19-2016
10:46 AM
|
0
|
0
|
1343
|
|
POST
|
Hello, Though not the "machine wide" solution like I'm looking for, I did find a set of registry keys that will work for per-user installations. By running this registry update after the software is installed the end user can avoid having to manually entering ArcGIS Pro's licensing information.Note - this example shows a "Standard" license level, other options are BASIC and ADVANCED. I'm still open to better ideas Rich
... View more
07-06-2016
12:16 PM
|
2
|
0
|
10869
|
|
POST
|
Thank you for your response. None of these help documents describe how to define the license information for your application as part of an installation (i.e., they all require user interaction to enter the licensing information). The problem is ESR has failed to realize (again) that they have customers with 100's if not 1000's of installations and that the licensing step has to be automated to enable enterprise deployments of their software. What I'm looking for is the physical location/file that the licensing information for ArcGIS Pro is stored at. If we find it, then we could copy/deploy it with the application. For example, In Desktop this information is found at HKLM\Software\WOS6432Node\ESRI\License10.3 or \License10.4 and several of the settings can actually be set within the desktop install package itself (i.e., the MSI).
... View more
07-06-2016
11:23 AM
|
1
|
1
|
10869
|
| Title | Kudos | Posted |
|---|---|---|
| 8 | a week ago | |
| 1 | 2 weeks ago | |
| 1 | 06-17-2026 08:21 AM | |
| 1 | 06-15-2026 08:41 AM | |
| 1 | 06-10-2026 08:40 AM |
| Online Status |
Offline
|
| Date Last Visited |
Monday
|