Customizing the Timeout Values (PC Server)

 

By Jesse Wiegand 11/27/02

mailto:jesse@printpoint.net.au

 

Note:  Please consult a PrintPoint representative before performing any of the steps in this tutorial.

 

The purpose of this tutorial is to give instructions on changing the Timeout Value’s within the 4D Server application and the PrintPoint Client application. This is to be done only if you are having excessive timeout errors from within the application. It should be noted that this is a “Possible” fix to the issue but has not been thoroughly tested and is not guaranteed to fix the problem.

 

 

From the PrintPoint server:

 

  1. Make sure there are no clients logged onto the Server Application.

 

  1. Select “Database Properties” from the file menu. You will see the “Database Properties” window. From within that window, select the 3rd tab from the right. Your window should look like the below window. In the “Client/Server Connections Timeout” section, choose “No Timeout”. Then click <OK>.

 

 

Once this step is completed, close the Server application.

  1. Right click on your <Start> button and choose “Explore”

 

 

  1. On the left side of your screen map to the PrinPoint 4.5_Server_Folder\Additional Tools\4D Customizer 654 folder

 

 

 

 

 

 

 

  1. From the right side of the window double click on <Custo.exe>.

 

  1. From the “File” menu select “Open”. From the “Open” window, using the dropdown button in the “Look in:” area, map to C:\Winnt\ACI and double click on the “tcp.opt” file.

*Note: If this is a Windows 9x operating system you will map to C:\Windows\ACI

 

 

  1. From the “Chooser : tcp.opt” window double click on <Preferences>.

 

 

  1. From the “Preferences: tcp.opt” window change the “Timeout” to 1800 then click on the <X> in the upper right hand corner.

 

 

  1. That will take you back to the “Chooser : tcp.opt” window. Click on the <X> in the upper right hand corner of that window also.

 


  1. When prompted, click on the <Save> button. Then close the Customizer.

 

 

 

Now you will need to adjust the “Timeout” settings on your clients and restart your Server application.