Troubleshooting Instance Migrations
This section describes common problems that you might encounter as you migrate PPM instances.
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:
logging.conffile (located in the
<PPM_Home>/confdirectory) in a text editor.
Set the value of the
HIGH,and then save and close the
kStart.shscript, and then recheck the
serverLog.txtfile to determine whether it contains any additional information.
Restore the default value of the
Note: Restoring the default value ensures that the file system does fill up with unnecessary information recorded in the
If the Web browser accessing the 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 PPM URL (for example, existing requests) are updated to point to the new URL.