Applications Systems

DPA will not start due to insufficient memory or Windows errors

Troubleshooting information when DPA or DPA web pages will not start due to memory limitations, receiving a "[764 prunsrv.c] [error] Failed creating java" error, or a "'cscript' is not recognized as an internal or external command" error.

First published date

11/29/2018 10:24 PM

Last published date

11/29/2018 10:24 PM

Overview

If DPA will not start and no DPA web pages can be viewed, try the following steps. To learn how to start DPA, view the readme.txt file located in the top directory holding the DPA files.

Note: This is a different situation than when a monitored database cannot be monitored. If you are experiencing monitoring problems, choose Options > Support tab > Log Viewer for more information.

If the following information does not help you identify the problem, contact SolarWinds Support.

Product section

Database Performance Analyzer

Resolution

Check the logs located in DPA_home/iwc/tomcat/logs/.
If the logs suggest that a port is already in use, change the DPA settings to an available port. See this article: Change the default ports in DPA
If the logs suggest that not enough memory can be allocated, install DPA on another computer.
If the error logs do not show errors but you cannot access DPA from a browser:
- Make sure you do not have a firewall that prevents DPA from listening on the ports that are specified in DPA_home\tomcat\conf\server.xml. Also, make sure the client machine can ping the server running DPA
If you're getting the following message on Windows: "[764 prunsrv.c] [error] Failed creating java" errors when you try to start the Ignite PI Server service:
- Download JVM from http://java.sun.com/ ( Oracle, available at www.oracle.com, obtained on May 29, 2019) even if you already have it installed. The registry entries may be corrupted and installing or reinstalling JVM fixes the problem.
When starting the DPA server on Windows, if you get "'cscript' is not recognized as an internal or external command":
- Make sure "c:\windows\system32" is in your path (Windows Script Host 5.6 or above is required).
- If the startup.bat script fails, manually create a file called java_loc.txt and place it in the DPA_home\iwc\tomcat\ignite_config directory. The file should contain one line with the full path to a java executable. For example: C:\Program Files\Java\j2re1.5.2_03\bin\java.exe

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.