nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problemas con los scripts de ArcMap Toolbox

JackieFisher

<\/HEAD>

Estoy operando en ArcGIS for Desktop (10.4.0.5524) y he comenzado a tener errores fatales al ejecutar scripts desde el ArcToolbox. Merge, Union, Append ... todas las operaciones con las que he trabajado antes en Shapefiles ahora dan un error fatal y me expulsan de ArcMap. ¿Alguna sugerencia?<\/P><\/BODY><\/HTML>

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

JackieFisher

I'm signed in to the AGOL, as soon as it processes for just a few seconds, then kicks me out. Here is the screen from the Connection Test.

JayantaPoddar

Is the Add Basemap option grayed out?

Then you could check the globe icon is crossed in Windows Taskbar.

Right-click the globe icon > Test Connection now.

JackieFisher

All scripts appear to run correctly. However, next issue (don't know if related or not) is I can neither add an ESRI Basemap to a new *.mxd, nor can I add or change an existing one in an older *.mxd that already has one. Any ideas?

JayantaPoddar

Good to know. Let us know if the issue gets resolved, after your testing.

JackieFisher

Moving the script launch back to the Foreground seems to have corrected that issue. Can now run the conversion scripts (at least) with no issue. Will be testing it later today on other applications. Thanks for the help.

JackieFisher

Disk is no where near full (still have 700Gb of Free Space). Where we're at this morning after changing the Normal.mxt & going through the Repair procedure is that I no longer have the fatal error. Have only attempted the Table to Excel & Excel to Table tools but they don't run either. At least it's not stopping the program anymore. Will work through Jayanta's last suggestion.

curtvprice

A fatal error that crashes ArcMap (you didn't say what "kick out" means exactly, but I'm assuming memory could not be read or the application closed... usually suggests issues with Windows, temp file space, system problems. Especially if many unrelated tools are all failing. In this case a reinstall of ArcGIS isn't going to do much for you unless it addresses the root issue. Is your disk full?

JayantaPoddar

Try these two steps

1. Disable Background Processing in ArcMap. Foreground and background processing—Help | ArcGIS for Desktop

2.If the above step doesn't resolve the issue, try changing the security setting of Internet Explorer to Medium.

Else, it would be wise to contact your local Esri Support before you uninstall the ArcGIS Desktop.

JackieFisher

Thanks for the additional info. Did find the file ... renamed it to Normal_old.mxt. After a restart, still ended up with the fatal error just requesting a Table conversion to Excel. I've gone through the repair process already. Any more ideas other than an uninstall / install?

JayantaPoddar

Find Normal.mxd and delete/rename it.

I have the file in the following location.

C:\Users\<CurrentUserName>\AppData\Roaming\ESRI\Desktop10.4\ArcMap\Templates

You need to "Show hidden files, folders and drives".

JackieFisher

Am having a hard time finding the *.mxt file (or directory). Will set up the search when I get home & just let it run. Question about upgrading to 10.5 ... would that resolve the issue or better to get this repaired first?

JayantaPoddar

Reinstalling should be your last resort.

You could try repairing ArcGIS Desktop if https://community.esri.com/docs/DOC-2121?sr=search&searchId=59e7ff51-0670-4c81-9df2-2c4ff480313b&searchIndex=2‌ doesn't work.

JackieFisher

If I need to reinstall ... would it be advantageous at this point just to upgrade anyway?

JackieFisher

I will give that a try. Didn't know if anything had changed because I had not yet upgraded to 10.5.

XanderBakker

Did anything change or your computer between the time it worked and now?

If ArcMap closes just from running a standard geoprocessing tool, that isn't a good sign. You could try to delete the Normal.mxt from your user folder and see if something changes, but you may have to reinstall ArcGIS.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.