Application server does not connect

If you have an application server that does not connect and that shows as disconnected at the primary server, you can check certain configuration files on both the primary computer and the Windows system.

To determine why the application server does not connect:

  1. Do these steps on the primary computer:
    1. Log in to the primary computer as the Ricoh ProcessDirector system user (aiw1 is the default).
    2. Navigate to /aiw/aiw1/config.
    3. Verify the host= value in the communications.cfg file. If you are not sure that your network accepts short names, use the fully qualified host name of the primary computer. For example, host=myhost.boulder.co.com. Use a text editor, such as vi, and update the entry if necessary.
  2. Verify the settings for the application server in the Ricoh ProcessDirector user interface:
    1. Click the Administration tab.
    2. In the left pane, click System → Servers.
    3. Verify that the value in the IP or Host column for the application server lists the correct IP or host name.
  3. Verify the settings for the application server in the Ricoh ProcessDirector user interface:
    1. Click the Administration tab.
    2. In the left pane, click Objects → Servers.
    3. Verify that the value in the Computer IP address or host name column for the application server lists the correct IP or host name.
  4. Check the NFS connections for the primary computer and the application server.
    1. Log in to the Windows system with the user ID that the application server runs under.
    2. Open a command prompt and type this command:
      net use
      The results should show the shared drives on the computer. You should see the drive letter you chose when you installed the application server, the primary computer (listed as the Remote system), and the status of the connection.

      If you do not see the drive letter or if the status is listed as Unavailable, continue with 6. to try to restore the connection.

    3. At the command prompt, type this command, replacing primary_server with the hostname or IP address of the primary computer:
      showmount -e primary_server
      The results should indicate that the application server is mounted to the primary computer. If it is not mounted, repeat the procedure for configuring NFS.
  5. If the primary computer has a mapped drive and is mounted, but is still not connected to Ricoh ProcessDirector, make sure that the user ID has read and write permission to the mounted directory.
    1. At a command prompt, type the drive letter for the drive that the application server uses.
      For example, type: Z:
    2. Type these commands to create and delete a file in that directory:
      cd /aiw1
      echo. > file
      del file
      If any of those commands fails, the user does not have the correct permission for the directory. Try to restore the connection with the correct permissions.
  6. Stop the application server and reboot the Windows computer. Then, start the application server.
  7. After the application server starts, access the servers table using the Ricoh ProcessDirector user interface:
    1. Click the Administration tab.
    2. In the left pane, click System → Servers.
    3. Verify that the value in the CStatus column for the server is Connected.
  8. After the application server starts, access the servers table using the Ricoh ProcessDirector user interface:
    1. Click the Administration tab.
    2. In the left pane, click Objects → Servers.
    3. Verify that the value in the Connection status column for the server is Connected.
  9. If the value is not Connected, stop and start the primary server and repeat step 7. to check the application server status.
 
Copyright © 2006, 2018