Troubleshooting: Client runs slowly and eventually freezes

Issue

The Client starts to runs slowly and eventually freezes.

Details

Low memory on the Application Server might cause the Client to run slowly and freeze.

In IMPAX web services are used to request and transmit data and authentication information between the Clients and the Application Server. The web services may be consuming too much memory.

Solution

To determine which web service is using a lot of memory (for example, due to a memory leak) you can assign them to separate application pools.

To split web services into separate application pools and recycle worker processes

1. Contact Agfa Support for the CreatePools.zip file and place it on the Application Server.

2. Extract the contents of the file to a directory in a location that is easy to remember.

3. At a command prompt, navigate to the directory used in step 2.

4. Type Create-Splitted-IIS-Impax-Pools.vbs.

   The web services are split and the following text is displayed:

   The IMPAX web services have been split into separate application pools. The log file can be found in your C:\Impax\Logs directory.

5. Open Control Panel.

6. Select Administrative Tools > Internet Information Services (IIS) Manager.

7. Navigate to connection_name (local connection) > Application Pools.

8. Right-click AgfaHC.BackOffice.Web.Services and select Properties

9. In the AgfaHC.BackOffice.Web.Services Properties dialog, select the recycle worker processes at the following times checkbox.

10. Click Add.

11. In the Select Time dialog, specify the start time of the recycling process. Ensure the time chosen is during off-hours such as late evening or overnight.

12. To close the Select Time dialog, click OK.

    The start time is displayed in the field to the left of the Add button.

13. To save the change and close the AgfaHC.BackOffice.Web.Services Properties dialog, click OK.

14. Repeat steps 8 to 13 for all other application pools except DefaultAppPool.

To determine which w3wp process belongs to which application pool

1. At a command prompt, type cd \WINDOWS\system32.

2. Type iisapp.vbs.

   Each w3wp process and PID number is displayed, matched to its corresponding application pool, as shown in the following example:

   Microsoft ®) Windows Script Host Version 5.6
   Copyright ©) Microsoft Corporation 1996-2001. All rights reserved.
   W3WP.exe PID: 7972 AppPoolId: AgfaHC.User.Security.Web.Services
   W3WP.exe PID: 8084 AppPoolId: AgfaHC.User.Web.Services
   W3WP.exe PID: 6156 AppPoolId: AgfaHC.Pacs.Web
   W3WP.exe PID: 8008 AppPoolId: AgfaHC.Pacs.Web.Services
   W3WP.exe PID: 6208 AppPoolId: AgfaHC.User.Administration.Web.Services