PDXpert PLM Software
PDXpert Application Server setup
Last update 2023-07-25
The PDXpert Application Server and the SQL database server must be installed on the same computer.
You must have administrator rights to your computer, and be the only user logged into Windows. (Confirm using the Windows command query user)
1. Installation options §
Choose one of the following options (A. or B.) to install the PDXpert system.
A. Standard installation with integrated SQL Server§
The standard installation automatically downloads and installs SQL Server Express LocalDB. This is a secure, low-profile, minimal footprint version of SQL Server. It's intended to support workgroups of up to about 10 users. The installation is fast, and won't affect other database applications.
Run the PDXpert system installation program from your server's local storage.
B. Optional installation for separate SQL Server§
Use this option if you prefer PDXpert to use your selected SQL Server instance, and don't want PDXpert to install its own SQL Server instance.
SQL Server account
The service user is assigned a Windows administrator account, such as the Local System account (NT AUTHORITY\SYSTEM); and
The user who installs PDXpert must be one of the SQL Server instance's system administrators.
For the recommended procedure to manually install SQL Server for PDXpert, see Custom installation: SQL Server.
Procedure B §
Run the PDXpert installer on the computer where SQL Server is installed:
For PDXpert 10.0 and later: From the Windows db=0 option:menu, open a command line prompt using , and execute the system setup using the
- For releases earlier than PDXpert 10.0: Run the setup EXE file by double-clicking the Windows icon.
After installation and before running the PDXpert client.
When SQL Server was installed, if a Windows administrator account other than SYSTEM was assigned for PDXpert, then allow the PDXpert service to use the account:
In the Windows Control Panel > Administrative Tools > Services.
Find and select the PDXpert Server. Right-click and select the command.
Don't add this account to the PDXpert Filter Service.
Select the Log On tab, then select This account: and enter the assigned Windows administrator account (e.g., WinAdmin) and its password.
After clicking the PDXpert Server service (if prompted, accept restarting the PDXpert Filter Service).button, restart the
Open the PDXpert Server using the PDXpert Server desktop icon or the Windows Start menu.
On the Manage tab, next to the button, note the data directory (similar to C:\ProgramData\PDXpert\Data\).
If you added a Windows administrator account to the PDXpert Server service, then the account must have full read/modify/delete permissions for this data directory and all of its subfolders.
The SQL Server instance name is shown to the right of the PDXPERT was assigned, then click the button to select your installed SQL Server instance. Select (or enter) the local instance name that was installed for the PDXpert Server, typically .\PDXPERT.button. If the name is empty, or an instance name other than
You'll see two messages: Changing database server and then Status: Starting services. These processes may take up to 3 minutes. If it takes longer, SQL Server may not be accepting the connection. Shut down and restart the PDXpert Server application, and this may finish the task.
2. Continuing the setup§
To complete the PDXpert Application Server setup:
During installation, the PDXpert software license agreement is shown. If you agree with the terms of the license, mark the acceptance checkbox, and click the Next button.
Although you can specify options for the PDXpert Application Server, we recommend using the default values to simplify administration and technical support.
The installer creates a folder for your database and library on your system drive. If you prefer to use another location for your data, allow the installation to proceed. After installation is complete, use the Settings tab on the PDXpert Application Server console to select your preferred location for the data folder.
When the installation is complete, click the Finish button. On the Windows Desktop, there are two icons:
The PDXpert client application is used for administrative tasks (license entry, user account management, etc.) and normal product data management activities.
The PDXpert Application Server is used for database management tasks such as backup, restore, relocation and reset.
Uninstalling the PDXpert Server§
This procedure does not uninstall the SQL Server database application or instance, or delete the PDXpertDB database. Refer to Microsoft's documentation to uninstall SQL Server.
On the server computer:
Search for Add or remove programs and open; or
Search for Control Panel, and select [category] Programs ⇒ link, or [icon] click on the link.
In the Apps > Installed apps or Uninstall or change a program list, find the PDXpert Server application. This is shown as PDXpert Server with Local Client or, in earlier releases, as PDXpert PLM.
If you see PDXpert Network Client, PDXpert PLM Client or simply PDXpert, then your system has the PDXpert client application installed. See Uninstalling the PDXpert client topic.
Right-click to select themenu command. Or, in older Windows, select the installed PDXpert Server item, and then click on the button at the top of the list.
Related topics §
Install Guide Contents
- 001. Installation overview
- 002. Preparing the server computer
- 003. Standard PDXpert System setup
- 004. Standard PDXpert PLM client setup
- 005. Installing LocalDB for PDXpert client ODBC
- 006. Custom installation: SQL Server
- 007. Custom installation: PDXpert server
- 008. Custom installation: Private cloud
- 009. Custom installation: Client deployment
- 010. Upgrading the PDXpert Application Server
- 011. Upgrading the PDXpert PLM client
- 012. PDXpert server post-install checklist
- 013. Install license CA certificate chain
- 014. Moving PDXpert server database and files
- 015. Managing a PDXpert test server
- 016. PDXpert Application Server diagnostics
- 017. PDXpert PLM client diagnostics
- 018. Microsoft SQL Server diagnostics
- 019. Microsoft SQL Server log files
- 020. Connecting SQL Server Management Studio
- 021. Upgrading SQL Server
- 022. Service configuration settings
- 023. Application folders and files
- 024. System architectural diagram
- 025. Release notes (change history)