PDXpert PLM Software Installation Guide
PDXpert client diagnostics
- PDXpert client installation diagnostics
- PDXpert client connection diagnostics
- PDXpert client operation diagnostics
If your PDXpert installer fails to run, or doesn't uncompress correctly, it's likely that the file has been corrupted during download. Return to the download page to obtain a new copy.
Do not run the installer directly from the download page. When prompted, click the Save As button in your browser, and save the installer to a convenient location on your computer's local hard disk.
After the download is finished, run the installer from the saved location.
You must have administrator rights to your computer, and be the only user logged into Windows.
For new installations only
The PDXpert client will examine your system for its Windows and .NET prerequisites and, if missing, will automatically download and install these from the Microsoft website.
During installation, you may receive this installation error: Cannot access a disposed object. Object Name: 'System.Net.HttpWebResponse'.
This error usually indicates a partial or corrupted download of the Microsoft .NET installer. You should separately download and install the current .NET framework. When the installer is finished, restart the PDXpert client installer.
Errors during upgrades may sometimes occur when Windows Installer loses track of installation history, and sees mismatched information in the system Registry. This mismatch is discovered when the PDXpert client installer attempts to uninstall an earlier release prior to installing the upgrade. A typical error message is The feature you are trying to use is on a network resource that is unavailable. Typically, the reference to a network resource is inaccurate and Use source: pdxpert.client.setup.msi will fail.
Manually uninstalling PDXpert may be successful, particularly on newer Windows:
- Open the Windows Control Panel
- In recent Windows releases, open Programs and Features; in older Windows, open Add or Remove Programs.
- Scroll down to the PDXpert PLM item, select it, and click the Uninstall or Remove button.
You can now try to run the PDXpert installer. If the error remains, then you'll need to repair the PDXpert installation using one of the following options.
Use the Microsoft Fix It tool to uninstall the previous PDXpert installation.
The web page specifically mentions that the tool "removes bad registry key on 64 bit operating systems". However, the tool can be installed on, and may repair the bad registry key in, 32-bit systems — it's a bit ambiguous. The technique described in the next option is known to be compatible with all x86 and x64 Windows.
There's an Advanced-Download to run on a different or disconnected computer link for saving a local copy of the tool.
Microsoft Windows Installer Clean Up Utility, msicuu2.exe, was created to remove incorrect Registry data and prepare for a new install. Although it's no longer available from Microsoft, you can find this utility on a trusted IT download site. The tool is compatible with all 32-bit and 64-bit versions of Windows.
- To install msicuu2.exe, log into Windows using an administrator account. By default, the setup program will install the Windows Installer Clean Up Utility's files to the folder: C:\Program Files\Windows Installer Clean Up (32-bit) or C:\Program Files (x86)\Windows Installer Clean Up (64-bit).
- On the Start menu, select All Programs, and click on the Windows Install Clean Up shortcut. The window will list all programs that are installed on your computer that use Windows Installer.
- Select the PDXpert application only.
- Click the Remove button, which immediately deletes the PDXpert application from the Windows Installer database.
- After the clean-up, delete all files - but not any folders - that remain in the %ProgramFiles%\PDXpert folder (by default, C:\Program Files\PDXpert).
- Re-run the PDXpert installer.
If you choose to use the utility, be extremely careful to select only the PDXpert installation for clean-up. You should consider uninstalling the Windows Installer Clean-Up Utility after you're done. You'll find the Windows Installer Clean Up Utility entry in the Add/Remove Programs (XP) or Programs and Features (Windows 7) control panel.
The PDXpert server and client go through several steps to establish a working database connection.
- Each computer's firewall and anti-virus (FW/AV) must allow communications on TCP port 1433 (for SQL Server) and TCP ports 48084 through 48087. It's usually sufficient to set your FW/AV to allow communications between the pdxpert.exe, pdxpertserver.exe and sqlservr.exe applications. Ensure that your AV doesn't override your FW settings (for example, it doesn't change SQL Server's Inbound connections: Allow setting).
- If the Welcome to PDXpert dialog is displayed more than once, the PDXpert client is not able to find the PDXpert Application Server. This is usually because the log-in account name or password is invalid, the PDXpert Application Server has not yet been installed, the server machine name is incorrect, or communication is blocked by a firewall or antivirus software.
- If the Software License Key dialog is displayed, then the PDXpert client is able to communicate with the PDXpert Application Server. This does not yet confirm that the client can connect to the SQL Server database.
- If the PDXpert PLM client application window is displayed, then the PDXpert client is communicating with both the PDXpert Application Server and the SQL Server database.
All systems must have the PDXpert Application Server installed.
Ensure that the PDXpert client communication service is started
This section refers to service Start and Stop buttons that appear on releases before PDXpert 7.0. PDXpert 7.0 and later manages the communication service automatically.
After installation, PDXpert Application Server application will respond to client requests for service only when client communication service is started. When it's started, the Start button is disabled, and the Stop button is enabled. Conversely, the communication service is stopped when the Start button is enabled. On the PDXpert Application Server console, click on the Start button to start the client communication service.
The PDXpert client must communicate with the PDXpert Application Server to verify the user, validate the software license, and obtain the database connection parameters. You use the Welcome to PDXpert PLM window's Machine name to tell the PDXpert client where to look for the PDXpert Application Server.
When the PDXpert client is started for the first time, it checks the localhost for the PDXpert Application Server and, if not found, broadcasts a request for the PDXpert Application Server's network location. If the server doesn't respond, then the client's Welcome to PDXpert PLM window will again be displayed. In the PDXpert server computer name text box, enter the name of the computer where the PDXpert Application Server has been installed. If the server computer has been assigned a static IP address, you can use that instead.
If the Welcome to PDXpert PLM window is displayed repeatedly when the PDXpert client is launched, this may be caused by one of the following problems:
- The PDXpert Application Server has not yet been installed.
- The firewall/anti-virus on the PDXpert Application Server computer is blocking the inbound PDXpert client connection.
- The firewall/anti-virus on the PDXpert client computer is blocking the outbound connection to the PDXpert Application Server computer.
- The server computer name is incorrect.
- The client's TCP port numbers have been set to something other than 48084-48087, and doesn't match the PDXpert Application Server port number.
- If other PDXpert clients cannot connect or you only have a single client installed, then:
- If the PDXpert client is installed on the same computer as the PDXpert Application Server, enter localhost into the PDXpert server computer name text box.
- Verify that the PDXpert Application Server computer's firewall is configured to allow communications through ports 48084-48087 (or the four contiguous ports starting at the base TCP port displayed on the PDXpert Application Server window's Information tab).
- Reboot the server computer, or stop and then restart the PDXpert Server service in the Services control panel.
- Review the PDXpert Application Server computer configuration.
- Review all of the solutions mentioned in the next section, below.
- If other PDXpert clients can connect and operate normally,
then you may want to compare the values from one of the other client
- The client computer's firewall must allow communications through the specified TCP ports (typically 48084 to 48087).
- The client computer's network settings allow communication on the same network as the PDXpert Application Server computer.
- Verify the correct value in the PDXpert server computer name text box. This is the computer name (or machine name) where the PDXpert Application Server has been installed. To eliminate the network DNS server as a source of error, you can enter the server computer's IP address (similar to 10.1.4.98 or 192.168.1.27) instead of the computer name.
- Verify that the Server TCP port number text box matches the server's TCP port number (typically 48084 to 48087), which is specified on the PDXpert Application Server's Settings tab.
The PDXpert client must provide the PDXpert Application Server with a valid user account name and password.
If the Welcome to PDXpert window is displayed repeatedly when the PDXpert client is launched, this may be caused by an invalid user account name or an incorrect password.
- Enter the correct user name, as assigned to you by your application administrator. If this is the first time you're logging into PDXpert, then use the default user account name of Admin
- Enter your correct account password. Ensure that the keyboard Caps Lock is correctly set. If this is the first time you're logging into PDXpert, then leave the password blank. The default Admin user account does not have a password until after you log in for the first time and assign it.
If you cannot log into the PDXpert client, then an administrator can verify your account name and clear your password on your Person record. If no one can log into the PDXpert client, the default administrator account can be reestablished using the Reset Admin button on the PDXpert Application Server console.
After you've entered your account credentials on the Welcome to PDXpert dialog, you may receive an error that the database is not available: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.
- Wait for SQL Server to become active: Immediately after SQL Server is installed, it may take a while to start or may fail to start. Although it can happen with any configuration, this seems particularly common when using Windows XP, Windows Server 2003, and/or SQL Server 2005. Solution: Before starting the PDXpert client, wait at least a minute or two for SQL Server to finish its initialization and to construct the PDXpert database. It's often good practice to reboot the server computer after SQL Server has been installed.
- Firewall and/or anti-virus configuration: The most common source of SQL Server communication problems is that access to the Microsoft SQL Server database is being denied because the server computer's firewall and/or anti-virus is blocking communications between the SQL Server database and the PDXpert client. Solution: Temporarily disable both the firewall and anti-virus (FW/AV) on both the server and workstation computers. If you can then sign into the PDXpert client, one of the disabled FW/AV components requires reconfiguration to permit communications between the PDXpert client and the SQL Server database.
- Enable SQL Server's TCP protocol: Immediately after installation, the default configuration of SQL Server has TCP communications disabled. The PDXpert Application Server installer will enable TCP only while it installs SQL Server Express. If another edition of SQL Server was pre-installed before running the PDXpert Application Server installer, then it's possible that the TCP protocol was not enabled. Solution: Enable the SQL Server TCP protocol.
On 64-bit Windows, you may see this error when attempting to export data in a Microsoft Access or Excel format. The Microsoft 64-bit OLEDB driver is not installed on your system.
Solution: To obtain the required OLEDB driver, install the 64-bit Microsoft Access Database Engine 2010 Redistributable (AccessDatabaseEngine_x64.exe) which can be downloaded here:
If your system already has the 32-bit version of Microsoft Office installed, then do not proceed with installation. The OLEDB 64-bit driver installation will likely fail with the following error:
The OLEDB 64-bit driver cannot be used with your 32-bit version of Office, and you must either
- upgrade to the 64-bit version of Microsoft Office, or
- export using only plain text formats such as comma-delimited (.csv) or tab-delimited (.txt).
You may see this error when
- The server client communication service has been stopped while a client is logged into the system. Solution: Don't stop the PDXpert Application Server's client communication service until all users have logged out of the PDXpert client application.
- SQL Server is being stretched beyond its ability to handle client requests (for example, if you're using SQL Server Express with more than 10-20 users). Solution: Assess your SQL Server configuration and consider upgrading to a higher-performance edition and/or faster hardware.
PDXpert relies upon a few standard Microsoft Windows fonts (Arial, Verdana, Tahoma, etc.) and styles (normal, bold, italic). This error indicates that your computer has a corrupted or missing Windows font. An example of this error, Font 'Arial' does not support style 'Italic', indicates that the italic Arial font is not available on your computer.
When you have this error you can reinstall the font or copy it from another Windows computer.
- Go to your C:\Windows\Fonts directory and find the named font file.
- Right-click on the file and select the arial.ttf, ariblk.ttf and ariali.ttf. command. Paste the file to another directory, such as your computer Desktop. Although only one file was copied and pasted, you'll probably see several files, such as
- Right-click on each file and select the command.
If the reinstallation doesn't work, copy the font from a different Windows machine that does work and place it into the \Fonts folder.
Finally, if all else fails, you can uninstall, then re-install the font: http://windows.microsoft.com/en-US/windows-vista/Install-or-uninstall-fonts
If a user opens too many item records, the PDXpert client application can crash. On restarting the client, PDXpert attempts to restore the previous workspace settings and, in re-opening the item records, again crashes.
Solution: On the PDXpert client log-in screen, mark the Reset my account settings checkbox, and then log in as usual. Keep the total number of open PDXpert objects to a manageable size, and close item windows when you've finished using them. More details can be found in this Knowledge Base article.
You may see this error when you have many items open within PDXpert, or many other applications open alongside PDXpert. Although this can appear with any version of Windows, it's far more common in 32-bit Windows XP and/or while using a CAD application with many design objects.
Solution: This may be cleared by reducing the number of open objects displayed in other applications, or restarting the PDXpert client to reset the allocated system resources.
This is typically the result of having Microsoft Visual Studio installed on the same computer. When Visual Studio is updated (new version or patch) an empty <DbProviderFactories/> may be added to the machine.config file. There may be several of these files, such as:
Solution: In each .NET machine.config file on your computer, look for the section <system.data>. Remove any empty XML tag <DbProviderFactories/> and save the file.
You will see this error when your screen has been "zoomed" in your Windows user settings. Button captions, textboxes and icons may be scaled, while bitmaps, buttons and other controls may remain at 100%. The reason is that the selected scaling factor is passed to some, but not all, elements on the screen.
Solution: This may be addressed by returning to the standard Windows 100% scaling factor.
- On the Windows Start menu, select Control Panel.
- In the Control Panel window, select Display.
- On the panel Make it easier to read what's on your screen, select Smaller - 100% (or similar text)
- Restart your computer to reset the screen scaling.
Installation Guide Topics
- Installation overview
- Standard installatation
- Advanced: Preparing the server
- Advanced: SQL Server
- Advanced: PDXpert application server
- Advanced: PDXpert client
- Advanced: Group Policy
- Upgrade your installation
- Moving your PDXpert PLM database and file library
- Microsoft SQL Server diagnostics
- Microsoft SQL Server log files
- PDXpert server diagnostics
- PDXpert client diagnostics
- PDXpert system file locations