PDXpert Application Server diagnostics

Last update 2020-12-28

Check the SQL Server connection

Installation and operation errors are often related to communication problems between the PDXpert Application Server and the Microsoft SQL Server database engine.

If the SQL Server database instance is valid and running, the database server release is shown in the SQL Server text box, such as SQL Server 2019 Standard Edition (64-bit) (15.0.2070.41). If the connection is invalid or SQL Server is not running, this text box will be empty. Refer to the SQL Server diagnostics help topic.

Check that the PDXpert service is started§

For PDXpert 7.0 and higher: The PDXpert Application Server is a service that can be stopped and started from the Windows Control Panel, in the Services console.

  1. Open the computer Services panel to search the Windows Start menu

    • On Windows 10 / 8 / Server 2012 (and higher): Computer Management ➔ Services & Applications ➔ Services

    • On Windows 7 / Server 2008: Control Panel ➔ Administrative Tools ➔ Services

  2. Find PDXpert Server in the list. If the Status is not shown as Running (that is, the column is empty), then select it and click the Start the service link.

For releases prior to PDXpert 7.0: The PDXpert Application Server can be opened by selecting it from the PDXpert folder in the Start menu. When the application is running, the Start button is disabled, and the Stop button is enabled. Conversely, the application is stopped when the Start button is enabled. Click on the Start button to start the PDXpert Server service.

"The file exists" error is shown when running a report/export§

When exporting data or running a report, SQL Server often needs a temporary file in the server machine's %TEMP% folder, such as tmp475B.tmp. If Windows doesn't periodically clear the %TEMP% folder files, then after 65,535 temporary files, the folder contains every possible filename, and none are available for the export file.

Clear the %TEMP% (for example, C:\Windows\Temp) folder on the server.

Microsoft reference

Analysis of log file entries

System.IO.IOException: read past EOF at Lucene.Net…§

Windows Update may sometimes interrupt PDXpert's indexing service during installation or after restarting Windows. If an index file is damaged, the client communication service will not service client log-in requests, with a client error message such as The server could not be contacted.

Delete the index folder to restart the indexing engine and rebuild the files:

  1. Open the computer Services panel to search theWindows Start menu

    • On Windows 10 / 8 / Server 2012 (and higher): Computer Management ➔ Services & Applications ➔ Services

    • On Windows 7 / Server 2008: Control Panel ➔ Administrative Tools ➔ Services

  2. Find PDXpert Server in the list. If the Status shows Running, select it and then click the Stop the service link. Don't close this window yet.

  3. Open Windows Explorer, and go to the PDXpert data directory. This is the \Data\ folder, as shown on the Manage tab of the PDXpert Server window.

    On recent versions of PDXpert, click the Open… button next to the path name.

    Close the PDXpert Server window.

  4. Delete the \Data\Index\ folder.

  5. On the Windows Services panel, select PDXpert Server and then click the Start the service link.

  6. Open the PDXpert client on the server machine. Use the Item Explorer Search page to confirm that searching for an item returns relevant results.

This problem is not common because the index service is often idle. If you observe this problem often, or you've recently imported a lot of data, then try stopping the PDXpert Server service before downloading or installing Windows Updates.

 

Install Guide Contents