A4. Troubleshooting - LUPMISManual

Annex 4 Troubleshooting

Level of expertise required for this Chapter: Expert; general Map Maker training

GIS data are very complex. They are often large and have complex relations, both internally and to external data. Problems can easily arise, but can always be solved.

A) Most common errors are due to unclean data: Polygons have not entered correctly, they overlap each other (and have not been intersected, see  Chapter 3.3), boundaries of adjacent polygons are not identical (and have not been ‘snapped’ with the Snap-tool from the toolbar left or other tools), attribute data have been linked through wrong link column, etc etc.

All these errors can be identified and corrected. If they are not ok, they might cause crash of the system.

B) Processing of GIS requires large computer resources, in particular on memory: Shortage of memory (RAM) of the computer will either cause either a very slow processing of some processes or even freeze the entire computer (see below for instructions how to close the application, and to recover the data).

Some commands are more sensitive than others, in particular buffering, georeferencing, format conversion require large memory. Often it helps, to re-do a command, which failed in an earlier attempt, again after rebooting the computer.

C) Like any GIS software, also Map Maker is not completely bug-free. To repeat the process or to use different commands (or tools) will help.

- - - - -

Most important is frequent backup of your data !

- - - - -

Advice for trouble shooting: If the computer fails, Map Maker does not respond or unexpected data appear, you have to:

• Close Map Maker (x at top right)
  

• If you can not close Map Maker, you have to Ctrl-Alt-Del > Task Manager > Windows Task Manager window: Applications > Map Maker > End Task
  

• If this fails, but you can access the Task Manager, try with Process > Look for MMM.exe > End Process.
  

• After having exited Map Maker, restart Map Maker.
  

• If the problem continues in Map Maker, reboot the computer.
  

• If you can not exit from Map Maker at all, press the on button of the computer for a couple of seconds. The computer will turn off. Restart the computer and Map Maker.
  

• If the system appears not to react or to be very slow, look for other activities, which might slow down your processor or your harddisk, such as virus scanning, file transfer, statistical or graphical processing.
  

• If the system appears to work smooth, but Map Maker does not open, even if clicked both on the desktop and from folder C:\Map Maker\MMM.exe, go to the task manager (as explained above) and the delete all MMM processes, and reboot.
  

• If this also fails, repeat the previous step and delete as many processes as you can, and reboot.
  

• In practice hardly ever observed, there can be a corruption of the Map Maker program: Re-install Map Maker.
  

• If problem continues or messages like this:
  

appear, un-install Map Maker, delete the entire Map Maker folder, and re-install Map Maker. If you have LUPMIS, re-install Map Maker from the LUPMIS installation routine for Map Maker (step 3 of installation), as this will also re-configure for LUPMIS.

• If you can not log in, for example after installation, the first step of the installation (Apache, MySQL) was not successful. Uninstall, delete folder xampp, check that no services are running, and repeat the entire installation:
  

• If the xampp control panel shows services running under MySQL, identify the conflicting services and delete them. MySQL will not run together with VMWare on the same server:
  

If the Selection Manager in Map Maker shows erratic behaviour like shown below, install Map Maker (step 2 of the installation) and LUPMIS (step 3) again:

- - - - -

More, individual troubleshooting help can be found at:

• Technical notes on process of Structure Plan (Chapter 7.5.5)
  

• Technical notes on process of Local Plan ( Chapter 7.6.5)