Perform these simple steps to verify that your Project.net installation is set up and configured correctly. Specific directions for completing each step are included in the original installation instructions, referenced at each step below.
Generally, someone other that the person who did the installation should check for errors. In addition to this list, you will need the user names, passwords and settings used by the original installer.
 Project.net Will Not Start or You Cannot Login
 Check DB installation/connection
- Log into Oracle Home Page, check existence of db
- Use tnsping to check existence of database listener with tnsping <database SID>.
- Also, check that sqlplus pnet/<pnet password>@<database SID> connects.
- Verify the JDBC settings in the Tomcat configuration file as outlined in Deploy Project.net to Tomcat Server ( Lin*x or Windows).
 Check installation of JRE and Tomcat
- Check location of JVM
- Verify JVM was upgraded with JCE
- Check installation directory of Tomcat
- Check TOMCAT_HOME/bin/Catalina.sh for the correct JAVA_OPTS settings.
- Check that Tomcat is configured to auto-start (depends upon OS how this is done)
- Make sure ActiveMQ is installed and configured to auto-start
 Check deployment & configuration of Project.net
- Verify TOMCAT_HOME\webapps\ contains the Project.net application, either /ROOT or /pnet.
- Can you get to the login page at http://<hostname> (root.war installations) or http://<hostname>/pnet?
- If you cannot, can you reach the login page using port 8080 (http://<hostname>:8080 or
- If you can only reach the login page when you use port 8080 then the issue is in your Apache httpd and Tomcat integration.
 You Can Log Into the Application But Something Does Not Work Right
- Login as appadmin
- Check all settings from Step 9 [wiki:Production-Tomcat55#Step8:ConfigureProject.netSystemSettings Configure Project.net System Settings].
- Check installation of license properties and key (Step 9 from above page)
- Register as a test user using license key.
- Verify receipt of email from system while registering
- If the hostname is incorrect then double-check the System Settings in the administration module and the defaulthost token in the default configuration.
 The Activity Log stopped listing new activities
If you notice that the Activity Log no longer shows current events in the log it means a part of Project.net called ActiveMQ has stopped working. To fix this you will need to have system administrator access to the server running Project.net.
 Fixing Apache ActiveMQ on a Linux Project.net Server
- Open a console window and log into the server.
- Determine if ActiveMQ is running by executing the following command:
> ps -efa | grep java
- This will return a list of all running Java processes. Check to see if any of them are running activemq; if ActiveMQ is no longer running it will be absent from the list.
- 3. You can also check the ActiveMQ log file:
> tail <apache_activemq_install_dir>/data/wrapper.log
- If ActiveMQ stopped you will see something similar to:
INFO | jvm 1 | 2012/02/02 14:36:24 | INFO | Connector vm://localhost Stopped INFO | jvm 1 | 2012/02/02 14:36:24 | INFO | ActiveMQ JMS Message Broker (localhost, ID:myhost.project.net-33044-1318941048586-0:1) stopped INFO | jvm 1 | 2012/02/02 14:36:24 | INFO | ActiveMQ JMS Message Broker (localhost, ID:myhost.project.net-33044-1318941048586-0:1) stopped STATUS | wrapper | 2012/02/02 14:36:25 | <-- Wrapper Stopped
- 4. To restart ActiveMQ
> service activemq start
- 5. Again, check the ActiveMQ log file for as message like:
> "INFO TransportConnector - Connector vm://localhost Started"
 Fixing Apache ActiveMQ on a Windows Project.net Server
- Click the Start menu.
- In the Search programs and files box type services.msc.
- Click Services.msc when it is displayed in the Programs list above; this will open the Services control panel.
- Look for the ActiveMQ service in the list of installed services. Its Status should show Started and its Startup Type as Automatic'.
- If neither of these are true right-click on the service and select Properties from the pop-up menu.
- In the properties dialog set Startup type: to Automatic and click the [Start] button.
- Close the dialog with the [OK] button.
- Close the Services control panel.
 Project.net Log Files
To help debug installation and application issues Project.net provides a logging mechanism utilizing the log4j logger. In addition, the application servers have log files of their own. For installations using Apache Tomcat, the Tomcat log files are saved in CATALINA_HOME/logs.
To control Project.net's level of logging you need to create the file CATALINA_HOME\webapps\ <Project.net deployment directory (ROOT by default)> \WEB-INF\classes\log4j.properties. When log4j.properties is missing logging is turned off. This file also specifies the location of the log file.
For example, the following log4j.properties file sets the logging level to debug (the highest level) and places the resulting log file in C:\Tomcat5\logs\pnet-log.log (Note: Do not use Debug level continuously because it can affect Tomcat performance and the log files grow rapidly).
log4j.rootLogger=DEBUG, logfile, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%d %p [%c] - <%m>%n log4j.appender.logfile=org.apache.log4j.RollingFileAppender log4j.appender.logfile.File=C:\\Tomcat5\\logs\\pnet-log.log log4j.appender.logfile.MaxFileSize=8192KB # Keep three backup files. log4j.appender.logfile.MaxBackupIndex=100 # Pattern to output: date priority [category] - message log4j.appender.logfile.layout=org.apache.log4j.PatternLayout log4j.appender.logfile.layout.ConversionPattern=%d %p [%c] - %m%n