This section covers commonly experienced installation problems, as well as what to try and where to get help in general. See also Making the Installed Files Available to Clients and General Troubleshooting on page 32. Most Commonly Experienced IssuesProgram already installedIf you got any error messages about already having the program installed, check for the following files on your system:
Open the files; they contain the path and version number of program if it is currently installed. You can either uninstall that version, or do some sneaky editing to fool the program into thinking it's gone. See Installing the Same Version Multiple Times on the Same Computer on page 35. UNIX client installation freezingIf you run the client installation of the multiuser installation with ./setup , the installation can freeze. This can happen with a normal user or root. To solve this, get the latest XFree86 at http://ftp.xfree86.org/pub/XFree86 Be sure to follow the installation instructions and system prerequisites stated on the site. General installation or startup problemsDepending on how your system is set up, you might not have the correct permissions to the directory where you're trying to install. Make sure you can read, write, and execute in the program directory and in your system temporary directory. Trouble starting or running the program on clientIf you have any problems starting a client, with messages such as "Cannot determine current directory" or "Cannot initialize gallery," check the file access rights on the server. All clients must be able to read and execute in all directories within the installed program directory on the server. The program not starting, or claiming it's still runningIn UNIX, killing the program doesn't always bring down the underlying process, just the interface. When you try to start it again, the operating system thinks the program is still running, so nothing happens. If you kill the program, use a command like ps -ef to list processes, then kill any that correspond to the soffice.bin file or the server installation of the program. The following Solaris command searches for all processes containing soffice : ps -ef grep soffice It also might have started and you just can't see it. The program occasionally likes to hang out up at the very top of your screen, sometimes. If you see a horizontal line that looks like the bottom of a window, drag it down. If it won't move, hold down the Alt key, then drag it. Cannot find file filenameStart the program in a terminal window. Navigate to the program directory on your computer (not the server computer) and type ./soffice Command not foundSearch for the . sversionrc file in your home directory or sversion.ini in Windows (locations vary) and do one of the following options:
Installer cannot run in this modeThe JRE that comes with the program wasn't installed or is damaged. Reinstall it and reselect it; see Specifying the JRE on page 34. Installation failed messageThe program was running while you installed. Shut it down, restarting your machine if necessary, and run the installation again. Also check the quick launch icon, the seagull icon in the lower right corner of your task bar. Right click it and select Close. Linux installation problemsThis is a broad category; however the following are solutions to the installation failing, and not being able to start an installed version of the program.
Missing java.iniMake sure you're installing only the client version, if you're on a networked installation of the program. If that doesn't work, reinstall and reselect the 1.3.1 JRE. See Specifying the JRE on page 34. *.dll not foundMake sure that no other tasks except explorer and systray are running. Press Ctrl. + Alt +Delete to get the task manager and end all other tasks. Installed the wrong languageUninstall the program and reinstall with the new language setting. Other Things to TryTry all the basics:
Good Sources of Information OnlineNote If you're having problems, always check Troubleshooting on page 37. There's a mass of help and troubleshooting information out there; here are the sources that are worth checking.
Repairing Damaged InstallationsIf you suddenly start having problems with particular applications, or if the program just won't start, the files might be damaged. Use the built-in "file repair kit."
Removing the ProgramTo remove the program, follow these steps. Multi-User UninstallFor clients, complete the single-user uninstall. For the server, delete the installed program's main directory from the server computer. Single-User Uninstall
|