Share this page

# Troubleshooting Instance Migrations

This section describes common problems that you might encounter as you migrate OpenText PPM instances.

### PPM Server does not start.

If you cannot start the PPM Server, check the `serverLog.txt` file (located in the `<PPM_Home>/server/<PPM Server>/logs` directory) for error messages. If the `serverLog.txt` file contains no error messages, increase the server debug level to determine whether any additional helpful information is written to the log.

To increase the server debug level:

1. Open the `logging.conf` file (located in the `<PPM_Home>/conf` directory) in a text editor.

2. Set the value of the `SERVER_DEBUG_LEVEL` parameter to `HIGH,` and then save and close the `logging.conf` file.

3. Run the `kUpdateHtml.sh` script.

4. Rerun the `kStart.sh` script, and then recheck the `serverLog.txt` file to determine whether it contains any additional information.

5. Open the `logging.conf` file.

6. Restore the default value of the `SERVER_DEBUG_LEVEL` parameter.

   Note: Restoring the default value ensures that the file system does fill up with unnecessary information recorded in the `serverLog.txt` file(s).

7. Run the `kUpdateHtml.sh` script.

### Server starts, but you cannot access applications.

If the Web browser accessing the OpenText PPM URL generates a "Not Found" or an "Access Denied" error, check the `server.conf` file and the external Web server (if one exists) to ensure that the PPM Server installation directory is specified correctly.

If the PPM Server has recently been upgraded and the URL has changed, make sure that any saved links to the previous OpenText PPM URL (for example, existing requests) are updated to point to the new URL.

https://admhelp.microfocus.com PPM 8942
Tips to improve your search results... OpenText™ Project and Portfolio Management Help Center PPM Help 26.2-26.3 All View Local Help Center View Online Help Center Version: