How do I test Pervasive/Actian communication from my workstation to the server and vice versa? (using Pervasive System Analyzer)
Description
Cause
Resolution
[BCB:5:Third-party support:ECB]

NOTE: To successfully test the Transactional and Relational engines with System Analyzer, there are default databases that need to be on the server. To create the sample databases, on the server, run C:\ProgramData\Actian\PSQL\RecreateSystemDBs.bat.

  1. Launch the Pervasive (PSQL) System Analyzer tool:
    • Version 15.1 and older: from the Windows taskbar, click Start and then select Programs, Pervasive, Utilities, Pervasive System Analyzer. Depending on version, you may have to expand more folder(s) to find the PSA shortcut.
    • Version 16.1 and later: Start, All Programs, Actian PSQL 12, PSQL System Analyzer.
  2. Click Next twice.
  3. In the Test Network Communication windows, type the appropriate computer name (server name) into the Target machine field and click Next. For example, type the computer name of the Sage 300 CRE or Sage Estimating file server if performing this test from a workstation, or the computer name of the workstation if performing this test from the server.
    • If the test is successful, you will see a message confirming it was successful. Click Next.
    • If the test fails, you will see an error message, along with the IP address returned. Make a note of this IP address and the reason for the failure. Click Next.
  4. In the Test Transactional Engine window, select I want to run the transactional tests
    • Enter the path to the Actian Samples directory on the server (e.g. \\servername\c$\ProgramData\Actian\PSQL\samples)
    • and click Next.
    • Note if the test passed or if there were errors
  5. In the Test Relational Engine window, select "I want to run the relational tests"
    1. Enter the servername and "demodata" for the Engine DSN and click Next.
    2. Note if test is successful or if there are errors.
  6. click Next one time and then click View Log File.
    Note: At the end of the log are the test results. These results confirm the success or failure of the communication test.
  7. Click Finish.
  8. Perform steps 1 through 7 while logged unto the target computer. For example, if you first ran the PSA test from a workstation to your server, you should then run the same PSA test from your server to the workstation. Connectivity requires two-way communication.

If a PSA test fails for any computer, click on the article link below to learn how to test network connectivity.

DocLink: Potential security vulnerability with Pervasive System Analyzer
Defect ID
Steps to duplicate
Related Articles