

The background server threw an exception! Duh! But for real, some part of the background processing failed when running the tool.
#Arcgis 10.3 trial code
When you check the messages (either by clicking the link in the “failed” pop up, or Geoprocessing Menu > Results > + Current Session > + Tool Name > + Messages), the error code is a super helpful “Background Server Threw an Exception”. You ran a tool from the ArcToolbox, and it failed. Geoprocessing Tools “Background Server Threw an Exception” Problem: Remove the join(s) then try your action again.

NOTE: If you’re working with joins/relates, this error may be due to the fact you cannot edit joined data.If it still fails, lastly, try opening a new, blank ArcMap session, adding the offending file, and try your action again. If it still fails, try closing all your programs, the relaunching ArcCatalog/ArcMap and try again. The only way to release the lock is to close the offending program (the error won’t tell you, but it’s whatever program you’re not currently using) and wait a minute or three for the program to completely close and the lock to be released. What Happened:ĪrcGIS works on a constant cache system, meaning if a file is in use in one program (another ArcGIS suite software, Excel, Word.) it cannot be used/changed modified in ArcMap.

You are attempting to do some action in ArcMap or ArcCatalog and you have gotten a super “friendly” message that the action cannot be completed due to an existing lock. Cannot acquire a schema lock because of an existing lock. This will “erase” the letter in the pathname, and the MXD will look for data in the same place as it did on the other machine, but skips the drive letter.Ĭannot because it is in use by another application/user. In the future, this error can be prevented by marking a box in the Map Document Properties to “save relative pathnames”. If not, you will have to do it again until it finds all of the sources. This method should repair all of the data source errors at once.
#Arcgis 10.3 trial series
You open your MXD to be greeted with a series of red exclamation points in the Table of Contents instead of your data drawing in the Display Window. Red Exclamation Points in the Table of Contents Problem:
