Solve client problems

Log-in problems§

Using the account name and password§

The PDXpert client must provide the PDXpert Application Server with a valid user account name and password.

If the PDXpert client's Welcome to PDXpert PLM window is shown repeatedly, this may be caused by an incorrect user account name or password.

  1. Enter the correct user name, as given to you by your application administrator.

    If no user accounts have been set up, use the default account name Admin.

    If you've been given a domain user account, include the domain with your user name, such as domain\username.

  2. Enter your correct account password.

    The password is case-sensitive. Ensure that your keyboard's Caps Lock is correctly set.

    If no user accounts have been set up, use the default account password        (blank).

  3. Enter the server's machine name or IP address.

    If the PDXpert client is on the same computer as the PDXpert Server (that is, it was installed as part of the PDXpert system setup), use localhost.

Client connection diagnostics§

The PDXpert website includes the latest client log-in solutions. Search the web for PDXpert client diagnostics.

The PDXpert client application communicates with the PDXpert server. The PDXpert server responds to requests from each PDXpert client, and exchanges product data with the SQL Server database.

If the main PDXpert PLM window or the Software License Key dialog is shown, then the PDXpert client can communicate with the PDXpert Application Server.

If the Welcome to PDXpert PLM log-in dialog is shown more than once, then the PDXpert client connection to the PDXpert Application Server has an error.

Log-in errors§

User-provided log-in data includes the log-in account name, account password, server machine name or IP address, and an encryption option.

A refusal to connect may be the result of one of these problems:

  • The user log-in account name or account password is invalid: Try logging into the client with a known good user account. If the log-in succeeds, the user account has an error (usually a misspelled account name or incorrect password). Ask your administrator to make sure that your account name is correct or to clear your password (PDXpert client ➔ Tools menu ➔ User Management... command: X button).

    If none of the user accounts are known, then clear the super administrator account password using the Reset Admin button on the PDXpert Application Server console. The super administrator can then log in to clear all account passwords using the Tools menu User Management... command.

  • The server machine name is incorrect, or the server's DNS machine name is not recognized, or the server's original IP address has changed: Your server's machine name (like MYSERVER) must exist, and be mapped into a useful IP address (like 192.168.1.47). If you're having trouble connecting to a named server computer, try entering the server machine's IP address into the Server computer's machine name text box. If this is successful, then your DNS server isn't reliably resolving the machine name to IP address.

  • The server machine is not on the network: The PDXpert client must communicate with a reachable server. Ping the server to ensure it's visible to the client.

  • The PDXpert Application Server software has not yet been installed: Run the PDXpert system setup program on a computer on your network.

  • A network router is misconfigured: Router settings must allow communication between the PDXpert Application Server computer and the PDXpert client workstation.

System security setting errors§

When the PDXpert client connection is blocked by firewall or anti-virus software, you may see The server could not be contacted.

Both client and server computers' firewall and anti-virus (FW/AV) must allow communications on HTTP port 48084, and TCP ports 48085 through 48087. It's usually sufficient to set your FW/AV to allow communications between the pdxpert.exe and pdxpertserver.exe applications. Ensure that your AV doesn't override your FW settings (for example, it doesn't change the firewall's Inbound connections: Allow setting).

To test the firewall and antivirus, disable both FW/AV on the server and client computers.

If the client can now connect to the server, then:

  1. Exit the PDXpert client and re-enable the antivirus software. Log into the PDXpert client. If the client log-in fails, then set each computer's antivirus to allow communications between the PDXpert server and client applications.

  2. Exit the PDXpert client and re-enable the firewall. Log into the PDXpert client. If the client log-in fails, then set each computer's firewall to allow communications between the PDXpert server and client applications.

Client stops working at log-in§

If too many item records are opened, the PDXpert client application may run out of Windows resources and stop working. On restarting the client, PDXpert uses the previous workspace settings and, in re-opening the item records, again stops working.

  1. On the PDXpert client log-in screen, open the Options and mark the Reset my account settings checkbox.
  2. Enter your user account information as usual.

The next section contains technical background and recommendations.

Windows resources§

Microsoft Windows uses one or more code pointers to manage each image and control (called, respectively, GDI Object handles and User Object handles).

Windows limits the handle resources that any one application can use, as well as the total handles available for all applications. These limits are not increased by adding system memory (RAM).

PDXpert must display many user controls in every window: one part with BOM and file attachments may need hundreds of handles. If only a few unused handles are in the pool, PDXpert is more likely to reach its limit than an email application that needs a dozen handles per window.

PDXpert shows a warning in the client status bar if the allowed GDI or user handles are more than 90% consumed. The warning is removed after resources have been reduced below 85%. PDXpert can only warn about its own handle pool, it cannot warn that the shared handle pool is low.

Low resources warning

To avoid Windows closing PDXpert without notice, release resources that can be used for new windows.

  • Keep open only the windows you need. Close unused items, datagrids and reports, collection members and other windows.

  • Other applications compete for the limited number of handles. Close what you don't need when using large, complex applications. Look at applications with many graphic elements (CAD), windows (email clients), and tabs (browsers).

  • After you've been working a while, restart the PDXpert client so Windows can reset the handle pool, possibly assigning handles freed by other applications.

  • Resources are consumed faster than they return to the pool. There is often a delay between an application releasing resources and Windows collecting them for re-use.

  • Some applications may never fully release unused handles until you restart the application or Windows.

If you're comfortable evaluating technical issues in Windows, you may consider changing the handle limits through Windows Registry settings. Search the web for increasing user and GDI handle limits

3006

Help Guide Contents [as PDF]