Skip to main content
OCLC Support

Use the port query utility

  1. Last updated
  2. Save as PDF
Learn how to use the Microsoft Port Query to test whether you can connect from a Workstation (or Web Server) to the database server in Amlib.

Check Communication to Database Server using Microsoft Port Query

Microsoft Port Query is an easy to use tool that enables you to test whether you can connect from a Workstation (or Web Server) to the database server, and whether the RDBMS is listening for connection requests.

  1. Launch the Microsoft Port Query program, which will be located:
    • Amlib Client: C:\Amlib\Utility\PortQryUI\portqueryui.exe
    • NetOPACs: C:\Netopacs\Utility\PortQryUI\portqueryui.exe
    • ZServer: C:\Zserver\Utility\PortQryUI\portqueryui.exe

       Note: Replace C:\Amlib or C:\Netopacs with the actual path where the applications have been installed

  2. Enter the Destination IP address of the database server used when installing Amlib (for example: tardis, 127.0.0.1, etc.)
  3. Select the Manually input query ports option
  4. Enter the Ports to query:
    • If using Microsoft SQL Server, enter: 1433
    • If using Oracle, enter: 1521 (older versions of Oracle may be using: 1525)
  5. Protocol: TCP
  6. Then click the Query button to start the search

Query Results

  1. If the Query result is LISTENING (for example: TCP port 1433 (ms-sql-s service): LISTENING) then this indicates:
    • the Workstation (or Web Server) can communicate to the database server OK
    • you will need to proceed to the next level of Amlib troubleshooting to identify the problem you are experiencing
  2. If the Query result is NOT LISTENING (for example: TCP port 1433 (ms-sql-s service): NOT LISTENING) then this indicates:
    • the Workstation (or Web Server) is unable to communicate to the RDBMS on the database server

      You should refer this problem to your organisation’s database or network administrator to follow up.
       
    • Possible reasons why it is unable to communicate to the RDBMS on the database server:
      • the database server is not running
      • the database server is disconnected from the network
      • the workstation (or web server) is disconnected from the network
      • there is a problem with the network (for example: switch is faulty, DHCP is not running, etc.) or network configuration
      • the RDBMS is not running on the database server (check in Windows Services whether the RDBMS (Microsoft SQL Server or Oracle) is running
      • the enterprise firewall is preventing connectivity via this Port
      • the workstation firewall (for example: Windows XP Service 2 firewall) is preventing connectivity via this Port
      • there a problem with hardware (for example: network card in either database server, workstation or web server)
  3. If the Query result is FILTERED (for example: TCP port 1433 (ms-sql-s service): FILTERED) then this indicates:
    • the enterprise firewall is preventing connectivity via this Port
    • the workstation firewall (for example: Windows XP Service 2 firewall) is preventing connectivity via this Port

      You should refer this problem to your organisation’s database or network administrator to follow up.